How To Demoralize Employees: A DIY Guide for Terrible Companies
-
This is why I hate web filtering rules. They categorize, but by no means are they 100% accurate, leading to many WTFs just like this one. In my opinion, good for filtering known malicious site, but iffy on all else.
Edit: Ok, I see in this case the wrong link was posted, but my point is still valid even if not exemplified here. :-/
Actually, this is a case where it's simply a matter of the category not explaining the policy at hand. (I'm A-OK with my employer blocking those dumb 'domain parking' pages, they are a cesspool of terrible advertising up to and including malvertising.)
-
I'm with blakey on this one. If you're providing information then you should provide all the information.
I agreed that blakey had a point. By the post you were replying to I was just replying to his generized sense of entitlement.
Let's face it, every single blakey story is "someone didn't tell me what I needed to know and I'm going to hold my breath until they tell me, because I CBA to look it up myself."
-
Let's face it, every single blakey story is "someone didn't tell me what I needed to know and I'm going to hold my breath until they tell me, because I CBA to look it up myself."
WTF?
No I just emailed back for clarification.
-
Woo we just agreed to a business plan to roll out IE9 by November 1st.
No, that isn't a typo. IE9.
-
No
FTFYt, that isn't a typo.
-
-
Woo we just agreed to a business plan to roll out IE9 by November 1st.
In defense of your IT department, they've only had 3½ years to come up with the plan. This is a web browser we're talking about- it's not like there's an easy way to keep it up-to-date.
-
Actually, most people here are stuck with IE8, due to incompatibilities with the internal tools.
-
Some people here have IE8, some IE11.
There's no pattern - all of our web apps work equally well/poorly on both, it just seems to be random.
-
I was just emailed a spreadsheet with the names of 82 servers that I have access to, and was asked to fill out a business justification for why I need access to each one.
Am I insane for thinking that's not my responsibility?
-
No.
A co-worker had something similar here. He wrote, "to perform my job duties", did a "Fill Down" in Excel and sent it back. I should follow-up and ask if they ever replied.
-
There was a mass follow-up:
"Hi All,
We have been getting some broad/vague statements in the justification field. The information provided will be used during IT Security audits. Below are some good examples for justification"
-
Woo we just agreed to a business plan to roll out IE9 by November 1st.
No, that isn't a typo. IE9.
Look who's jumping at every new fad now, hipster.
-
So I'm an admin on a production server, there's a clone of that server. The clone is a dev server. I'm not an admin on the dev server, so I get to send all my requests for changes on the dev server to someone who doesn't know what to do, since the PHBs won't let me be an admin on the dev server.
Fun.
-
Am I insane for thinking that's not my responsibility?
I'm assuming you're not the Supervisor/manager in charge of your area: "No."
Question: are you part of one or more security groups that grant you the access? Usually the description in the security group would justify your access (If they're Doing It Right™).
-
Correct, I'm not the manager.
That's what I was saying......."Software Developer" should be a group that has access to servers X, Y, Z......etc. I should never be granted access because of who I am personally, but instead, which groups I'm a member of.
-
Idiots, i would love if there was an admin to handle the boring work instead of doing it myself
-
Code review for a decently long (~300 line) SQL query, produced this emailed conversation:
John Smith:
This looks like it was originally one of my SQL scripts. There’s been an awful lot of case changes to the code. The code still works but it doesn’t match the format that we’ve been using. :)
This won’t affect the code review, tho’.
(Note: he's not referring to the SQL Case keyword, he's referring to me writing my SQL in lowercase. Which is not mentioned as part of the code review checklist.)
John Smith:
Always follow the template. That way the code always looks the same regardless of how many people worked on it. :)
As for caps, Microsoft uses them like this in its examples:
DECLARE @TranName VARCHAR(20); SELECT @TranName = 'MyTransaction'; BEGIN TRANSACTION @TranName; USE AdventureWorks2012; DELETE FROM AdventureWorks2012.HumanResources.JobCandidate WHERE JobCandidateID = 13; COMMIT TRANSACTION @TranName; GO
Me:
I guess if it was good enough for 1977, it’s good enough for all time.
(Sometimes you have to snark.)
John Smith:
Actually, the copyright info on this page shows © 2014.
I kind of just let it drop there. I hate this job.
-
Sounds like my co-worker:
Nitpicky, but in the JavaScript you've got an unholy mix of K&R style and Allman style formatting; we try to keep consistent with K&R style in JavaScript.
The response that I wish that I had:
Sorry, I forgot to Ctrl + K, Ctrl + D since I was too busy being amazed at how much code that you copied and pasted all over the place.
-
BTW I should mention that I don't know where "the template" I'm supposed to follow is, and frankly I don't give a shit either.
-
Obviously the template is any file he doesn't disapprove of the formatting of.
-
I'm actually more concerned about "actually the copyright date" thing. Did he completely not get at all that my email was tongue-in-cheek?
-
-
He didn't get it. He would have earned a whoosh badge if he were here.
-
I guess if it was good enough for 1977, it’s good enough for all time.
This made me LOL'd. (Ok I'm easily amused.)
Am I the only one who thinks this guy :) too much? Or is the DissedCourse smiley icon just creeping me out?
Watch your back, @blakeyrat.
-
I guess if it was good enough for 1977, it’s good enough for all time.
I don't really get your hatred for capitalized sql keywords. Then again, many people don't get my hatred of goddamned camel case. Still, I suck it up and go with the standards where applicable.
-
I find it useful to put SQL keywords in caps, not because I have to, but because I'm often using them in contexts where I've not got (useful) syntax highlighting for SQL. Having to put SQL in some other language's string isn't a great solution, I accept, but it is quite useful…
-
I don't really get your hatred for capitalized sql keywords. Then again, many people don't get my hatred of goddamned camel case. Still, I suck it up and go with the standards where applicable.
I might have if he didn't make the: "but if we all follow the same style guide, all our code looks identical SO WE ARE REPLACEABLE COGS" argument.
Because fuck that attitude regardless of the intent. I'm sick of being dehumanized here. If they want all-caps SQL, I'm not stopping him from checking it out, capitalizing it, and checking it back in. But I am not going to be any more of a replaceable cog than I am now. It's bad enough I have to sign in using a fucking concentration camp serial number.
-
I might have if he didn't make the: "but if we all follow the same style guide, all our code looks identical SO WE ARE REPLACEABLE COGS" argument.
He's right but for the wrong reason. It's good because it makes it easier to pick up someone else's code without having to deal with disparate formatting, etc.
I'm sick of being dehumanized here.
Yes, it sounds like a thoroughly horrible place to work.
-
I might have if he didn't make the: "but if we all follow the same style guide, all our code looks identical SO WE ARE REPLACEABLE COGS" argument.
What, this isn't a common thing in the industry? We hear that around here all the time. Apparently highly-trained software engineers (ok, so I'm not really, I went to an 'accelerated' for profit school and got lucky) aren't doing a job that's any harder than the guys on the manufacturing floor, and we're grossly overpayed to just sit on our butts staring at computer monitors, snapping software legos together. The company could save a lot of money by just laying off the higher paid engineers and bringing in a gaggle of interns. Since we'd have more bodies to throw at the problem, it'd go faster, too! More eyes means less bugs as well. It's a win-win situation!
-
If they ever try that for real, let us know so we can avoid their products and services while they implode.
-
He's right but for the wrong reason. It's good because it makes it easier to pick up someone else's code without having to deal with disparate formatting, etc.
I'd have to see a LOT of evidence of that, I'm not taking it on faith.
In any case, there are "pretty print" tools for T-SQL. Like I said, he can knock himself out. It's the company's code now.
-
I hate to say it, but a lot of company managers really do think this way. I got my start as a an Access coder in a company that paid $15/hr (1995 dollars) for inexperienced programmers because they literally didn't see the point in hiring more experienced people (since it was Access, they may have had a point, but using Access for a commercial product was a WTF all in itself). When I left (whether I quit or was fired was a question of who got the last word in), the owner turned to the graphic designer and said, ' so, how long will it take you to get up to speed programming in Access?" I wish I were kidding.
And for the record, the title of the article really is a direct quote from my old boss. He repeated it several times over the next week, too.
-
I'd have to see a LOT of evidence of that, I'm not taking it on faith.
I see evidence of it every day when I cringe at the way some people around here format stuff. I'm kind of surprised that someone like you doesn't have that even worse.
-
Moved cubes this morning. :( Not going to be as easy to slack-off from this position.
-
Why is the frowny smiley like a "recoil in horror" smiley now? WTF. :( There's no actual frowny face anymore.
-
Because the licensing of this set of emojis doesn't scare Jeff.
-
Right; but what I'm complaining about is that the emotion labeled "frown" isn't a frown. I give no shits for licensing or Atwood.
-
Right; but what I'm complaining about is that the emotion labeled "frown" isn't a frown. I give no shits for licensing or Atwood.
I take no shits from you either. But you wanted to know and that's the actual answer. I guess you can blame it on open artwork or something.
-
The funny thing about working in a company full of fat middle-aged people is they all eat lunch at like 11:30.
-
<- young, thinish, plan to stay that way, eat lunch at 11:30 anyway.
is there anything wrong with that?
-
Yeah it's fucking irritating. I'm still wiping off the breakfast crumbs at 11:30. And the cafeterias here close at fucking 1:00, because why would they stay open longer when everybody eats at 11:30?
-
<- young, thinish, plan to stay that way, eat lunch at 11:30 anyway.
is there anything wrong with that?
Your plan is doomed to fail. But 11:30 lunch time is cool.
-
-
<- Young, thinish, plan to stay that way, doomed to failure on the young part, eat lunch at 11:30
better?
-
-
Why is the frowny smiley like a "recoil in horror" smiley now? WTF. :( There's no actual frowny face anymore.
They're all "walked in on parents getting it on in bedroom" looks now.
-
<- young, thinish, plan to stay that way, eat lunch at 11:30 anyway.
is there anything wrong with that?
Young, thinnish, no choice in the matter, usually eat lunch at 2.
-
I don't understand how anybody who doesn't know what the word "frown" means would decide to make a set of emoji icons.
-
I don't understand how anybody who doesn't know what the word "frown" means would decide to make a set of emoji icons.
You've never been to Germany, then.