I spent over a decade in enterprise software. Good companies, smart people, complicated systems. What I kept bumping into was the distance — between the people writing the software and the people whose problems it was supposed to solve.
Big organizations are good at many things. Working directly with clients on hard problems isn’t usually one of them.
So I started Imagile. The pitch isn’t complicated: a small, expert team that works directly with clients to build software that actually works. No layers. No handoffs to three other departments. Just us and the problem.
This blog is where we share what we learn doing that. Not thought leadership. Not content marketing dressed up as thought leadership. Just things we’ve figured out — about software, about AI, about how to build things that last without costing a fortune to maintain.
We have opinions. We’ll share them. You might disagree. That’s fine.
A few things coming up:
- How AI is changing what software development actually looks like (it’s weirder than you think)
- Why most cloud migrations fail, and what you’d do differently if you started over
- Why we use Azure and .NET, and when we’d reach for something else
- What “good software” actually means when AI is writing most of the code
More coming soon. Hopefully you find something useful here.
— Sunny