Part of Agent Enablement and Underwriting teams.

• Varied projects aimed at improving the productivity of our sales agents.
• Varied data migration projects - mostly involving Salesforce.
• Partook in redesign of Underwriting Domain to increase the visibility of our decision-making process.

Scaffolding of MVP for a contractee team.

• Worked with business to define domain & map it to the database and GraphQL API design.
• Set up CI and toolchain for backend development & testing.

Greenfield project, layered architecture, CQRS, DDD, TDD.

• Created backoffice APIs, SPA admin panels, and part of analytics for a mobile game, and its web-based prototype
• Built infrastructure for testing, and convinced the team to adopt the same approach for the rest of the project
• Coached junior developers

Greenfield project, layered architecture, CQRS, DDD, TDD.

• As a team, we built from scratch working multi-tenant affiliate platform on top of the Amazon Attribution program, before appropriate APIs were even available and backoffice for parts of the process that could not be automated
• Built a BDD-like testing solution allowing for fast writing human-readable integration/E2E tests
• Built specification-driven prototype of our planned public APIs
• In addition to backend work, I've set up our frontend architecture, which provided a Stimulus-like experience for our frontend developers, after we decided against React and SPA frontend
• I performed some light DevOps and security-hardening tasks

I've migrated the whole system from "ball-of-mud" to event-driven architecture, to cover critical paths with tests, and then extract the whole domain. It greatly reduced the overhead of constant semi-blind bug-fixing.

• Taken the role of informal teach-lead during a process of bringing in previously outsourced software
• Dockerized our infrastructure, set up GitLab and private container registry, built CI pipelines
• Offloaded long-running and external, pooled workloads to queue
• Introduced automated testing
• Created a unified customer panel to replace 7+ separate ones—doing the same in a slightly different way
• Greatly improved customer journey and automatic valuation process UX for our customers
• Integrated multiple payment systems and CAT software

Microservices light where in place—understood as independent, minimal Django sub-applications communicating via REST endpoints or events brokered by Kafka. Deployed together on a single server, but ready to be extracted and scaled independently at a moment's notice. React SPA on the front feed by our GraphQL API. All well-tested.

• It took me two weeks to learn Python/Django enough to contribute fully-tested production code, and two months to be able to contribute meaningful improvements to our whole code-base
• Moved legacy PHP supporting systems and almost 3-years worth of data to our main infrastructure
• As a team, we built a customer journey that provided both great UX and gathered every possible bit of data that could help our sales which we feed to our CRM and marketing automation

Starting architecture could be described as "the less you know, the better you sleep", migrated to "it's ugly, but it can be understood, works and is stable", and further to "let's extract things that shouldn't be here in the first place to separate Symfony-based projects" - It was a set of ugly compromises enforced by legacy and vendors. But hey, it worked and was stable after just a few months of work which was a great improvement from the business standpoint.

• Migrated the company from FTP deployment and SVN to Git, and on-premises GitLab for the deployment process
• After banning FTP access to production I built and maintained GIT<->SVN bridge for the transition period
• Understood, fixed our implementation and documented a badly misused caching system of our legacy CMS
• Increased template and code reuse by orders of magnitude
• Replaced an assorted collection of PHP 5.2.17 (version enforced by vendor) scripts augmenting our legacy CMS, by self-built Symfony-inspired light framework enabling us to introduce automated testing and creation of Vagrant-based local environments for developers
• Introduced automated testing
• Introduced proper logging solution
• Fixed a multitude of errors falsifying our analytics data
• Replaced template-embedded frontend scripts with a proper build process and React-based components
• Improved uptime/availability of our main property from around 97.6% to 99.4%
• Improved loading times for our customers and their consistency by order of magnitude
• Lead a focused effort to improve the SEO of our properties
• Added to search engines indexes millions of missing pieces of content—lost after previous CMS migration
• Reworked our advertising system to allow new ad formats and better experience for our customers
• The whole process improved our traffic and Unique Users numbers by around one third
• Evaluated multiple potential replacements like a Washington Post CMS solution, in-house or outsourced Drupal, etc.

WordPress with my own OO abstraction layer over relevant APIs, which speed up the development of this and multiple other projects I was involved with.

• Taken over after the software house failed to deliver both in terms of features and quality and built our product from scratch just in time to meet our investor's roadmap
• Build a visual Landing Page builder for our marketing with A/B testing capabilities, later adapted to manage the whole website by our non-technical staff without my involvement
• Integrated content-marketing/sales part with our custom CRM and call-center
• Set up our payment system
• Supported the project during its lifetime as a sole developer/ops

• As a team, we built and maintained a framework allowing for ultra-fast delivery of customized, feature-complete WordPress websites for Scandinavian businesses
• Built an internal application automating the generation of SEO reports used by our sales
• Taken part in cleanup and hardening effort after two separate security incidents

Building, adding features, and maintaining various websites, WordPress plugins, and themes.

Occasional migration from Joomla or custom solutions to WordPress.

Writing for multiple internet media entities, including o2 sp. z o.o. (currently: Grupa Wirtualna Polska), Antyweb and Polish edition PC World Computer about IT-related and unrelated topics.

Working as an editor/managing editor in two big blog networks.