13 ms·
Programming is terrible – Lessons learned from a life wasted (2013) [video]
- Aldo_MX 12y agoThe slides for those who prefer to skim through them before deciding if watching a 1-hour conference or not: https://github.com/tef/emfcamp2012/raw/master/programming_is_terrible.pdf https://github.com/tef/emfcamp2012/raw/master/programming_is...
- derekp7 12y agoThanks -- the slides in the video are kind of hard to read.
- ffn 12y agoThis is one of the funniest tech-talks I've heard (the funniest is XOXO's lottery collective talk). Thanks OP.
- tluyben2 12y agoWatched this quite a while ago; good watch if you like this kind of humor.
- Jamie452 12y agoFrom the first 10 minutes this seems more like standup to me!
- lettergram 12y agoI started watching it, and had to remember after 15 minutes to come back and up vote.
- encoderer 12y agoHe bashes the "myth of the 10x" engineer. Clearly the idea of the 10xer has too big a place in the mythology of our industry. It's oddly masochistic and as far as I know it's unique to us. There are no doctors blogging about "10x doctors" for example. Anybody who has watched N0tch code on Twitch knows that there are certainly people who are far more productive coders than the average engineer. I have no idea if he's coding 10x faster than I could but it's probably close. And my ego is... healthy sized. But it ignores the truth that few of us work as "programmers." A software engineer has many responsibilities and doing the other things well brings a force multiplier to your work. I personally subscribe to the belief that we all have a superpower or two, and figuring them out and pressing their advantage is a strong catalyst to success. So figure out what you 10x at and be happy for it.
- rch 12y ago> There are no doctors blogging about "10x doctors" There are still 10x equivalents though. For instance, a PhD MD that chairs a department at a major hospital, publishes significant research, participates in NIH or similar organisations, and still sees patients is going to be a very different sort of professional than your local GP. It's the notion that 10x applies only to NCLOC production that needs rethinking, so you're in the ballpark in that respect.
- IgorPartola 12y agoBut which doctor will give you better care? And which doctor will save more lives, or improve them in a meaningful way? Those are different jobs. Is a security researcher more or less productive than a programmer on a team of 10?
- BrainInAJar 12y agobut those 10x equivalents are specialized, and there's absolutely a place for your local GP. Whereas every company is falling over themselves to hire the 10x programmer. A local GP is what you want for tracking your longitudinal health and being a personal interaction with the health care system for you. Not someone chairing a department & publishing research
- engendered 12y agoWhereas every company is falling over themselves to hire the 10x programmer. Is this true? I've been involved in a number of hires over the years where we quite specifically did not want a "10x programmer". We knew the position didn't pay enough, and had enough tiresome, non-novel work (e.g. building data processes for client data. Not big enough or interesting enough to be big data or technically challenging) that we simply wanted, in effect, a marginally competent chair warmer. From seeing hiring and employment practices, this seems to be absolutely common across the industry. Similarly there is another comment that opines that every programmer thinks they're a 10x programmer. Now maybe it's because I have a work history in places like financial firms and banks and insurance and telecom, rather than pure software or Google-esque, but this is absolutely untrue. I found that the vast majority of developers were simply careerists.
- okasaki 12y agopage 10 of the slides says: > kill yourself now That's totally inappropriate no matter how funny you think you are.
- bcook 12y agoComing from a link titled "Programming is terrible – Lessons learned from a life wasted" I expected some humor that may not be Politically Correct. Strangely, your response bothers me more than the quote. Could you not find anything positive to say?
- GFK_of_xmaspast 12y agoCouldn't you?
- throwawaymaroon 12y ago...you've really escaped the cycle of negative feedback, haven't you? ;)
- sp332 12y agoFor an industry with a very high rate of depression, and disproportionately populated by demographics where suicide is the #2 leading cause of death, it's a very inappropriate joke. Source: Men http://www.cdc.gov/men/lcod/2011/LCOD_menallages2011.pdf http://www.cdc.gov/men/lcod/2011/LCOD_menallages2011.pdf and women http://www.cdc.gov/women/lcod/2011/WomenAll_2011.pdf http://www.cdc.gov/women/lcod/2011/WomenAll_2011.pdf
- bcook 12y agoI have suffered from chronic depression for almost 20 years now, so I am sympathetic to your perspective. Most humor is "inappropriate" in my experience. So, inappropriateness seems VERY appropriate when attempting to be humorous... Hehe, go watch some stand-up by Louis CK, Richard Pryor, or George Carlin for example.
- AndrewDucker 12y agoIf you liked this, then you'll like the associated blog: http://programmingisterrible.com/ http://programmingisterrible.com/
- ScottCraig 12y agoHilarious
- gtirloni 12y agoPrevious threads: http://bit.ly/18tRRMz http://bit.ly/18tRRMz
- Havoc 12y agoProgramming is great. It helped me streamline my thinking so to speak. Once your passion becomes your job it becomes tainted though.
- barbs 12y agoWhilst the video was uploaded in 2013, the title implies that it was presented in 2012. (Sorry for nitpicking)
- csours 12y agoPutting aside all the ad-hominem and everything-is-terrible, I think I learned a lot from following the references Tef makes in this talk. Some references (sorry for the formatting, if this becomes a thing I'll do the wiki and the logo): Slides: https://github.com/tef/emfcamp2012/raw/master/programming_is_terrible.pdf https://github.com/tef/emfcamp2012/raw/master/programming_is... Blub Paradox: http://www.paulgraham.com/avg.html http://www.paulgraham.com/avg.html http://c2.com/cgi/wiki?BlubParadox http://c2.com/cgi/wiki?BlubParadox Perl and 9/11: http://www.paulgraham.com/hijack.html http://www.paulgraham.com/hijack.html 10x: http://hfs.sagepub.com/content/16/1/70.short http://hfs.sagepub.com/content/16/1/70.short http://www.construx.com/10x_Software_Development/Origins_of_10X_%E2%80%93_How_Valid_is_the_Underlying_Research_/ http://www.construx.com/10x_Software_Development/Origins_of_... http://www.construx.com/10x_Software_Development/Productivity_Variations_Among_Software_Developers_and_Teams__The_Origin_of_10x/ http://www.construx.com/10x_Software_Development/Productivit... Waterfall (same pdf, linking from 2 sources): http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/wate... http://leadinganswers.typepad.com/leading_answers/files/original_waterfall_paper_winston_royce.pdf http://leadinganswers.typepad.com/leading_answers/files/orig... Conway's law: http://en.wikipedia.org/wiki/Conway%27s_law http://en.wikipedia.org/wiki/Conway%27s_law Unrelated, Pournelle's Iron Law of Bureaucracy (I just like this law): http://www.jerrypournelle.com/reports/jerryp/iron.html http://www.jerrypournelle.com/reports/jerryp/iron.html X-Y Problem: http://meta.stackexchange.com/questions/66377/what-is-the-xy-problem http://meta.stackexchange.com/questions/66377/what-is-the-xy... Atwood, Don't Learn to Code: http://blog.codinghorror.com/please-dont-learn-to-code/ http://blog.codinghorror.com/please-dont-learn-to-code/ Wason selection task: http://en.wikipedia.org/wiki/Wason_selection_task http://en.wikipedia.org/wiki/Wason_selection_task LMGTFY: https://www.google.com/search?q=pieget+constructive+learning https://www.google.com/search?q=pieget+constructive+learning https://www.google.com/search?q=curry+howard+isomorphism https://www.google.com/search?q=curry+howard+isomorphism Amazon Links, no referral: http://www.amazon.com/Mindstorms-Children-Computers-Powerful-Ideas/dp/0465046746 http://www.amazon.com/Mindstorms-Children-Computers-Powerful... http://www.amazon.com/Peopleware-Productive-Projects-Teams-3rd/dp/0321934113/ref=asap_bc?ie=UTF8 http://www.amazon.com/Peopleware-Productive-Projects-Teams-3... http://www.amazon.com/dp/B00B8USS14/ref=wl_mb_recs_2_title http://www.amazon.com/dp/B00B8USS14/ref=wl_mb_recs_2_title http://www.amazon.com/Design-Essays-Computer-Scientist-ebook/dp/B003DKG5H6/ref=sr_1_2?s=digital-text&ie=UTF8&qid=1426476643&sr=1-2 http://www.amazon.com/Design-Essays-Computer-Scientist-ebook...
- Animats 12y agoHe's talking about the guy who did Viaweb, which became Yahoo Store. First server side application which allowed designing a web site via a browser, written in LISP. The way to deal with overoptimistic programmers is to put them on maintenance programming, fixing bugs in the code of others, for a few months or years.
- nocman 12y agoUm, I'm assuming that you are purposefully avoiding mentioning Paul Graham's name. You know, they guy who wrote the software that runs the site on which you are posting your comment. :-D (wasn't sure if you were trying to be funny by doing so, or if there is something else relevant I've missed in the many posts above and below this that I haven't read)
- binarytrees 12y agoWho cares if you're 10x, we'll all be 10x dead at some point. In 50-100 years I doubt most of your 10x work will still be around. Might as well go enjoy some life before it ends.
- socceroos 12y ago^ this guy gets it. Life is short, do your best at your profession but keep everything in perspective - do what you love!
- M8 12y agoGitHub and BitBucket are going to delete sources after a period of time? Could you please point me to that licence agreement paragraph? Are museums going to throw away paintings in 50-100 years as well?
- supercoder 12y agoWhat's to suggest the majority of peoples work is stored on github or bitbucket ?
- forloop 12y ago1) This sounds like rationalisation. Clearly there's advantages to being 10x at something valuable. 2) The premise of the 10xers not being around in 50-100 years could be correct. It depends on the amount of money invested in anti-ageing technology. Coming down on one side or another, in a binary fashion: I think your comment is false.
- shawn-furyan 12y ago2) Well, given the associated uncertainty, that's not strictly true. The relationship between money spent on aging research and lifespan extension could converge on a marginally higher average lifespan rather than growing infinitely long with infinitely increasing expenditure. Until better than marginal gains are realized, I would say it's premature to hold massive lifespan lengthening out as a realistic possibility since we don't know what road blocks lie ahead. Sure, it's possible in the 'anything is possible' sense, but, IMO, not as a practical consideration.
- billions 12y ago10X developers have and exercise vision. Similar to how a CEO is arguably the best business person in the company, a developer may have the same differentiation in performance without the business domain counterpart's visibility in the organization. A CEO knows not to enter a competitive market, a great dev knows not to increase code complexity. A CEO knows to choose opportunities worth pursuing, a great dev knows which resources to use and avoid. A great dev makes decisions based on 100s of datapoints instead of 10s. It's like chess-and there are certainly 10X chess players.
- pawelkomarnicki 12y agoI find the whole idea of using "writing speed" as the factor describing how good is a programmer, plainly: stupid. Honestly, you can be a mindless person making weird, overblown constructs all day, and then you can be a smart developer that thinks before writing few characters and solving the same problem. I would rather consider efficiency as the factor: process and output efficiency. Process efficiency is how organised is the process of the development — a.k.a. getting things done. If somebody keeps shipping stuff, they are process efficient. Even if it's the smallest thing ever, just keeping the flow going. Then there's the output efficiency — how efficient is the thing that was shipped. Is the code high quality? Is the algorithm performing well in the problem's domain? Is the code running "fast"? I personally think that the best developers optimise their work on these two fields: they keep delivering great output code most of the time. Because what is better: lots of bad code in short time, or good code taking more time?