3 ms·
That's why there's SREs (badass generalists): too many developers get ensconced in a tiny silo and afraid/unwilling to venture outside their turf. Frankly, som
by bayareanative 7y ago
That's why there's SREs (badass generalists): too many developers get ensconced in a tiny silo and afraid/unwilling to venture outside their turf.
Frankly, someone who hasn't:
- written a self-bootstrapping compiler
- designed and microcoded a branch-predicting, pipelined processor
- written a toy OS that works
- spent an inordinate time with assembly
- ran fuzzing against a library
can't legitimately call themselves an engineer. People who don't grasp the implications of their implementation decisions are vast the majority... and how many of them can fix things when something malfunctions at a layer that they they're unwilling/incapable of debugging? Either they can depend on some other specialists, find a local generalist engineer to fix it for them or they can "be the change they seek."
- jdsully 7y agoThat's an incredibly high bar. I'd honestly be shocked if even the hardcore NT Kernel developers had built a microcoded branch predicting processor.
- jki275 7y agoThat’s a very unrealistic standard. Almost no one has done all those things. Most people working in the industry haven’t done most of them. Most people with MS degrees in the field haven’t done all of them.
- ameyv 7y agoWriting simple compiler or OS or bootloader for learning is fine.. but "microcoded a branch-predicting, pipelined processor" is hard code stuff.. I would rather say people should at least improve algo & data structure, ability debug issues, even if they are not able to fix it...ability to find or debug thing is important.