DEV-FLOW — the story of a domain that once helped .NET developers worldwide
This address was once part of the global .NET developer community. Today it is a knowledge hub for anyone who wants to understand practical software development — from web APIs to WordPress plugins.
📖What came before — a domain with a tech history
If you landed on codingflow.net through Stack Overflow or a .NET conference, you probably remember the old version: a personal tech blog with tutorials on ASP.NET Core, Angular single page applications, unit testing and domain-driven design, written by an active speaker in the international .NET community.
Jason Taylor’s original tech blog
Australian software developer Jason Taylor used codingflow.net as his personal blog, publishing detailed walkthroughs on modern web development. The best-known posts covered ASP.NET Core web APIs, Angular single page applications, the mediator pattern and domain-driven design.
That material ended up as reference links inside Stack Overflow answers. The GOTO conference in Copenhagen linked to the speaker profile in 2019. Other .NET blogs such as passos.com.au cited more than a dozen tutorials directly. The result is a backlink structure that still exists today, even though the original content has long since been archived.
Why this site still exists
Stack Overflow, blog.cwa.me.uk, gotopia.tech, gotocph.com — all of them still point at codingflow.net. Deleting those connections would delete a small piece of the former .NET community’s internet history.
So we keep the domain as what it was at its core: an address for knowledge about building software. We extend the original .NET profile into neighbouring ground — WordPress plugin development, web APIs across different stacks, modern tooling setups, practices that survive contact with a real project.
What stays is the standard: hands-on, honest walkthroughs. No hype, no listicles, no manufactured complexity.
🗂️Topic clusters — what is here and what is coming
Three clusters, each with a clear focus. Read across them or jump straight to whatever is currently broken.
⚙️Modern Web Dev
Web APIs, frontend frameworks, build tools — the current stack.
- →Building Your First Web API with ASP.NET Core 9 and VS Code
- →What Happened to ASP.NET Core JavaScript Services
- →CSS Grid vs Flexbox: When Do I Use Which?
Planned: Vite vs Webpack in 2026 · TypeScript for JavaScript developers · when a single page application is actually worth it.
🔌Plugin Development
Building WordPress plugins properly — architecture, security, WP.org standards.
Nothing published here yet — this cluster is being written. Planned: plugin boilerplate setup · configuring PHPCS for the WordPress coding standards · submitting to the WP.org repository · secure REST endpoints inside plugins · running a licence server for commercial plugins.
🛠️Best Practices
Testing, Git workflow, tooling — the boring, important subjects.
- →Git Workflow for Beginners: From Chaos to Clean Commits
- →Python Virtual Environments — Why You Should Never Work Without One
- →Docker for Beginners: From Zero to Your First Container
- →Docker Compose Tutorial: Your First Stack
- →Claude Code Workflow Tips From Real Projects
Planned: unit testing for web APIs · CI/CD with GitHub Actions, minimal setup.
👤Who is behind this?
Fair question. There is no research institute and no consultancy behind this site. What there is: hands-on experience running websites and servers, building WordPress plugins, and the patience to check every claim against official documentation before publishing it.
Frank Stemmler
Builds and runs websites for a living, and has shipped several WordPress plugins including commercial ones with their own licence server. Writes here about the tools that survive contact with a real project — Docker, Git, Python tooling — and the occasional post-mortem of something that broke in production.
Every article links its primary sources: documentation, standards, specifications. Where something is not verified first-hand, the text says so.
The domain itself has a longer history (see above). We do not see ourselves as successors to the original Jason Taylor blog — that would be presumptuous — but as the place that carries the subject forward, focused on what individuals and small teams can actually use.