Software Health Check | Umut Yerebakmaz

1. Data and Database

When did you last try restoring from a database backup?

We are not sure we take backupsWe have backups but have never tried restoringMore than a year agoWithin the last few months; we test it regularly

Does the application slow down at peak times?

Often; users complainSometimes; we do not really know whyRarely; we know the causeNo; we monitor slow queries and fix them

2. Security

Where are your passwords and API keys kept?

In the code or in a shared fileOn the server; it is unclear who can access themIn a separate place, but they are never changedIn a place with restricted access, and they are rotated regularly

Are the libraries and server software you use up to date?

They have not been updated in yearsWe update when something breaksWe do a batch update now and thenUpdates are tracked automatically and applied regularly

3. Deployment and Monitoring

How do you deploy to production?

By copying files to the server by handWith commands run by hand; the steps vary from person to personSemi-automatically; rolling back is a hassleAutomatically in one step; it can be rolled back within minutes

When the system goes down, who notices first?

UsersAn employee, by chanceA simple uptime checkOur alerting system; errors and logs are monitored in one place

4. Testing and Code Quality

5. Architecture and Technical Debt

How hard is it to add a new feature?

Something else breaks every timeHard; it depends on the few people who know the codeMostly predictable; we hesitate to touch some partsPredictable; it is clear what goes where

Is the architecture of the system written down?

No; nobody fully knows itIt is in people’s heads, not on paperThere is an old or incomplete documentThere is an up-to-date diagram, and the reasons for decisions are written down

6. Team and Knowledge

What happens if the person who knows the system best leaves tomorrow?

Work stopsIt takes us months to recoverWe struggle but keep goingKnowledge is spread across the team and written down; it makes no difference

Who makes the technical decisions?

No one in particular; whoever is aroundAn outside agency or vendor; we cannot oversee themSomeone on the team, but the reasons are not recordedThere is a clear owner, and decisions are written down with their reasons