←back to thread

414 points henry_flower | 1 comments | | HN request time: 0.001s | source
Show context
m4r1k ◴[] No.43112034[source]
I once saw a talk from Brian Kernighan who made a joke about how in three weeks Ken Thompson wrote a text editor, the B compiler, and the skeleton for managing input/output files, which turned out to be UNIX. The joke was that nowadays we're a bit less efficient :-D
replies(7): >>43112150 #>>43112344 #>>43112772 #>>43114120 #>>43117365 #>>43118374 #>>43118624 #
xattt ◴[] No.43114120[source]
I’m wondering what the process was for the early UNIX developers to attain this level of productivity.

Did they treat this as a 9-5 effort, or did they go into a “goblin mode” just to get it done while neglecting other aspects of their lives?

replies(5): >>43114283 #>>43115981 #>>43118732 #>>43118755 #>>43126073 #
ironmanszombie ◴[] No.43115981[source]
Back in my early career, the company I worked for needed an inventory system tailored to their unique process flow. Such system was already in development and was scheduled to launch "soon". A few months went by and I got fed up with the toil. Sat down one weekend and implemented the whole thing in Django. I'm no genius and I managed to have a solution that my team used for a few years until the company had theirs launched. In a weekend. Amazing what you can do when you want to Get Shit Done!
replies(2): >>43117965 #>>43120528 #
1. deaddodo ◴[] No.43117965[source]
That's fine when it's self-motivated, but it sets a terrible precedent for expectations. Doing things like this can put in management's mind unrealistic expectations for you to always work at that pace. Which can be unhealthy and burnout-inducing.