if it's still there when you retire... good luck!
1,111 karma · joined June 30, 2016
if it's still there when you retire... good luck!
You're forgetting the mentality you're dealing with: as far as they're concerned, if you're not productive, regardless of the environment, the problem is you. Never them.
I don't think they're struggling very hard. If anything, they're struggling to make it look like there's anything except complete bias.
Not to mention ambiguous. I've never found two people who can agree on the proper interpretation of even one of the guidelines in HIPAA or PCI. My experience with both has been managers who would rather spend a week trying to get out of having to be compliant than spend a day just complying.
I would recommend the polar opposite, actually: use a framework that has nothing in common with anything that you already know. After all, half (or more) of the point of personal projects is to learn new things, right?
o.p. has had three different employers in 10 years (and actually this goes back more like 15 years, since "open offices" became a fad, and five different employers). Every place is exactly the same.
source: am o.p.
Actually I've had 3 over the past ten years. They're all the same. You've never noticed?
I know Walter. He made a big point of sending e-mails at 2 AM, CC-ing the recipient's boss, and then following up at 8:00 the next morning asking why you hadn't responded yet.
They also want you _doing_ something every hour of every day - and learning/studying/researching/prototyping/experimenting/refactoring/migrating doesn't count as _doing_ anything, because there's no "business driver" behind it. So you have to invent things to do because there's going to be a daily standup at 8 AM tomorrow morning where management engages in the daily "who can I fire because _I_ have to _do_ something, and firing somebody is something" ritual.
And expect those changes to take an hour (maybe two).
Or when somebody can write a 5-line shell script in Bash that:
a) typical non-programmers can and will use b) produces enough diagnostic information that anybody (programmer or not) can use to troubleshoot when something inevitably goes wrong - whether it's user input, network connectivity, a missing dependency...
I get what he's saying, but he's talking about a pretty small subset of what we really do.
You've led a charmed life. In my 25 years in this business, I've found that very little induces the same level of panic in management as "experimenting" with something, especially something that you can't put a solid "business case" behind and "estimate" down to the nearest half hour.
Hell, I'd settle for just not discouraging it so damned hard.
Well, actually yes, yes I am. You can make a compelling case that this shouldn't be the case, or that they people paying me are shooting themselves in the foot running things the way they're running things, but the fact remains that in today's daily standup/weekly status report/what have you done for me lately "agile" corporate environment, I am absolutely paid to write code and if I don't write code, they'll stop paying me.
But you didn't die, so it must be Snapchat.
... I'm going to assume you left out a "not" in that sentence ...
Not Apple. They have OS/X.