4 ms·
Huh. Today is my 40th year of writing software as a professional (getting paid for it, I mean -- I was writing code long before my first real job). Anyway, in
by kabdib 7y ago
Huh. Today is my 40th year of writing software as a professional (getting paid for it, I mean -- I was writing code long before my first real job).
Anyway, in all that time I've done (...counts...) four all-nighters. I did plenty of nights until 2 or 3 in the morning, but I've only seen a sunrise at work four times. This includes stints at Atari, Apple, a number of Silly Valley startups, Microsoft, and my current gig.
Each one of those all-nighters pretty much killed me for a day or two. In retrospect I do not regret them, they were necessary to the team and for me to keep my word about completing a critical component on time. I'd probably do the same again.
- n4r9 7y agoDespite the name being fairly clear I think people have different conceptions of what an all-nighter is. I interpreted the following quote from the article as saying that they went home very late into the night and then came back to the office the next day. > "I remember doing my first 'all-nighter'," she says. "I came back into the office the next day with a swagger."