HN user

newobj

3,699 karma

this website is full of freaks

Posts18
Comments706
View on HN

if you get into a config system that's complicated enough, and has modularization or inheritance, you'll know that the semantics of "remove this" "add that", override this, default to this, this stuff is hard to express in most config languages, or worse, you start enforcing application level semantics. when you have turing complete language you just ... do those things. we reduced the configuration data of a tool suite once by 90%+ by moving from json to python. there was a tremendous amount of duplication and overlap, with tons of TINY exceptions and variations. it was so hard to see those differences, brittle to maintain, things would get stale, ... moving to python you basically had the "base" thing expressed in one file, and a bunch of tiny delta files encoding the exact deviations. All those deviations were of the forms I described above. Adding a thing to a list. Removing a thign from a list. Overriding a whole list. Do a thing if not already done. And so on. It's also then easy to build all kinds of diagnostics, validators, etc, right into the same framework, without having to munge the data into some other form first.

To my students 3 months ago

The engineer who only does high level system design and never codes has existed for decades and is often the most useless and derided engineer in the org.

Thank you, but, now I have 10 further “explain it to me” questions. (I never did analysis so this stuff is entirely over my head. I had one semester of algebraic structures. It was the hardest class I ever had in my life.)

Speed of code-writing was never the issue at Amazon or AWS. It was always wrong-headed strategic directions, out to lunch PMs, dogshit testing environment, stakeholder soup, high turnover, bureaucracy, a pantheon of legacy systems, insane operational burdens, garbage tooling, and last but not last -- designing for inter-system failure modes, which let's be real, AI has no chance of having context for -- and so on...

Imagine if the #1 problem of your woodworking shop is staff injuries, and the solution that management foists on you is higher RPM lathes.

if they're so bad they're good ... they're actually just good. probably because they capture something increasingly rare: the human and personal touch of an artist who's not straight jacketed by "safe mode" marketing, editorial norms, analytics, blah blah blah