9 ms·
Three virtues of a great programmer
- ChrisArchitect 3y ago(1991)
- henryreynolds 3y agoImpatience also makes you write more performant software because you can't stand waiting on build/test/run cycles.
- samatman 3y agoI would say that the character arc of Perl, and the profession generally, leads me to this observation: laziness and impatience are virtues. Be careful with hubris.
- mcbuilder 3y agoI'd say wisdom should be the third, but that in turn often leads to hubris.
- ludston 3y agoWisdom is to know yourself. Hubris is the belief that your accomplishments and skills are greater than they are. Are these not mutually exclusive?
- dgfitz 3y agoI'd even go so far as to say !hubris Pride often leads to unintentional blindness and irrational defensiveness. Humility is where the fun is.
- Enk1du 3y agoHubris was really about building the community. It encouraged you to build things that you would want to share, so that we could all benefit from your Laziness and Impatience.
- scj 3y agoI'd argue hubris is balanced by laziness and impatience. Where I don't believe the three are equal. I'd add a conditional lesser virtue when working on certain codebases that should have been accounted for when making perl6: Fear.
- pugworthy 3y agoIf you're not familiar with Larry Wall's style this might seem a bit off putting. The first time I ever saw him speak was the 1997 first annual O'Reilly Perl conference. I remember thinking, "This guy is a jerk" while also thinking "I love this guy"
- iamcreasy 3y agoIs there any publicly available talk of Larry Wall that might evoke it today?
- cratermoon 3y agoAny of his "State of the Onion" talks. https://www.youtube.com/watch?v=a1SEt_-QMDo https://www.youtube.com/watch?v=a1SEt_-QMDo
- Enk1du 3y agoA quick explanation of the Three Virtues by Larry and then an impromptu explanation of why Hobbits would make good programmers https://www.youtube.com/watch?v=G49RUPv5-NU https://www.youtube.com/watch?v=G49RUPv5-NU
- UncleOxidant 3y agoBy all accounts he's actually a really nice guy.
- hyperhello 3y agoI don’t have the time or want to read the page, but I’m sure I’m already as good as him.
- amiantos 3y agoYou're only dunking on yourself here, the page is four sentences long. Being proudly ignorant is still just ignorance.
- teach 3y agowhoosh
- petsfed 3y agoYou missed the joke. Should I diagram it for you?
- drewcoo 3y agoIn UML, the joke would be much longer. And is the punch line solid or dotted?
- slowmovintarget 3y agoSelf-composite diamond for recursive association.
- stacktraceyo 3y agoYikes
- artemonster 3y agoMaybe someone can do a quick TL;DR; version of it? :)
- niggerman5000 3y ago[flagged]
- zbentley 3y agoOh Larry, never change. I often give a similar list as a glib answer in interviews when asked "what are your greatest strengths?" Mine are usually: I'm stupid (not smart enough to overcomplicate), lazy (prefer turning MVP in on time rather than adding too many bells and whistles), and forgetful (document everything because I won't remember what I was doing the next day).
- lexarflash8g 3y agoWhat is your biggest weakness: "I work too hard" -- humblebrag
- amarant 3y agoAs someone currently recovering from burnout, that is indeed my greatest weakness, and it's anything but a brag! Working too hard means you're liable to disappear for 6+months, no sane employer should want that!
- multiplied 3y agoDo you work too hard or spend a lot of time on work? (before downvoting me, please consider that those things maybe different)
- amarant 3y agoA bit of both I suppose. In my case I think taking on too many responsibilities and stressing out too much over any production issues that arose were the main ingredients for disaster. But there were others as well. Burnout is complicated.
- elvis10ten 3y agoAs someone who has worked hard for years (at some point I had three con-concurrent jobs), I’m not sure working hard is the variable that causes burnout :thinking_face: I will say tho, it gave me persistent back problems and RSI for two years :). But that again is not just “working hard”. It was bad posture, lack of stretching, breaks and exercise, I think. Edit: Perhaps it’s the nature of the work or working hard unhealthily (physical and mental?) or the person’s characteristics.
- petsfed 3y agoI've never really liked his inclusion of hubris here. Hubris is often defined as unjustified arrogance. Justified confidence, even if you're a jerk about it, was never the fatal flaw of a Greek hero. So I've always substituted arrogance for hubris: the belief that you better understand, and can better address, the requirements than any off-the-shelf library/program/ecosystem.
- mattbee 3y agoWhen you learn programming, you are told to never roll your own crypto, or to always use the ready-made libraries, or to avoid manual memory management - and you can have a perfectly fruitful career following rules like that. But you don't get big changes or ambitious intellectual growth without spotting that - if you did choose to break those sorts of rules - you could build something really new and exciting. Anyhow that's how I've always taken the "hubris" part - knowing when there's an opportunity to achieve something in a way that someone will tell you is too risky.
- bluefirebrand 3y ago> When you learn programming, you are told to never roll your own crypto, or to always use the ready-made libraries, or to avoid manual memory management I've always taken this sort of advice, such as "never reinvent the wheel" to mean "inventing the wheel is time consuming so give yourself an advantage by using already existing wheels", which really has nothing to do with hubris. I never took it as "Don't bother trying to reinvent the wheel because you aren't capable of it"
- eloisant 3y agoYou can build a better wheel if you want to focus on that. If you want to build a car however, focus on building the car and not creating a new kind of wheel.
- shiroiushi 3y agoIf you want to build a better car than everyone else's current cars, you might need to create a new kind of wheel. Look at the Apollo moon rovers, for instance: they couldn't use off-the-shelf wheels for those.
- tmaly 3y agoOne could have also titled it Three Virtues of ChatGPT
- Simon_ORourke 3y agoI'd add a variation on that third one - it's all they've got going for them. The really great coders I've worked with live and breathe the work, and come 5pm on a weekday they just continue on coding only this time for fun at home themselves.
- lexarflash8g 3y agoIf you come at 5pm or past to work on an OSS project or your own side project more power to you. For a corp job why work longer than you need to when you are not paid for it? Bragging rights?
- HermitX 3y agoI would also like to add one more thing: hesitation. From my own experience, in my programming career, the most time my team wasted was on redoing something from scratch. Why redo it? Because the previous design was not comprehensive enough to meet subsequent requirements. If everyone could spend more time researching and discussing the plan before starting, and get things right in one go, in my view, this is much more effective than rushing into development work.
- leetrout 3y agoHindsight / survivorship bias affects this viewpoint. You will never get it "right" the first time as much as you can avoid doing it "very wrong". The key is to have enough experience and taste to appropriately break down problems into pieces that encapsulate the volatility of the various domains. Then you can refactor easier which should be the real goal. Prune and tend to the garden.
- AnimalMuppet 3y agoYeah. It's easier to not do something stupid than it is to do something smart. Take the time to avoid doing stupid things (which takes somewhat more time than you expect!) and don't take the time to try (and usually fail) to be overly smart.
- hinkley 3y agoReversible decisions are a simple enough concept to grasp, but a difficult one to really comprehend. Some people see effective people making 'bad' decisions and miss the bit where there were eight bad ways to accomplish something and they rejected 6 as being more work overall. Then they take their misreading of the situation as justification for YOLOing decisions to avoid analysis paralysis.
- quietbritishjim 3y ago> Because the previous design was not comprehensive enough to meet subsequent requirements. YAGNI. Hesitation to avoid unnecessary work, sure. But not to anticipate future requirements. The number of times I've had to fight a fancy design that left expansion points / abstractions for future features that were never needed (or not in the form the designers expected) enormously outnumber the times any such thing was useful. Just make the code do its current job in the simplest way possible. That's the easiest design to expand later.
- rlv-dan 3y agoHobby programmer perhaps. But a professional systems developer in a larger corporation? Not so sure...
- GMoromisato 3y agoI'd add Curiosity instead of Impatience. Impatience is related to Laziness. In both cases we want the computer to do the work instead of us. But Curiosity is orthogonal and important. The best programmers I know were always curious: Why was it built that way? Why does it give that output? Why did she say that? Curiosity is the beginning of knowledge. If you're not curious, you will miss out on a lot of opportunities for learning and improvement.
- softfalcon 3y agoSeconded, and I’d add this is a quality of a great human being. Curious people are curious about others too, not just systems. It’s related to caring. You have to care to be curious and we could use more people taking care in their lives.
- squishington 3y ago[dead]
- woooooo 3y agoIt doesn't work as well rhetorically as having all 3 virtues be typically thought of as flaws.
- GMoromisato 3y agoYou're right! I didn't catch that. Maybe Snooping? Nosiness? Meddling?
- dkz999 3y agoDisruption? "Fixing what isn't broken"? Im going with: Making perfect the enemy of the good.
- Izkata 3y agoKinda works anyway: "curiosity killed the cat"
- deleted 3y ago[deleted]
- annoyingnoob 3y agoHow did that work out for Perl?
- IvyMike 3y agoThey had a good run.
- augustk 3y agoI think programming is an basically an exercise in effective communication. Edsger Dijkstra said that "Besides a mathematical inclination, an exceptionally good mastery of one's native tongue is the most vital asset of a competent programmer." This means being able to write down a description of a problem or a solution in a clear and concise way. This is the test I would use if I hired people (not only programmers). At my job I have noticed that quite a few people cannot write proper sentences or are way too verbose in their writing.
- soneca 3y ago> ”… an exceptionally good mastery of one's native tongue …” Does that imply that one cannot be a competent programmer if working on an environment where the spoken tongue is not their native one?
- ineptech 3y agoNo, I'm 90% certain both Dijkstra and OP meant that what's critical is mastery of any tongue. In context, he was talking about what makes someone good at programming, not about the need to contribute to a team or communicate ideas. https://www.cs.virginia.edu/~evans/cs655/readings/ewd498.html https://www.cs.virginia.edu/~evans/cs655/readings/ewd498.htm...
- jdbernard 3y agoI don't think so. I think the core of Djikstra's thought is that mastery of your native tongue coincides with strong communication skill and ability to logically organize and present thoughts. You can articulate your thoughts and do so in a way that others can understand. Working outside your native tongue may add hurdles, but from my experience having worked with brilliant people who's native tongue is not English, those hurdles can be overcome. The skills still translate.
- RugnirViking 3y agoPresumably the point is not the specific emphasis on your native tongue exactly, but rather a mastery beyond what might be regularly implied by mastery of a language (able to converse like a local) and rather mastery unique even among native speakers (able to convey ideas many different ways with a particular glibness that others can easily understand)
- djaouen 3y agoPerl. Lol
- lacoolj 3y agoI found my new bible
- picometer 3y agoI’ve had a variety of responses to this list over my programming life (~10 years hobby, ~10 years professional). When I first encountered them as a hobbyist, they were surprising, as perhaps intended, due to the framing of classic vices as virtues. On some reflection though, it made sense, and shaped my understanding of programming as somehow _inherently different_ than other types of creation. When I got started with a professional career, they functioned to soften the edge of anxiety. It meant that the community of programmers who came before me - which presumably included Larry Wall - would understand that these patterns in coder behavior were ultimately beneficial and that I would maybe fit in with a corporate programming environment. (Now I know that this isn’t always true; sometimes coworkers, both programmers and non-programmers, don’t always realize these unintuitive points, and in some special cases, those programmer instincts aren’t actually valuable.) At some point, I disagreed with the framing. As others have pointed out, the patterns can be reframed as classic or functional virtues such as curiosity. Then I backpedaled and realized that the framing is important because these are unintuitive patterns and it makes us re-think habitual incentives that reward, e.g., work that is more productive but not more effective. How did it hit me now? I realize that it’s also related to power dynamics. Programmers are assets to their employers but they’re also potential disrupters. The traditional “virtuous” framing of potentially-less-effective behavior, like patience, is related to the organizing and taming of a workforce. It’s also related to the types of problems we encounter. When we work with computers, Larry’s list does usually lead to more effective outcomes. But when working with other humans, who have their own agency and idiosyncrasies, the traditional virtues are better-adapted behavior. This is also more true for the complex technical systems we deal with nowadays. So, as our careers transition from programming to system engineering and/or management, the traditional virtues become more relevant. Anyhow, this is an evergreen and thought-provoking nugget of wisdom. Thanks to Larry Wall and those who have preserved it.
- h0l0cube 3y agoThe main annoyance I have with Larry’s take is that efficiency is confused with laziness, which are entirely different things. Laziness, at its extreme, is to delay doing something until absolutely necessary, or even avoid entirely, efficiency is to optimize for the least possible effort, which is sometimes the same as being lazy
- komodus 3y agoCuriosity, we waste time learning a thousand useless 'shiny' things at the same time, then we apply all we learnt solving problems easily
- pompino 3y agoOne missing virtue is never impart programming advice or wisdom on the internet - Because 10 other programmers who know nothing about you or your job will tell you in detail all the ways in which you're doing it wrong.
- marssaxman 3y agoThis is essentially Cunningham's law, eh? Perhaps you want to learn how you could do it better!
- pompino 3y agoYeah, good point.
- hansvm 3y agoThe internet is famously hostile. If only two other people complain about my methodology I think I must have done something right.
- Enk1du 3y agoIt was kind of a thing at the time. In the Afterword of Æleen Frisch's Essential System Administration (also 1991) subtitled "Don't Forget to Have Fun", there are listed _seven_ virtues of a system administrator: * Flexibility: being able to wriggle out of tight spots and escape when irate users seem to have you cornered * Ingenuity: realizing that you can use syslog to send messages to your friend on another system * Patience: remaining capable of waiting until the final sendmail bug is fixed * Persistence: the compulsion to try just-one-more-thing to fix a problem before going home * Adherence to Routine: insisting on real milk and sugar-in-the-raw in your coffee (which is Kona or nothing) * Attention to Detail: noticing that the clock on one of your systems is using Aleutian time, and changing all the others to match * Laziness: writing a 250-line Perl script to avoid typing 15 characters I took the last one to heart and have admired those who could utilize the first one, because I never could.
- dang 3y agoRelated: The Three Virtues of a Great Programmer - https://news.ycombinator.com/item?id=32487944 https://news.ycombinator.com/item?id=32487944 - Aug 2022 (2 comments) Larry Wall's Three Great Virtues of a Programmer - https://news.ycombinator.com/item?id=24107571 https://news.ycombinator.com/item?id=24107571 - Aug 2020 (1 comment) Develop the three great virtues of a programmer: laziness, impatience, and hubris - https://news.ycombinator.com/item?id=11516215 https://news.ycombinator.com/item?id=11516215 - April 2016 (72 comments) The Three Virtues of a GREAT Programmer - https://news.ycombinator.com/item?id=10942079 https://news.ycombinator.com/item?id=10942079 - Jan 2016 (4 comments) The Three Great Virtues of a Programmer: Laziness, Impatience, and Hubris - https://news.ycombinator.com/item?id=9788088 https://news.ycombinator.com/item?id=9788088 - June 2015 (67 comments)
- AtlasBarfed 3y agoThe most reposted four lines ever?
- nickm12 3y agoInteresting that the title bounces between the "virtues of a great programmer" and the "great virtues of a programmer", which have two very different meaning. I can get behind these "virtues" as being part of the psyche that drives programmers to do what they do, which is what I think was Larry Wall's original point. These have nothing to do with what makes someone a great programmer, though.
- baerrie 3y agoMy whole life I have been called lazy. In filmmaking as an assistant this was a weakness, work harder not smarter and all that. I still feel insecure about it sometimes but over the past few years of transitioning into coding full time I have learned that this is my best trait. Life is short, you must demand to live your life how you want otherwise you will be convinced that working hard for someone else makes sense.
- cloverich 3y agoCongrats on the jump, changing careers is hard!
- RustyRussell 3y agoI always said the fourth virtue is fear (of complexity). Keeps the others in check, particularly hubris:)
- golergka 3y agoI would add stupidity. I know I'm stupid, that's why I write types, tests and documentation.
- librasteve 3y agoi always thought that the Laziness virtue was a tacit reference to lazy evaluation of arrays (LISP-like) ... I get the feeling that most ML languages have quietly dropped this aspiration (Haskell, ML, ELM, I'm looking at you) ... meantime Larry's opus magnus "raku" (renamed from per6) is still lazy at heart
- 65 3y agoIt's funny, I can't get myself to do many other creative activities I think I should enjoy (illustration, leather working, cooking) because of the tedium of doing the same thing over and over inherent in those activities. Programming is great because every single thing you're doing isn't tedious. It's the opposite of tedium. Maybe it's not so much laziness, but more so a hatred of tedium.
- from-nibly 3y agoThis aligns well with ADHD. As someone who has ADHD and is also a programmer this is why I love programming so much!
- forinti 3y agoYou can't mention these without explaining false laziness, false hubris, and false impatience. I think Larry Wall gives us some great insights wrapped in great humour.
- phantomathkg 3y agoHugged to death by HN again. Here's the archive version. https://archive.is/yS4op https://archive.is/yS4op
- lr4444lr 3y agoThat last one ("hubris") I'm going to call out. Maybe the author means another word, for what he describes, but the actual "hubris" I'm seeing among my colleagues is the belief that lots of people out there don't know how to write code, but that their own $%^& doesn't stink. It's the utter subjectiveness of "best practices" that aren't tied to actual issues of performance, security, or flexibility, or worse - blowing one or more of these attributes of good code way out of proportion to the actual importance of the code. And "readability"? Don't get me started ... there's hardly a linter rule that I haven't seen turned into a caricature of what it was intended to do. What devs do is part art and part science, and there's hardly consensus on which part is which.
- xarope 3y agoI interpreted this "hubris" to mean that I believe I can make a difference, rather than feel that I can't contribute. You can understand why I, personally, would think this is a virtue.
- RangerScience 3y ago“audacity” might be a better word for you for that :) (To be clear: I mean this as a good thing. Audacity… seems pretty important, and very nice to have, at the right times and places)
- sverhagen 3y agoWrite code "that other people won't want to say bad things about" sounds like using the hubris (arrogance?) to throw up walls to be left alone. Maybe in some organization you might be the star player that can do this to the benefit of the greater good, but in most places collaboration of some sort is paramount, and the hubris thing doesn't sound good. Wouldn't want to hire this archetype.
- hirvi74 3y agoI just look at popular Github projects and ask myself why doesn't my code look that nice? I completely agree with your take though. There is so much "distraction" in what are best practices, readability, etc.. It's all so subjective. Best practice for what? Readability for who? I feel like software engineering : engineering :: psychiatry : medicine.
- neilv 3y agoLaziness, Impatience, and Hubris were especially clear/obvious in Perl at the time. Perl was a gazillion times more powerful than Bourne and C-shell (including all the Unix shell tools like `awk`), much more rapid than working in C, incredibly terse (perhaps too much so), and also portable (to all the oddball systems you might have). And the purposes to which Perl was put were often to automate things you'd been doing manually, or that you couldn't do without Perl. You'd be quietly doing big things with Perl. And there were sayings about how you'd automated your job, and presumably spent your time writing more Perl scripts and reading Usenet. And the occasional joke of replacing someone else with a one-line Perl script. Also, note that not only was this before the dotcom boom (when programmers suddenly were no longer nerds but getting rich and fashionable), but also-- a lot of the programmers using Perl professionally weren't even professional programmers, but actually sysadmins or random university researchers, who happened to have the power of Perl. The majority of professional programmers on Unix actually didn't know Perl. So, Perl people speaking of Perl people in terms of vices could be seen as a self-deprecating, joking spin conscious of the unusual power that they wielded.
- bdjsiqoocwk 3y agoAnd then, python.
- bamboozled 3y agoI love Python, but basically 96% of Python code and developers absolutely suck at everything, I'm fixing a shit python codebase right now. It's like a language which people love to use to write shit code.
- throwawaymaths 3y agoDiscernment: The virtue of not thinking you're building something great when you're building something awful
- glouwbug 3y agoThe best programmer saves their earnings and retires early
- donatj 3y agoOur three weapons are Laziness, Impatience, and Hubris… and an almost fanatical devotion to the pope.
- donatj 3y agoAnd of course python ... Monty Python
- 01HNNWZ0MV43FF 3y ago"Laziness, impatience, and hubris" ~ "Lean manufacturing, short iteration cycles, and ?"
- W3cUYxYwmXb5c 3y agoOldie but a goodie
- boringuser2 3y agoHow about making a static website that doesn't require extensive hosting lest it crash for a few thousands of visitors? Serving static blog content should be trivial if your code isn't absolute lunacy.