4 ms·
If the code is so smart that it's not easily understandable, it's not easily fixable. My transition from junior to senior was accompanied by the realization th
by SketchySeaBeast 4mo ago
If the code is so smart that it's not easily understandable, it's not easily fixable. My transition from junior to senior was accompanied by the realization that simpler is nearly always better.
- cat_plus_plus 4mo agoWrite me simple AI inference code that has high performance in big batches.
- SketchySeaBeast 4mo agoI don't know enough to speak about that particular domain, but if the junior is writing something the senior can't understand, that's always going to be a problem. That code becomes the team's responsibility, and that code needs to be able to be maintained by the entire team, not only by the junior with something to prove. Who is getting called at 2 AM when something breaks? Not the junior.
- cat_plus_plus 4mo agoHehe you think L9s do oncall? Senior not understanding is a problem all right. It's not necessarily junior's problem.
- SketchySeaBeast 4mo agoI feel like you keep missing the point and are more interested in gotcha's.
- AlotOfReading 4mo agoDoes tinygrad not count for some reason?
- cat_plus_plus 3mo agoNo senior architect around here is capable of understanding tinygrad
- deleted 4mo ago[deleted]
- sjducb 4mo agoGood programmers write code that’s so simple and obvious it looks like anyone could have written it. Bad programmers make the simplest things really complicated.
- SketchySeaBeast 4mo agoGreat programmers write code that makes you wonder why everyone doesn't do it like that.