3 ms·
What "politics" I adopt depends mostly on what I'm building. If it's a library that someone else will use, I try to play as conservatively as possible, and I f
by kstenerud 14y ago
What "politics" I adopt depends mostly on what I'm building.
If it's a library that someone else will use, I try to play as conservatively as possible, and I fully expect that despite my best efforts those developers will uncover lots of bugs regardless.
If it's a mission critical application, I'll also be conservative. The more pain there is in fixing things later, the more careful I'll be up front.
When I'm writing a game, I'll play it more fast-and-loose. So long as any glitches don't crash it or open an exploit or ruin the user experience, it's usually an acceptable trade-off.
When I'm writing stuff for myself, I go crazy, trying out all new fads and methodologies just for the hell of it. This way, I learn new things and get enough experience with them to mark them as conservative-safe and liberal-safe.
My only sticking point is this: If someone competent cannot follow your code, you haven't documented things properly.
- dasil003 14y agoThis is essentially what I commented on G+ and what I came here to say. A programmer who does not understand the tradeoffs of liberalism vs conservatism as Yegge defines them is not a good engineer. At best they might be talented at doing things a very specific way, sort of like a designer whose stuff all looks the same and is often inappropriate for the job at hand. Such a person is more an artist than a designer, and I'd make the same distinction for someone who writes log-processing code in Haskell or codes software for a spaceship in Ruby.
- pjscott 14y agoActually, I'm pretty sure you could make a good case for log processing in Haskell. There are some businesses with lots of log data, containing any number of dimensions along which you might legitimately want to slice and dice, with their formats and schemas changing over time. Haskell's type checking is really good at catching the type of bugs that tend to crawl out of this kind of application, and its speed is a good thing when you're dealing with a whole lot of logs.
- dasil003 14y agoSure, bad example, but the point stands. Not everything requires type safety, and playing fast and loose with dynamic typing is not always faster. Programmers shouldn't be ideological, they should always be striving for the best solution by understanding the tradeoffs in any given situation. To do so effectively requires both liberalism and conservatism as Yegge defines them.