Add them to the on-call schedule.
Ask HN: How to enforce engineers to understand the code they are shipping
21–24 of 24 posts
Re: Ask HN: How to enforce engineers to understand the code they are shipping
#22Trying to enforce "deep understanding" is optimizing wrong layer. Focus on: . Fast rollback . Good observability . Small PRs Understanding become emergent, not enforced.
[dead]
Re: Ask HN: How to enforce engineers to understand the code they are shipping
#23But do we need the level of understanding to be that deep? If you know how your system works overall, how components interact, what interfaces are exposing/consuming, what security, performance implications are there, what data structures carry around... If you have the understanding of that, do you really need to know the actual implementation details? Maybe taking the perspective of a system/product architect is en…
Yea, isn't a lot of software already developed like this? I doubt the lead developers of Chrome know the implementation details of every component of chrome. They know the high level architecture and leave a lot of the specific implementation to various teams.
Re: Ask HN: How to enforce engineers to understand the code they are shipping
#24Setup a demo day at the end of each sprint and pick a random developer and ask him to give a complete walkthrough of the code, this will force all the developers to really prepare or actually understand( what they have prompt created) before the demo day. This is atleast I have setup in my corporate job at a Bank in Danmark, I am also building my own startup sekorti.com and forcing myself to do the same(Explain the code to my junior developer before it can be deployed in production).