Who among us have called in sick to the day job just to put in a solid block of daytime hours on a side project? It's happened to me a few times over the years, and I've been 97% guilt-free about it.
I do that regularly, especially when I'm particularly excited about something new. I've woken up in the middle of the night, registered a new ___domain, and then emailed the office to tell them I'm not coming in that day. More than a few times.
Discussions like these, among many clearly intelligent people, can sometimes get lost in the weeds. What's missing is a basic contextual foundation, without which all the wonky details in world are nearly meaningless. Why discuss AMT, Germany, and tax loopholes without first agreeing on inequality.
Most would agree that in a capitalist system there MUST be some inequality to provide incentive; extreme inequality is unsustainable; an economy (and society) is at it's best when inequality is low; and progressive earnings taxation is in fact the only proven and viable solution to address extreme inequality.
I rarely see this foundation laid here or in "the media". We can bitch and moan about the 0.1%ers and the tax code they've written for us, and it's certainly entertaining. But let's try to agree generally on where we want to go before discussing how to get there and who's going to drive.
Yes I think everyone has had one of those "Wanna get away?" moments. Hopefully they're very early in your career and only ever happen once. Mine was small and I was very Jr so nothing more than my pride got hurt.
The worst is when someone else notices it before you. We came in to work on Monday and some reported that they couldn't log into the system. We checked logs and noticed there were timeout errors on some SQL queries. Huh, that's odd, why is there a query "update Users set deletedat=now()" with no "where" clause running in production??? Turns out someone was in a hurry and tried to make a test pass without thinking to much about what the code was doing. Then - push right to prod on a Friday evening!
If you think that's bad, ~12 years ago I worked on a project that was an online insurance form. The output from the application form was going to be printed out and then submitted to the existing paper-based workflow for handling applications - which involved scanning the application and then workers typing in the data from the scanned form.
Not more than 2.5 years ago I wrote a script to take the bill of materials from a CAD program and cross-reference it with a flat-file database (read: Excel spreadsheet) that contained information on how 'old' part numbers mapped to 'new' part numbers. Shame the CAD program couldn't just be scripted to do this. Anyway, the final output of this was a bill of materials that said what you'd expect: I need X quantity of Y parts, here are the part numbers for each.
This was emailed to a "warehouse" specialist, who then, I found out, printed out my BOM, then compared it to that day's (printed) inventory of parts, came up with what needed to be issued directly and what needed to be ordered, and then he manually entered that into the actual warehouse logistics system.
And lest you think I was lazy, I asked to be allowed to script all this out, too, only to be told "there is no way for us to submit anything to our logistics system that way, everything has to be entered manually."
This wasn't some no-name company, this was a major aerospace company.
I managed to get employee of the quarter because the company I worked for (a major company that made inkjet printers) had been tasked to find out more about third party ink cartridges from their service system.
This company had a Pick database, and rather than extend it normally someone had the bright idea of storing each ink cartridge record in a .INI file. That's right, each record was a .INI file and the fields were stored as column=value.
To get at this data, they tasked one of their employees to open each file, copy the first field to an Excel spreadsheet, then copy the second field to the Excel spreadsheet, etc. There were something like 10,000 ini files, and it took about 6 weeks for the guy to input the data.
I was rather young and bored on the call centre helpdesk, and I had been fooling about with Linux and Perl. When I heard what he was doing, I rather naively said that this was what Perl was designed for. The guy deliberately said he didn't believe me, and I took that as a challenge so that night I went home and whipped up a Perl program that processed the ini files into a CSV file. I then installed ActiveState's Windows port of Perl and ran it over a copy of the ini files. About 5 seconds later it produced the csv file.
I told the guy to not tell anyone as I wasn't really meant to install ActiveState's program on any corporate computers. He ignored this and the next thing I know I was made employee of the quarter.
I think the highlight of this story is that the company had the culture to reward you instead of burying your achievement under policy-violation blanket.
I'm not a programmer by trade. I just seem to be one of the few engineers in my tiny little specialized ___domain that doesn't mind writing a little bit of code now and then to solve a problem.
You can imagine how it felt at the time - 18 years old and I had just destroyed the accounting system for a sales-driven organization. Was convinced that was my last night at the company and had to stew in my own juices from that evening until telling my boss about it the following morning.
