Engineering Economics on Adrián Moreno Peña | VP of Technology @ Worksome ⸱ Product & Engineering Leader (Copenhagen)

The SaaSpocalypse That Never Came: A Build vs Buy Test in Disguise

Sat, 22 Aug 2026 10:00:00 +0200

Remember the SaaSpocalypse?

The one where AI was going to make Salesforce irrelevant, kill every subscription, and turn the software industry into a ghost town because every company would be running custom software alone. We were promised the software equivalent of Y2K. Planes falling out of the sky. Banks imploding. Vendors disappearing.

Yet, the lights stayed on.

What actually happened wasn’t an apocalypse. It was something quieter, and honestly, more interesting: “build vs buy” for software products stopped being an engineering conversation.

Project vs Product Work: when is your work done

Fri, 24 Jul 2026 08:00:00 +0100

This is one of the pet peeves that some people working with me might have noticed: when engineers can only think of “PM” meaning “Project Manager”. There’s a role called “Product Manager” for a reason - you’re building a digital product that involves endless projects.

The reason why it triggers me is because there’s a fundamental gap between finishing a task and owning an outcome. One is project thinking, the other is product thinking. As a hiring manager representing in-house teams (like I do at Worksome or did at SumUp before), this is one of the main things I look for.

Stop Architecting, Start Gardening

Fri, 17 Jul 2026 12:00:00 +0200

🪏 A garden doesn’t launch — it produces continuously.

You don’t plant the tomatoes, the lavender, and the hedgerow all at once because the dependency graph says they’re connected. You put a few things in the ground. Some thrive. Some get eaten by slugs. A wet July rots the roots of what you were sure would make it. You adjust. Next season you plant differently — not because the plan was bad, but because the weather didn’t read your plan, and the bugs didn’t care.

The Other Debt: When "Good Engineering" Ignores Economic Sustainability

Mon, 16 Feb 2026 22:00:00 +0000

We engineers love talking about technical debt. It’s our go-to metaphor, and it works - people understand debt. But we’ve been looking at sustainability through only one lens. We obsess over code quality, architecture, test coverage - and we call the absence of these things “technical debt”.

What we rarely talk about is the literal debt. Code that is technically good but the business can’t afford to maintain is not good code.