The languages
Five courses, each running from your first program to the parts that only show up in production. Text, with a lab and a worked solution in every lesson.
Open the language coursesWPSifero publishes courses and technical writing about programming. Five language courses — Python, JavaScript and TypeScript, PHP, SQL and Go — run from your first program to the parts you only meet under real traffic. Five more go deep into WordPress and WooCommerce, because that is where the two hardest things in this trade meet: a codebase you did not write, and a database under load.
Every course is text. No video, nothing to scrub through, nothing to re-watch at half speed. You read a lesson, type the code yourself, and finish with something that runs.
$ wpsifero --curriculum
$ _
Three shelves: the languages, the platform, and the disciplines that apply to all of it.
Five courses, each running from your first program to the parts that only show up in production. Text, with a lab and a worked solution in every lesson.
Open the language coursesThe platform that runs a large share of the web, written against WordPress 7.0 and WooCommerce 11.2 rather than against tutorials from three versions ago.
The subjects that do not care which language you write: query budgets, cache invalidation, REST contracts, capability checks, accessibility, tooling.
Long-form work where the measurement matters more than the opinion.
Most post-purchase support tickets are "where is my order". Here is the plugin architecture that answers them without shipping customer data to a tracking service.
Ana Ferreiro · @aferreiro
WooCommerce engineering
Covers the WooCommerce order lifecycle: checkout, HPOS, session handling, transactional email and the post-purchase layer where most storefront complaints actually originate.
11 complete text courses, 198 lessons, no video. Written to be read at your own pace and typed out rather than copied.
Language and platform courses that start at a first script and end at the parts you only meet in production.
Courses built against WordPress 7.0 and WooCommerce 11.2, covering plugin and block development through to performance and security.
Newest first. Every entry is tagged by discipline and carries an estimated reading time.
Eight disciplines, each with its own archive and its own set of recurring failure modes.
Hooks, the database layer, cron, and the parts of core that decide how your plugin behaves under load.
Order lifecycle, checkout, HPOS, sessions and the post-purchase communication layer.
Query budgets, object caching, Core Web Vitals and measuring before you optimise.
REST design, webhooks, authentication, idempotency and talking to couriers and ERPs.
Capability checks, nonces, sanitisation, SQL safety and threat modelling for plugins.
Block themes, progressive enhancement, ARIA, and interfaces that work without JavaScript.
Local environments, static analysis, CI, release packaging and debugging technique.
Server configuration, caching layers, queues, observability and deployment practice.
This section exists so readers and reviewers can hold us to a stated standard.
Performance numbers come from a stated environment. We publish the query count, the cache state and the sample size, because a benchmark without its conditions is an advertisement rather than a measurement.
Where a recommended pattern has a cost, that cost appears in the same article rather than a follow-up. If an approach fails past a certain order volume, we say at which volume it fails.
WPSifero maintains its own plugins. Whenever an article touches a product we build, the relationship is disclosed inside that article, at the top, in plain language.
Five bylines, each responsible for a slice of the stack. Bios describe coverage, not credentials.