fjcururuvy7
Joined 2 months ago
Joined 2 months ago
As does caveman.
Set acceptable review standards, outline appropriate frameworking, document approaches, test standards, documentation standards and overall just set good examples in both context and the codebase.
If your codebase is slop it's because you approved it.
Other than practicing some leet code in between jobs, it's extremely rare any of that stuff comes up.
The hard parts in my job isn't and hasn't been the computer science parts in a long time, or at least when it does come up it's not something I really think about much. The trade offs are almost always domain, business or product based. The technical solutions are just down stream of those constraints.
The problem is a lot of the science might be correct but that doesn't make it pragmatic and more often than not, it's just counter productive.
It's incredibly difficult now dealing with zoomers in the workplace that think I'm some old boomer that never learned "proper computer science".
No, sorry Timmy, it's not because I don't understand microservices, it's because I actually do.
Just fork it and have the agents maintain security patches moving forward.