6 questions every tech company should ask itself

Who at your company is responsible for the architecture of the whole system?

Not for one individual application, component or team. Who makes sure all the technology decisions make sense together as a whole?

How many of your current technology decisions would you make the same way today?

How many of them are the result of a deliberate long-term strategy — and how many happened because a specific problem needed solving fast?

What happens when your two most experienced developers leave?

Will you still have enough knowledge left about why the system works the way it does?

How many of your temporary fixes have already become a permanent part of the system?

And do you know which of them represent the biggest technical, operational or business risk today?

Do you know what your architecture should look like in three years?

Or does its shape emerge gradually, based on whatever problem needs solving right now?

Do you have a system written in Delphi that you need to keep developing?

The system works and makes money, but a full rewrite is expensive and risky. Do you know who'll be able to develop it in five years — and whether there's a safe path to gradual modernization, instead of relying on one last remaining expert?

If you couldn't answer one of these questions with confidence, that isn't necessarily a problem.

But it's good to know before an architecture problem turns into a business problem.

Not sure about the answers? I can answer them for you — an independent diagnosis of your process and team for a fixed price.

About the development audit →

Did question 6 hit close to home? Legacy Systems & Delphi →

Solution

And in exactly that kind of situation,
an independent software architect can make real sense — without hiring one full-time.

Architect as a Service →

Jakub Lebeda · Company ID (IČO) 19074671 · +420 607 720 317