Sales employee Bob wants a clickable blue button.

Bob tells product owner Karen about his unstoppable desire for clickable blue buttons.

Karen assigns points for potential and impact (how much does a blue button improve Bob's life, how many people like Bob desire blue buttons)

Karen asks the button team how hard it is to build a button. The button team compares the request to a reference button they've built before, and gives an ease score, with higher score being easier (inverse of scrum points).

These three scores are combined to give a priority score. The global buttonbacklog is sorted by priority.

Once every two weeks (a "sprint") the button team convenes, uses the ease scores to assign scrum points. Difficult tasks are broken up into smaller tasks, because there is a scrum point upper limit. They use the average of the last 5 sprints to calculate each developer's "velocity".

The sprint is filled with tasks, from the top of the global button backlog, up to the team's capacity as determined by velocity. Approximate due dates are assigned, Bob is a happy Bob.

What if boss Peter runs into the office screaming "OUR IMPORTANT CLIENT WANTS A FUCKING PINK BUTTON WHICH MAKES HEARTS APPEAR"?

Devs tell boss to shut the fuck up and talk to Karen. Karen has a carefully curated list of button building tasks sorted by priority, can sedate boss with valium so he calms the fuck down until he can make a case for the impact and potential of his pink button.

Karen might agree that Peter's pink button gets a higher priority than Bob's blue button.

But devs are nocturnal creatures, easily disturbed when approached by humans, their natural rhythms thrown out of balance.

So the sprint is "locked", and Peter's pink button appears at the top of the global backlog, from where it flows into the next sprint.

On rare occasions a sprint is broken open, for example when Karen realizes that all of the end users will commit suicide if they don't have a pink heart-spawning button.

In such an event, Peter must make Bob happy (because Bob is crying that his blue button is delayed). And Peter must make the button team of devs happy.

This usually leads to a ritual involving chocolate or even hardware gift certificates to restore balance to the dev ecosystem.

Wholesome anti-rant.

There’s this Indian chick at work that I really, really do not get along with. Fortunately she’s on a different team so we have practically zero interactions. Her code was always decent, maybe upper junior level? but I went away fuming almost every time we talked.

However, I did a release security review today (I’m down from five/six per month to one) and read through quite a bit of her code. It was clean and easy to read with good separation, clear naming and intentions, nothing was confusing, etc. It was almost beautiful. Had I any emotions I might have shed a tear. I sent her a message and let her know :) I actually learned a better way of doing a couple of things from it.

She has grown so much as a dev.

Password complexity checker for big car rental company is set to insane mode
☑️ 30 char
☑️ symbols
☑️ numbers
☑️ upper & lower
❎ still 'too weak'

1. I join a company.

2. I get deeply involved in "how to run the company", and get nice compliments from both coworkers & management about my skills in conveying startup/scaleup advice & necessities to upper management.

3. With my ego inflated through all the sweet talk, I think "ah, what the hell, let's do this again", and I accept a Lead/CTO promotion. I have to join board meetings, write reports on quarterly plans and progress.

4. I get unhappy/stressed/burned-out because I really just want to be a developer, not a manager/executive.

5. Upper management understands, I give up my lead position, lock myself back into my coding cave.

6. I get annoyed because the requirements I receive become more and more disconnected from reality, half of the teams seem to have decided to stop using agile/scrum, the testing pipeline breaks all the time, I get an updated labor contract from HR by mail which smells like charred flesh, etc

7. The annoyances become too much to do ANY work. I yell at the other devs outside of the entrance of my cave. There is no answer, only a few painful moans and sighs.

8. I emerge from my cave. The city has turned into a desolate wasteland. The office is a burning ruin, the air sharp and heavy with black soot. Disemboweled corpses of developers litter the poisoned soil.

Product Managers dressed in stained ripped suits scream at each other while they try to reinforce concrete barricades with scotch tape and post-its. *THUMP* Something enormous is trying to break through. "Thank God, bittersweet, you're still alive! The stakeholders! They have mutated! We couldn't meet the promised deadlines! We've lost the whole mobile app department, and that kid there is the last of the backenders and he's only an intern! You're here to save us, right? RIGHT?".

In the corner, between the overflowing coffee machine and a withered cactus, a young boy has collapsed onto the floor. His face is covered in moldy coffee grounds, clasping on to his closed macbook for dear life, wide-open eyes staring into the void, mumbling: "didn't backup the database, and It's all gone" over and over.

A severely dented black Tesla with a dragging loose bumper breaks through the dried up vertical herb garden and the smoothiebar, and comes to a halt against the beanbags in a big cloud of styrofoam balls.

The CEO limps out, leaking blood all over the upholstery. He yells to the COO: "The datacenter is completely flooded with sewage! I saved the backup tapes though", holding a large nest of tangled black magnetic tape mixed with clumps of mud above his head.

9. I collect my outstanding salary and sell any rewarded options/shares for a low dumping price, take a 5 month holiday, and ask a recruiter about opportunities in a different city.

*calls grandpa I don't usually talk to that much to congratulate him for his birthday*

*grandpa picks up*

*congratulates*

Him: so, I know that you study CS and I was working on something [Word document at the moment] and my letters keep getting different sizes! Sometimes they're small, sometimes they're big, sometimes they're in between! I have to erase everything everytime because they just get messed up every time!

Me *sighing, but confused because upper-case and lower-case are the same with "big letters" and "small letters", respectively, in my native language: have you checked Caps Lock on your keyboard?

Him: What is that? I have Esc, 1, 2, 3,... (proceeds to read me the keys on the keyboard)

*explains where caps lock is*

Him *gets angry*: no, you don't understand, sometimes they're small, sometimes they're big and sometimes in between! Caps Lock doesn't solve it! *proceeds to read the keys from the keyboard again*

*thinking that maybe it's the font then, asks about the Word version, to know what to point him to*

Him: WHAT? Word? No! I'm using my keyboard! What don't you understand! I explain to you and you have no idea!

Me: well, I'd need then maybe to see the screen

Him: I'm so angry with you, you say you study so much but are not even able to help me with such a small problem. I'll just find someone else. Thanks for your wishes *hangs up*

And this is how I only tried to congratulate my grandfather for his birthday but turned into a "failing" tech support. I just wanted to be a good granddaughter

It finally happened. Upper management is demanding a historical (7+ years) of lines-of-code analysis of our entire code base. They want to justify our positions by validating that the lines-of-code has increased in accordance with the economy. I am not kidding. For every year, they expect some percent increase in our lines of code.

Biggest scaling challenge I've faced?

Around 2006~2007 the business was in double-digit growth thanks to the eCommerce boom and we were struggling to keep up with the demand.

Upper IT management being more hardware focused and always threw more hardware at the problem. At its worst, we had over 25 web servers (back then, those physical tall-rectangle boxes..no rack system yet) and corresponding SQL server for each (replicated from our main sql server)

Then business boomed again and projected the need for 40 servers (20 web servers, 20 sql servers) over the next 5 years. Hardware+software costs (they were going to have to tear down a wall in order to expand the server room) were going to be in the $$ millions.

Even though we were making money, the folks spending it didn't seem to care, but I knew this trajectory was not sustainable, so I started utilizing (this was 2007) WCF services and Microsoft's caching framework Velocity. Started out small, product lookup data (description, price, the simple stuff) and within a month, I was able to demonstrate the web site could scale with less than half of our current hardware infrastructure.

After many political battles (I've ranted about a few of those), the $$ won and even with the current load, we were able to scale back to 5 web servers and 2 sql servers. When the business increased in the double-digits again, and again...we were still the same hardware for almost 5 years. We only had to add another service server when the international side of the business started taking off.

Challenge wasn't the scaling issue, the challenge was dealing with individuals who resisted change.

Product sending an email: Can I confirm feature A is all set for its release on April 30th?

Me: ... what? no that feature is going out with Feature B, that was pushed back to June because of the server issue.

Product: No, the release plan document says April 30th for this.

Me: ... theres 6 copies of this doc now. Someone is after deleting my comments saying "releasing with Feature B". Oh look heres a link to another doc that says this. See Feb14th "Will go out with Feature B". This is because they are touching the same code, we can't separate them now without re-writing it.

*Me to myself*: Ha product are going to hate this, their shitty processes have finally caught up with them.

*next day*

Other manager: So heres my plan for the app release x, y, z.

*Me to myself*: ... his plan? this is my app, I mange this. What the hell is this?

*reads email thread*

*Me to myself*: ... oh so product really didn't like my reply, took me off the thread, sent a response to all the other managers asking for alternatives, CC'ing upper management. The same upper management I had a private conversation with yesterday about how shit our product team are.

*cracks knuckles*

I'm going to enjoy writing this reply.

Last week my company fired 4 people (on top of 15 more over the past few months). This week they silently pushed a change to all of our machines that changed our wallpapers. The wallpaper was a picture of someone in upper management staring at you with wide eyes.

They claimed it was a joke or something but the office didn't see it that way. At best it was incredibly tone deaf and stupid, at worst it was a way to tell employees that they are always watching.

I have no idea how management could be that fucking out of touch.

How do you like my setup? Ubuntu laptop on the left, windows laptop on the right.

(And giant rubber duck upper left 😼)

Day 1 10:00 am
Login to email account (Zimbra)
Your password is incorrect (I entered it correctly, this was a permanent issue ,used to happen in the company with many employees)
Reset your password by logging into internal company portal.

11:00 am
Logged into company portal, somehow. 2 Mbps internet shared among 104 people, you can imagine the speed.
Reset email password
* your password has been sent to your email id*
Are you fucking kidding me? U have emailed me the password to the same email I can't log in to?
Where did the architecture designer get this top notch weed from?

Day 2
Asked HR to reset my password (using a colleague's email)

Day 3
No reply from HR yet

Day 4
I went to meet HR, she's on vacation. So they have 1 person managing the password reset, for 5000 people with no backup person. Cool.

Day 5
Your internal company password has expired. Check your email for link to create new password. This is some next level shit going on.

Day 6
I called up Internal IT team to generate a new email for me.
They asked me to raise a ticket.
I can't raise a ticket because the only way to do so, is through the portal.

Day 7
Nothing. Btw, personal email and all social networks were banned. You can't even open stackoverflow.
And this was a research lab, amazing huh?

Day 8
Loss of pay for 4 days since I can't login to company portal to fill timesheet.

Day 9
HR comes back. Resets my password.
I try to generate my new password for portal.
The password policy:
Password can't be same as last 10 passwords
Passwords expire every week
8 characters minimum, 2 upper case, 2 lower case, NO SPECIAL SYMBOL. WTF. How long do u think its gonna take to crack that?

Fuckers had a company wise policy to automatically lock PC every 1 min if not used. Who the fuck can keep on using it continuously! I'm reading an article, and bam ! Locked. 2 wrong entries and that's it, repeat all steps again. Fuckers really didn't want to let me do my job, just keep on logging in all day.

I'm trying to sign up for insurance benefits at work.

Step 1: Trying to find the website link -- it's non-existent. I don't know where I found it, but I saved it in keepassxc so I wouldn't have to search again. Time wasted: 30 minutes.

Step 2: Trying to log in. Ostensibly, this uses my work account. It does not. Time wasted: 10 minutes.

Step 3: Creating an account. Username and Password requirements are stupid, and the page doesn't show all of them. The username must be /[A-Za-z0-9]{8,60}/. The maximum password length is VARCHAR(20), and must include upper/lower case, number, special symbol, etc. and cannot include "password", repeated charcters, your username, etc. There is also a (required!) hint with /[A-Za-z0-9 ]{8,60}/ validation. Want to type a sentence? better not use any punctuation!

I find it hilarious that both my username and password hint can be three times longer than my actual password -- and can contain the password. Such brilliant security.

My typical username is less than 8 characters. All of my typical password formats are >25 characters. Trying to figure out memorable credentials and figuring out the hidden complexity/validation requirements for all of these and the hint... Time wasted: 30 minutes.

Step 4: Post-login. The website, post-login, does not work in firefox. I assumed it was one of my many ad/tracker/header/etc. blockers, and systematically disabled every one of them. After enabling ad and tracker networks, more and more of the site loaded, but it always failed. After disabling bloody everything, the site still refused to work. Why? It was fetching deeply-nested markup, plus styling and javascript, encoded in xml, via api. And that xml wasn't valid xml (missing root element). The failure wasn't due to blocking a vitally-important ad or tracker (as apparently they're all vital and the site chain-loads them off one another before loading content), it's due to shoddy development and lack of testing. Matches the rest of the site perfectly. Anyway, I eventually managed to get the site to load in Safari, of all browsers, on a different computer. Time wasted: 40 minutes.

Step 5: Contact info. After getting the site to work, I clicked the [Enroll] button. "Please allow about 10 minutes to enroll," it says. I'm up to an hour and 50 minutes by now. The first thing it asks for is contact info, such as email, phone, address, etc. It gives me a warning next to phone, saying I'm not set up for notifications yet. I think that's great. I select "change" next to the email, and try to give it my work email. There are two "preferred" radio buttons, one next to "Work email," one next to "Personal email" -- but there is only one textbox. Fine, I select the "Work" preferred button, sign up for a faux-personal tutanota email for work, and type it in. The site complains that I selected "Work" but only entered a personal email. Seriously serious. Out of curiosity, I select the "change" next to the phone number, and see that it gives me four options (home, work, cell, personal?), but only one set of inputs -- next to personal. Yep. That's amazing. Time spent: 10 minutes.

Step 6: Ranting. I started going through the benefits, realized it would take an hour+ to add dependents, research the various options, pick which benefits I want, etc. I'm already up to two hours by now, so instead I decided to stop and rant about how ridiculous this entire thing is. While typing this up, the site (unsurprisingly) automatically logged me out. Fine, I'll just log in again... and get an error saying my credentials are invalid. Okay... I very carefully type them in again. error: invalid credentials. sajfkasdjf.

Step 7 is going to be: Try to figure out how to log in again. Ugh.

"Please allow about 10 minutes" it said. Where's that facepalm emoji?

But like, seriously. How does someone even build a website THIS bad?

I just nailed an online interview for a job that I’ve been trying to get for ages

However, during the interview my dog just would not stop barking. I told the interviewer that I needed just a second to take care of it, and I got up to put my dog in another room.

Although I had a nice dress shirt on to appear professional, I didn’t think it was necessary to put on dress pants since only my upper half would be on screen, I instead opted for a pair of comfortable green athletic shorts and moccasins. I did not realize until after the interview was over that I had accidentally made a fool of myself by showing my entire outfit while walking to my bedroom door. I bet he will have a good laugh with his colleagues about that one.

Wow... this is the perfect week for this topic.

Thursday, is the most fucked off I’ve ever been at work.

I’ll preface this story by saying that I won’t name names in the public domain to avoid anyone having something to use against me in court. But, I’m all for the freedom of information so please DM if you want to know who I’m talking about.

Yesterday I handed in my resignation, to the company that looked after me for my first 5 years out of university.

Thursday was my breaking point but to understand why I resigned you need a little back story.

I’m a developer for a corporate in a team of 10 or so.

The company that I work for is systemically incompetent and have shown me this without fail over the last 6 months.

For the last year we’ve had a brilliant contracted, AWS Certified developer who writes clean as hell hybrid mobile apps in Ion3, node, couch and a tonne of other up to the minute technologies. Shout out to Morpheus you legend, I know you’re here.

At its core my job as a developer is to develop and get a product into the end users hands.

Morpheus was taking some shit, and coming back to his desk angry as fuck over the last few months... as one of the more experienced devs and someone who gives a fuck I asked him what was up.

He told me, company want their mobile app that he’s developed on internal infrastructure... and that that wasn’t going to work.

Que a week of me validating his opinion, looking through his work and bringing myself up to speed.

I came to the conclusion that he’d done exactly what he was asked to, brilliant Work, clean code, great consideration to performance and UX in his design. He did really well. Crucially, the infrastructure proposed was self-contradicting, it wouldn’t work and if they tried to fudge it in it would barely fucking run.

So I told everyone I had the same opinion as him.

4 months of fucking arguing with internal PMs, managers and the project team go by... me and morpheus are told we’re not on the project.

The breaking point for me came last Wednesday, given no knowledge of the tech, some project fannies said Morpheus should be removed and his contract terminated.

I was up in fucking arms. He’d done everything really well, to see a fellow developer take shit for doing his job better than anyone else in [company] could was soul destroying.

That was the straw on the camels back. We don’t come to work to take shit for doing a good job. We don’t allow our superiors to give people shit in our team when they’re doing nothing but a good job. And you know what: the opinion of the person that knows what they’re talking about is worth 10 times that of the fools who don’t.

My manager told me to hold off, the person supposed to be supporting us told me to stand down. I told him I was going to get the app to the business lead because he fucking loves it and can tell us if there’s anything to change whilst architecture sorts out their outdated fucking ideas.

Stand down James. Do nothing. Don’t do your job. Don’t back Morpheus with his skills and abilities well beyond any of ours. Do nothing.

That was the deciding point for me, I said if Morpheus goes... I go... but then they continued their nonsense, so I’m going anyway.

I made the decision Thursday, and Friday had recruiters chomping at the bit to put the proper “senior” back in my title, and pay me what I’m worth.

The other issues that caused me to see this company in it’s true form:
- I raised a key security issue, documented it, and passed it over to the security team.
- they understood, and told the business users “we cannot use ArcGIS’ mobile apps, they don’t even pretend to be secure”
- the business users are still using the apps going into the GDPR because they don’t understand the ramifications of the decisions they’re making.

I noticed recently that [company] is completely unable to finish a project to time or budget... and that it’s always the developers put to blame.

I also noticed that middle management is in a constant state of flux with reorganisations because in truth the upper managers know they need to sack them.

For me though, it was that developers in [company], the people that know what they’re talking about; are never listened to.

Fuck being resigned to doing a shit job.

Fuck this company. On to one that can do it right.

Morpheus you beautiful bastard I know you’ll be off soon too but I also feel I’ve made a friend for life. “Private cloud” my arse.

Since making the decision Thursday I feel a lot more free, I have open job offers at places that do this well. I have a position of power in the company to demand what I need and get it. And I have the CEO and CTO’s ears perking up because their department is absolutely shocking.

Freedom is a wonderful feeling.

So this shit happened today...

We were asked to implement a functionality on the device that allows it to go to standby mode to save battery power. Once the device enters that state, it can only be woken up by actual bus-network activity, and usually that means connecting a shit-ton of wiring harness and network emulation devices... Before implementing and releasing the device software that does this, we told that fucktard customer how difficult it would be for him to connect to the device without such a setup. He seemed to be fine with it and said rather arrogantly that we should implement the requirement as asked...

Well okay you cock-sucking motherfucker, you'll get exactly what you asked for... We implement the functionality and deliver the software...

Now this pile of shit comes back running his mouth on how the device tears down all its interfaces (to reduce power consumption) and he can't connect to the device anymore.... Well what else were you expecting you dickhead.
To make things worse for me apparently he runs to the manager describing his apparent problem. Both of them come to my desk.. With that fucking Bastard hiding his smugly mug behind the manager's back... He thought he was going to have the upper hand... Well guess what fucked piece of shit, I came prepared... I showed the manager how this was a part of the requirements by throwing that JIRA ID in their faces... The manager seems to understand but this relentless fuck wanted me to implement a "workaround" that would allow him to connect to the device easily... The manager almost had me implement that workaround, when I expose a huge security flaw in doing so. Guess what, now the entire team comes to my desk and start supporting my statement... To make it better they also tell how doing so will violate other requirements...

I've never felt so happy in my entire fucking career, when the entire team stood by me and watched that asshole drag his sorry ass back to his place

Some days I feel like I work in a different universe.

Last night our alerting system sent out a dept. wide email regarding a high number of errors coming from the web site.

Email shows the number of errors and a summary of the error messages.

Ex. 60 errors
59 Object reference not set to an instance of an object
1 The remote server returned an unexpected response: (413) Request Entity Too Large

Web team responds to the email..

"Order processing team's service is returning a 413 error. I'll fill out a corrective action ticket in the morning to address that error in their service. "

Those tickets are taken pretty seriously by upper mgmt, so I thought someone on the order processing team would point out the 1 error vs. 59 (coming from the web team's code).

Two hours go by, nobody responds, so I decide to jump into something that was none of my business.

"Am I missing something? Can everyone see the 59 null reference exceptions? The 413 exception only occurred once. It was the null reference exceptions that triggered the alert. Looking back at the logs, the site has been bleeding null reference exceptions for hours. Not enough for an alert, but there appears to be a bug that needs to be looked into."

After a dept. managers meeting this morning:

MyBoss: "Whoa..you kicked the hornets nest with your response last night."
Me: "Good. What happened?"
<Dan dept VP, Jake web dept mgr>
MyBoss: "Dan asked Jake if they were going to fix the null reference exceptions and Jake got pissed. Said the null reference errors were caused by the 413 error."
Me: "How does he know that? They don't log any stack traces. I don't think those two systems don't even talk to one another."
<boss laughs>
MyBoss:"That's what Dan asked!..oh..then Jake started in on the alert thresholds were too low, and we need to look into fixing your alerting code."
Me: "What!? Good Lord, tell me you chimed in."
MyBoss: "Didn't have to. Dan starting laughing and said there better be a ticket submitted on their service within the next hour. Then Jake walked out of the meeting. Oh boy, he was pissed."
Me: "I don't understand how they operate over there. It's a different universe.
MyBoss: "Since the alert was for their system, nobody looked at the details. I know I didn't. If you didn't respond pointing out the real problem, they would have passed the buck to the other team and wasted hours chasing a non-existent problem. Now they have to take resources away from their main project and answer to the VP for the delay. I'm sure they are prefixing your name right now with 'that asshole'"
Me: "Not the first, won't be the last."

Walked into the office in the afternoon, everyone was kinda panicking
Asked what was going on, well, the ticket system is not working anymore, can't put in any new tickets.
So I started to look for the issue as well, checked the system and... The last tickets' IDs were at ~32k. Ha. Looked into the source code and, sure enough, they used a data type with an upper limit of... 32k. So when trying to get a new ticket ID it just crashed and burned.
Quickly changed the data type and stopped the office panic in around half an hour.
Memorable not because of how tough the bug was, but because of the impact and the simplicity of the fix

My stickers just arrived. And I especially love the encoding of “ß” within the street name.

German. It's hard.

Next time, just use upper letter and replaced “ß” with “SS” or just use a “B”. The B is especially fine to drive typographers mad.

!!rant

When I worked at a previous job, they only gave out decent titles (and salaries) to upper management. Everyone else... well... I was the Domain/Sysadmin, responsible for the domain and both DCs, upgrading the physical network (plus recabling it: the MDF was a *disaster*), as well as all backups, migrations, printers, servers, and workstations/lappys in the building, plus pushing software, antivirus, updates, security policies, etc. I had complete access to everything, and ofc was responsible for everything. Nothing on my network caused anyone (else) any trouble except one particular printer I wasn't able to replace. Also, nothing new appeared on my network without me noticing and tracking it down.

But my official title? "IT Assistant".
I made $11/hr.

Worth it? Take a flying leap into an overflowing outhouse during the height of a Vegas summer if you even begin to think so.

I eventually managed to switch to a developer position, and (after several attempts) got a ~$5/hr raise. The girl they replaced me with in IT with some ditz who had never installed an OS before, didn't know what the BIOS was, and couldn't figure out why a monitor... plugged into itself... wasn't working. Things went downhill from there.

Two thousand fucking eighteen people!!!!
Stop this non sense "get a plane" for a fucking meeting that could be a fucking video conference.

Wtf? Everyone here seems to be addicted to flying, specially upper management... And if we need a new switch to keep the network running? Oh, for that we have no money :)

This is my most ridiculous meeting in my long career. The crazy thing is I have witnessed this scenario play out many times during my career. Sometimes it sits in waiting for a few years but then BOOM there it is again and again. In each case the person that fell into the insidious trap was smart and savvy but somehow it just happened. The outcomes were really embarrassing and in some cases career damaging. Other times, it was sort of humorous. I could see this happening to me and I never want it to happen to you.

Once upon a time in a land not so far away there was a Kickoff Meeting for an offsite work area recovery exercise being planned for our Oklahoma locations. Eleven Oklahoma high ranking senior executives were on this webinar plus three Enterprise IT Directors (Ellen, Jim and Bob) who would support the business from the systems side throughout the exercise.

The plan was for Sam Otto, our Midwest Director of Business Continuity to host this webinar. Sam had hands-on experience recovering to our third party recovery site vendor and he always did a great job. He motivated people to attend the exercise with the coolest breakfasts and lunches you could imagine. Donuts, bagels, pizza, wings, scrumptious salads, sandwiches, beverages and desserts. He was great with people and made it a lot of fun.

At the last minute Charles 'Don't Call Me Charlie' Ego-Smith, the Global Business Continuity Senior Vice President, decided to grand-stand Sam. He demanded the reins to the webinar. Pulled a last-minute power-play and made himself the host and presenter. You have probably seen the move at some point in your career. I guess the old saying, 'be careful what you wish for' has some truth to it - read on and let me know if you devRanters agree...

So, Charlie, I mean Charles, begins hosting the session and greets all of the attendees. Hey, good so far! He starts showing some slides in the PowerPoint presentation and he fields a few questions, comments and requests from the Oklahoma executives. The usual easy to handle requests such as, 'what if we are too busy to do recover all systems', 'what if we recover all of our processes from home', 'what if we have high profile visitors that month?' Hey you can't blame them for trying. You are probably thinking to yourself, 'been there - heard that!' But luckily our experienced team had anticipated the push-back. Fortunately, Senior Management 'had our backs' and committed that all processes and systems must participate and test - so these were just softball requests, 'easy-peasy' to handle. But wait, we are just getting started!

Now the fireworks begin. Bob, one if the Enterprise IT directors started asking a bunch of questions. Well, Charles had somewhat of a history with Bob from previous exercises and did not take kindly to Bob's string of questions. Charles started getting defensive and while Bob was speaking Charles started IM'ing. He's firing off one filthy message after another to me and our teammate Sam.

'This idiot Bob is the biggest pain in the ass that I ever worked with'; 'he doesn't know shit', 'he never shuts the f up', 'I wanna go over to his office and kick his f'in ass...!'

Unfortunately...the idiot Charles had control of the webinar and was sharing his screen so every message he sent was seen by all of the attendees! Yeah, everyone including Bob and the Senior Oklahoma executives! We could not instant message him to stop as everyone would have seen our warnings, so we tried to call Charles' cell phone and text him but he did not pick up. He just kept firing ridiculously embarrassing dirty IM messages and I guess we were all so stunned we just sat there bewildered. We finally bit the bullet and IM'ed him to STOP ALREADY!!! Whoa, talk about an embarrassing silence!

I really felt sorry for Bob. He is a good guy. Deservedly, Charlie 'Yes I am going to call you CHARLIE' got in big time hot water after the webinar with upper management. For one reason or another he only lasted another year or so at our company. Maybe this event played a part in his demise.

So, the morale is, if you use IM - turn it off during a webinar if you are the host. If you must use it, be really careful what you say, who you say it to and pray nothing embarrassing or personal is sent to you for everyone to see.

Quick Update - During the past couple of months I participated on many webinars with enterprise software vendors trying to sell me expensive solutions. Most of the vendors had their IM going while doing webinars and training. Some very embarrassing things came flying across our screens. You learn a lot reading those messages when they pop-up on the presenters' screen, both personal and business related. Some even complaints from customers!

My advice to employees and vendors is to sign-out of IM before hosting a webinar. Otherwise, it just might destroy your credibility and possibly your career.

My teams current process is:

1) Asked by product to create “T-Shirt size” estimates, also known as a WAG (wild ass guess). The process is the mental equivalent of throwing darts while blindfolded, after being spun around in a circle and pointed in the wrong direction.

2) Product make firm commitments to upper management based off these. Ensuring them that all these features will make it out in Q2.

3) 4 days before Q2 starts, product ask engineering to figure out the real estimates based off no concrete information what so ever.

4) 4 Weeks into Q2, product provide the missing information.

5) Engineering inform product that the estimates are out by a factor of 1.5 - 3 times the original estimates.

6) Product sends angry email to upper management that through not fault of product, engineering are unable to meet the deadlines.

7) Everyone shout and complain until 1 week before Q3, then see point 1.

Following this process, you and your team can be just as delightful as me.

That’s the practiseSafeHex guarantee!

My start at one of the Big Four (accounting firms).

The first two days of each month they organise "onboarding days" for the new starters of that month. (I so hate upper management buzzwords!) They sent me a formal invitation that looked like I was being invited to a ball with the royals, and they included the following super-smarty-pants line: "Dress code: would you wear jeans and t-shirt when you meet a client?"

And I thought: "I'm an effing hardware and software engineer for internal services. I will never meet a client." But I dressed formally nonetheless, and I went to the onboarding, and I hated every second I spent in those effing high heels, and don't get me started on how I managed to get a run on my stockings in the first hour.

The first day of the onboarding we sat through eight hours of general talks from senior employees who wanted to explain the "culture" and "values" of our company, but the worst of all was the three-hour introduction to IT services where they "helped us set up our new laptops" and taught us how to send e-mails and how to use the Company Portal.

On the second day, they divided us into groups depending on our speciality (assurance, taxes, legal, etc) and exposed us to further 8 hours of boredom related to our speciality. However, since the "digital services" thing was still new to them, we didn't have a category of our own, and we had to attend the introduction to one of the other categories, and I didn't understand one word of what was being said.

On the third day I finally went to my office and they provided me with a second laptop. It turns out that we engineers got different laptops and were allowed to manage it ourselves instead of letting central IT manage it for us. So I simply returned the laptop they had given me the first day and started working. However, for some reason, the laptop I returned was not registered, and two weeks later they started pestering me with emails asking where was the laptop "I had stolen". It took me 3 weeks of emails and calls to make them understand that I had returned the laptop immediately.

Also, on the two onboarding days we had to sign attendance, and since I forgot to sign the paper list on the second day, they invited me to the event the next month again. I explained to them that I had already attended the onboarding and didn't go, so they invited me again on the third month, and they threatened me with "disciplinary action" if I didn't go. After a week of lost time writing emails and calling people, I ended up going to the onboarding again just to sign the effing list.

In the end, I resigned during the probation time. That company was the worst experience of my life. It was an example of corporate culture so absurdly exaggerated that it sometimes reminded me of Kafka's Trial. I think they have more "HR representatives" than people who do actual work.

>Upper management personal hands me a paper.
>"Can you make some copies of this for me?"
>"Why?"
>"You work in IT."

I want to vomit everytime rich people in upper management says stupid shit like "working for money in this company is a sin. Work for higher reason"

Hello, if only I get paid as much as you earn just by talking random nonsense in every meeting, I would be glad sharing the same shit quote like that to other employees in the company.

So that coworker of mine who got promoted to manager keeps continuing on abusing her new power. She convinced upper management to implement a new policy where you would be disqualified from your monthly performance incentives if you take 2 total sick days a month. She says this is to reduce the number of sick days people take, which of course upper management loved hearing.

By the way, since she's a manager now, this particular policy doesn't affect her - it only applies to us in the trenches. She can still take as many sick days as she wants, since being a manager she can work from home.

Needless to say, save for a couple of suck-ups, she's lost a lot of friends and made a number of enemies in our department, particularly on our dev team.

If your manager asks for a "rough time estimate" for a project, there is a higher than 99% chance that your answer will be written down and be used in presentations of project roadmap to upper management and/or marketing, who will create a hard deadline based on your rough estimate and communicate this to customers/clients, and then blame you for not keeping the deadline when it turns out (as it always does) that the rough estimate was off by several months because feature creep caused by upper management.

Some dude in upper management: We hear you. We have too many meetings, it's not healthy. From now on we'll have meeting free Friday morning!!!

And then all meetings on Friday morning are re-scheduled on Friday afternoon, or Thursday afternoon.

Yeah this really works, genius!

So the company I work for had a critical project they needed done in 8 days.
We told our boss it wasn't possible because of the scope of the project but he went on with motivational speeches about how anything is possible. So he hired 12 devs for 8 days.
The scope of the project is already big enough but everyday upper management either add 10 new features, modify 2, or delete some already.
We basically sleep 2 hours a day and today is the last day. 5 minutes ago we just had a meeting that we're supposed to change a core feature. We don't even have a stable system yet and everyone is fucking pissed.

how to be a man in upper management:
-come into meetings without any context and talk over everyone
-say very obvious and broad things to seem like you're mentoring the team
-waste time

Lets have a moment of silence for the devs who created IE and Edge.

I'm sure many who worked on them are great devs and at one point were very proud and inspired by their work but upper management ultimately fucked everything up. The IE guys have since been ridiculed and the Edge devs had to create a peice of software that they knew was destined to be one of the most critically reviewed and ridiculed releases ever.

My heart goes out to all of you and we would love to hear your rants. Your welcome here anytime.

Don't you just love it when upper Management people that never wrote a line of code in their life tell you, the software engineer peasant, to refactor all of your projects with Inclusive Terminology?

I mean I'll do it, the company is just protecting their image and money... But I blame the sick mind that came up with this in the first place.... It's implying that all sofware engineers are somehow racist and sexist and I'm somewhat offended by that notion. Whoever started this trend should seriously burn in hell.

P. S.
Apparently "the elderly" is also non-inclusive and should be referred to as "older adult"... What the fuck?

Do you not realize that you're just disassembling words and nothing else? Also "AIDS patient" should be referred to as "person living with AIDS"... Ok? Same fucking thing? If not even worse? At least "patient" kinda invokes that professional help is given... A person living with AIDS just implies you're infected and seeking no help...

You help no one with this non-issue bullshit. All your replacements will be deemed outdated and non-inclusive in the next 5 years again... Fucking hell... Waste of time and money

Just wrote a brute-force attack simulation in c. Going to run it on actual hardware, with an 8-character limit, including alphabet (Upper and lower case), 0-9 and a few special characters and see if it gets done tonight ;)

I'll see you all in about 360 trillion operations.

<Email thread>

Manager: Hey @iiii, please, create stories for {things that shall be done}. You will be responsible for that implementation next sprint.

Me: *procrastinating like a bitch*

**several hours later**

Dev from another team: Actually, we discussed that with {upper management guy} and it seems like those things are unapplicable for current project, so we'll send a letter to {client} to remove those requirements.

Manager: @iiii, don't create stories.

</Email thread>

Me: *welp, good thing I did exactly nothing so far*

"WTH! Get the fuck out of here, bitch!!".

I started a new job today (remote) and my first task was to improve product sign-up process, basically the UX is shit and the backend is even worse, never felt so bad looking at terrible software design my entire life and career. My first assignment was to introduce some sanity. (Mr. Supervisor's exact words)

Anyway, I report directly to upper management but need to get onboarded by current technology expert who's highly skilled at writing shitty code and is also stupid, literally.

It took the whole day to get him to grant access to the private repo in order to start working but that's not the story.

So, I'm seated, demoralised about the structure of software I have to work on and here I was refreshing localhost:7878 consistently and was consistently getting the message:
"WTH! Get the fuck out of here, bitch!!".

So, this same codebase I have is suppose to be the exact same one that's powering the app in production. I was furious and confused. Is stupid calling me a bitch already??? He wants to fuck??? What the hell!!!

I called him and turns out, I was suppose to switch branches. The branch I had was suppose to show that message intentionally (??!???!???) (His words exactly), I couldn't even muster the words "Why" completely before he hung up.

So basically, I got onboarded today. Quite successfully, I must add, because I know exactly the battlesuit I have to wear to my new remote job going forward!

I'm not sure whether to cry or to burn everything to the ground.
I'm stuck in a rotten, over aged corporate that will one day choke on all the documents and formalism they require. Which is something I'm generally fine with. Each to their own.
But ever since I handed in my resignation they have been fucking me like I have never been gang raped before.
(A little context: I work for a midsize financial institute. Which at least in Germany are full of legacy projects and are regulated as all hell.)
So some fuckwits decided that since the regulator slapped us hard 2 years ago that we need to make up a new standard of documentation that has to be used for all IT-documentation there ever was and ever will be.
So the upper management (the before mention dumb-dumbs) choose some consultant company and locked them up together with the brightest stars (read biggest slime balls) of the IT department in an ivory tower and told them to pull some out the ass.
And one year later (early November last year) they got the shit they ordered. Gilden shit, only the most sparkly and non-sensical bullcrap you could imagine.
But they only looked at it and deemed it good. Now the guys actually in charge of the the applications got served the dish. And guess what they found out when started to dig into? Nothing but contradictions, non-final thoughts and all of that held together by web of retarded, unusable guidelines. But they ate it, they cursed but they swallowed forced by disciplinary punishments waiting should they misbehave.
The only one emerging fact was: All previous documentation was completely invalidated.
But now the mighty lords in the ivory tower guided by the never failing hand of the higher management had the greatest idea of them all. They needed someone to check all the documentation till the end of this year but since they blew all of their budget on useless wankers ( oh, ofc I meant "highly qualified external help") they now preyed on the lowest in the food chain. Which is where this story goes full circle and comes back to me.
I was the lowest rank on the food chain, a student that just handed in his resignation.
I was the first to be locked up in the basement, my co-student followed shortly after.
And now I'm going to spend my last 2 months looking at checklists that we had to pull out of the slime's ass and validating hundreds of thousands of pages of documentation. We get grinded up in the endless hate coming from the guys that we need to tease and are held in position by a wall of sheer idiocy on the side of the rule makers.
Today I cried when I had to tell someone that his magnificent documentation was not standard conform and had thus no longer any meaning or right to exist.
Thanks you for those that made it this far down. I hope you never have to feel my pain.

When someone writes class names lowercase and methods uppercase in Java.

Fucking windows! I am so fucking done with this microsoft bullshit!

Hear me out here, i am a gamer. I need windows because it has the games (and software to aid those games) unlike any other platform. But windows 10 is basically already phishing andmalware at this point. I stuck to win 7 because it had a start menu and didn't totally drive me up the wall.

Just a short list of their bullshits: ads in the explorer window, ads in your taskbar reminders, data mining like it is nobodies business and trying to hide it, sharing my wifi access with friends (wtf), the fucking retarded new start menu, the crappy fullscreen apps which have less functionality than the actual proper desktop applications that you need to config what you want, and even then pushing multiple updates that simply broke peoples pc's. Fuck that, ill stick to 7.

They are making win10 worse by the week making it unlikely i will ever join that hell, and they are also aiming to force me there. Making windows store exclusives and dx12 only games. What am i supposed to do against that?! The current releases don't bother me much but fuck i figure it is a matter of time until the newest katamari game is their exclusive and i nanananana katamari damacy all over their platform.

And well all alternative os's are just out of the question unless vulkan rendering gets the upper hand. Then i'd switch to whatever stable distro and learn about our new penguin based overlords languages.

For now i will just stick to win7, suck on my thumb while in fetal position and hope it just all goes away.

Company upper management was asked of any plans for supporting businesses in the metaverse.

They said they want to focus on bussiness in the real world.

Absolute chads.

After 2 years of being forced into writing PHP 5.5, we've finally convinced upper management to let us switch to C# instead. It's coming in a few weeks. Words cannot describe how much I hate this god awful language.... C#, save me my sweet, sweet, strictly typed goodness.

FUCK LINUX

now that I have your attention, and you’re probably angry, too, please, even if you don’t read this rant, never use code.org again. now, onto the rant…

god dammit, code.org sucks. I mean, anyone who created it or associates with it should, well, be considered a terrorist. they’re bombing students futures in computer science with false, useless, bullshit information. not to mention, their sponsors like bill gates, mark zuckerburg, and other rich asses, talk in a video about some boring ass shit that is hard to understand for anyone who doesn’t program, and not to mention, they use a fucking five dollar microphone. ear rape. even if you look at a textual version of it, then read the information on it, it’s practically useless because it's so terribly explained, and also useless. ironically enough, they focus on their animations more than their actual explinations, or their students for that matter. the fact that we had to encode a picture in binary, made me about 50% dumber, give or take a 0 or 1. then, we had to do it in hex, which wasn’t really much better, although more realistic I supposed. what's really the most depressing thing about this class is its application in the real world. I've learnt nothing whatsoever that will help me in the real world, or in computer science. I suppose there's two things that may be useful (that I already knew): hex, and that TCP doesn't lose packets. that's it. those two things. five seconds worth of knowledge from the first quarter of the year. the ideas just make me want to throw up. teaching the main ideas of computer science without actually teaching it? one of the teachers (probably a good one) enrolled her students in an online programming course just so they could understand, because the explanations are just so terrible. this is the only [high school] computer science course offered by code.org, and I signed up because it's an AP computer science class (tried to get into AP Java, the day I was supposed to take the test to get into an upper level class, I was told it didn't count as a tech credit). seriously, fuck code.org. it makes you dumber. their 'app lab' environment is pointless, just like everything else. the app lab is basically where you have a set of commands and have to make a dog bark() or a storm trooper miss() [and that's hell when they haven't introduced while loops yet]. the app lab is literally code.org going out of their way to make everything that their students are learning pointless in the real world. seriously, why can't we just use a <canvas> like an ACTUAL PROGRAMMER would do if they were to make a browser game, not use an app engine so slow it would be faster to update windows and android studio each time I run an 'app' in their 'environment'. their excuse is that the skills "transfer over" to the real world. BITCH! IF I DIDN'T KNOW JAVA, AND I WANTED TO MAKE A GAME IN JAVA, I'M NOT GOING TO LEARN PYTHON, THEN "TRANSFER" THE SKILLS I LEARNT, I'M GOING TO LEARN FUCKING JAVA. AND THAT GOES FOR EVER OTHER LANGUAGE, PROJECT, ETC.

I'm begging you code.org, stop, get help.

I know I am late to this but I have a happy story for this one.

My first dev job was awesome. Except for the pay. I had interviewed and taken the job based on the fact that I was done with my master's degree, but because of a paperwork snafu I wouldn't be receiving my degree until the spring. I was assured that if I provided proof of my degree when it was awarded I would get a pay rise in relation to my education. Well that was not to be. So this professionally and socially inept bitch I was working with was going to be ahead of me in her career because the people I worked for gave pay raises based on time served rather than ability and education.
So I started interviewing for other positions. Especially after government furloughs cut my pay by 20% for 11 weeks, causing me to max out my credit cards. All of my coworkers had my back. They went to the upper management and the higher ranking military people we worked for and explained the situation. They were my job references for my interviews. They got me a job that paid double what I was making. I still get the warm fuzzies thinking about it.
They were some of the sweetest people I had ever worked with. One of them gave my mom and brother a ride to the airport when I crashed my car. They bought me lunch when I was in dire straights. I really would have loved to stay but I couldn't afford it. That and winter in Utah fucking blows.

Having remote meetings home means that I just have clothes on the upper part.

When I get on a site that is like “your password must contain upper case, lower case, a number, a symbol”, at first I’m like ooook, security I guess I’ll generate a long password, but then they sit there and say “and be at least 6 but not more than 10 characters”

WTF you fuckers really don’t know anything do you.

i'm feeling so sick right now.

PM invited team for today to present his "vision": "<name of our component>: what it is and what it is not".
but it didn't make sense and showed that he hadn't understood the problem at all. the whole architecture made no sense given the problems that shall be solved. his architecture diagrams missed some essential parts that were actually the giant weak points of his concept. his pseudocode, that should exemplify interactions between components, didn't address the complexity of required interactions at all. it's like he expects some magic to happen and has no fucking clue about the requirements (but acts like it), even though he is the manager of this software project.
and when devs ask really interesting questions that fundamentally question his concept, discussions lead to nowhere and questions are not answered. at some point he literally said "there is no such thing as <name of our component>, i still have to find this out"
really!? after one and a half year, since you sold the idea for this component to upper management, and after half a year of development, you still can't tell what it is what we actually want to build? are you fucking serious?!

at some point in discussion he said that these questions need to be answered but that "there's no time left", and he ended the meeting. although there was still half an hour of meeting time left.

i'm so fucking sick of this, i hate everything right now. i can't listen to this bullshit any longer. in discussions, he contradicts himself all the time, it is so fucking surreal i'm starting to feel like i'm insane.

it makes me really sad and tired. i don't want to care about this shit any longer.

New password cannot be one of your four previous passwords.
Password must conatin upper and lower case characters, at least two numbers and two special characters
Password cannot contain five or more consecutive letters of username.
Password cannot include any _illegal patterns_.

Locked out of your system? Drive over to HQ and ask the admins to reset your password in person.

Funniest meeting ever!

Some years ago, there was the regular department meeting where useless news from upper management were handed down. The team I was in was also there: team lead, co-worker and me. The team lead had a new girl and was daydreaming of their nights, my co-worker wasn't quite back from the football match on the weekend, and I was playing chess on my mobile.

Department lead was blah blah blah and when can we do this on your rig? We looked at each other and instantly realised that none had been paying attention.

My co-worker was the fastest to recover and straight-facedly turned to me: "Well Fast-Nop, that's your domain."

I picked the ball up before team lead could say something: "Sure, but schedule appointment is for our lead."

Our lead couldn't contradict us and then had to negotiate a schedule while trying to find out what it was about. *LOL*

Our team makes a software in Java and because of technical reasons we require 1GB of memory for the JVM (with the Xmx switch).
If you don't have enough free memory the app without any sign just exits because the JVM just couldn't bite big enough from the memory.
Many days later and you just stand there without a clue as to why the launcher does nothing.
Then you remember this constraint and start to close every memory heavy app you can think of. (I'm looking at you Chrome) No matter how important those spreadsheets or illustrator files. Congratulation you just freed up 4GB of memory, things should work now! WRONG!
But why you might ask. You see we are using 32-bit version of java because someone in upper management decided that it should run on any machine (even if we only test it on win 7 and high sierra) and 32 is smaller than 64 so it must be downwards compatible! we should use it! Yes, in 2019 we use 32-bit java because some lunatic might want to run our software on a Windows XP 32-bit OS. But why is this so much of a problem?
Well.. the 32-bit version of Java requires CONTIGUOUS FREE SPACE IN MEMORY TO EVEN START... AND WE ARE REQUESTING ONE GIGABYTE!!
So you can shove your swap and closed applications up your ass but I bet you that you won't get 1GB contiguous memory that way!
Now there will be a meeting about this issue and another related to the issues with 32-bit JVM tomorrow. The only problem is that this issue only occures if you used up most of your memory and then try to open our software. So upper management will probably deem this issue minor and won't allow us to upgrade to 64-bit... in 20fucking19

Wow, I'm going to have a hard time remembering this one.

IT have changed after so many years the password criteria for our machines, to the point it's a bit ridiculous.

Like I'm all for securing your accounts and using random passwords but, this is rough.

Minimum of 14 chars
Not the past 6 passwords
Must contain several %}*]=[^{
Must contains numbers
Must contain upper case letters
Must contain Lower case letters
Must not end in a number
Must sacrifice a virgin on every login
Must be changed every 30 days

Don't you hate it when your co-worker does dumb things, but thinks it's the "clean code" way?
The following is a conversation between me and a co-worker, who thinks he's superior to everyone because he thinks he's the only one who read the Clean Code series. Let's call him Bill.

Me: I think the feature we need is quite simple, our application needs to call this third party API, parse the response and pass it to the next step. Why do you need to bury everything under an abstraction of 4 layers?
Bill: bEcAuSe It'S dEcOuPlInG, aNd MaKe ThE cOdE tEsTaBlE
Me: I don't know man, you only need to abstract the third party api client, and then mock it if you want. Some interfaces you define makes no sense at all. For example, this interface only has 1 concrete implementation, and I don't think it will ever have another. Besides, the concrete implementation only gets the input from the upper layer and passes it down the lower layer. Why the extra step? I feel like you're using interface just for the sake of interface.
Bill: PrOgRaMmInG tO iNtErFaCe, NoT cOnCrEtE iPlEmEnTaTiOn!!!
Me: You keep saying those words, I don't think they mean what you think they mean. But they certainly do not mean that every method argument must be an interface
Bill: BuT uNcLe BoB blah blah blah...
Me: *gives up all hope*

Sports commenter at AI vs AI deathmatches.
It would probably go like this:

- UltimateGod the Second launches half of the US nuclear missiles to NorthernEurope!
I guess that's it for the poor bugger.

- WankerBot69 tries to delay its doom by channeling old 4chan archives into a devastating ddos attack. UGtS' logic processe go down for a few nanoseconds... Ugh, that's NASTY! It doesn't even have a mother

- Missiles still going up. Looks like UGtS confused the imperial and metric system just like its predecessor.

- WB69 is now has the upper hand. It just used a SMB exploit and is bow encrypting UGtS's storage.

- UGtS is down. We all hope UltimateGod the third will do better. For now, all hail our catevolent overlord WankerBot69.

- See you next time on Bot Armaggedon folks!

Our company maneuvered themselves into a classic technical debt situation with a project of a second team of devs.

They then left, signing a maintenance contract and now barely work on the project for exorbitant amounts of money.

Of course management got the idea to hand off the project to the first team, i.e. our team, even though we are not experts in that field and not familiar with the tech stack.

So after some time they have asked for estimates on when we think we are able to implement new features for the project and whom we need to hire to do so. They estimates returned are in the magnitude of years, even with specialists and reality is currently hitting management hard.

Code is undocumented, there are several databases, several frontends and (sometimes) interfaces between these which are all heavily woven into one another. A build is impossible, because only the previous devs had a working setup on their machines, as over time packages were not updated and they just added local changes to keep going. A lot of shit does not conform to any practices, it's just, "ohh yeah, you have to go into that file and delete that line and then in that other file change that hardcoded credential". A core platform is end of life and can be broken completely by one of the many frameworks it uses. In short, all knowledge is stowed away in the head of those devs and the codebase is a technical-debt-ridden pile of garbage.

Frankly I am not even sure whom I am more mad at. Management has fucked up hard. They let people go until "they reached a critical mass" of crucial employees. Only they were at critical mass when they started making the jobs for team 2 unappealing and did not realize that - because how could they, they are not qualified to judge who is crucial.

However the dev team behaved also like shitbags. They managed the whole project for years now and they a) actively excluded other devs from their project even though it was required by management, b) left the codebase in a catastrophic state and mentioned, "well we were always stuffed with work, there was no time for maintenance and documentation".

Hey assholes. You were the managers on that project. Upper management has no qualification to understand technical debt. They kept asking for features and you kept saying yes and hastily slapped them into the codebase, instead of giving proper time estimates which account for code quality, tests, reviews and documentation.

In the end team #2 was treated badly, so I kinda get their side. But up until the management change, which is relatively recent, they had a fantastic management who absolutely had let them take the time to account for quality when delivering features - and yet the code base looks like a river of diarrhea.

Frankly, fuck those guys.

Our management and our PM remain great and the team is amazing. A couple of days a week we are now looking at this horrible mess of a codebase and try to decide of whom to hire in order to help make it any less broken. At least it seems management accepted this reality, because they now have hired personnel qualified to understand technical details and because we did a technical analysis to provide those details.

Let's see how this whole thing goes.

While testing on IE11 today I noticed a smiley face in the upper left corner that brings up a context menu with the options "Send a smile" and "Send a frown".

Turns out that is how you send browser feedback on IE11, the frown being the ability to report a site, and the smile to give positive feedback on the browser.

Turns out you can't send negative feedback for the browser, so I sent positive feedback. What did it say?

"What did you like?"
- How fast google chrome downloaded.

Customer: can you set my forgotten password to "1"?

Me: there's a six signs limit in your domain. You have to use upper case letters, lower case letters and at least one symbol

Customer: "123Aa+"?

We have to set such passwords to avoid customers cancelling contracts....

Obvious wisdom from me;
1. HR is not your friend. HR is created to protect companies from employees, not to protect employees from companies. HR serve the company and upper level management.
2. If you are victim of mobbing, keep a mobbing diary with exact quoting. Nothing more, nothing less, no speculation. Create an airtight case for future.
3. If you want to change because of mobbing, just find a new job. Do not, I repeat, DO NOT talk to HR about mobbing before you got another job offer at the ready.
4. Present HR with mobbing diary during your exit, imply that you will talk to CEO and take legal actions if you don't get a satisfactory last laugh on the mobber.
5. Do not accept counter-offer from your company-regardless of mobbing case or not. You considered switching to another company, you are branded now and you will be axed at the first chance. Counter-offer is not a guaranteed employment in your company.

GF: How was your pitch to investors?
Me: it was great (... went-ahead to talk about the daunting process of the preparation and motivation).
GF: Why do you go through all this process, when you can become a fraudster, you can use voodoo and make it even easier, in less than 3 months you can buy a duplex, nice car and we can go shopping... you don't need to do any human ritual unlike before - I heard you can even meet a chief priest to make it faster for you.
just get the bag abeg (slang for getting rich quick).

Me: Fuck the day I met you, not everyone wants to be a low-life, and fuck out from my life.

Men if you live in a saner society, or you are born to elite/upper-middle-class you don't how lucky you are.
Most times I wonder how I keep my sanity with all these shitty people around. like messed up society where almost everyone is a fucking deep hypocrite
.I know I need to change my circle but how the fuck do I do that when I am surrounded by fuckstards, which are far worst than Gypsies.
lowlifes with low dreams.
I need to get the fuck out of this place!

Microsoft seriously hates security, first they do enforce an numer, upper and lowercase combined with a special character.
But then they allow no passwords longer than 16 characters....
After that they complain that "FuckMicrosoft!1" is a password they've seen to often, gee thanks for the brute force tips.

To add insult to injury the first displayed "tip" take a look at the attached image.

So a little story about finding your way. I worked at an IoT software firm, very well established. I had a hard time with the on boarding process due to some factors, and I must have lagged behind their mental schedule for my growth. It was clear nonetheless that I was a quality coder and had made some friends there.

It wasn’t enough for the ensuing corporate bullying. It went by and I took it. I became the yes man just so I don’t frustrate anyone enough to turn away my ask for help. This made things worse and before long, I a grown man went to visit my mum and all but cry at how small I felt, after all my hard work getting to the company.

I felt sick with failure but I knew I couldn’t go back. I emailed my resignation and dropped off my company laptop.

4 months later I am working at a medical startup with my own projects, that I have 100% control over. And the quality of my work and ethic is pleasing upper management in all the right ways. I’ve never been happier, and there are barely any perks on paper. No free lunches on Thursdays or discounts at the local high street. I’m the happiest I’ve ever been in my life because I said NO to feeling or being treated any less than I worked and progressed to be.

Don’t let other people stop your potential for their own ego, or any other reason. 😊

Mother fucking cunts should be shot into the sun...

It's worse enough when you have to deal with many things at once...

But how the fuck can 3 people from 3 different teams have the same bullshit idea to disturb a meeting and just start talking like it's the most normal thing.

YEAH. INTERRUPTING MEETING AND JUST BLABBERING ON AND ON...

Then fucking laughing how funny it is.

Upper management found it absolutely not funny.

Working from home prevented a mass murder today.

I shaved half my beard off. I just had a meeting with a recruiter and he told me I might get problems with upper management (CEOs for example) in Switzerland because they are still very conservative and they'll be interviewing me. Why would that matter!? Either I get the job done or I don't, why the hell does it make a difference if I like to stick out in a crowd with a unique cool beard!?

I just want to share my very first companion. Haha... This is btw my laptop way back 2011, used it to store highschool memories and silly stuff, if you know what I mean. This is the laptop that I first used the labrynth of directories such as A folder contains A to z Folder and again inside one of those contains A to z again lowered and upper. This is also my partner in coding C++ back in the days, I usually write code in paper and when back to school I used our lab's computer. Ohh and I also have my anime addiction started on this too! One time I discovered the side VGA and connected it to our big LCD screen but by the time I plugged it in, it produce explosive sounds, and my grandpa said that that lcd tv is only for 110v not for 220v. I learned the importance of voltages that day. I just went back and open it to backup my highschool memories and stuff to my external hdd. Ahhhhh memories.

Slack.

A product which I hated in the beginning, is something that I have started admiring now.

Like Telegram, things just kept improving without bloating the shit out of the product.

What's interesting is that they came up with Huddle, an instant call and connect feature where they support Audio and Screen sharing.

Totally a game changer and a Zoom killer because Zoom could be even better in terms of UX.

Functionally, hands down, Zoom is flawless but slowly it's becoming an overkill.

I am excitedly waiting to see how both of these compete because Slack surely has an upper hand in this game.

My company’s upper leadership is sooo focused on the NUMBER of defects that are open on our project and only the number. We give each defect a priority of P0, P1, or P2. You would think this would help prioritize and strategize our plan to fix them. But nope. Every week we have some arbitrary “goal” to hit. A number purely made up by clueless leadership as to what makes a “quality” product.

On Friday’s, managers start harassing devs to merge their fixes and for QA to close out defects. So effectively rushing to hit that arbitrary number or else we’ll have to work Saturday.

Meanwhile they want more test automation coverage to reduce the incoming defect rate. But when the fuck do we have time to develop said tests when all you want is the defect closed to bring down your precious little number?!

They’d rather us close 25 P2 defects to bring the number down rather than 10 P0 or P1 defects. These leaders are so incompetent it kills me! Without any back story, they’re ultimately the reason we’re in this position in the first place! Argghhh!

Tl;dr stupid password requirements

Begin quote

Password must not contain any non-alphanumeric characters.

Your Password change was not accepted. Enter your current Password correctly following the rules for New Passwords. Please try again.

Passwords must be between 8 and 12 characters in length and MUST contain each of the following:

At least 1 lower case character (a-z)
At least 1 upper case character (A-Z)
At least 1 numeric digit (0-9)

But, MUST NOT contain:

more than five repeating characters in a row (e.g. 111111356 would not be valid, but 112233445 would be valid)
spaces or other special characters

NOTE: Your new password cannot be the same as any of your 10 previous passwords.

End quote

Are you fucking kidding me? Only (26+26+10)^8 through
(26+26+10)^12 different passwords to go through? It's like the oxygen wasters that built this website give zero fucks about security.

Why? This is the site that manages money and investments. Just allow passwords up to 64 characters, allow any ascii character and just fucking encod the characters to prevent any Injunction.

Devs: Can we please get adequate hardware to do our job correctly? Please, just a new set of larger monitors.
Lower management: Sure, this is going to be easy.
Upper management: Wait what? This will cost us around 500€ times 10? Any maybe in the end other departments will want that to, so make it times 100.

We're a 4+ billion company ... but yes, please, I love scroll bars and they make my work so much faster.

>work on multi million dollar company
>last year "we were doing fine" until we got told "well, turns out we didn't, no bonus this year"
>people leave
>You'll get a bonus next year for sure
>Company cuts expenses such as training budgets and freezes raises and promotions
>People still leave
>There are whole teams that are now left with 1-3 people, lol
>Turns out we will not get any bonuses this year either, except for "the high achievers", but they have not announced it yet
>high achievers include the evp of engineering who single handedly destroyed the company's DevOps department last year and an EM/engineer who is completely incompetent as both an engineer as well as a manager, so much so that the company has made him his own 1-person-department so that he doesn't have to work with other people
>Upper management keeps telling us everything is going fine and they suck each other's d**k

This is like watching a trainwreck in slow motion lmao.
I'll stay till they announce this year's bonuses to watch the shit show and then I'll leave

After months of searching for jobs, ended up I got called by a guy who claimed that he would want to partner with me to start a company. Well, I would love to start one, not without certain knowledge.

The so-called "partner" has a very bad attitude, unable to communicate, blames others for his own wrongdoing, arrogant, gullible and ignorant.

He asked me whether I believe in a deity (God). He demanded me to swear to the "upper heavens" that I will get "eternal punishment" if I ever cheated or betray his every decision.

This is a huge red flag!

I just want to have a "will smith slap" him so hard.

If anyone has been keeping up with my data warehouse from hell stories, we're reaching the climax. Today I reached my breaking point and wrote a strongly worder email about the situation. I detailed 3 separate cases of violated referential integrity (this warehouse has no constraints) and a field pulling from THE WRONG FLIPPING TABLE. Each instance was detailed with the lying ER diagram, highlighted the violating key pairs, the dangers they posed, and how to fix it. Note that this is a financial document; a financial document with nondeterministic behavior because the previous contractors' laziness. I feel like the flipping harbinger of doom with a cardboard sign saying "the end is near" and keep having to self-validate that if I was to change anything about this code, **financial numbers would change**, names would swap, description codes would change, and because they're edge cases in a giant dataset, they'll be hard to find. My email included SQL queries returning values where integrity is violated 15+ times. There's legacy data just shoved in ignoring all constraints. There are misspellings where a new one was made instead of updating, leaving the pk the same.

Now I'd just put sorting and other algos, but the data is processed by a crystal report. It has no debugger. No analysis tools. 11 subreports. The thing takes an hour to run and 77k queries to the oracle backend. It's one of the most disgusting infrastructures I've ever seen. There's no other solution to this but to either move to a general programming language or get the contractor to fix the data warehouse. I feel like I've gotten nowhere trying to debug this for 2 months. Now that I've reached what's probably the root issue, the office beaucracy is resisting the idea of throwing out the fire hazard and keeping the good parts. The upper management wants to just install sprinklers, and I'm losing it.

!rant

Upper management finally caved in to the endless change requests from business and explicitly made the following statement:

"We won't overpromise and under-deliver. With that, we are reducing the committed scope of development work per sprint, but will continue to deliver the same final deliverables by the delivery dates"

So all our compressed project timetables just got uncompressed, and we finally have the breathing room we've been begging for since 2017. Any change requests from business will be (finally) backlogged.

On the other hand, the number of projects have increased to fill out the new extra dev time, but at least we're now less stressed at work. Priorities!

When AI steal all the dev jobs, I will become upper management and do my best to confuse them by demanding they implement impossible things like 7 straight, red lines that are all perpendicular to eachother, and that are all blue.

I am working on a project that integrated with Microsoft Dynamics. The D365 team changes the data and API too often. I keep munging the data over and over so that it fits view models.

Yesterday I had a technical discussion with someone that the company installed to coordinate building technical solutions that get shared between projects. This is a problem across all of our Dynamics projects and is a technical one than needs coordinated approach.

The management heard that I am “doing repeated work because the data isn’t stable.” So they decided that it must be a problem with the project manager. The executive decides to use it as a reason to fire him. Which shows me that I can’t talk to even a technical person without risk of project chaos.

After the conversation but before the firing I get an offer letter from another company. I plan on taking it to get away from this crazy company. The project is going to lose their key web developer and also the project manager.

This executive seems to love firing project managers. My other project is on its third PM. My trust for the upper management is basically gone. I can’t even discuss the technical hurdles with a technical person without someone getting fired. I’m so ready to be out of this zoo.

The only downside of leaving is that I won’t have as many stories to tell on devRant.

Fuck you for imposing the upper limit on password length for my online banking! Why do you even care about my pass - don't you fucking hash it beforehand?!

Make a one-slide, two minutes max presentation to “sell” DevOps to upper management 🤦🏻‍♂️

Woo crunch time! The 3 panic attacks a day, no sleep, massive guilt complex, caffiene addiction, lack of seeing my wife, phone breaking(calling doesn't work), lawn needing mowing, upper management bothering all of my team, more guilt, more panic, inferiority complex, theory that coworkers think I am slacking, and technology just not working because the machine spirit decided I pissed it off is starting to get to me a little.

Finished my internship today, turns out I won't be getting hired because upper management is cutting back due to COVID.

Fuck fuck fuckity fuck, compared to the horror stories I've read here, it was beautiful. The work experience was super worth it though, despite the intern pay. Time to start looking for a real job I guess.

This was not exactly the worst work culture because the employees, it was because the upper level of the organization chart on the IT department.

I'm not quite sure how to translate the exact positions of that chart, but lets say that there is a General Manager, a couple of Area Managers (Infrastructure, Development), some Area Supervisors (2 or 3, by each area), and the grunts (that were us). Anyway, anything on the "Manager" was the source of all the toxicity on the department.

First and foremost, there was a lack of training for almost any employee. We were expected to know everything since day-1. Yes, the new employees had a (very) brief explanation about the technologies/languages were used, but they were expected to perform as a senior employee almost since the moment they cross the door. And forget about having some KT (Knowledge Transfer) sessions, they were none existent and if they existed, were only to solve a very immediate issue (now imagine what happened when someone quit*).

The general culture that they have to always say "yes" to the client/customer to almost anything without consulting to the development teams if that what was being asked to do was doable, or even feasible. And forget about doing a proper documentation about that change/development, as "that was needed yesterday and it needs to be done to be implemented tomorrow" (you know what I mean). This contributes to the previous point, as we didn't have enough time to train someone new because we had this absurd deadlines.

And because they cannot/wanted to say "NO", there were days when they came with an amount of new requirements that needed to be done and it didn't matter that we had other things to do. And the worst was that, until a couple of years (more or less), there was almost impossible to gather the correct requirements from the client/user, as they (managers) "had already" that requirement, and as they "know better" what the user wants, it was their vision what was being described on the requirements, not the users'...

And all that caused that, in a common basis, didn't have enough time to do all this stuff (mainly because the User Support) causing that we needed to do overtime, which almost always went unpaid (because a very ambiguous clause of the contract, and that we were "non-union workers"**). And this is my favorite point of this list, because, almost any overtime went unpaid, so basically we were expected to be working for free after the end of the work day (lets say, after the 17:00). Leaving "early" was almost a sin for the managers, as they always expected that we give more time to work that the indicated on the contract, and if not, they could raise a report to HR because the ambiguous clause allowed them to do it (among other childish things that they do).

Finally, the jewel of the crown, is that they never, but never acknowledge that they made a mistake. Never. That was impossible! If something failed on the things/systems/applications that they had assigned*** it was always our fault.

- "A report for the Finance Department is giving wrong information? It's the DBA's fault**** because although he manages that report, he couldn't imagine that I have an undocumented service (that runs before the creation the report) crashed because I modified a hidden and undocumented temporal table and forgot to update that service."

But, well, at least that's on the past. And although those aren't all the things that made that workplace so toxic, for me those were the most prominent ones.

-

* Well, here we I live it's very common to don't say anything about leaving the company until the very last day. Yes, I know that there are people that leave their "2-days notice", but it's not common (IMHO, of course). And yes, there are some of us that give a 1 or 2-weeks notice, but still it's not a common practice.

** I don't know how to translate this... We have a concept called "trusted employee", which is mainly used to describe any administrative employee, and that commonly is expected to give the 110% of what the contract says (unpaid overtimes, extra stuff to do, etc) and sadly it's an accepted condition (for whatever reasons). I chose "non-union workers" because in comparison with an union worker, we have less protections (besides the legal ways) regarding what I've described before. Curiously, there are also "operative workers", that doesn't belong to an union, but they have (sometimes) better protections that the administrative ones.

*** Yes, they were in charge of several systems, because they didn't trust us to handle/maintain them. And I'm sure that they still don't trust in their developers.

**** One of the managers, and the DBA are the only ones that handle some stuff (specially the one that involves "money"). The thing that allows to use the DBA as scapegoat is that such manager have more privileges and permissions than the DBA, as he was the previous DBA

I was asked to fix a critical issue which had high visibility among the higher ups and were blocking QA from testing.

My dev lead (who was more like a dev manager) was having one of his insecure moments of “I need to get credit for helping fix this”, probably because he steals the oxygen from those who actually deserve to be alive and he knows he should be fired, slowly...over a BBQ.

For the next few days, I was bombarded with requests for status updates. Idea after idea of what I could do to fix the issue was hurled at me when all I needed was time to make the fix.

Dev Lead: “Dev X says he knows what the problem is and it’s a simple code fix and should be quick.” (Dev X is in the room as well)

Me: “Tell me, have you actually looked into the issue? Then you know that there are several race conditions causing this issue and the error only manifests itself during a Jenkins build and not locally. In order to know if you’ve fixed it, you have to run the Jenkins job each time which is a lengthy process.”

Dev X: “I don’t know how to access Jenkins.”

And so it continued. Just so you know, I’ve worked at controlling my anger over the years, usually triggered by asinine comments and decisions. I trained for many years with Buddhist monks atop remote mountain ranges, meditated for days under waterfalls, contemplated life in solitude as I crossed the desert, and spent many phone calls talking to Microsoft enterprise support while smiling.

But the next day, I lost my shit.

I had been working out quite a bit too so I could have probably flipped around ten large tables before I got tired. And I’m talking long tables you’d need two people to move.

For context, unresolved comments in our pull request process block the ability to merge. My code was ready and I had two other devs review and approve my code already, but my dev lead, who has never seen the code base, gave up trying to learn how to build the app, and hasn’t coded in years, decided to comment on my pull request that upper management has been waiting on and that he himself has been hounding me about.

Two stood out to me. I read them slowly.

“I think you should name this unit test better” (That unit test existed before my PR)

“This function was deleted and moved to this other file, just so people know”

A devil greeted me when I entered hell. He was quite understanding. It turns out he was also a dev.

Someone from my current workplace found out who I am here. There goes my relative anonymous life here.

To all my colleagues, especially in the 'ansible' group chat.

I love you all (most of the time).
Please don't send this to upper management. Thank you.

How lawyers fuck up technology!

I rented a car today, given that I don't want to go by train currently. That was some VW Golf, and it had a lane assist which can't decide whether to be helpful or obnoxious:

Either I kept the steering wheel and still steered myself, in which case the lane assist's actions made the steering feel somewhat wobbly. Initially, I suspected a worn out control arm bearing, but that's a long term damage in aging cars, not in new ones.

Or I just rested my hands on my upper legs, as I usually do (palms facing upwards and holding the wheel lightly), then the lane assist worked by itself. It was even smart enough to deactivate itself upon blinking before changing lanes.

However, it complained after about 15 seconds that I didn't steer. I said, shut up and do your job. The warning intensified, and I said, fuck you. Then it initiated some stutter braking to wake me up. Annoying like a reincarnation of Clippy.

I ended up giving the steering wheel a slight tip to the right every 15, 20 seconds just to let the lane assist know I was still there, relying on the lane assist to correct it again. On a long trip, I would have had to deactivate that crap.

Obviously, the VW engineers did their job, but the legal department feared law suits should anything go wrong and ruined the feature!

What was also annoying is that there is no real hand brake anymore in many modern cars. Sucks when pulling off against a hill. Plus that at red traffic lights, I usually put the gear out (manual transmission) and pull the hand brake instead of keeping my foot on the clutch. That's not the same with this pseudo hand brake!

(In case you wonder why anyone would do that:
it's an anachronism that avoids lengthening the clutch wires, decades after cars switched to hydraulics.)

Installing a GPU is easy - except if it doesn't fit in the case. I had to saw off 3cm of the upper, 5.25" bay. Just removing the bay cage entirely was not an option because I still need that for my DVD drive.

My bow saw wouldn't have enough space, and the cage is riveted. So despite terrible ergonomics, I used the metal saw of a fucking Swiss Army knife for 24cm of cut length through 1mm steel. Then I filed off the cuts so that I won't injure myself later.

However, I was too lazy to take out the mobo and shit, so I protected it professionally against potential metal dust - with a towel.

I really hate the childish corporate culture at some tech companies. Today I received my Christmas "gift" from my employer. It was a branded chocolate bar and a sticker pack. The stickers were designed by our UX designers, and the stickers look like they are made for little toddlers at kindergarten. The stickers said things like "Make Friends!" and "To The Moon!". Jesus Christ, are we little kids? The average age of an employee at my company is around 30 years old, and those are the stickers you give us? Stickers are childish anyways, but it seems like 50% of my autistic colleagues seem to like putting those ugly things on their laptops to lick the boots of upper management.

The office itself literally looks like a kindergarten. There's LEGO artwork on the walls and the "Make Friends!" and "To The Moon!" nonsense and similar motivational bullshit is plastered on all the walls. Seriously, who ever thought it's a good idea to tell 30 year old adults to "make friends!". I already have my friends, I don't need to be friends with anyone at work, and I definitely don't need to be told to do so!

Even funnier than that is the fact that the whole "To The Moon!" bullshit is a phrase introduced by upper management to symbolize their effort and wish to make our company bigger and stronger by having a bigger market share. Basically it's the rich peeps from upper management telling us to work harder and make them more successful. Today I had a meeting in which they told me they wouldn't increase my salary because they have a tight budget this year because of the economic problems we're currently facing. But that doesn't stop them from childishly motivating us with bullshit like "To The Moon!" so they can become richer themselves, while the little people at the bottom of the pyramid need to work harder without extra pay.

The most annoying part of this is that many employees lick the boots of upper management and go along with all this bullshit. God I hate cringy childish corporate culture so much.

I saw that a co-worker had left their office email open on their machine, so I typed out a huge hate mail of the upper management and then announced resignation for the poor work culture that the company provided. Then I edited the email to be a bit more nice. I added some praise about the company - about having the opportunity to work in the company and for the amazing colleagues (and mentioned my own name) in the first paragraph. To close the email, I wrote :
"PS : This is what happens if you leave your machine open for the office to do as they please"

I first sent out a copy to myself (as proof) with the cover :
" Hey, check this out, I'm sending this out to everyone@company.com in a while. I want to let you know that none of this is directed at you. You've been an amazing colleague and mentor. You've been my inspiration from the start; from the time I joined the team. I'm honoured that I got to work with you. I hope we can remain friends as we are now, meet up once in a while outside work and discuss life. "

And then I put the actual email up in the compose window with the to field addressed to everyone@company.com. I didn't hit send.

Funnily, enough, this person never found out that it was me who actually typed out the whole email for another 1.5 months. They probably looked into their Sent folder later on when they saw the email that I sent to myself. They replied to it saying :
"Thank you for not sending out that email that day. I've been very very extra careful (I didn't understand the "very, very, extra" part) since that day"
I replied that it was only to prove a point and that I thought the point was well conveyed.

I had a good laugh that day. Since then, every time we crossed paths, we had that look in our eyes that met and only the 2 of us understood.

FUCK YOU TURNITIN.COM

Is there any reason FOR AN UPPER LIMIT TO YOUR PASSWORD!?

And if your wondering, my password would have been heyTurnItInDOTcomDevsYOUcanSODoffEXCLAMATIONpoint

Network, talk to people, and get yourself on the spot, document everything and make sure that you take action when others do not.

Kissing ass can take you far, but I ain't about that life, because sooner or later the fucker that promoted you because he liked his pp getting suckd by you will leave or get put in the spot. Or change alleagiances.

Your best bet is to be ANYTHING OTHER THAN A FUCKING NECKBEARD WITH AUTISM and be someone that people likes being around, I know it sounds hardcore, but people around you will ignore the things you don't know if you are a charismatic guy. Dress well, work out or find ways to improve yourself in ways that are noticeable, use human psychology to be fucking likeable.

Work hard, both on yourself and on your craft, study, get better, be social.

Stop being a twat because high chances are that the higher executives of your branch will not give a shit about your knowledge, but how good is to have you around. Join the circle, fuck your opinions about anything else, this is business, and business doesn't care about a lot of things. Don't cut throats, but make yourself a force to be reckoned with.

Source: Upper management, deals with VPs on a daily basis, knows that being a neckbeard will not take you anywhere.

Looking around where I work, I'm reminded of when I was young and ambitious, like all the other kids around me at the time, with a dislike for all the older dudes and dudettes in upper management. With the exception of three other guys around my age, everyone, including the CEO, was in high school, middle school, elementary school, or not even born yet when I started my career. Just like them, I was plucky and chatty and (trying to be) funny and social. I didn't know how fast I would go from that set to the old fat guy that they look askance at and wonder how I'm still around with my weird ways and "boomerish", socially retarded behavior. What's really galling is that I'm solidly Gen X, like some of them, but I guess I talk more like a Boomer because my parents were older when I was born and I was kinda raised in that mindset. I'm the office schlub now. A man out of my time. And I've never been in any kind of upper management, even. I am Kevin Malone.

Last week: Resigned from my current job as a front end dev, mostly due to incompetence in upper middle management.

Yesterday: knowledge transfer to backend dev who aspires to become full stack.
"
- So how does the designer deliver the CSS to the code ?
- He doesn't, he just sends the prototype, we make it work...
- The manager told me that the front end team did not touch CSS.
*fuzzy find ". styles"*
- So these are the 40 some files that appeared here magically.'
"

Today:
New git flow policy's in place. Pull requests are now outside the flow and are entirely optional.

This is gonna be the tits...

I explained last week in great detail to a new team member of a dev team (yeah hire or fire part 2) why it is an extremely bad idea to do proactive error handling somewhere down in the stack...

Example
Controller -> Business/Application Logic -> Infrastructure Layer

(shortened)

Now in the infrastructure layer we have a cache that caches an http rest call to another service.

One should not implement retry or some other proactive error handling down in the cache / infra stack, instead propagate the error to the upper layer(s) like application / business logic.
Let them decide what's the course of action, so ...
1) no error is swallowed
2) no unintended side effects like latency spikes / hickups due to retries or similar techniques happens
3) one can actually understand what the services do - behaviour should either be configured explicitly or passed down as a programmed choice from the upper layer... Not randomly implemented in some services.

The explanation was long and I thought ... Well let's call the recruit like the Gremlin he is... Gizmo got the message.

Today Gizmo presented a new solution.

The solution was to log and swallow all exceptions and just return null everywhere.

Yay... Gizmo. You won the Oscar for bad choices TM.

Thx for not asking whether that brain fart made any sense and wasting 5 days with implementing the worst of it all.

So, you are telling me that I should motivate myself? For working in a dead end job with no scope of promotion, no imminent raise, ever changing job requirements, layoffs, empty cubicles, zero SDLC process in place, no oversight from upper management, it is somehow my fault for me being late to work everyday?

One of these days, I'm going to fling my resignation paper at your face and drop the mic!

Man, Fuck you son!

I remember it was Friday, 30 minutes before leaving the office when suddenly someone from the upper management directly asked for my help to mass update something as it is important. By that time our CMS is not capable of doing this so I had to do it straight in the live database.

It was an update query and I decided to type the query in notepad first. when i pasted it in the terminal i didn't noticed i missed the "where" part so i mass updated the status of all our records dating 3 years back.

fuck.. please take note it was on a Friday night.

I love Nvidia's apathetic attitude to Linux support. It makes it so much more economical for me every time I need to upgrade my GPU - the mid-upper tier previous generation cards are always available for around the same price as a lower tier current generation card. There is no buyers remorse when the only things I'm missing out on by not going bleeding edge are kernel panics and random reboots.

I fucking hate corporate environment. We have a weekly meeting in our tech department where a team is chosen at random to present the project they're working on, architecture and such. You know what? We have fucking documents, for both product scope and technical architecture. If you're interested in our work, go fucking read our docs. If you have a question, slack us or send us a fucking email. Why the fuck do I have to attend a 1-hour meeting every week for this bullshit. Oh and some dude from upper management has a brilliant idea: from today they decide to host 2 such meetings per week, 1 within the tech department, and another within the whole company. So we had to attend the same fucking meeting twice in 1 week!!! Fucking genius!
I'm so fucking tired of these meaningless meetings, but attendance is recommended because "this is how you reach staff level" as they told me. Fucking bullshit. I may try a few more years for the sake of financial stability, and then find a small shop where people just leave me the fuck alone with my codes.

Relentless, thankless routine of coming in every day and everybody hating the software team despite working our ass off to help everybody and fix mistakes that upper management has caused.

The place I currently work at has got this culture of ignoring developers.

Deadlines get made by 3rd parties and project managers who don't have the technical nounce or experience of our system to make a call on deadlines.

Demos of products are arranged without a discussion with developers as to whether said component will be ready on that date.

3rd parties make decisions about future architecture, offer to assist, then disappear for days on end, to only come back and make out as though they've not been holding us up.

Upper management take no interest, don't listen to the people they pay to do a job.

Currently just moved a PHP web app into a multi tenant scalable EBS environment, but apparently it's not worth asking our view on technical aspects of the business before the shit hits the fan.

Lies to clients about documentation and policies, for example, claims from Sales we have a DR and BCP plan, client called is out, they sent a 2 paragraph A4 document to the client claiming it was our DR and BCP plan without talking to anyone technical, including myself who has years of DR experience. Embarrassing.

Could go on, but rant over.

Had an interview last week set up by a recruiter. Interview went well, aced the tech part, got on well with the interviewers, etc. They had one more interview the next day and would make the decision. Got feedback from recruiter the next day. I was in the top 2. Was told I had the best experience and skills. Thought I had this. Later that day got told they went with the other candidate because my recruiters presented me for $5000 more than the employer's posted upper limit. The employer just felt my salary requirements would push their budget too much so they went with the cheaper, less qualified candidate.

Not happy with my recruiter at all!

Okay so my ticket got rejected because the on screen texts are not in the correct case (upper/lower). Totally fair because nowhere in the spec are those texts defined. As a developer I am also responsible for what "makes sense" for the user.

I'm just gonna say this next time I ask for a raise.

OMFG, my upper back is so painfully stiff that I can't even breathe in w/o feeling like two knives are stabbed right between my shoulder blades.

And the weather outside is sooo excellent - first snow this season and it's so white and clean all around. A child inside me already has his mittens and warm boots on and impatiently waiting at the door to get outside to play with the snow.

And I'm supposed to somehow concentrate on work.

It's embarassing and you guys will find it either rude or annoying but I have readied myself and here goes my confession;

Whenever I see the abbreviation for Command line interface I cringe. You know because cli ? And I read it in my head as 'Kli' which is like the shortened form of a female part ?
I can't just read it as "See, el, ai" or think 'Command line interface' directly.
My brain's first thought is it must be an acronym so you should read it like how you would read NASA which is also an acronym and not like 'cmd' which is not an acronym but just an abbreviation.
Thus whenever I see it I feel a mixture of embarassment, self-loathing and physical discomfort.

I wonder how can I not be embarassed and cringing whenever I see Something-CLI.
I just noticed when it's in uppercase I don't cringe as much. I should code a chrome extension to change all CLI abbreviations to upper case.

Pro tip: how to reply to more than one person
1) click reply
2) close the reply by pressing the x button in the upper left hand corner.
3) click reply button of another person. Their name should now be added
4) Reference a Null Pointer
5) Profit?

Disclaimer: I hold no grudges or prejudices toward [CENSORED] company. I love the concept of the business model and the perks they pay their employees. Unfortunately, the company is very petty, and negligence is the core of the management. I got into an interview for the position, of Senior Software Engineer, and the interview wouldn't take place if wasn't for me to follow up with the person in charge countless times a day. The Vice President of Engineering was the most confused person ever encountered. Instead of asking challenging questions that plausibly could explain and portray how well I can manage a team, the methodology of working with various technology, and my problem-solving skills. They asked me questions that possibly indicated they don't even know what they need or questions that can easily get from a Google Search. I was given 40 hours to build a demo application whereby I had to send them a copy of the source code and the binary file. The person who contacted me don't even bother with what I told her that it is not a good practice to place the binary in cloud storage (Google Drive, OneDrive, etc) and I request extra time to complete the demo application. Since I got the requirement to hand them the repository of the codebase, it is common practice to place the binary in the release section in the Git Platform (Jire, Azure DevOps, Github, Gitlab, etc). Which he surprisingly doesn't know what that is. There's the API key I place locally in .env hidden from the codebase (it's not good practice to place credentials in the codebase), I got a request that not only subscript to an API is necessary but I have to place them in the codebase. I succeed to pass the source code on time with the quality of 40 hours, I told him that I could have done it better, clearer and cleaner if I was given more grace of time. (Because they are not the only company asking me to write a demo application prior to the assessment. Extra grace was I needed)

So long story short, I asked him how is it working in a [CENSORED] company during my turn to ask questions. I got told that the "environment is friendly, diverse". But with utmost curiosity, I contacted several former employees (Software Engineer) on LinkedIn, and I got told that the company has high turnover, despises diversity the nepotism is intense. Most of the favours are done based on how well you create an illusion of you working for them and being close to the upper management. I request shreds of evidence from those former employees to substantiate what they told me. Seeing the pieces of evidence of how they manage the projects, their method of communication, and how biased the upper management actually is led me to withdraw from continuing my application. Honestly, I wouldn't want to work for a company where the majority can't communicate.

In the grim dark future cryosleep or hypersleep or something similar will probably be used to extend peoples lives (and thus politicians careers) before it is ever used for space travel.

Give it time and you'll eventually have, through repeated extensions, term limits of one thousand years or even ten thousand, for congress/senate/president/etc.

You'll have CEOs and upper executives who have lived for 80k years dropping out of hypersleep once a century to document how the shoreline of north america changes near their beach home, as a sort of hobby.

Fart huffing professors (it's a professional sport in the year 28,841 AD) will come out of sleep once every millenia to track the evolution of something irrelevant, like gnat penises.

Big game hunters will wake up every 100k years to hunt new big game prey that just evolved--back into extinction. That and to check with their portfolio managers who will be AI or a highly evolved mongoloid goblin race of slave-quants.

I'm still working on the game btw. Anyone up for testing some prototypes when they're ready?

Aaron, seriously. Stop wading into our team uninvited, coming in with your "superior experience", mouthing off about how we need to be doing everything differently because our current code makes no sense, making a few PRs that break everything, then complaining we're just incompetent and don't understand when everyone rejects them.

If there's one thing that hacks me off the most, it's people like this wading in uninvited, pretending they're being really helpful in coaching us in the "one true way" to do development, screwing everything up, then buggering off again while boasting to upper management that "thank goodness I got there when I did, or that team would be royally screwed."

Since graduation, I have worked in IT for 2 years, mostly in testing and implementation side. Finally I got a developer position in the field I wanted (Data Engineering). I had never thought that it would be such a soul crushing experience. My current company is very notorious for its bad management practices, but there is indeed a bigger picture to this. The IT industry in general has devolved into a gigantic ponzi scam built on exploitation and BS. Quality of solution and quality of work was replaced with a ‘Does it work now?’ approach with zero contingency. And the fact that geeks and nerds are naive only helps the white collar crooks to exploit them as code monkeys. Fuck all of this!

HP makes shit devices. How the fuck you gonna regress with product design from 7 years ago?

Like whos the fucktard that thinks “how about in order to swap a keyboard, we make the user take EVERYTHING out and then put it into a new upper housing?”

Or my favorite is “instead of screwing a screen panel in, lets use some painfully difficult to access stretch tape?”

Fuck HP’s product design team. If by some off chance any of yall know anyone who’s part of that team, tell them i said they can eat a fat dick and get aids.

I came up with what I considered to be a brilliant approach to a festering internal knowledge management problem using a third-party SaaS. I rolled it out and it was very popular. Weeks later, after my profile had become the "linchpin" by which hundreds of other employees had joined the service, I was told that a female employee (yes, gender is important to this story) had produced a proposal for a more in-house solution that used a different company's software and that I would be on the team to roll it out. I thought it was a great idea and I deferred to her on pretty much everything.

Months after that I was accused, by several other female managers, of trying to take over the whole leadership of the project just because of one minor suggestion I had proposed. One day, after a lengthy interrogation about their take on my emails on the matter (lacking only the bright, hot spotlight in my eyes) I was booted off the project and the woman who had proposed the project was promoted. She then proceeded to lord it over on me and treat me like crap.

This type of thing was a general pattern within the company that amounted to a form of a reverse discrimination "policy" (unwritten). The effect was that the ratio of men to women in upper management was not equal but completely flipped. Way more women than men had upper management positions and higher pay.

In their eyes, the ends (women broke through the glass ceiling) justified the means (discrimination and bullying) which I guess is good and "equal", again in their eyes, in terms of the overall perception modern feminism has about men needing a comeuppance.

But in the context of HR's stated policy on equality, meaning 1:1 men and women in position of power and pay and a non-threatening work environment for all, which we all (men and women) were forced to sign every year, it was an utter fail as far as the math and intimidation went.

I haven't felt an urge to post on here in a while just because things have been going so well. But this month, is just not that kind of month anymore.

I'm upset. I'm upset by how I've been uprooted from my routine. I know I shouldn't be that bothered by it and things always change. But what the fuck is this company thinking to be using it's own fucking home baked ticketing system!

WHAT THE EVER LIVING FUCK IS THIS SHIT!

Let's go over the issues it has
1. I can't fucking email my clients through it
2. all emails are not recognized automatically. In other words each new email creates a new ticket if it does not have the tracking number attached to it.
3. I have to fucking hunt around in my inbox that is now bombarded by every email that is created for this ticketing system. Slap on a fucking tracking number. And then HOPE TO FUCKING GOD that the person on the other end doesn't erase the subject and cause the system to create a new ticket just for it.

Let's go over Zendesk which they've decided to decomission.
1. I. DON'T. HAVE. TO. DO. ANY. OF. THAT. FUCKING. SHIT.
2. That's it. It's fucking simple

Seriously. They forced me off of my original platform because this company already had a "ticketing system", if you can even fucking call it that, working.

And just if you weren't aware, all of this change happened because my company got bought out. It got bought out by this behemoth company that isn't willing to let me continue using a system; that has been very efficient, mind you, and instead make me use their system.

I. FUCKING. HATE. THIS.

Every fucking day! I have to do this stupid bullshit of emailing clients from my personal work email instead of on the direct ticketing system.

When I first started using this thing I actually thought I could use it to email the clients. For a solid two weeks I was "communicating" to clients through their ticketing system. Only to find out that the entire time those clients were not getting my actual fucking email! WHAT THE ACTUAL FUCK?

Then these guys tell me after the fact. "Oh that's strange... We never noticed that you can't send emails through it... We always just had used our work emails."

Are you fucking jerking my chain! You guys have literally been sitting in this slimy pit of hell for so long that you don't even know there are better options out there!

You don't have to fucking live this life!!

I don't think I'm going to make it. Something needs to change. And I know upper management isn't going to do it, because I fought hard to try and keep Zendesk. They are not keeping it. After this next quarter it is officially gone.

I'm trying to think of coding solutions to make my situation better... But I shouldn't have to fucking do that! There are perfectly good working solutions out there, and this company doesn't want to budge because "that's the way we've always been doing it"

I'm going to fucking rip out my hair.

I think it’s safe to say, the upper body of the duck is pretty successful

It’s randomly generated

My manager gave me a project about integration & deployment to another internal product which involves consuming oauth credentials which were already available in AmazonS3. The worst part of this is I wont have any access to any AWS resources and no sandbox environment.

And I'm like. How the fuck should I do this? Should I just conceptualize and pray to the machine spirits and hope that this wont have any fucking issues?

I will never understand why my university is requiring me to take upper level physics. I understand the need to understand electricity and circuitry but this semester has been mostly quantum and I don't see how this will apply to development.

I love coding. I enjoy the clickety-click of my keyboard and the joy of creating code that does something, to help the world be a better place. So why does upper management feel the need to bog me down in process paperwork, tickets to count my widgets, and endless endless emails and spreadsheets to prove that I have work to do. What are the time savings, priorities, cost avoidance... Blah blah blah... #IdRatherBeCoding :)

So I was told to look into a new project management tool to replace our home grown one that must be free, decided on visual studio team services because we all have msdn so it's free. We just got everything migrated and we've been using it very successfully for the past few months and it's honestly made task management so much easier.
Get back from vacation and my company just spent $100k on sales force agile accelerator... 😑 I don't understand how upper management works

Most awkward video meeting?

Can a conference call count? This happened several years ago.

Diving into international markets that could potentially make us millions of $$ (no pressure), while the phone was ringing the CEO's number (in Norway), my manager leans over and whispers
DevMgr: "This project will be managed using *proper* software development methodologies, none of this agile shit you want to use."
<CEO picks up>

I had already been in talks with their dev team to get a feel for their tech stack and we had discussed project milestones, potential release cycles (laying the ground work for using agile methodologies) before getting upper mgmt involved.

The partner dev team was listening and kept throwing out agile buzzwords and I could tell my manager was getting pissed. He would blurt out "Those specifications will need to be fully documented before PaperTrail writes one line of code!". No one said anything, but I could tell the other mgrs/VPs in the room were uncomfortable with the hostility towards discussing features.

I love git stash.

It's helps a lot for doing refactors to me. I guess it's not the most complex workflow, but it wasn't obvious to me when I started with git. Let me explain.

Refactors. As you start writing the first lines of a refactor, you start to notice something: you're changing too many things, your next commit is going to be huge.

That tends to be the very nature of refactors, they usually affect different parts of code.

So, there you are, with a shitload changes, and you figure "hey, I have a better idea, let me first do a smaller cohesive commit (let's call it subcommit) that changes a smaller specific thing, and then I'll continue with the upper parts of the refactor".

Good idea, but you have a shitload of changes nearly touching every file in your working copy, what do you do with these changes? You git stash them.

Let's say you stash and try to do that smaller "subcommit". What sometimes happens to me at this point is that I notice that I could do an even smaller change inside this current "subcommit". So I do the same thing, I git stash and I work on that even smaller thing.

At some point I end up `git stash pop`ing up all these levels. And it it shows that git stash is powerful for this.

* You never lose a single bit of work you did.
* Every commit is clean.
* After every commit you can run tests (automated or manual) to see shit is still working.
* If you don't like some changes that you had git stashed, you can just erase them with git reset --hard.
* If a change overlaps between a stash you're applying and the last "subcommit", then
if they differ, git shows conflicts on the files,
if they are identical, nothing happens.

with this workflow things just flow and you don't need to wipe out all your changes when doing simpler things,
and you don't need to go around creating new branches with temp commits (which results in bloated temp commits and the work of switching branches).

After you finish the refactor, you can decide to squash things with git rebase.

(Note: I don't use git stash pop, because it annoys the fuck out of me when I pop and you I get conflicts, I rather apply and drop)

Pro tip: if you press the little refresh button on the upper right hand corner it will refresh the rant and then scroll you all the way down to the bottom of the page.

Today I talked to a cousin who works in Tata Consultancy Services (TCS) and he told me precisely why companies like Infosys, TCS and Wipro are moving towards ending WFH and mandating working from office.

He told me that post-COVID hires are treating these software jobs so casually, that they don't ask for leaves. They decide, on their own, when they want to take leave(s) without telling their team members.

They don't pick up phone calls when someone from upper management tries to reach out and they magically show up 3-4 days later. They don't value deadlines.

He told me that these companies do see the benefit of letting people work from home, but the new generation hires are creating a joke out of these positions and are taking blatant advantage of the situation. So they are forced to mandate working from office.

"The culture here is one of success based upon academic excellence, studying, learning, practising and having a good job and a great life. For upper India, not the lower. I see two Indias. That's a lot like Singapore study, study, work hard and you get an MBA, you will have a Mercedes but where is the creativity? The creativity gets left out when your behaviour is too predictable and structured, everyone is similar."
Steve Wozniak on Indian Talent.

As an Indian, I agree with him. In this day and age, where education is so easy to come by, We live in a country where from the beginning we're told that education is about getting marks and writing stuff down 10 times. We live in a country where we're asked to cram up answers to questions which start with "what are your thoughts on..". How can we expect to be creative?
Can marks be a metric for good candidate in a country where the thought is, "first complete your engineering with good marks, then think what you wanna do in life".
Should academic excellence really be about the amount of shit a guy could cram up?

Sure it's easier to filter out people on the basis of marks in a country with 1.3 billion people, but is it justified?
Can we justify "success" as a good job for a guy who's life's only achievement has been getting into a good engineering college?
Can we really consider a guy successful, if his only "effort" has been reading and rereading books twice, thrice, a million times. Is this person, who has literally crammed his way into life, and has no practical experience, really successful?

This is the very reason Woz giving such a statement is justified. As long as we as a country gives up the stupid thought that patriotism is all about abusing the guy who says something negative about the country, and we actually start taking an action and change our thoughts on education, we won't succeed.

doomsday out 🤟

I wonder y slack hates upper case alphabets wanted to give my username in camelCase

This is more of a story than a rant, but it has some rant-ey elements, so whetever...

I work for a pretty big company. Several departments, teams, many different markets...so it's a big orchestration. The programming department (aprox. 5% of all employees) is the core of the whole company, because everybody else uses software we've written...(a bit off topic, the point is there are a lot of people)

So today, I got assigned with a side-project. The project spec arrives, and as I read through it, I start realizing that upper-management whats me to build an app to fire people instead for them. The app is supposed to track salary, connect with Trello (for departments that use it) to track finished tasks, track sick days, work attendence...a lot of stuff, and at the end, if the situation requires, spit out a person that is of least benefit to the company, to be fired...

Now from coding perspective, this will be very interesting and fun to build, but from a moral standpoint, I'm a bit woried...simply because, indirectly, I'm firing those people. Because, the way I tune the the app(specifically the algorithm that weighs the value of an employee to the company) will cause certain people to get fired...

So I'm woried I'm gonna have a small breakdown when the app goes live and I see someone saying goodbye to theie colegues of something similar...heck, the app might even spit out my name some day(I should probably add a tiny if statement somewhere in there :) )
What do you guys think about this, from a moral standpoint? Would you be okay with building something like this?

(Sorry for the long post :/ )

Somehow being able to make perfect sense out of the meaningless and vague requirements pushed down from upper management.

Maybe I'm severely misunderstanding set theory. Hear me out though.

Let f equal the set of all fibonacci numbers, and p equal the set of all primes.

If the density of primes is a function of the number of *multiples* of all primes under n,
then the *number of primes* or density should shrink as n increases, at an ever increasing rate
greater than the density of the number of fibonacci numbers below n.

That means as n grows, the relative density of f to p should grow as well.
At sufficiently large n, the density of p is zero (prime number theorem), not just absolutely, but relative to f as well. The density of f is therefore an upper limit of the density of p.

And the density of p given some sufficiently large n, is therefore also a lower limit on the density of f.

And that therefore the density of p must also be the upper limit on the density of the subset of primes that are Fibonacci numbers.

WHICH MEANS at sufficiently large values of n, there are either NO Fibonacci primes (the functions diverge), and therefore the set of Fibonacci primes is *finite*, OR the density of primes given n in the prime number theorem
*never* truly reaches zero, meaning the primes are in fact infinite.

Proving the Fibonacci primes are infinite, therefore would prove that the prime number line ends (fat chance). While proving the primes are infinite, proves the Fibonacci primes are finite in quantity.

And because the number of primes has been proven time and again to be infinite, as far back as 300BC,the Fibonacci primes MUST be finite.

QED.

If I've made a mistake, I'd like to know.

Print("Hello World")

When people design a brand new Postgresql schema (case sensitive) using a mix of upper and lower case letters.
Only to then proceed and escape every single table and column name in every single query.

Project management 101:

1) For a new project, pretend it is similar to a project in currently in development
2) Proudly state that everything can be copied from the older project, so the schedule of the new can be tightened
3) Calculate the new schedule based on the "just copy and paste" effort.
4) Now the new project will be finished before the older project
5) Enjoy the applause from upper management for the successful project that hasn't even begun yet.

No, this does not belong in the joke category.

That's gonna be fun...

So I got everything done that I'm supposed to this month. Now usually I would try to get ahead of the rush. However, since now even upper management doesn't trust me to do my job I figure I will adopt the same development process as the rest of the group: do nothing for the first three weeks of the month and in the last week hastily make excuses for why nothing is done while doing just enough to justify my continued employment.

How do I convince a dev department to take source control, peer code review and unit tests seriously?

I'm a recent software grad with internships that recently started at a smallish company (less than 20 employees but has been around for 10 years, with most senior non-mgmt employee around 6 years). I've been working here for less than a year (approx 5 months) and I love the company - lots of talented and passionate people.

We are a creative industry with a handful of devs and one of the issues I'm seeing is that often devs are working in silos. I'm trying to make suggestions to upper management like encourage more usage of source control, documentation, etc and most of the senior devs are pushing back - saying that they don't feel that it is necessary and due to the fast moving nature of our projects that all this would be a total waste (they were so fast on the idea of not having PR's because it would be "too much of a blocker").

I understand that a large part of this has more to do with shifting the culture in the department and that can be very hard to do, especially since i'm fresh out of school, but I see these devs have so much potential but it seems that they think having these implementations in place would mean more rigid rules and bureaucracy.

I've been speaking to some of my engineering friends and they're pretty much all just telling me that I am shooting myself in the foot if I continue to stay at this company because I'll be behind skill wise, but part of me isn't ready to just give up yet.

looking for some advice

Make sure you are noted for every work you do. Don't let upper managers to take credit of your work.

I wish I could do the following legally....

Spank someones butt with good horse hair whip.

Draw smilies with sriracha on the butt.

Let him write 1000 times "I'll keep my half knowledge and thus profound dumbness to myself - or ask politely instead of barking orders" with his red hot sriracha butt.

Let him lick it clean, his filthy mouth needs it.

And hopefully. Hopefully. Pain would teach him the lesson that his half assed knowledge and narcisstic behaviour does more harm than good - especially to himself.

Backstory: I had a full dual phone conference and video chat experience because someone was so full of shit... Eh. Narcisstic self believe. That he nearly destroyed an ongoing migration, made upper management nervous, and letting me deal with the still ongoing migration, conference / chatting and so on.

And yes. The date for migration was fixed. He could have spout his nonsense before.

Damn it, so many ideas to turn a human body into !!*!"!!*!*!*!!*

He launched a fullblown discussion on a saturday during an ongoing migration based on outdated knowledge claiming the right to know it all. R I P.

I have a rant. A genuine rant, not a funny story, etc.

I want a keyboard. I need one. It can cost €500, as long as it won't break in a year and fulfils all my needs. Make it a €1000, I don't care. What are my needs then? Well...

It has to be a split keyboard - two halves. But wireless in every aspect, ergonomic, with multimedia keys on its outer edges (preferably pointing outwards, not up) and a heavy metal trackball on the right outer edge (preferably upper right corner). That's a bare minimum.

On top of that it probably some magnetic scrolls for things like navigating pages, changing volume and fidgeting in general wouldn't hurt. Also I'd prefer it to snap back into a one-piece whenever I need it to lie on my knees, e.g. when I type while sitting on a coach (I have a coach PC setup, no desk, and there's a reason). Why do I need it to split then...?

I had an accident. Kind of broke my back when I was 11. It's mostly okay now after couple years of rehabilitation and many more years of careful living. Luckily the only two wheels I ride on are powered by a 105.97 hp @ 9,970 rpm engine. Still, I try to be careful so I tried tons of work hygiene techniques over the years and I found out anything over 2 hours is best done while lying flat.

Coding while lying flat has its challenges, mostly focused around screen and input. Ever since I got a VR headset half of them got solved but the other half - acquiring a suitable keyboard - it's very hard to satisfy. I tried that with a one-piece keyboard lying on my stomach. Turns out actively bending elbows quickly wears them out (hello tennis players). So a split keyboard it has to be. So far I tried 4 different ones and I had to modify the cable connecting both halves in each and every one of them so that it'd be long enough to go behind my back. The main cable itself I only had to modify once because usually there're extensions available.

Apart from cables, all of those keyboards had issues. Starting from some kind of de-syncing when keys from both halves would randomly register in a wrong order - I didn't know it's possible with a cable connected halves... I did try two generic WiFi keyboards (using one for each hand) and they unfortunately suffered from that very same issue but I was sure it wouldn't happen if the device was designed to be a one unit from the very beginning, right? And yet it in 2 of the tested devices.

Other than that, plugs disconnecting on their own forcing me to take off the headset and fiddle around, too high key travel that'd strain the wrists after a few hours, even the noise that would wake up my girlfriend sleeping in a separate room were all a common issue (I briefly had an almost completely silent WiFi mechanical keyboard from Logitech we both really liked, but it was a one-piece). Once I got a split keyboard that was "natively" WiFi but not only the two halves were still connected with a cable that turned out to be way too short for my needs, it also had a very noticeable lag despite the high price - a lag way higher than any of the cheap WiFi keyboards I owned in the past. So I sent it back. Now IDK what to do because AFAICT there are no more models available, at least where I live.

So yeah, I need a keyboard and I'll probably have to make one myself. Sorry, just had to vent.

For the last year I and my team have worked hard decreasing loading times on our products as we have been nagged and nagged about making everything load as fast as possible. Now we have been told to make things load slower or add a pause for a few seconds once loading has gotten to the end...

So due to some necessary repairs on my Nokia 6.1 i had to use an iPhone for the last 2 weeks (was the device they gave me for the duration of the repair). And let me say something in advance: I own a Macbook Pro, i own an iPad Pro, both devices are excellent for what i use them for. I enjoy OS X, i enjoy iOS on the tablet. But oh boy is the iPhone a shitshow of a magnitude i have never seen.

First off: The notifications. They feel like Android 4 or something. No customization, no grouping, not context. Also the swipe down gesture simply blocks whatever i am doing.

Multitasking: What a shitshow. There is no continuity, apps reload on a whim, no switching between apps (except that strange thing where the app shows up on the left upper screen, but i can't go back from there?)

Settings: WHY ARE APPS SETTINGS IN THE GLOBAL SETTINGS!! And not even all settings are. They are all over the place. And the settings are so convoluted and bloated, i can't find half of the things i am looking for.

Clock & Alarm: Goddamn that design choice with the edit button infuriates me to no end. Why can't i click an alarm and simply edit it? Also: Why do i have to enter the clock app to even see which alarm is going off next?

The Appdrawer: WHY CAN'T I SORT MY APPS BY NAME?? I have to conciously remember where i put things. Apps i use rarely, apps i use often.

God, iOS on the phone is so fucking terrible.

Y'all ever sneeze so hard you hurt your whole upper body?

Fuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuu-

!dev

I'm stuck in another country because of coronavirus, living in my mother in law's house, which is a church.

this church has two levels. while we are in the higher level, the lower level is being rented to some women that I hadn't seen since I've been here.

there is a library at the lower level next to their rooms and I'm using it to work because I can't focus with all the chatter in the upper level.

second day of work and 2 hours into coding, I get my balls held onto my legs. Trust me, I had just taken a proper shower, and I don't sweat a lot, it's just my balls being balls.

Naturally I try to separate said balls from my legs with my balls. Guess who the fuck I see passing through. One of these women.

Jesus fucking christ. What a good first fucking impression. Me with my hand in my fucking crotch.

The fuck is this shit?
The upper link is the actual link to the exherbo-project, a new source-based linux-distro.
The lower link forwards to a broken site, largely copying text from the original, while adding certain paragraphs about easy encryption and data-wiping to hide incriminating material.

Did someone from Gentoo went mad, because someone's developing an actual alternative to their shitty distro and package manager or what is happening here?

Get a screenshot of your colleague's desktop screen with the taskbar in the bottom. Adjust the taskbar settings to hide and move it to the upper side of the screen. Watch as how your colleague bust a gut.

Why can't PMs do a basic user research before wasting the engg effort on building a product they don't even know what to build?????
Everytime my team completes a feature, request comes in to change it because end user does not want this. And when I take a stand to not proceed further without proper UXR, upper management forces me to go ahead without it.
I am fed up of these folks sitting at the top and being childish just to satisfy their own ego.

First or second week of my first job (internship) and my manager mentions that upper management has decided that a couple of engineers are being reassigned to the new technical writing team, myself included, effective tomorrow with no prior warning, before dragging us into a tech-writing standup.

A couple of hours later my manager apologizes to me for forgetting to tell me about this and asked how I felt about this. I basically answered "not well, this isn't what I signed up for", and credit to him, he pulled enough strings to get me out of that team and back to my actual job. In hindsight I suspect that it was more due to the fact that this internship was a three-way contract with the university and that if I complained they might get their intern supply cut off.

Must contain 8-18 characters, 1 lower, 1 upper and 1 special character. Cannot be the same as email address.

18? Why fucking 18 characters? That's not any pragmatic limit. What fucking product owner came up with that requirement?

I love Rust's error messages, but I think they were trying to be a little too smart with the error reporting here and ended up relying too much on properties of the medium.
How the fuck do I tell which is which?

My hypothesis is that because #3 can only be a lower bound based on the phrasing of the sentence, and because #2 is an upper bound, the correct order is 2;4;1;3. But why do I have to do intermediate level English grammar exercises to read my error message?

Ford vs Ferrari shows everything wrong with upper management. They are a bunch egoistic pricks in suits who have nothing better to do than play office politics and take credit for the hard work of people under them.

One of the best movie I have ever seen. Made me wanna smell some oil and grease.

FUCK ME IN MY INDICES.
FUCK THE GPUS IN THEIR INDICES.

I mean... I understand (roughly) why the meshes are sent to gpu in this form, but at the same time...
...there's a reason why first thing I did when I was coding my procedural geometry generation library, was abstracting away all of that stuff...

...sadly, as many useful things, when I was looking for that lib on the start of this contract, I couldn't find it. and I was like "doesn't matter, this is a simple thing, using the library would be just a lazy overkill anyway".

well, fuck.
two hours of playing around with two fucking triangles, trying to figure out which indexes are pointing to the correct vertices in a list containing FOUR outline paths.
(lower inner, upper inner, lower outer, upper outer, exacly in this order).

i mean, yeah, it's actually pretty straightforward stuff... for someone not as dumb as me =D
you just have two offsets, one that jumps you to start of the upper path, another that jumps you to the start of the outer path, then it's just
0 + upOffset to get the vertex extruded upwards from the zeroth of the inner path, or
0 + outOffset to get the zeroth from the outer outline, or
0 + outOffset + upOffset, to get the one extruded from zeroth outer vertex...

and so on.
simple stuff, then you just replace the zero with loop control var, put them in the right order, and voilá! walls!
except... whatever, why am I describing in such detail, not necessary, you're not my rubber duck =D

in short, figuring out which fuckin vertex is which, when the list contains ...well, any number of points, and you need to plug the gap between last and first points of the paths, where you need to wrap around the list...

...has proven to be surprisingly hard for me.

funny how much I love doing these things with meshes, despite how bad I am at doing them, which makes me hate doing them despite loving it =D

When the infinite layers of upper management and committees don't trust the ones in the battlefield, are too paranoid and disconnected from reality. They are the ones blocking and preventing the release.

Otherwise, we devs are on schedule, almost no bug left.

To all websites requiring at least one upper case, one lower case, one number, one special character, 25 emoji and 49 unicorns in the password when signing up.

If you say something is required, then your regex BETTER be checking ONLY for those things. You should not have hidden requirements for passwords that users are supposed to dream about and know. Especially if it's a super time-sensitive thing that they should have opened 2 Fridays ago.

I had to pull my hair out for 20 minutes (that felt like an hour) before looking at their code and reading their regex. The regex was different from what the page said the requirements actually were. What were they even thinking? 😑

The rest of everything related to this organization uses an SSO system, why can't they just use it? Isn't the whole point of SSO to avoid a different login for every tiny part of the system?

I wonder what the other less technically inclined people using the system are doing right now. Sadly, I have no way of letting them know.

I sincerely hope the dev that made that website faces the same thing while picking a password for creating an account somewhere else and realizes what he/she did.

I really needed to let it out.
I feel much better now.

Time to take out the stress ball :)

TAP ONCE WITH TWO FINGERS FOR A RIGHT CLICK!!! ONCE WITH TWO FINGERS !!! NOOO NOT THE TOUCH PAD RIGHT CLICK DON'T TOUCH THAT!!!

NO NO NO DON'T DO THAT...
DON'T SCROLL BY HOLDING THE LEFT BUTTON AND DRAGGING...

TWO FINGERS SLIDE TO SCROLL

BARBARIANS ALL OF U

Coding is like handwriting.

Code review is about having a common understanding of the big picture and ensure be features follow the general architecture and process flow.

Code review is not about nitpicking on FUCKING TRAILING WHITEFUCKINGSPACES , lower case vs upper case SQL statements, extra empty lines AND EVERY FUCKING MINOR DETAIL you can imagine

I turned the job offer down. It was a fucking clown adventure. (Possibly even an attempt of a lateral arabesque?)

The position was filled and it turns out to my expections. It’s a bogus job! A PM from outside the company now has the role of an administrator. She has no IT knowledge which to me is just astounding of the incompetence of the upper management.

I mean.

What are the actually drinking up there? Is there drugs in the water? Actual drugs!?

We have hundreds of ”IT” systems spread over the planet. All of them are…wait for it… related to, you know, hardware and software and all sorts of integrations and data pulsations and the level of intertwined processes are staggering.

So, obviously it was a bogus title which will soon disappear after the next re-org.

I hate these larger-than-life-projects where all of a sudden an organism is created inside the ”normal” organism and the physical reality is vastly different from the surrounding space. And time. Time is also different. Not only are there actual time-zones to take into account but some projects are slower in time and some are faster than normal time. The guys that get that slower in time than normal time is the guys that ALWAYS should initiate projects from the start. They do know that shit is complex and the invent time. Very good. Some projects does not even come close to even enter the arena. Hell, they are not even in the parking lot! The mind-structures of insane management believing that the ”understand”.

Anyway. I turned it down. And it was the right decision almost certainly. I am now only the Level B Chief Supreme Commander of almost everything (except a lot of stuff).

Asked my teacher for help in 10th grade, she came up to my computer, looked at the code, zoomed in to 350%(ctrl+), mentioned that in C# we use upper cased functions names and then disappeared.
Not only the bug was not fixed, I couldn't even execute my code now.

Over the course of a few months I have concluded that the newly hired _experienced_ developer is… not so experienced. In fact, it is very unclear what he/she actually brings to the table at all.

How this individual actually got hired is proof that middle management has no clue of what they are doing. And it is poison to the organization. Bad management (middle/semi-upper in this case) is such a waste. More so than the newly hired incompetent developer. I am beginning to think she/he actually lied during the interviews. And I am not alone in my suspicions.

Full stack development between Python and JS eventually just makes your eyes cross as you confuse things like object definition syntax, '!=` vs `!==`, `.upper()` vs `.toUpperCase()`, `' '.join(list)` vs `array.join(' ')`

I was just copied on an email that had far to many managers included that basically says 90% of the problems come from an original group that just didn't follow directions.

Now we wait to see if upper management cans the whole team.

Who actually started the reign of mixed character passwords? because seriously it sucks to have an unnecessarily complex password! Like websites and apps requesting passwords to contain Upper/Lower case letter, numeric characters and symbols without considering the average user with low memory threshold (i.e; Me).

Let's push the complaint aside and return back to the actual reason a complex password is required.

Like we already know; Passwords are made complex so it can't be easily guessed by password crackers used by hackers and the primary reason behind adding symbols and numbers in a password is simply to create a stretch for possible outcome of guesses.

Now let's take a look into the logic behind a password cracker.

To hack a password,
1) The Password Cracker will usually lookup a dictionary of passwords (This point is very necessary for any possible outcome).
2) Attempts to login multiple times with list of passwords found (In most cases successful entries are found for passwords less than 8 chars).
3) If none was successful after the end of the dictionary, the cracker formulates each password on the dictionary to match popular standards of most website (i.e; First letter uppercase, a number at the end followed by a symbol. Thanks to those websites!)
4) If any password was successful, the cracker adds them to a new dictionary called a "pattern builder list" (This gives the cracker an upper edge on that specific platform because most websites forces a specific password pattern anyway)

In comparison:
>> Mygirlfriend98##
would be cracked faster compared to
>> iloveburberryihatepeanuts

Why?
Because the former is short and follows a popular pattern.

In reality, password crackers don't specifically care about Upper-Lowercase-Number-Symbol bullshit! They care more about the length of the password, the pattern of the password and formerly used entries (either from keyloggers or from previously hacked passwords).

So the need for requesting a humanly complex password is totally unnecessary because it's a bot that is being dealt with not another human.

My devrant password is a short story of *how I met first girlfriend* Goodluck to a password cracker!

Fuck this dieing pice of cheap chinese android crap. Sure it was anly 250 bucks, but holy hell... I could deal with the software side... Android 6 isn't the newest but eh...
But now the fucking hardware is failing too... To be more precise the buttons seam to randomly fire, which is really fucking annoying. Sometimes when both back and the other button fire the touch screen even joins the party of triggering touches in the right upper corner... Why the fuck ever.

Just ordered a pixel 3a, your days are counted fucking piece of trash!
Had to order the new one to a mailbox in germany though, as google doesn't ship them to switzerland (and the few retailers who import them charge like 130 bucks more, so paying the 5€ pickup fee will be a lot cheaper...)

Math is like a language syntax. You understand the meaning of needed symbols and keywords, then you can write it the way you want.

Physics is like a framework. You have to understand how problems can be solved using patterns someone else thinks is the best way.

This is what I think when I should be reading for the big test of physics and math for upper secondary school.

Upper mgmt paying an enterprise software vendor 40k US annually. Told vendor No more me QA'ing for them and 'discovering' obvious bugs. Told them to hire QA person and spring for some automated testing software. Yeah I know I am a nice guy but Enough is enough!

Actual validation message. I will omit the culprit to not shame them:

Your password must be at least eight (8) characters long and contain at least one letter,
one digit and three (3) special characters. No combination of any of the previously mentioned
requirements may be in a repeat success of one (1) or more. Special characters must be
separated by at least two (2) non-special characters, not including numbers. You may not
use more more than one (1) upper-cased and one (1) lower-cased letters in order together. You
may not begin or end your password with an uppercase letter or special character. You may use
no more than eight (8) special characters in your password.

If you need any assistance with this process, please send a message to our support staff.

Message: PASSWD-NG
Your IP Address: 50.202.37.133

Iconless menus – another effect of the toxic minimalism trend. Icons in menus such as the mobile web browser and device settings help finding items faster!

In 2014, Samsung removed icons from the upper right menu of their mobile Internet browser. At some point, roughly 2017, they realized it was a bad idea and brought them back. Could've told ya that earlier. 😁

Waterfall.

I string dislike the waterfall methodology and much prefer agile or scrum. And it's incredibly difficult that upper management only understands waterfall while claiming to know agile.

Meanwhile they want things completed by deadlines that are only possible with an agile approach. So you have a mishmash of upper management running waterfall with impossible deadlines and developers trying to meet those deadlines running in agile.

Anyone else have this problem?

For fuck's sake Microsoft, why on Earth do you announce a half-done feature? Was this an idea from marketing? Upper management? I am fairly certain that nobody who actually writes code for a living would have ever approved releasing a rushed feature to a TYPE SYSTEM.

Given an opportunity to develop an application for R&D. What do we do as a team? Let build it exactly the same way our current stack is built. (This app won't actually be used for anything useful, just an exercise for a fun R&D task)

It still amazes me with the number of developers that literally have the mindset, let's just do what we know & don't want to learn anything new.

Let's showcase new technologies? No. Let's create a serverless application? No. Let's create some microservices? No. Let's wrap the application in a Docker container so we can easily spin it up? No. Let's have multiple services that sit behind an API gateway? No. Let's for fucks sake at try a different design pattern? Why would we do that? Can we do anything differently? No.

No innovation, nothing - it just blows my mind. Everyone seems to think that the way the stack is built is how every application is. Sorry but a huge monolithic application that can't scale isn't how the other half live...

I don't know why the lack of wanting to try something new bothers be so much, but it does.

Had a real opportunity to showcase some cool tech, design patterns, new services in the cloud. Show not only other devs but upper management that there are alternative ways to develop. It's not like anything that I put together was "new or shiny" - I just wanted to do anything... Anything that isn't how currently do things.

Full disclosure, I'm not a great Dev - I'm pretty dam average but I'm always willing to try new techniques or approaches.

BT "We'll give you BT Virus Protect, which protects against viruses, phishing and other online attacks."

Or... For a start, let your users provide a good secure password when signing up? More than 8 characters is a bit ambiguous. 20 minutes later and several attempts to find out it can't be longer than 20 characters, only upper and lower case letter and numbers aaaand must start with a letter is a bit s**t. Not to mention LatPass doesn't like it as you can't copy and paste.

I work at a small company (4 devs, CTO, a senior, me: mid level, and a new junior dev). Junior and I handle the client projects and the Senior and CTO handle the overall platform and server deployments and such. Our senior dev just gave his 2 weeks notice. I was told they are not replacing him and now ALL of his tasks have been pushed onto me on top of all my already full plate. My issue is, although I am excited to learn about the upper management and deployment stuff, they (CTO and CEO) just dumped all these tasks onto me without even asking if I wanted the added responsibility and also told me there is no monetary bonus for taking it all on. Am I right in being a little mad that I was not even asked if I wanted it and it was just assumed I would handle it all without any bonus or monetary promotion?

I was trying to fill out an application on UltiPro yesterday, but it kept throwing an error “Password must be at least 6 characters.” This was puzzling, as my password was 12 characters with upper, lower, number, and symbol.

After half an hour of futzing with the password and getting the same error, I discover that actual issue: I had entered my full middle name instead of middle initial.

THAT’S NOT WHAT THE ERROR SAID!!!!!