We aim to be the most effective software development agency in the world.
Kraków
Joined August 2014
- Tweets2.3K
- Following3.5K
- Followers4.9K
- Likes272
“How do we cut software costs?”
Usually the answer is: smaller team, cheaper vendor, more pressure.
That rarely works.
The budget usually isn’t leaking because developers type too slowly. It leaks because you’re paying for activity — features nobody uses, too many things in progress at once, code you still maintain years later, cloud resources nobody turned off.
The cheapest code is often the code you never write.
We put together four practical ways to actually bring costs down — without the usual “just hire fewer people” advice: pragmaticcoders.com/blog/how…
Most IT budgets don’t blow up in one dramatic moment.
They leak.
A bit on maintenance nobody separated from new features. A few “small” scope changes nobody called a budget decision. Technical debt that makes every next change more expensive.
And you only find out when the invoice lands — or when someone asks why progress is so slow.
A lot of vendors call that transparency. Usually it’s just a list of hours.
We wrote about what real cost transparency looks like from week one: what you should see, what questions to ask, and what often gets left out on purpose.
Worth a read if you’re the person signing off on the budget: pragmaticcoders.com/blog/cos…
Project slipping? Budget burning? Roadmap drifting?
Most clients ask for one thing first: more detailed timesheets.
Understandable. Low trust → you want visibility.
But a timesheet tells you who worked and for how long.
It won’t tell you:
A good vendor doesn’t sell you a sense of control through longer comments on every task.
They show you outcomes: what you got for the budget, what you didn’t, why, and what decision you need to make next.
You’re not buying minutes. You’re buying control over outcomes.
Full article: pragmaticcoders.com/blog/is-…
"Engineers should sit in the basement and write code."
More boards think that way than you'd expect.
Tech is supposed to stay in the garage. Tech shouldn't touch "the business". Tech shouldn't talk to users. That's what PMs, Product Owners and sales are for.
The lesson is simple: if you cut your dev team off from users, you're paying for guesswork. And guesswork in software is very expensive.
We talk about this in the full episode here: youtube.com/watch?v=IdpzlmfI…
---
W tym artykule bez zbędnych technikaliów wyjaśniamy, co C-level powinien wiedzieć o observability w projektach IT.
Bez observability time to discover (czas do odkrycia błędu) liczymy w godzinach, a z observability – w minutach. O większości najczęstszych błędów powinniśmy dowiedzieć się w ciągu 10 minut od wdrożenia zmiany.
Dopóki nie wiemy, że jest problem, on rośnie, a my nawet nie zdajemy sobie sprawy, że trzeba nad nim pracować.
W tym artykule bez zbędnych technikaliów wyjaśniamy, co C-level powinien wiedzieć o observability w Waszych projektach IT: pragmaticcoders.pl/blog/obse…
