Single comment thread
See full discussion

You can follow just 'good practices', sadly there's no such thing as a guideline for it, most big tech is built on top of legacy code/practices anyways, but it all relates back for what you need at any specific part of your journey.

For example if you're working in a team, doing PR reviews comes as a good practice to catch bugs before sending code to prod, as a solo dev this might come as an overkill because you wrote the code yourself.

Docker/Kubernetes come handy for a app that needs to be reliable and easy to make updates in real time, and already has a team supporting it behind it, but might be an overkill for a small team of less than 5 devs, could even be a waste of time in the earlier stages of the product.

For infra same rules apply, you don't need a crazy aws configuration to deploy a simple app with fewer than 10 users, but as soon as the users start growing that's when big tech 'good practices' might come handy such as (IaC, CI/CD pipelines, etc)

If you want just to grow as a dev focus on business needs of each of the stages a business might face and from there just learn each of the 'good practices' at any given moment a company might face.

Hope this is useful!

Home
Search
Messages
Notifications
More