Writing
Custom software, product decisions and real systems.
Short pieces on when a business needs custom software, what to build first, and systems that have to work in production. New articles go here.
21 Oct 2026
Product
The Happy Path Isn't the Real Work
On paper, the process looks simple: a customer arrives, an order is placed, payment is collected, and the job is done. In reality, payments can be partial, deliveries can be delayed, and prices can vary. A system needs to account for these situations from the start.
5 min read
18 Oct 2026
Product
Handover Means More Than Sending the Code
When the system goes live, the work isn’t over — it also needs to be clear who takes ownership. The code can be ready, but if knowledge still lives in one person’s head, the project hasn’t really been handed over.
4 min read
14 Oct 2026
Product
A System Passing Testing Doesn’t Mean It’s Ready for Everyone
A system that works well with a small group may not have experienced real workload, different user roles, or enough edge cases yet. A successful testing phase doesn’t mean the system is ready for everyone — it simply gives you enough evidence to move to the next stage.
5 min read
11 Oct 2026
Product
If the Same Fact Lives in Three Places, You Don’t Have a System
If the same work is being managed through WhatsApp, Excel, and someone’s memory, there is no single source of truth. Software is not just another spreadsheet — it should give the same fact one authoritative home.
4 min read
7 Oct 2026
Product
If the Process Isn’t Clear, Software Won’t Work Miracles
Software doesn’t automatically turn a messy process into an organized one. If the process, responsibilities, and decision-making rules aren’t clear first, the system will often just spread the same confusion faster.
4 min read
30 Sept 2026
Product
“The Competitor Has It — So Should We” Isn’t Enough
Copying a feature from another product means making a decision without understanding the context and trade-offs behind it. This is where business expectations and engineering reality can quickly diverge.
4 min read
27 Sept 2026
Software Engineering
Working in Banking Taught Me Why Accuracy Matters
In banking, “approximately correct” is not enough. The lasting lesson: a system looking correct is not the same as a system actually being correct.
6 min read
23 Sept 2026
Software Engineering
“One More Feature” Is Usually Not a Small Change
New requests can come up once a project is underway. But not every addition is simply a continuation of the existing scope — some requests expand the boundaries of the project.
4 min read
20 Sept 2026
Product
What Does It Actually Take to Build a SaaS Product?
A SaaS product can look simple from the outside. Behind the screens is a system that has to work for many users at once — and grow without being rebuilt.
5 min read
16 Sept 2026
Product
How Much Does It Cost to Build a SaaS MVP?
Two products can both be called MVPs and still need completely different systems. A useful estimate starts from what the first version actually has to do.
5 min read
13 Sept 2026
Product
Find the Bottleneck First
Automation is not about systemizing everything at once. Start by identifying the part of the process that causes the most time loss and errors.
5 min read
9 Sept 2026
Product
Why “Cheap Software” Often Ends Up Costing More
A low price is attractive at first. But when software does not fit the way your business actually works, the real cost shows up later in wasted time, mistakes, and extra work.
5 min read
6 Sept 2026
Product
When Does a Business Actually Need Custom Software?
Spreadsheets and disconnected tools stop helping when the process no longer fits them. Custom software is for that gap — not for rebuilding everything.
5 min read
2 Sept 2026
Product
“We Just Need a Website” Often Means More Than a Website
A website is the part customers see. “We just need a website” is often not the complete requirement.
5 min read
30 Aug 2026
Software Engineering
Changing a Working System Is Not the Same as Writing in a Blank File
When you build a new system, everything feels easier. Most changes, though, land on a system that is already running.
4 min read
26 Aug 2026
Software Engineering
When I get a requirement, I don’t start coding
The important part is understanding what you are actually trying to solve. The code comes after that.
4 min read
17 Aug 2026
Backend Architecture
Why a simple feature grows once it reaches the backend
Behind one button there is often validation, a database, a transaction and a call to another service.
4 min read
16 Aug 2026
Software Engineering
The bug was not in the Java code
Sometimes you read the same Java code for hours while the cause sits somewhere else entirely.
3 min read
15 Aug 2026
Databases
Some backend decisions are made by the database, not by Java
When the data model is thought about late, no amount of service code written afterwards will fix it.
4 min read
14 Aug 2026
Backend Architecture
Not everything has to be a microservice
A microservice architecture is sometimes not the solution but an extra problem.
4 min read
13 Aug 2026
Software Engineering
The backend problems tutorials do not show
Learning to write code is one thing. Turning that code into a system people use is another.
3 min read
12 Aug 2026
Backend Architecture
One guest record across the stay
Hotel software falls apart when reservations, the restaurant and the guest portal each keep their own version of the guest.
6 min read
11 Aug 2026
Software Engineering
Solving one problem without creating the next one
Every technical decision has a price. A fix that removes one problem can quietly create behaviour somewhere else.
4 min read
10 Aug 2026
Java
What good backend code looks like to me
Tidy classes are worth having. But the code that survives is the code that does not hide what the system does.
4 min read
4 Aug 2026
Software Engineering
Reservations that still hold at 21:00
A booking system is not a calendar widget. It is a promise about a room, a table or a station — and the promise has to survive a busy Saturday.
5 min read