Sometimes a simple website is the right answer. Other times, a seemingly simple button sits on top of quoting, permissions, data models, automation, payments, documents, integrations and operations. Recognizing the difference matters more than starting with a stack.
modern web · software quality · business systems
The web is more capable, and more confusing, than ever.
I care about turning fast-moving web technology into systems that remain clear, maintainable and commercially meaningful. Not just what a framework can do, but what kind of operating model, quality bar and long-term consequences it creates.
Web technology as leverageFrontend, backend, edge, AI and tooling are not separate trends. Together they shape a new way of building software.
Quality inside complexitySpeed only matters if it does not make the system unreadable, fragile or impossible to operate.
Business model meets softwareSometimes a simple page is enough. Sometimes one button hides an entire service that has to work reliably.
Current web problems
01A simple interface can hide a serious service.
The real question is not how many screens get built, but what business capability the system makes reliably available.
02The modern web became hyper-complex.
Frameworks, runtimes, build tools, edge platforms, AI workflows. Powerful material, but very easy to lose the signal.
03AI does not replace technical judgment.
The hard part is less and less about producing code, and more about deciding which code actually matters.
Point of view
Software development is now a business, technology and quality problem at the same time.
Web technologies are moving incredibly fast. So is the noise around them: fragmented toolchains, unclear boundaries, performance traps, maintainability risks, and AI-generated code that can be leverage or just confident clutter. In that environment, technical judgment matters more, not less.
Data, runtime, client-server communication, integrations, authorization, errors, ownership. These are the points where a system either stays clear, or slowly turns into everything talking to everything.
Good abstractions, clear module boundaries, stable data models and understandable operating models do not block speed. Over time, they are what make speed possible.
Topic map
The current problems of the web are the interesting ones.
I am less interested in listing technologies than in understanding where software quality breaks down: at the boundaries, inside the complexity, between tools, in performance, or in the moment when fast-generated code becomes hard to distinguish from actual value.
core ideaMaintainable intelligence
The central question of the modern web is how to use speed, automation and AI while keeping systems understandable, repairable and commercially meaningful.
Sometimes a clean page is enough. Sometimes that same interface is the visible part of an entire service model.
In a good system, it is visible where data ends, where behavior starts, and why responsibility sits where it does.
The web platform is strong, but modern application development is often a loose alliance of frameworks, build tools and runtimes.
A fast UI, stable backend, good caching, edge strategy and measurable operations are part of the same quality question.
In modern development, the risk is often not one bad technology. It is too many good technologies half-connected.
The hard question is not whether machines can write code. It is whether we can tell which code carries a real decision.
Codeva
Codeva is where these questions meet real constraints.
At Codeva, we do not just write software. We get involved in the business and technology decisions around it: what is worth building, what should stay simple, and what deserves a serious system behind a simple interface. That matters to me because software quality is not something you can understand properly in laboratory conditions.
TypeScriptPHPLaravelReactAstroCloudflare
TanStackSymfonyWordPressNode.jsVitePostgreSQLDocker
EffectHonoDrizzle ORMZodVitestPlaywrightRedisMySQL
DDDDomain ModelingCQRSEvent SourcingHexagonal Design
Typed BoundariesAPI DesignDesign SystemsObservabilityPerformanceEdge Computing
TDDProperty TestingCI/CDIaCMonitoringRefactoringProduct StrategyTechnical DiscoveryAI Engineering
Event StormingUbiquitous LanguageBounded ContextsStrategic DesignADRsContinuous DeliveryPlatform Engineering