For each domain, I prefer to follow "the Onion Architecture". These clear boundaries lead to less friction and therefore less decision-making when it comes to changing things within the codebase.

Less friction = better DX

And... If you haven't explored @effect-ts.bsky.social yet and want to learn about it, don't hesitate to reach out. I'm more than happy to jump on a call to share my experience and give you an introduction.

A huge shout-out to the organizers for doing an amazing job, the speakers for delivering high-quality content, and the participants for the thought-provoking conversations.

It was fun, inspiring, and simply an amazing experience. Thank you so much!

I can't wait for next year!

It’s an incredible tool (no doubt!), one that should be integrated into daily workflows. However, I don't buy the hype around that "it's over for software engineers."

When it comes to truly well-crafted, quality software, LLMs still have A LOT to prove.

Not so bad.

As humans, we tend to think in extremes, and I believe this is partly why there’s such a buzz about "AI taking over software engineering jobs."

In my view, every seasoned software engineer knows that we're not there yet—and IMO it’s unlikely we'll see that scenario anytime soon.

That said, it was the perfect opportunity to let an LLM build the entire app while I played the role of a guide. And here’s the final result.

He writes the letters in mirror image, which is hilarious, and according to his teacher, it's completely normal at this stage.

Inspired by this, I decided to invest 30 minutes to build a simple app to help him trace the correct path for each letter.

I do it via coder.com

There are a lot of benefits in having your dev environment in the cloud. For example, when building web apps you get a similar latency like your users (without artificially throttling your connection via the DevTools in the browser).

What many label as "over-engineering" is often the result of thoughtful, proactive design by skilled engineers.

In reality, what might seem like unnecessary complexity can be a nuanced approach to solving complex problems.

This is what we should strive for.

I challenged the routing part and built a lightweight wrapper: github.com/akoenig/effe...

Maybe my post nerd-sniped somebody who wants to take over the request / form validation? 😁

From there it could move into areas like persistence, etc. as Effect offers primitives for these use cases as well.