Ronny Calderón
PRO
@ronny
Hi @RCM I do DevOps/DevSecOps interviews as additional work (often payed) in my day to day job, and usually what happens is that I'm asked to interview people since the recruiters can't do the technical part, but what I'm not clear I understand is if it's a platform for interviewers or interviewees.
Hey Ronny! The value added is for interviewers. The goal is to save time creating and reviewing technical assignments sent to candidates, and grab ammunition for potential follow up interviews!
I've been testing it against Claude sonnet 3.5, and it's bonkers how good some suggestions are, and it will lookup on the internet if it's not finding anything.
Specially neat for low documented libraries (e.g kamal).
Having the reasoning as well useful when you need to correct it a little.
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!