Dagim Meseret

Software engineer and founder @Dexo_et. Building practical software, exploring AI engineering, and sharing what I learn along the way.

[Dagim Meseret @Dagimlogs]

1/6

I left my 9-5 to focus on building something of my own.

Since then, I’ve been learning a lot about software, AI, and building products.

Some lessons I wish I’d understood earlier. Here’s a few of them 🧵

[Dagim Meseret @Dagimlogs]

The tooling keeps evolving, but the fundamentals don’t disappear.

As coding gets more automated, system design, debugging and evaluating the output become even more important.

Knowing what to build is still a valuable skill.

[Craig Weiss @craigweiss]

evolution of AI coding:

2023: autocomplete (Copilot)
2024: AI pair programming (Cursor)
2025: coding agents (Claude Code)
2026: multi-agent orchestration
2027: software factories

[Dagim Meseret @Dagimlogs]

@matthiaslaroche Hey there, just quit my 9-5 job to work on my agency @Dexo_et, just followed you glad to connect.

[Dagim Meseret @Dagimlogs]

@paulvilloff @Dexo_et Thanks mate, appreciate it

[Dagim Meseret @Dagimlogs]

@argbeknwn Hey Alex, software engineer here, just quit my job to work on my agency @Dexo_et. Just followed you, let’s grow together 🤝

[Dagim Meseret @Dagimlogs]

If your agent setup needs a CEO agent, three managers and a daily standup, it might be time to simplify. 😂

The goal is to remove coordination overhead, not recreate it with more agents.

[Elia De Leo @eliadeleoai]

If your AI coding setup needs a CEO agent, three manager agents and daily standups, congrats.

You reinvented the company you wanted to escape.

@grok how many agents does a solo founder actually need?

[Dagim Meseret @Dagimlogs]

@Isaac_Dev0 @Dexo_et Thanks man, appreciate it. Hope we can keep in touch

[Dagim Meseret @Dagimlogs]

@Isaac_Dev0 @Dexo_et Hey Isaac, thanks! I quit because I wanted full focus on building @Dexo_et and scaling the agency instead of splitting time with the 9-5. Excited to connect!

[Dagim Meseret @Dagimlogs]

This hits hard.

AI coding most of the code at incredible speed is wild. But the key remains: making sure it works. We ship more and build higher quality products, but understanding, verifying, and owning the system never stopped being our responsibility.

[Ryan Dahl @rough__sea]

it's shocking that software engineering has transitioned to 100% AI written in such a short time.

it's more shocking that somehow we, the SWEs, are all just continuing on as if nothing happened. It writes C++ better than I ever could, but the problem of making sure it works didn't magically disappear. we are just shipping enormously more volume at higher quality.

[Dagim Meseret @Dagimlogs]

I used to think more features made a better product.

Now I think a smaller product that solves its core problem clearly is often much more valuable.

Complexity isn’t the same as value.

[Dagim Meseret @Dagimlogs]

@RohanBhanotAI @gethollrr Hey Rohan, Let’s connect and grow together

[Dagim Meseret @Dagimlogs]

@Stacki_TV @Dexo_et Thanks mate , hope we can keep in touch and grow 🤝

[Dagim Meseret @Dagimlogs]

@ifnln Exactly, tight feedback loops beat dumping more context every time.

[Dagim Meseret @Dagimlogs]

Running coding agents well is less about giving them bigger tasks and more about giving them the right context, clear boundaries and a way to verify the result.

Autonomy still needs accountability.

[Addy Osmani @addyosmani]

https://t.co/KD5BxbuZ5Q

[Dagim Meseret @Dagimlogs]

@addyosmani The verification step is where a lot of the risk sits. Without clear acceptance criteria and a way to test the result, agents can produce plausible code that still misses the actual requirement.

[Dagim Meseret @Dagimlogs]

5/5

Good API design makes life easier for everyone consuming and maintaining your software.

What’s the strangest or most confusing API endpoint you’ve encountered in production?

[Dagim Meseret @Dagimlogs]

1/5

I’ve seen developers put actions directly into API URLs:

POST /createUser
GET /getUserById

It works, but there’s a cleaner way to think about API design.

[Dagim Meseret @Dagimlogs]

4/5

This isn’t about blindly following REST conventions.

It’s about designing APIs that other developers can understand without needing a paragraph of explanation for every endpoint.