Hacker News new | ask | show | jobs
by datameta 1115 days ago
I have some thoughts on the vast differences between working on a team delivering firmware that is indefinitely the lifeblood of the hardware, vs working on a team writing hardware test tools that get used by people for one cycle (1-2 years) and nobody bats an eye when they're broken/unusable or difficult to extend to the next generation of hardware...

Clean, readable, beautiful C with well thought out descriptive names for everything, comments that get anyone up to speed on the code section. Self-descriptive, pleasant to work with.

VS

MVP Python repo that has a super wide directory structure with poorly thought out grouping that takes 5x as long to memorize. When trying to understand a code section, told: "Just hit tab complete on the command line". Okay, that tells me the relationships between objects, classes, methods, containers, etc... But how does it work? Obfuscated not just from the users but the devs themselves.

Yeah.