Most embarrassing and lucky moment on the first week of job.

Me and my best friend were selected in the same company as developers. I was having some trouble with my system. So I mailed the description to our support department. Pop up was displayed from our chat client and person on the other end happened to be a lady. She wanted me to share a team viewer link with click access. So I did it and within 2 minutes of efforts she solved it. I thanked her, closed the chat conversation and started installing few packages. Meanwhile, I was curious to see her as she was really nice throughout the conversation. So I opened LinkedIn, searched for her name and found her profile. I zoomed in her photo and she was a pretty chick. I didn't stop and found her on FB too, and quickly saw all her DPs. I just copied her profile URL and sent it to my friend ( the one that got selected with me ) and told him about my conversation with her. Then I asked my friend
"She's hot. Should I send her a friend request or have to find some more troubles in my pc and talk to her few more times ? :P "
He replied "Dude what are you wanting for ? "
Out of no where, a pop up showed up. It was the girl we were talking about. The exact message was

"You can now close your team viewer session, and we can talk over FB :)"

Embarrassing AF!

Sit down before you read this.

So I interviewed a guy for a "Support Engineer" internship position.

Me and the team lead sit down and are waiting for him to enter, but apparently he's actually making a coffee in the kitchen.

This isn't exactly a strike since the receptionist told him that he can go get a drink, and we did too. It's just always expected for him to get a glass of water, not waste 3 minutes brewing a coffee.

In any case he comes in, puts the coffee on the table, then his phone, then his wallet, then his keys and then sits on our side of the table.
I ask him to sit in front of us so we can see him. He takes a minute to pack and tranfer himself to the other side of the table. He again places all of the objects on the table.

We begin, team lead tells him about the company. Then I ask him whether he got any questions regarding the job, the team or the company . For the next 15 minutes he bombards us with mostly irrelevant and sometimes inappropriate questions, like:
0: Can I choose my own nickname when getting an email address?
1: Does the entire department get same salaries?
2: Are there yoga classes on Sundays only or every morning?
3: Will I get a car?
4: Does the firm support workspace equality? How many chicks are in the team?
5: I want the newest grey Mac.

And then.. Then the questions turn into demands:
6: I need a high salary (asks for 2.5 more than the job pays. Which is still a lot).
I ask him why would he get that at his first job in the industry (remind you, this is an internship and we are a relatively high paying company).
He says he's getting paid more at his current job.
His CV lists no current job and only indicates that he just finished studying.
He says that he's working at his parent's business...
Next he says that he is very talented and has to be promoted very quickly and that we need to teach him a lot and finance his courses.

At this point me and the team lead were barely holding our laughs.

The team lead asks him about his English (English is not our native language).
He replies "It's good, trust me".
Team lead invites him for an English conversation. Team lead acts like a customer with a broken internet and the guy is there to troubleshoot. (btw that's not job related, just a simple scenario)
TL: "Hello, my name is Andrew, I'm calli..."
Guy: *interrupts* "Yes, yes, hi! Hi! What do you want?"
TL: "Well, if you let me fi..."
Guy: "Ok! Talk!"
TL: "...inish... My internet is not working."
Guy: "Ok, *mimics tuning a V engine or cooking a soup* I fixed! *points at TL* now you say 'yes you fixed'".

Important to note that his English was horrible. Disregarding the accent he just genuinely does not know the language well.

Then he continiues with "See? Good English. Told you no need to check!".

After about half a minute of choking on out silent laughter I ask him how much Python experience he has (job lists a requirement of at least 1 year).
He replies "I'm very good at object oriented functional programming".
I ask again "But what is your experience? Did you ever take any courses? Do you have a git repository to show? Any side.."
*he interrupts again* "I only use Matlab!".

Team lead stands up and proceeds to shake his hand while saying "we will get back to you".

At last the guy says with a stupid smile on his face "You better hire me! Call me back tomorrow." Leaves TL hanging and walks away after packing his stuff into the pockets.

I was so shocked that I wasn't even angry.
We both laughed for the rest of the day though. It was probably the weirdest interview I took part at.

I know I should not be naming names but WalmartLabs Hackfest 2016 was actually a fuckfest. It was supposed to be a 14 day online hackathon followed by an offline event for top teams. I got in top 6 among the 4350 participants.

In the offline event:

1. They didn't allow us to give live demo of the project. Instead they asked us to present a ppt. The HR idiot even asked me to take screenshots of my cli app and put that in instead.

2. 4 out of the 6 teams actually presented their startup products. It was supposed to be a 14 day hackathon for fucks sake. How can you present some shit that you were working on for the last 1.5 years! This one team literally had "Copyright 2015" mentioned on their product page. This another team had 100,000+ downloads on his app already. Of course Walmart didn't care about it. They didn't listen to my complaint. I wish I had created a scene there :( Another team was boasting on stage about how they got selected in the FB startup accelerator and how they won 3 more hackathon (evidently equally shit) using their shit. This was met with praises from the judges.

3. The results were declared after 3 fucking months! Don't organize this shit next time if you don't have any interest, bitch.

4. The code was supposedly never checked. Other teams kept working on their shit for the 3 months in between. In the live presentation, this guy even had photoshopped a feature which wasn't even present there (and he boasted about it later on).

5. Hackerearth (platform for the hackathon) was equally incompetent in this mishap of a hackathon. One of the teams which won had one the previous hackathon (Pluralsight hackathon) as well on Hackerearth using the same fucking product. What pieces of shit >.<

6. The hackathon was supposed to be tech based and all the categories were like that. Instead the teams presented business models and shit like that and judges focused more on that. They were not concerned about the technical aspects at all. The more noise you made, the more lies you told, the better chance you had to win it.

7. They were supposed to give prizes in 4 categories but silently reduced it to 3 on the event day. They still publicised it as 4 prizes until now.

All of the above is true and I am willing to testify if someone asks for it. I am going to write a nice blog post about it and post it to their idiot HR.

Hackathon: WalmartLabs Hackfest 2016
Team name: psyduck (which is just me)

Sorry for being too salty but it was indeed a fuckfest.

I once participated in a programming competition. We named our team "NameNotFoundException". Although we didn't win but a few days later we got a call from the organizing committee. They thought that there was something wrong with their system and wanted to know the name of our team. We laughed our asses off.

So, there's this big company in Poland with its name starting with C and having CEO famous for saying that every software developer can be replaced with a finite number of college students.

They recently lost a HUGE government contract and so stories of people working there came to light. My two personal favourites:

1. A tester who has been fired for finding too many bugs and mistakes in their product. He was also told that bugs are to be found by clients on production, not in-house.

2. A programmer who was yelled at by his team leader for "wasting time" on code reviews instead of typing the code. He was also told he hadn't been hired to criticise other people code.

God, I'm so grateful I don't work there.

My classmate is a real SAVAGE!!

He (team leader) and his team participated in hackathons several times and kept losing.
He noticed something common about winning team, majority of those team members were women, even if they were non technical and their project was pure bs, they were winning in the name of women empowerment.

This time he came out with a plan, he fired his boys and invited women into his team, and even made one girl the team leader.
Result? HE WON!!!
NOT ONE BUT THREE HACKATHONS BACK TO BACK

AND

His so called women team was invited by Google to pitch their startup idea.

Now, if they gets funding, he's gonna kick out these women and bring back his teammates

A wild Darwin Award nominee appears.

Background: Admins report that a legacy nightly update process isn't working. Ticket actually states problem is obviously in "the codes."

Scene: Meeting with about 20 people to triage the issue (blamestorming)

"Senior" Admin: "update process not working, the file is not present"
Moi: "which file?"
SAdmin: "file that is in ticket, EPN-1003"
Moi: "..." *grumbles, plans murder, opens ticket*
...
Moi: "The config dotfile is missing?"
SAdmin: "Yes, file no there. Can you fix?"
Moi: "Engineers don't have access to the production system. Please share your screen"
SAdmin: "ok"
*time passes, screen appears*
Moi: "ls the configuration dir"
SAdmin: *fails in bash* > ls

*computer prints*
> ls
_.legacyjobrc

Moi: *sees issues, blood pressure rises* "Please run list all long"
SAdmin: *fails in bash, again* > ls ?
Moi: *shakes* "ls -la"
SAdmin: *shonorable mention* > ls -la

*computer prints*
> ls -la
total 1300
drwxrwxrwx- 18 SAdmin {Today} -- _.legacyjobrc

Moi: "Why did you rename the config file?"
SAdmin: "Nothing changed"
Moi: "... are you sure?"
SAdmin: "No, changed nothing."
Moi: "Is the job running as your account for some reason?"
SAdmin: "No, job is root"
Moi: *shares screenshot of previous ls* This suggests your account was likely used to rename the dotfile, did you share your account with anyone?
SAdmin: "No, I rename file because could not see"
Moi: *heavy seething* so, just to make sure I understand, you renamed a dotfile because you couldn't see it in the terminal with ls?
SAdmin: "No, I rename file because it was not visible, now is visible"
Moi: "and then you filed a ticket because the application stopped working after you renamed the configuration file? You didn't think there might be a correlation between those two things?"
SAdmin: "yes, it no work"
Interjecting Director: "How did no one catch this? Why were there no checks, and why is there no user interface to configure this application? When I was writing applications I cared about quality"
Moi: *heavy seething*
IDjit: "Well? Anyone? How are we going to fix this"
Moi: "The administrative team will need to rename the file back to its original name"
IDjit: "can't the engineering team do this?!"
Moi: "We could, but it's corporate policy that we have no access to those environments"
IDjit: "Ok, what caused this issue in the first place? How did it get this way?!"

TFW you think you've hit the bottom of idiocy barrel, and the director says, "hold my mango lassi."

Client: “Hey this thing isn’t working correctly.”
Me: “Hmm, looks like there was a bug in the last update. The team and I are going to work on a fix. In the meantime here’s a tool to help you get what you need.”
Client:”Yay!”

*A little while later*
Same Client:”Hey this thing isn’t working.”
Me:”Hey, yeah, it’s the same thing. That bug I told you about? Yeah, we’re still working on it. We’ll let you know when it’s finished I promise but we’re trying to fix it without introducing more bugs.”
Client:”Ok sounds good.”

*A little while later*
Same Client:”Hey this thing isn’t working.”
Me:”Bro...we just went over this...”

*A little while later*
Same Client:”Hey seems like there’s a bug in our system that was found by -insert random coworker’s name here-. Are we looking into to this?”
Me:”Wtf dude.”

*A little while later*
Same Client:”Hey this thing isn’t working.”
Me: -smashes my face against keyboard-

Summing up many ridiculous meetings I've been in.

Many years ago we hired someone for HR that came from a large fortune 500 company, really big deal at the time.

Over the next 6 months, she scheduled weekly to bi-weekly, 1 to 2 hour meetings with *everyone* throughout the day. Meeting topics included 'How to better yourself', 'Trust the winner inside you'...you get the idea.

One 2-hour meeting involved taking a personality test. Her big plan was to force everyone to take the test, and weed out anyone who didn't fit the 'company culture'. Whatever that meant.

Knowing the game being played, several of us answered in the most introverted, border-line sociopath, 'leave me the frack alone!' way we could.

When she got the test results back, she called an 'emergency' meeting with all the devs and the VP of IS, deeply concerned about our fit in the company.

HR: "These tests results were very disturbing, but don't worry, none of you are being fired today. Together, we can work as team to bring you up to our standards. Any questions before we begin?"
Me: "Not a question, just a comment about the ABC personality test you used."
<she was a bit shocked I knew the name of the test because it was anonymized on the site and written portion>
Me: "That test was discredited 5 years ago and a few company's sued because the test could be used to discriminate against a certain demographic. It is still used in psychology, but along with other personality tests. The test is not a one-size-fits-all."

VP, in the front row, looked back at me, then at her.
HR: "Well....um...uh...um...We're not using the test that way. No one is getting fired."
DevA: "Then why are we here?"
DevB:"What was the point of the test? I don't understand?"
HR: "No, no...you don't understand...that wasn't the point at all, I'm sorry, this is getting blown out of proportion."
VP: "What is getting blown out of proportion? Now I'm confused. I think we all need some cooling off. Guys, head back to the office and let me figure out the next course of action."

She was fired about two weeks later. Any/all documentation relating to the tests were deleted from the server.

A couple of weeks back, I met some of the kids from my old school. They had joined together to form a small team and were designing and deploying websites for local businesses.

Turns out that they were mailing each other and using Dropbox to manage the source code. This had been going on nearly for an year.

I spent a couple of hours showing them how to use git and gitlab. Basics on committing, pushing, pulling, branching and merging.

I will never forget the look on their faces! They had seen God and its name is Git.

I know that my coworker can't write a single fucking operable line of code. So I wrote a script that is called everytime someone pushes new commits. If the commits contain the username of my coworker, create a ticket in YouTrack with the Label "Rewrite", and assign it to the files changed.
So I had that running for a longer time, and my dumbfuck of coworker hardcoded the credentials of the server in a networking library. One of the credentials was his username. He then updated the copyright on the whole project(which adds a copyright in the top of every file), also in the included librarys(!). The script had a check if the files are related to the project or just librarys. In the end, he pushed all of that with another account(in fact, a reporter account), which had another name(and didn't even belong him). So the files didn't belong to the project, the script sees his username anyways, the script assigns a rewrite, and in the end, everyone in the team thinks I'm mad because I(the script with my account) assigned a rewrite to a HUGE library.

PS: It was great fun to remove these copyright notices.

In other news:

Today a team of a total of six developers helf a 45 minute meeting to decide upon the name of a class.

It was later made clear that the class would be renamed anyway later in production.

---- Startup RantLife ----

A senior developer joined the team, let's name him Bob, and this guy is really good no doubts about that.
He made suggestions, some improvements, but Bob is always waving his hands and says out loud that some part of the code base is really really bad.
I kept quiet until one day I had to pair with Bob to check a feature. Guess what happened, as usual, Bob clenched his fist and start pointing that this code is super ugly.
So let's check the history of changes and boom, Bob was the main writer.
That moment, I was completely silent, trying not to smile as Bob came up with an excuse, he never admits that he is wrong, now he needs a scapegoat and he starts blaming the process, the planning...
I believe that being humble and saying sorry is a quality that it requires time to develop.
So don't be like Bob, please :)

This is a long rant. Sorry in advance. I just want to let it all out.

I don't really know what John (not his real name) did to my boss, who I shall name as Steve. Does he have a personal grudge? Like wtf?

John wasn't even incompetent. He even helped us mobile developers in our designs using photoshop. He's flexible. Ok sure, he isn't a top performer, but he isn't a low performer either. But why the fucking hate? really.

We currently have a new project, and are assigned to our posts. Then Steve goes, "Ok John, you will remain in the old project." He already said it once, which is fine. But did he really have to bring it up EVERY TIME? "John doesn't have to go overtime because he's in the old project, so it'll only be us." Like really? Of course we know that. why do you have to keep repeating that John isn't included? He even pointed at John during this. John shouldn't have been in the meeting then. Dipshit.

There was a meeting with the Web team in regards to what the progress was. When it came to John, Steve had to say, "The design is so ugly." Ok.. first off, you are not the QA to say that. And everyone else says it's fine. Even the QA says it's fine. So wtf? Why do you hate him so much?

We have these friday meetings in where we present our topics to the team, like Object Oriented Programming, SDLCs, and the like. We presented our stuff, and Steve listened attentively to everyone. But when it came to John, guess what? he ain't listening. He's on his phone, on his EARPHONES even. fucking rude. When John finished, he said, "You didn't present everything." He talked for an hour and a half. His topic has many things. Of course he can't present everything. And that is all you have to say? What about the others then? The others didn't present everything but you didn't complain. Why do you have to humiliate him to everyone else?

Way to demoralize your employee. What a lead. Fucking piece of shit. I am treating John pizza since I can't do anything else for him. It's frustrating. I wouldn't be surprised is John left the company.

So, there was this person I met on the internet who was preaching about how the success of games depends primarily on luck.
His argument was that even though he made a great game(his opinion) and uploaded it to the appstore his game failed to gain popularity.
He stated that there are about 500 games uploaded daily and it is only the matter of luck whether or not a game gets noticed and that he ran out of luck.
Now, his game was a pretty ripped off copy of the overused tile matching games. I pointed out to him that the reason his game didn't do well was probably because he made a ripoff(I actually used 'a copy's but 'ripoff' sounds more rant like) and that he priced it fairly high, while there were free games with more features and better graphics and mechanics(based on the description of the game and screenshots).
He then began to rage(all caps obviously) about how I am talking out of my ass and that I probably haven't even made a game yet.
I politely(the only reason I was polite was because the account was known to my Twitter followers. Sometimes one has to protect one's name) told him that I am an indie game developer and that I have made a decent amount of games.
He then proceeded to mock me and dared me to name a few.
So I posted four links to my 48 hour competition games and one to an official game.
He then began to call me an imposter, so I did a shout-out to him through my Twitter account.
Instead of continuing on Twitter, he ran back to the forum, and began to shit talk about how anyone can do it if they have a team with them.
I corrected him on that, stating how I was alone at the time and these particular games were the results of me working hard and striving to improve myself.
Then the guy finally starts spamming on different threads about how I am an arrogant bastard and other explicit forms of abuses before finally getting banned.
Sometimes I don't even know why I bother.
When I was starting out, there was this developer who would point out the faults in my games so that I could work on them. That was a great help and probably accelerated my growth. He was a great mentor and is now a good friend and is now in my team.
I guess some people are so hung up on their pride that they will refuse to accept their mistakes and make any efforts to improve.

Our website once had it’s config file (“old” .cgi app) open and available if you knew the file name. It was ‘obfuscated’ with the file name “Name of the cgi executable”.txt. So browsing, browsing.cgi, config file was browsing.txt.
After discovering the sql server admin password in plain text and reporting it to the VP, he called a meeting.
VP: “I have a report that you are storing the server admin password in plain text.”
WebMgr: “No, that is not correct.”
Me: “Um, yes it is, or we wouldn’t be here.”
WebMgr: “It’s not a network server administrator, it’s SQL Server’s SA account. Completely secure since that login has no access to the network.”
<VP looks over at me>
VP: “Oh..I was not told *that* detail.”
Me: “Um, that doesn’t matter, we shouldn’t have any login password in plain text, anywhere. Besides, the SA account has full access to the entire database. Someone could drop tables, get customer data, even access credit card data.”
WebMgr: “You are blowing all this out of proportion. There is no way anyone could do that.”
Me: “Uh, two weeks ago I discovered the catalog page was sending raw SQL from javascript. All anyone had to do was inject a semicolon and add whatever they wanted.”
WebMgr: “Who would do that? They would have to know a lot about our systems in order to do any real damage.”
VP: “Yes, it would have to be someone in our department looking to do some damage.”
<both the VP and WebMgr look at me>
Me: “Open your browser and search on SQL Injection.”
<VP searches on SQL Injection..few seconds pass>
VP: “Oh my, this is disturbing. I did not know SQL injection was such a problem. I want all SQL removed from javascript and passwords removed from the text files.”
WebMgr: “Our team is already removing the SQL, but our apps need to read the SQL server login and password from a config file. I don’t know why this is such a big deal. The file is read-only and protected by IIS. You can’t even read it from a browser.”
VP: “Well, if it’s secured, I suppose it is OK.”
Me: “Open your browser and navigate to … browse.txt”
VP: “Oh my, there it is.”
WebMgr: “You can only see it because your laptop had administrative privileges. Anyone outside our network cannot access the file.”
VP: “OK, that makes sense. As long as IIS is securing the file …”
Me: “No..no..no.. I can’t believe this. The screen shot I sent yesterday was from my home laptop showing the file is publicly available.”
WebMgr: “But you are probably an admin on the laptop.”
<couple of awkward seconds of silence…then the light comes on>
VP: “OK, I’m stopping this meeting. I want all admin users and passwords removed from the site by the end of the day.”

Took a little longer than a day, but after reviewing what the web team changed:
- They did remove the SQL Server SA account, but replaced it with another account with full admin privileges.
- Replaced the “App Name”.txt with centrally located config file at C:\Inetpub\wwwroot\config.txt (hard-coded in the app)
When I brought this up again with my manager..
Mgr: “Yea, I know, it sucks. WebMgr showed the VP the config file was not accessible by the web site and it wasn’t using the SA password. He was satisfied by that. Web site is looking to beat projections again by 15%, so WebMgr told the other VPs that another disruption from a developer could jeopardize the quarterly numbers. I’d keep my head down for a while.”

A huge project came my way at work. Old spaghetti code, no source control, no test env and every other possible challenge you could think of. Based on my initial quote a deadline of June 19th was approved. Two days ago the president of the company tells my boss it needs to be done by Friday, no excuses. Horrible timing since I'm moving tomorrow and am off all next week. Not to mention I'm the only dev at the company that understands/knows how to work on this code. We also don't have a budget to contract out. Literally not possible to do in 2 days. I proposed a "quick fix" solution and new design which was approved. I Spent 2 straight days working on it with overtime, no lunch hour, and the president checking on me every hour for status updates. Managed to implement my "quick fix" and just put it live 2 hours ago. President approved, and said "thanks". He then sent an email to the company and all our agents across the country anouncing the change. In the email he directly thanks the Marketing dept and the "senior leadership team" for "making the quick turnaround of this request possible". He proceeds to name specific people responsible for making this happen. No where does he mention my name or my department. Not that I'm actually surprised but it would have been nice to get some recognition considering this literally wouldn't have worked without me. Guess I should be used to it by now. I'm also now on call during my week off in case anything breaks.

My team are the best coworkers I've had. Admittedly I'm only 4 years into my professional career, but my team makes me stay with my current job.

My team do a lot of silly things to keep everyone in a good mood, and stress free. This week we've had a game where in a quote moment you just yell the name of a primitive type (like BOOL). Why? No idea, but we're enjoying it.

We also have a chicken hat that we named Barry. He sits with people on their desk to do code reviews and such. When people leave they get their own Barry to take with them to their new job. We introduce people to him as a regular member of the team.

Sometimes work sucks. Being a developer can be hard, and can be stressful. Working with this team makes it worth it.

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.

True story.

I had been working for 6 months at the same place surrounded by 6 people (3 of them in my work team) .

On January I receive a message on skype for business "Hello, happy new year :)"

I answered "thanks", 10 seconds later I see the name of who wrote the message, someone called let's say YYY, so I ask one of my coworkers, "do you know who is YYY?" and I hear a voice of the girl seated right in front of me for the last 6 months answering "It's me", "Oh!" I said.

Awkward silence....

Rant to myself for being a shitty non social person.

Coding won over my first girlfriend!

My senior year of high school I taught myself C++ and thought it was the coolest thing (lol). So I wrote a stupidly simple program that would ask your name and output a random riddle. But if the name was hers it was a riddle in which case the answer was "a date". Looking back, even if she was on my robotics team it was the nerdiest thing.

We dated for 8 months and broke up as friends. But to this day it provides a great story as I pursue software development.

This ist basically my daily work. I have to write Java code in excel files which then are being converted into a DSL and then again being converted into Java code. On top of that many wrappers were built which abstract all this things away..

We have about 30 such excel files which contain about 50000 business rules.
There is no version control for this tables and 5 different team are working on the same tables parallel.

The name of this framework is Drools or as I call it: HELL 😡

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."

🍿🍿 pull up a chair and get comfy. This was a few years ago and anger has filled some details, so bear with me...

One day, during one of rare afternoons off of work, I was in the library to work on a group project for school. This was maybe a month before it was due, so we were tracking for decent progress and one less stressor over finals. It was about 80° F out, with the perfect breeze for the beach, but school comes first.

I'm team lead (which is terrifying, but less important) and my bro C shows up early to be ready to go on time because he's professional. I'M SO BAD I FORGOT DOUCHEBAGS NAME, so he's A (for asshole), shows up AN HOUR AND 15 MINUTES LATE. But it's not the end of the world, C and I worked around our database schema (which A sent us and we approved), so we could iron out kinks as we went.

A gets there... Fucking finally.

Fucker didn't have the database built (had 2 months to do it, we all agreed on schema a month prior. We're trying to be the adults our ages claim is to be).

*breathe in, count to 10* not a problem, A, just go ahead and start it now so we can at least check what we have.

Ok, my queen, I'll have it done in 10 minutes...

🤔🤔

We needed an id (sku... Which, in 99.9999% of companies is numeric), a short name (xBox one, Macbook, don't smart tv), a description and a price (with 2 decimals). All approved by all 3 of us.

His sku ranges from 3 to 9 ALPHA NUMERIC CHARACTERS, the names were even more generic than expected (item1, item 2, Item_3), no description, and he somehow thought US currency had 5 decimal places!!! (it's more accurate...)

There was an epic, royal, and expensive fight scene in the library (may have been during the Lenten season I decided to give up caffeine AND fast for 40 days to prove a point to an ass wipe of a history teacher, don't recall). I made him cry, he failed the class because C and I wound up fixing everything he touched (graded by commits, because it was also an intro to git, but also, a classmate saw it all), and I had to buy multiple people coffee for yelling in the library.

A tried making out buttons work (I was fed up and done thinking for the day, so moved to documentation), but he fucked those up. I then made those worse by having nested buttons, but I deleted all his shit and started over and fixed it.

I then cried, but C and I survived and have each others backs still.

I can't name one specific time that was the best memory per say. My team is super close - we get lunch almost every day, have (inappropriate) inside jokes and just act dumb together. Not one person on my team who doesn't fit in. Even our boss is cool. :) #LoveMyTeam

I've been wondering for a while, how the backend my team has to use could have so many issues. I was convinced they had no alerting system in place and have been commenting on it for a while now, and complaining about it.

Was on a Zoom call with one of the backend devs today, he shared his screen and had his email open. I saw a folder he had setup called alerts, and sub folders under that. One of them was named the name of the service/app we are using ... it had over 360,000 un-reads ... and emails are automatically deleted after 4 months in my company.

So they have alerts setup, they just don't care ... problem solved. Enjoy your weekend folks!

I give up. It‘s impossible to argue with Apple.

I tried to bring my unofficial iOS devRant app "JoyRant" into the AppStore. It was available via TestFlight for years and it wasn‘t a problem there, apparently. Now for the AppStore, it is a problem.

I talked with the Apple review team for 3 weeks and the discussion went in circles.
They said that my app tries to disguise as or to misrepresent another app on the store (the official devRant app, even though it‘s not available anymore, apparently).

I was asked to remove all of the mentions of devRant from any description or any place in the app. I did. Even though it was stupid because how are people supposed to know that they need a devRant account to use my app? I‘m not allowed to mention devRant.

After that, they said that it can not have the name JoyRant because it sounds too similar to devRant.
I changed it to devJoy everywhere, the app, the meta data for the app store, the github page where the required legal crap is hosted, and in the legal documents themselves.
Did it help? No, it didn‘t.

Apple then proceeded to claim that my app is trying to deceive the users into thinking that this is the official devRant app. Even though I have explicitly stated in the description that it is just an unofficial devRant client.

Now apple says that I should "revise the app content".
Which I assume means that I need to make it something different. Yeah. Great suggestion!

So, I will rename the app back to JoyRant and provide it via TestFlight, as it was before.

Thanks for reading. I needed to vent.

"IT BROKEN!", the QA tester spoke in unintelligible broken English.

The developer asked for more details.

Then the QA person attempted to explain the problem in a surge of verbal diarrhea and horrible English.

Why do we hire people who don't speak the language of the development team as our QA people? I have nothing against devs and qa guys from India...but it makes my job really difficult when I can't even begin to understand what you are telling me, or even worse...you just tell me "IT BROKEN!" and don't give me a single bit of useful information on how to reproduce the error.

There was this wonderful QA person I used to work with. Her name was Ranjana. She was a beautiful Indian girl with two children, and the best QA person I ever worked with. She took screenshots, grabbed logs, and gave steps to reproduce everything she found. And then one day at stand up we were told she had died. And since then...there has been no one who has ever come close to her level of excellence.

Hi Dev Ranter,

My name is John Smith and I came accross to your resume on Linked In and I was very impressed. Would you be interested in a 5 min call?

Job Details:
Required skills (all expert levels): C#, JAVA, Clojure, C, PHP, Frontend, Backend, Agile, MVP, Baking, Redis, Apache, IIS, RoR, Angular, React, Vue, MySQL, MSSIS, MSSQL, ORACLE, PostgreSQL, Access, Python, Machine Learning, HTML, CSS, Fortran, C++, Game design, Book writing, PCI - Compliance
Salary: $15/Hours no benefits
Duration: 2 Months (possible extension, plus we can fire you at will)
Place: Remote (with work tracking software)
Hours: 5am - 1pm, 6pm - 11pm
Expect to work on weekends

You will be managing people as well as building applications that had to be running as of yesterday. Team culture is very toxic and no one cares about you.

We care about you though (as long as you deliver)

Looking forward to talk to you.

John Smith
Founder, CEO, Director of Staffing, Entrepeneur
Tech Staffers LLC ( link to a PNG posted on facebook)
Est. 2020

There’s a junior on my team, who has an ego problem.

Within 6-8 months, they have not progressed much, up to the point they still struggle with language and framework syntax.

Yet, they want to get the credit for doing big and important tasks, the ones they have no clue at all how to execute.

Our team tried to break more the tasks and tickets almost to the point of a tutorial. Junior got upset and complained that they did not want the tasks to be broken for them.

If we give space, tasks take forever to get completed. If we try to pair, Junior does everything in their power to cut the meeting short and again take forever to complete anything.

If we prioritize our own tasks, Junior complains that nobody pairs/assist them.

Took one for the team and started to work on finding ways to get this wonderful person to learn. Junior does not learn. In fact, almost feels like things enter from one ear and leave from the other instantly. Despite being repeated multiple times. Chewed. Presented in all sorts of way. You name it, I’ve tried.

Yesterday was the last drop. They fucking rolled their eyes while was explaining something.

This person is dead for me and I will make my personal crusade to not go out of my tasks to help them.

Thanks for coming to my TED rant.

I was only seventeen back then and I was a Java Developer Intern, not knowing much about enterprise oriented coding.

The project leader in our dev team saw a lot of potential and passion in my work, but was convinced I wasn't taught enough to do the right thing.

I was mainly doing shitty mappers and services back then, which were somewhat used but never lasted long and were ditched a few months later, which always bummed me out. I wanted to make an impact on REAL projects that would deploy into production.

So Mister Mentor (GDPR forbid to use the actual name), who was always first to come and last to leave the office, taught me what it means to code for real.

We stayed after 5pm until 7-8pm multiple times a week and he taught me in a deeply understanding and calm way how to:
- Git (SVN)
- Refactor
- SOA
- Annotate
- Deploy
- Unit Test

And most importantly:
- How to debug like an absolute BOSS
(We even debugged native Java Libraries just for fun to see if we could break them)

Fast-forward a month later and little intern me made his first commit on production.

Without Mister Mentor, I wouldn't be half as good of a developer as I am today.

!rant
Observed a full deployment the other day and discovered it's extremely inefficient. I proposed an idea to fix it, and was shot down by a senior dev on the team. I was ranting about how asinine the process was and how my process could reduce the amount of time and training required to do deployments with out any additional cost or overhead. A senior dev from another department over heard me, found my workspace and told me (in a nutshell), "write up a document about why the current process is garbage and how yours is better, and how it works, I'll review it and we'll get it worded and formatted right. When we finish the document, I'll forward it to the CTO of your department with your name on it and my recommendation for review." Fuck yeah. 😈😎

Request from a senior backend dev in a previous company:

Talking to the team thats responsible for the auth API's is such a pain. For this new API can we just not add any auth to it? Its only going to return details about who the email address belongs too. Like name, address, date of birth, car registration etc. No one will care about that, and it will be easier for mobile to integrate right?

I was contacted by a college senior guy (he was part of the core team of the club that I recently joined in my college).

Him: Do you want to launch your own startup?

Me: Yeah, I would love to.

Him: Nice, Listen. Even I want to start my own company. If you don't know, the current trend is ML and AI . So, I would like to base my startup on an AI application.( He was in his final year )

Me: I haven't tried any ML or AI stuff before.Sorry.

Him: Take 2 months time to study the AI concepts and do the app.

Me: But first, tell me what the AI app is supposed to do?

Him: It can be anything I have to think, you take the AI part and the UI and integration; with your skills and my idea let's build a startup and I will appoint you as the head of Application Development in my company.

*wtf, seriously dude? you want me to build the whole app for you and all you will do is put your fucking startup's name on it. I am building an application all by myself why the f would I ask you to publish it for me*

Me: Okay, I am getting late, I have to leave..

Made sure I didn't meet him again

and I have also came out of that stupid club..

OK I can't deal with this user anymore.

This morning I get a text. "My laptop isn't getting emails anymore I'm not sure if this is why?" And attached is a screenshot of an email purporting to be from "The <company name> Team". Which isn't even close to the sort of language our small business uses in emails. This email says that his O365 password will soon be expiring and he needs to download the attached (.htm) file so he can keep his password. Never mind the fact that the grammar is awful, the "from" address is cheesy and our O365 passwords don't expire. He went ahead and, in his words, "Tried several of his passwords but none of them worked." This is the second time in less than a year that he's done this and I thought we were very clear that these emails are never real, but I'll deal with that later.

I quickly log into the O365 admin portal and reset his password to a randomly-generated one. I set this to be permanent since this isn't actually a password he should ever be needing to type. I call him up and explain to him that it was a phishing email and he essentially just gave some random people his credentials so I needed to reset them. I then help him log into Outlook on his PC with the new password. Once he's in, he says "so how do I reset this temporary password?" I tell him that no, this is his permanent password now and he doesn't need to remember it because he shouldn't ever need to be typing it anyway. He says "No no no that won't work I can't remember this." (I smile and nod to myself at this point -- THAT'S THE IDEA). But I tell him when he is in the office we will store the password in a password manager in case he ever needs to get to it. Long pause follows. "Can't I just set it back to what it was so I can remember it?"

Well I’ve had my LinkedIn status to open for a little while now. Time to check what exciting offers (me, an iOS developer / team lead) has received.

- Senior python engineer with multiple years machine learning experience.

- a job 3000 miles outside the only city I’ve marked myself as interested in.

- Architect for a .NET team.

- Senior UX Researcher.

- The same job for a bank 6 times. But each time they won’t initially give the name of the company. Only “my fav client to work with” until I respond.

... not much hope in this process

I've come to a conclusion today: Management are fucking with me. I know it sounds far fetched, but its the only thing that makes sense.

I was in a meeting today, discussing some bad emails back and forth. Part of my issue was the amount of time spent on useless meetings, or waiting around to give demos.

The meeting got cut short, so I could prepare a demo for a VP ... after an hour and a fucking half of waiting around ... theres no time to see my demo.

What the actual fuck, seriously .... seriously what the actual fuck. What if the name of mother fucking christ is going on with this team, that they call me into a mother fucking meeting to discuss the "developers attitude" only to go and cut it short ... so they can fucking waste my time ... for the second time in 3 mother fucking days.

Oh i'd rather fuck myself with a cactus than spend the rest of my days dealing with this utter bullshittery.

I like playing tf2.
I play every video game with max brightness on the lappy.

The problem is that when I alt tab back to anything else, eg chrome, I get dazzled and my eyes hurt.

I'm on linux and accidentally noticed that I can connect to the X server and do stuff.

So I'm listening for events with the PropertyChangeMask, and when the active window has the name "Team Fortress 2 - OpenGL", I run "light -S 100", otherwise I use what I already had.

Very happy with this hack, instant brightness changes on alt tab.

my team mate thinks that function name should be descriptive so you can understand what It will do.
Here are the examples of functions he created:

createArrayOfConsentChangedEventObjectForAConsentForAllDataProcessorsWithoutNameInEvent()

createArrayOfConsentChangedEventObjectForAConsentForAllDataProcessorsWithNameInEvent()

createAndPushConsentChangedEventWithAndWithoutNameForAParticularConsent()

I was supposed to review his code but this names are so annoying that I gave up on reviewing and just passed his code since functionalities were working as expected. -_-

Am I the only one who gets annoyed by long function names?

I was on vacation when my employer’s new fiscal year started. My manager let me take vacation because it’s not like anything critical was going to happen. Well, joke was on us because we didn’t foresee the stupidity of others…

I had to update a few product codes in the website’s web config and deploy those changes. I was only going to be logged in for 30 minutes to complete that.

I get messaged by one of our database admins. He was doing testing and was unable to complete a payment on the website. That was strange. There was a change pushed by our offsite dev agency, but that was all frontend changes (just updating text) and wouldn’t affect payments.

We don’t want to enlist the dev agency for debugging work, especially when it’s not likely that it’s a code issue. But I was on vacation and I couldn’t stay online past the time I had budgeted for. So my employer enlists the dev agency for help. It’s going to be costly because the agency is in Lithuania, it was past their business hours, and it was emergency support.

Dev agency looks at error logs. There are Apple Pay errors, but that doesn’t explain why non Apple Pay transactions aren’t going through. They roll back my deployment and theirs, but no change. They tell my employer to contact our payment processor.

My manager and the Product Manager contact Payroll, who is the stakeholder for our payment gateways. Payroll contacts our payment gateway and finds out a service called Decision Manager was recently configured for our account. Decision Manager was declining all payments. Payroll was not the person who had Decision Manager installed and our account using this service was news to her.

Payroll works with our payment processor to get payments working again. The damage is pretty severe. Online payments were down for at least 12 hours. Our call center had logged reports from customers the night before.

At our post mortem, we had to find out who ok’d Decision Manager without telling anyone. Luckily, it was quick work. The first stakeholder up was for the Fundraising Dept. She said it wasn’t her or anyone on her team. Our VP of Analytics broke it to her that our payment processor gave us the name of the person who ok’d Decision Manager and it was someone on the Fundraising team. Fundraising then starts backtracking and says that oh yes she knew about it but transactions were still working after the Decision Manager had been configured. WTAF.

Everyone is dumbfounded by this. How could you make a big change to our payment processor and not tell anyone? How did our payment processor allow you to make this change when you’re not the account admin (you’re just a user)?

Our company head had to give an awkward speech about communication and how it’s important. The web team can’t figure out issues if you don’t tell us what you did. The company head was pissed because it was a shitty way to start off the new fiscal year. Our bill for the dev agency must have been over $1000 for debugging work that wasn’t helpful.

Amazingly, no one was fired.

So we're hiring for a new junior dev and for the most part it's been going great! We have some promising candidates and I am so glad to finally have a new dev on the team!

However, I would like to take a moment and offer a few suggestions to the people who wish to work for this great and illustrious company:

PLEASE PLEASE PLEASE APPLY FOR THE JOB USING THE METHOD INDICATED IN THE AD. Please use our fancy, top-of-the-line, whiz-bang, cloud-based "talent acquisition" system that we paid way too much money for. I promise you, it's easy! Please don't send in your application by email, mail, telephone, Facebook, Twitter, Instagram, Snapchat, telegram or carrier pigeon. But most importantly...

FOR THE LOVE OF ALL THAT IS BEAUTIFUL IN THIS WORLD DO NOT SHOW UP AT OUR OFFICE UNANNOUNCED RESUME-IN-HAND. Believe it or not I do have an actual job that I spend my day doing! If I'm not in a meeting or at lunch or working from home, the best possible scenario is that you'll get 30 seconds of awkward small talk and be pointed to our whiz-bang, top-of-the-line "talent acquisition" system which you should have used in the first place (you did read the ad, right?). And at this point whatever you do...

DO NOT DEMAND AN ON-THE-SPOT INTERVIEW WHEN YOU SHOW UP UNANNOUNCED TO OUR OFFICE! Like, really? Do you think that you've wowed me so with your 30 seconds of awkward small talk that clearly I cannot wait to see what you will do with an entire hour? Look, I prepare for my interviews. I research you, your previous employers, your school and the hobbies you list on your resume. I check out your GitHub and LinkedIn. I may even Google your name! If that is all in order, I try to hassle some people into sitting in with me, find a time that works for everyone, and hope that there is a meeting room available. I'm not going to interview you at reception at 4pm on a Friday afternoon.

Please submit your application through our whiz-bang, top-of-the-line online "talent acquisition" system. Once I figure out how to log in, I promise I will spend an evening and read through all your cover letters with the utmost care. If you seem OK, you'll get an interview. There aren't that many developers in this town.

Back in the day, I joined a little agency in Cape Town, small team small office with big projects, projects they weren’t really supposed to take on but hey when the owner of a tech business is not a tech person they do weird things.
A month had passed and it was all good, then came a project from Europe, Poland to be specific. The manager introduced me to the project, it was a big brand - a segment of Lego, built on Umbraco (they should change the name to slowbraco or uhmmm..braco somewhere there) the manager was like so this one is gonna be quite a challenge and I remember you said you are keen on that, I was like hell yeah bring it on (genuinely I got excited) now the challenge was not even about complexity of the problem or code or algorithms etc you get my point… the challenge was that the fucking site was in polish - face palm 1 - so I am like okay code is code, its just content, and I already speak/familiar with 13 human languages so I can’t fail here ill get around it somehow. So I spin up IIS, do the things and boom dev environment is ready for some kick ass McCoding. I start to run through the project to dig into the previous dev’s soul. I could not relate, I could not understand. I could not read, I could not, I could not. - face palm 2 - This dude straight up coded this project in polish variable names in polish, class names in polish, comments in freaking polish. Look, I have no beef with the initial guy, its his language so why not right? sure. But not hey this is my life and now I should learn polish, so screw it, new tab - google translate, new notes, I create a dictionary of variables and class etc 
3 days go by and I am fucking polish bro. Come at me. I get to read the previous devs soul through his comments, what a cool dude, his code wasn’t shit either - huge relief. So I rock on and make the required changes and further functionality. 

The project manager is like really, you did it? I am like yeah dude, there it is. Then I realise I wasn’t the first on this, this dude done tried others and it didn’t go down well, they refused. - face palm 3 -

Anyway, now I am a rock star in the office, and to project managers this win means okay throw him in the deep - they move me to huge project that is already late of course and apparently since I am able to use google translate, I can now defeat time, let the travelling begin. - face palm 4 - I start on the project and they love me on it as they can see major progress however poland was knocking on the door again, they need a whole chunk of work done. I can’t leave the bigger project, so it was decided that the new guy on Monday will start his polish lessons - he has no idea, probably excited to start a new job, meanwhile a shit storm is being prepared for him.

Monday comes, hello x - meet the team, team meets x

Manager - please join our meeting.

I join the meeting, the manager tells me to assist the new dev to get set up.

Me: Sure, did you tell him about he site?

Manager: Yes, I told him you knocked it out the park and now we just need to keep going

Me: in my head (hmm… that’s not what I was asking but cool I guess he will see soon enough -internal face palm 5 - )

New dev is setup, he looks at the project, I am ask him if he is good after like an hour he is like yeah all good. But his face is pink so I figured, no brother man is not okay. But I let him be and give him space.

Lunch time comes, he heads out for lunch. 

1hr 15mins later, project manager is like, is the new dude still at lunch.

We are all like yeah probably. 

2hrs pass 

3hrs pass

Now we are like okay maybe something happened to him, hit by a car? Emergency? Something… 

So I am legit worried now, I ask the manager to maybe give him a ring. 

Manager tries to call. NOTHING, no response. nada.

Next day, 8am, 9am, 10am no sign of the dude. 

I go to the manager, ask him what’s up. 

Manager: he is okay. However he said he is not coming back. 


Bind's top {number} dev tools to make your 2018 easier!

//note 0: feel free to add your own
//note 1: no ides, only stuff thats useful for everyone

0) vscode, it got significantly better after the latest updates and is very versatile
1) gitkraken, now i use sourcetree because of the jira integration but kraken is available for linux too so
2) scaleway, they provide really cheap servers for whatever you want, easy to install images (docker too)
3) protonmail, an encrypted mail service that works a lot better than gmail (tutanota is a close 2nd but has a weeb name)
4) telegram, if you can, tell your team to ditch slack, because telegram is a lot more lightweight and even if you dont, just the channels make it worth giving it a shot
5) steemit, a blockchain based website where the users write the articles, you can find some good reads there (and photography if you like that stuff)
6) a dildo because it wouldnt be a bindview content without out of context penile objects

I'm sorry, but the Apple App Store review team sometimes doesn't have the slightest clue what they're doing. Some things they usually reject me for, I can literally name 100 apps that violate that same thing, that are ON the App Store.

But the one that always gets me the most, is they will reject your app for not having extremely strict blocking/reporting features in your app (if it involves user-generated content). Okay, I get this, so I implement it. But they reject my app without even looking for them.

It's a CHAT app, so I put the block button INSIDE the chat conversation (right? normal UX? am I crazy?), and they reject it because they couldn't find the block button on the first screen (a screen that didn't even have chats, they screenshotted the SIGN UP screen LOL).

What a joke. Normally I wouldn't care but this update that I'm trying to get approved is essential and fixes some important crashes that have been happening to 13% of active users.

One of our team members would write his name in a comment before and after every line of code he writes!
Like we got version control we can see the changes that have been made and by whom there is no need for this narcissistic behavior.

A dev team has been spending the past couple of weeks working on a 'generic rule engine' to validate a marketing process. The “Buy 5, get 10% off” kind of promotions.

The UI has all the great bits, drop-downs, various data lookups, etc etc..

What the dev is storing the database is the actual string representation FieldA=“Buy 5, get 10% off” that is “built” from the UI.

Might be OK, but now they want to apply that string to an actual order. Extract ‘5’, the word ‘Buy’ to apply to the purchase quantity rule, ‘10%’ and the word ‘off’ to subtract from the total.

Dev asked me:

Dev: “How can I use reflection to parse the string and determine what are integers, decimals, and percents?”
Me: “That sounds complicated. Why would you do that?”
Dev: “It’s only a string. Parsing it was easy. First we need to know how to extract numbers and be able to compare them.”
Me: “I’ve seen the data structures, wouldn’t it be easier to serialize the objects to JSON and store the string in the database? When you deserialize, you won’t have to parse or do any kind of reflection. You should try to keep the rule behavior as simple as possible. Developing your own tokenizer that relies on reflection and hoping the UI doesn’t change isn’t going to be reliable.”
Dev: “Tokens!...yea…tokens…that’s what we want. I’ll come up with a tokenizing algorithm that can utilize recursion and reflection to extract all the comparable data structures.”
Me: “Wow…uh…no, don’t do that. The UI already has to map the data, just make it easy on yourself and serialize that object. It’s like one line of code to serialize and deserialize.”
Dev: “I don’t know…sounds like magic. Using tokens seems like the more straightforward O-O approach. Thanks anyway.”

I probably getting too old to keep up with these kids, I have no idea what the frack he was talking about. Not sure if they are too smart or I’m too stupid/lazy. Either way, I keeping my name as far away from that project as possible.

Biggest challenge I overcame as dev? One of many.

Avoiding a life sentence when the 'powers that be' targeted one of my libraries for the root cause of system performance issues and I didn't correct that accusation with a flame thrower.

What the accusation? What I named the library. Yep. The *name* was causing every single problem in the system.

Panorama (very, very expensive APM system at the time) identified my library in it's analysis, the calls to/from SQLServer was the bottleneck

We had one of Panorama's engineers on-site and he asked what (not the actual name) MyLibrary was and (I'll preface I did not know or involved in any of the so-called 'research') a crack team of developers+managers researched the system thoroughly and found MyLibrary was used in just about every project. I wrote the .Net 1.1 MyLibrary as a mini-ORM to simplify the execution of database code (stored procs, etc) and gracefully handle+log database exceptions (auto-logged details such as the target db, stored procedure name, parameter values, etc, everything you'd need to troubleshoot database errors). This was before Dapper and the other fancy tools used by kids these days.

By the time the news got to me, there was a team cobbled together who's only focus was to remove any/every trace of MyLibrary from the code base. Using Waterfall, they calculated it would take at least a year to remove+replace MyLibrary with the equivalent ADO.Net plumbing.

In a department wide meeting:

DeptMgr: "This day forward, no one is to use MyLibrary to access the database! It's slow, unprofessionally named, and the root cause of all the database issues."
Me: "What about MyLibrary is slow? It's excecuting standard the ADO.Net code. Only extra bit of code is the exception handling to capture the details when the exception is logged."
DeptMgr: "We've spent the last 6 weeks with the Panorama engineer and he's identified MyLibrary as the cause. Company has spent over $100,000 on this software and we have to make fact based decisions. Look at this slide ... "
<DeptMgr shows a histogram of the stacktrace, showing MyLibrary as the slowest>
Me: "You do realize that the execution time is the database call itself, not the code. In that example, the invoice call, it's the stored procedure that taking 5 seconds, not MyLibrary."
<at this point, DeptMgr is getting red-face mad>
AreaMgr: "Yes...yes...but if we stopped using MyLibrary, removing the unnecessary layers, will make the code run faster."
<typical headknodd-ers knod their heads in agreement>
Dev01: "The loading of MyLibrary takes CPU cycles away from code that supports our customers. Every CPU cycle counts."
<headknod-ding continues>
Me: "I'm really confused. Maybe I'm looking at the data wrong. On the slide where you highlighted all the bottlenecks, the histogram shows the latency is the database, I mean...it's right there, in red. Am I looking at it wrong?"
<this was meeting with 20+ other devs, mgrs, a VP, the Panorama engineer>
DeptMgr: "Yes you are! I know MyLibrary is your baby. You need to check your ego at the door and face the facts. Your MyLibrary is a failed experiment and needs to be exterminated from this system!"

Fast forward 9 months, maybe 50% of the projects updated, come across the documentation left from the Panorama. Even after the removal of MyLibrary, there was zero increases in performance. The engineer recommended DBAs start optimizing their indexes and other N+1 problems discovered. I decide to ask the developer who lead the re-write.

Me: "I see that removing MyLibrary did nothing to improve performance."
Dev: "Yes, DeptMgr was pissed. He was ready to throw the Panorama engineer out a window when he said the problems were in the database all along. Didn't you say that?"
Me: "Um, so is this re-write project dead?"
Dev: "No. Removing MyLibrary introduced all kinds of bugs. All the boilerplate ADO.Net code caused a lot of unhandled exceptions, then we had to go back and write exception handling code."
Me: "What a failure. What dipshit would think writing more code leads to less bugs?"
Dev: "I know, I know. We're so far behind schedule. We had to come up with something. I ended up writing a library to make replacing MyLibrary easier. I called it KnightRider. Like the TV show. Everyone is excited to speed up their code with KnightRider. Same method names, same exception handling. All we have to do is replace MyLibrary with KnightRider and we're done."
Me: "Won't the bottlenecks then point to KnightRider?"
Dev: "Meh, not my problem. Panorama meets primarily with the DBAs and the networking team now. I doubt we ever use Panorama to look at our C# code."

Needless to say, I was (still) pissed that they had used MyLibrary as dirty word and a scapegoat for months when they *knew* where the problems were. Pissed enough for a flamethrower? Maybe.

Today a new person joined the team.

Started bitching about the entire team for not having documentation for our already written code and software.

Asks the manager for a new task that he can take up so that he can write documentation for all our already coded works.

Manager says Go On.

Troubles me with 400 questions every 3 minutes in the name of Knowledge Transfer for writing his documentation.

Sends a proud mail to the team for writing this new documentation that no one else had time to do.
He is a newbie and had no other task to do anyway.

I seriously don't know if I should feel proud of him, for writing new documentation,
Or if he's doing this to defame me.

The team is filled with snakes.

I need some advice: How could you stop laughing at a meeting? Help!

Yesterday, in a meeting with the development team, my boss accidentally wrote "Puto System" on the board (of course, I cannot post the real name of the project). For those who don't speak spanish, "Puto" means "asshole".

Oh, I laughed so fucking hard XD Well, we continued with the meeting, but I couldn't stop laughing, and then, I was going to ask a question about one of my tasks, and accidentally said "hard" instead of "boubt" (in spanish "dura" instead of "duda") and all of us laughed again.

At the time I'm writing this post I can't remember that without laughing, help! I need to get serious :'v

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.

Inappropriate experience at work: One of our project managers got arrested one day for fraud. Apparently an employee had been in the middle of an online purchase and walked away from their desk. He happened to see the unmasked entry of the CC info (this was before websites cared about masking sensitive form inputs). I guess the temptation was too great…and he was too stupid to realize he’d get caught…and he jotted it all down. He made thousands of dollars in purchases which, naturally, eventually led back to him.

The same guy, before he got arrested, had made a joke when someone in an office team email said “Feel free to have some cake in the break room.” He replied “No need to do anything to me for the cake.” His first name was “Free”.

Red flags in your first week of your software engineering job 🚩

You do the first few days not speaking to anyone.
You can't get into the building and no one turns up until mid day.
The receptionist thinks you're too well dressed to work in this building, thinks you're a spy and calls security on you.
You are eating alone during lunch time in the cafeteria
You have bring your own material for making coffee for yourself

When you try to read the onboarding docs and there aren't any.
You have to write the onboarding docs.

You don't have team mates.
When you ask another team how things are going and they just laugh and cry.😂😭

There's no computer for you, and not even an "it's delayed" excuse. They weren't expecting you.
Your are given a TI PC, because "that's all we have", even though there's no software for it, and it's not quite IBM compatible.
You don't have local admin rights on your computer.💀
You have to buy a laptop yourself to be able to do your job.

It's the end of the week and you still don't have your environment set up and running.
You look at the codebase and there are no automated tests.
You have to request access every time you need to install something through a company tool that looks like it was made in 2001.

Various tasks can only be performed by one single person and they are either out sick or on vacation.
You have to keep track of your time in 6 minute increments, assigned to projects you don't know, by project numbers everyone has memorised (and therefore aren't written down).
You have to fill in timesheets and it takes you 30 minutes each day to fill them in because the system is so clunky.🤮

Your first email is a phishing test from the IT department in another country and timezone, but it has useful information in it, like how to login to the VPN.
Your second email is not a phishing test, but has similar information as the first one. (You ignore it.)
Your name is spelled wrong in every system, in a different way. 2 departments decide that it's too much trouble, and they never fix the spelling as long as you work there. One of them fixes it after you leave, and annoys you for a month because you haven't filled out the customer survey.

This is my classmate's team name

No copyright infringement intended

team lead: what is the minimum lenght validation on the first name field?
dev: i decided to put minlenhgt 3
team lead: why? did you tests it
Dev: i tested it. 3 makes sense to me
Team lead: isint your first name 2 letters long?
Dev: oh i dodth think about that

Please allow me to share my thoughts since I can't totally outrage my frustration because we have this so-called fasting to control our anger towards a person we currently disagree with.

A letter from your loving, sincere, pretty and gorgeous working partner to my young, chubby, smart and clever colleague:

Please do cooperate in times of live editing from the FTP since CTO is not and will never be going to appreciate version control since CTO is too tired for giving a shit and just want deliverables be delivered as fuck perfectly regardless of the resources that we have.

As you know, I tolerated you for not getting the freedom of live editing as what you've experienced from your previous team lead. All I ask of you is to get fresh file from FTP whenever we touch the same file because firstly, God knows how frustrating it is how your hard work is going to be replaced and be gone as much as I do. Secondly, I don't want you to experience how pain in the ass could this be in the long run, and lastly, I don't want any hard feelings to be wasted just because of this.

P.S. I'm too shy to send this to you because I don't want to hurt your feelings and don't want to sound too seriouz and feel old. I also hope we share the same telepathic understanding so we can agree with each other.

Your loving, sincere, pretty and gorgeous working partner,
xoxo ❤️

(thinking of stating my first name) 😂

I started recently working for a big company, and when I say big, I mean really BIG.

Well, my colleagues are from different parts of the world, of course some names are harder to pronounce, so, let's say your name is 'Yagarishmakeshin', well, sometimes is easier(and I used to think friendly) to call you by a shorter name, for this example let's say 'Yag', you know, like Apu form the Simpsons, which is normal I think, people use to call me always by shorter names too and is fine.

Well, yesterday I received a complain from HR saying some people complain about this, it turns out this is offensive or degradating; I was also warned about not calling a girl 'girl', example:

- random girl at my team - So, I created this routine which is very effective and provides good performance
- me - Awesome girl, very cool

Well, Someone complain I call them 'girl' and is not fine.

I cannot tell you how frustrated I feel about this, is like, if you feel uncomfortable with a short name, just say it to me, something like 'Hey I prefer you call me by my full name' or something like that, but nah, you prefer to raise a complain like if I were a fucking predator or something; Also, I cannot retaliate or mention the topic, I need to change and pretend nothing happened.

Fuck you big corporations, and fuck you skinny stupid bitch

devRant is awesome, but Disney also manages to light-up my day.
This is how Wall-E became a beloved member of our team, and helped me put a smile on my face throughout a very frustrating project.

It all started in a company, not so far far away from here, where management decided to open up development to a wider audience in the organization. Instead of continuing the good-old ping-pong between Business and IT...

'not meeting my expectations' - 'not stated in project requirements'
'stuff's not working - 'business is constantly misusing'
'why are they so difficult' - 'why don't they know what they really want'
'Ping, pong, plok... (business loses point) ping, pong'

... the company aimed to increase collaboration between the 2 worlds, and make development more agile.

The close collaboration on development projects is a journey of falling and getting back up again. Which can be energy draining, but to be honest there is also a lot of positive exposure to our team now.
The relevant part for this story is that de incentive of business teams throughout these projects was mainly to deliver 'something' that 'worked'. Where our team was also very keen on delivering functionality that is stable, scalable, properly documented etc. etc.
We managed to get the fundamentals in place, but because the whole idea was to be more agile or less strict throughout the process, we could not safeguard all best-practices were adhered to during each phase of a project. The ratio Business/IT was simply out of balance to control everything, and the whole idea was to go for a shorter development lifecycle.
One thing for sure, we went a lot faster from design through development to deployment, high-fives followed and everybody was happy (for some time).
Well almost everybody, because we knew our responsibility would not end after the collection of credits at deployment, but that an ongoing cycle of maintenance would follow. As expected, after the celebrations also complaints, new requirements and support requests on bug fixes were incoming.
Not too enthusiastic about constantly patching these projects, I proposed to halt new development and to initiate a proper cleaning of all these projects. With the image in mind of a small enthusiastic fellow, dedicated to clean a garbage-strewn wasteland for humanity, I deemed "Wall-E" a very suited project name. With Wall-E on board, focus for the next period was on completely restructuring these projects to make sure all could be properly maintained for the future.
I knew I was in for some support, so I fetched some cool wall papers to kick-start each day with a fresh set of Wall-E's on my monitors. Subsequently I created a Project Wall-E status report, included Wall-E in team-meetings and before I knew it Wall-E was the most frequently mentioned member of the team. I could not stop to chuckle when mails started to fly on whether "Wall-E completed project A" or if we could discuss "Wall-E's status next report-out". I am really happy we put in the effort with the whole team to properly deploy all functionality. Not only the project became a success, also the idea of associating frustrating activities with a beloved digital buddy landed well in our company. A colleagues already kickstarted 'project Doraemon', which is triggering a lot of fun content. Hope it may give you some inspiration, or at least motivate you to watch Wall-E!

PS: I have been enjoying the posts, valuable learnings and fun experiences for some time now. Decided to also share a bit from my side, here goes my first rant!

Do you have a ‘Drama Queen’ on your team?
This happened last week.
DK = Drama Queen
DK: “OMG..the link to the document isn’t working! All I get is page not found. I’m supposed to update the notes for this project…and now I can’t! What the _bleep_ and I supposed to do now?!...I don’t understand how …”
This goes on for it seems 5 minutes.
Me: “Hold on...someone probably accidently mistyped the file name or something. I’m sure the document is still there.”
DK: “Well, I’ll never find it. Our intranet is a mess. I’m going to have to tell the PM that the project is delayed now and there is nothing I can do about it because our intranet is such a mess.”
Me: “Maybe, but why don’t you open up the file and see where the reference is?”
DK: “Oh, _bleep_ no…it is HTML…I don’t know anything about HTML. If the company expects me to know HTML, I’m going to have to tell the PM the project is delayed until I take all the courses on W3-Schools.”
Me: “Um…you’ve been developing as long as I have and you have a couple of blogs. You know what an anchor tag is. I don’t think you have to take all those W3 courses. It’s an anchor tag with a wrong HREF, pretty easy to find and fix”
DK: “Umm…I know *my* blog…not this intranet mess. Did you take all the courses on W3-Schools? Do you understand all the latest web html standards?”
Me: “No, but I don’t think W3 has anything to do the problem. Pretty sure I can figure it out.”
DK: “ha ha…’figuring it out’. I have to know every detail on how the intranet works. What about the javascript? Those intranet html files probably have javascript. I can’t make any changes until I know I won’t break anything. _bleep_! Now I have to learn javascript! This C# project will never get done. The PM is going to be _bleep_issed! Great..and I’ll probably have to work weekends to catch up!”
While he is ranting…I open up the html file, locate the misspelling, fix it, save it..
Me: “Hey..it’s fixed. Looks like Karl accidently added a space in the file name. No big deal.”
DK:”What!!! How did you…uh…I don’t understand…how did you know what the file name was? What if you changed something that broke the page? How did you know it was the correct file? I would not change anything unless I understood every detail. You’re gonna’ get fired.”
Me: “Well, it’s done. Move on.”

I really wonder who is that genius from API team who decided that a namespace with the name "main" is a great fucking idea...

Because of this shit I've had to resort to hacky pImpl implementation of the API.

Update on my old rant: I started writing type definitions for our project (it's basically a chunk of separate files where you document the objects you use; typed languages have this out of the box, js doesn't and it may become useful depending on the size of the project). Our codebase is reasonably big -not complicated, but big- and I felt like I was losing track of all the properties\objects\usage\comments\whatever. So I iiterally wrote some ts interfaces: properties with name and types, that's it, so you know what you're passing around.
Proposal was denied, I'll have to delete the documentation; "keeping the doc updated is going to require more work".

Me: Ok, but what am I supposed to do when I need to interface with your code? Run the debugger and figure out what the fuck you guys are passing around?
Team leader: Yes 😊

I get frustrated when I get reports from the support team/clients

"[insert application name here] is not working"

thats all no information on which module or segment ... 😭😭

then I just waste time getting all the information ...

When i worked for a large, international bank (whose name rhymes with shitty), I always had to use the following formula to estimate projects.

1. Take estimate of actual work
2. Multiply by 2 to cover project manager status reports
3. Multiply by 4 to cover time spent in useless meetings.
4. Multiply by 2 to cover user support and bug fix tasks.
5. Multiply by 2 to cover my team lead tasks.
6. Multiply by 3 to cover useless paperwork and obtaining idiotic necessary approvals to do anything
7. Finally, multiply by 3.14159 to cover all the other stupid shit that the idiots that run that company come up with.

It's only a slight exaggeration. Tasks that required less than a day of actual coding would routinely require two weeks to accomplish and get implemented.

git push origin stupid-long-feature-name
git pull origin develop
*Checks through all changes. No major conflicts. Accepts changes.*
npm test
*4 failing tests, none of them in pieces that I touched for my feature.*
*That's funny. QA was loaded from the develop branch, and everything works.*
*Actual data has dates from today. Expected data has dates from a week ago.*
*examines tests*
Why are all these expected dates hard-coded‽

tl;dr The external development team committed 4 tests that would only ever pass on the day they were written.

My former team had an "ux expert" who made ux templates for new features.

For years since he started his job, the team was told that there will be a first face-2-face meeting.

It never came to this point.

Instead all the team know about this guy is that his name is Thomas and that he does all the talk and decisions with our client without a word with the team, bringing their imaginations to li(f|v)e...

Genius! xD

No wonder the team got mad after some water had ran down the river.
At first they only questioned really poor design decisions.
But after a while the productivity of the team dropped, because they weren't willing to accept any of those design decisions.

Boi o boi.
Things escalated pretty well ;)

So one year ago, when I was second year in college and first year doing coding, I took this fun math class called topics in data science, don't ask why it's a math class.

Anyway for this class we needed to do a final project. At the time I teamed up with a freshman, junior and a senior. We talked about our project ideas I was having random thoughts, one of them is to look at one of the myths of wikipedia: if you keep clicking on the first link in the main paragraph, and not the prounounciation, eventually you will get to philosophy page.

The team thought it was a good idea and s o we started working.

The process is hard since noe of us knew web scraping at the time, and the senior and the junior? They basically didn't do shit so it's me and the freshman.

At the end, we had 20000 page links and tested their path to philosophy. The attached picture is a visualization of the project, and every node is a page name and every line means the page is connected.

This is the first open project and the first python project that I have ever done. Idk if it is something good enough that I can out on my resume, but definitely proud of this.

PS: if you recognize the picture, you probably know me. If you were the senior or the junior in the team, I'm not sorry for saying you didn't do shit cuz that's the truth. If you were the freshman, I am very happy to have you as a teamate.

Ever want to smack someone in the face with a sea bass? Like left out of the water for 3 days with all kinds of juicy and smelly goodness?
When we get an X number system errors, an email is sent to our team. Couple of hours ago I had to move the alerts from one system to another, re-naming some because I suck at naming things. I guess when I copied, I duplicated one. About an hour ago we get a system alert (as it should, there was a server hiccup) and there were two emails with the same data (just named differently)
DevA: “Why are there two emails?”
Me: “Oh, that’s me. I think I copied the alert instead of move. I’ll fix it tomorrow.”
DevA: “Hmm, but the data is the same. It’s a duplicate.”
Me: “Yea, I know. Networking responded and said it’s fixed. We won’t get another email.”
- 15 minutes later
DevA leans over and says to the boss (who was in a meeting and just sat down)…
DevA: “I looked at the alert, it’s duplicated, but the name is different. I don’t understand why.”
Me: “Like I said, the alert is duplicated. When I migrated, I copied instead of moved. No big deal.”
DevA: “Oh …oh ..yea.…OK.”
- 5 minutes later
DevA: “I looked at the query, we might have to add a filter to prevent duplicate emails. Probably some logic problems in the search.”
Me: “I just deleted the duplicate alert.”
DevA: “Oh…OK…that fixes it too.”

Good lord…as I was typing this, he just told another dev the ‘duplicate’ emails were because of a logic bug in the search. I’m getting my fishing pole.

Read the following in Morgan Freeman’s voice.

Okay everyone sit on down and get ready for story time. There once was a workspace that was a pain in the ass to setup. It often would take an entire day even for the most experienced devs on the team...for it was a workspace perched atop a swamp of shit that would require a whole year to refactor into something that isn’t shit.

It was inherited, passed down, stepped in and scrapped from the boot soles of every programmer that ever touched it. It was an amalgam of old, new, and third party components with a class path a mile long and no package management because the company although physically in the present, somehow maintained a temporal presence in the past. And there was nothing that the team hated more than setting that workspace. In short it was an unholy mess that made Satan cry and Dennis Ritchie spin in his grave so much that the state of California attached magnets and a coil to his body and casket to generate electricity.

Then one day the untalented clowns known as App Group decided that our IDE should be owned and configured strictly through them. They took poor Eclipse and mounted so much silly shit to it that it resembled a riding lawn mower with a fax machine and a blender duct taped to it. Eventually as everything the company touched did, it simply turned into a broken, shitty mess that not even Jesus Titty Fucking Christ could bring back the dead.

And then, every month or so the IDE would break in such a grand way that every developer had to rebuild their workspace...the very same Lovecraftian monster disguised as a code base. It was just too much to bear for old Deus. He was all out of fucks and there wasn’t enough alcohol in the world to quiet his injured soul. So he stood on a chair, carved his name in a rafter and tied a noose to it, put it around his neck and finally kicked the chair out from under himself. I am told he even pooped his pants and the post mortem shit in the seat of his pants was still better than the codebase at work. I’m Morgan Freeman.

Reported an important security vulnerability inside our organization, right before getting off work. A security team member contacts me over chat asking for some details on my investigation. At the end, he tells me: "thanks, I will copy and paste this conversation on the ticket so that everyone can see".

What I imagined: he would copy and paste the conversation as is, so that every line written by me is prefixed with my name.

What he does: he writes a summary of our conversation, barely mentioning my name, making it look like that part of the investigation was done by him.

Now I have so much anger inside of me that my internal organs are boiling.

Look here sir. If I have raised 12 defects on the feature you were working on its not a personal attack... I am not trying to publicly humilate you or doubting your ninja coding skills. We are on the same team. Just trying to make a better product that's my job as qa. So chill out with passive aggressive comments on the tickets.

You don't hear me making a peep when you take my name and say I missed the issue if someone higher up points out the same defects.

The stupidest technical question I have ever been asked is actually more of a design question, but I think it'll appeal to DevRant people.

I had thrown together a logo for a new system that my team was making. The logo was basically a flat, solid circle of our corporate shade of blue, with the name of the product overlaid in Helvetica Light. It looked okay. Ish. Good enough, anyway.

Our junior-most senior manager came to have a look. She was the sort of person who always had to give feedback, on EVERYTHING. Everyone had given this little logo the nod, but she had to stare at it for ages, and then eventually asked:

"I like the text, but can you rotate the circle a few degrees?"

.
.
.

After an awkward pause I'm pleased to report that she realised her own mistake and we laughed it off, so I was not forced to stand up, point at her, and yell "DURRRRRRRRRR".

Worst documentation I've seen?

Our "Coding Standards" 20+ page document. The team who put it together got so detailed, there wasn't much 'wiggle room' for natural deviations in a developer's coding style. For example, a section devoted to no abbreviations. So if you had a variable 'invoiceId', they complained you violated 'standards', even though 'invoiceId' matched a field name in a database table. Using Dapper or another ORM that relied on the 1:1 name match? Nope, you were still forced to inject your own mappers so the code didn't violate standards.

As you can probably guess, such a long, detailed document would have contradictions. I pointed out one of the contradictions. Example:

Page 5: Section B, sub-section B-5, paragraph 3 : "To minimize network traffic, when querying the database, request all the data necessary for the application."
Page 8: Section K, sub-section K-2, paragraph 4 : "For maximum performance, when querying the database, request only the most minimum amount of data necessary for the application ."

In a review I pointed out this contradiction (there were several more)
Me: "If we satisfy A, one could say the code is in violation of B. Which is it?"
<Pointy-Hair-Boss throws his pencil on the table>
PHB: "WHAT IS YOUR PROBLEM WITH STANDARDS! It couldn't be more clear! We are a company of standards because without standards <blah blah..straw man argument..blah blah>"
<deciding not to die on that hill, I move on>
Me: "On page 12, paragraph 9 code is in violation if a method has more than 3 parameters. That seems a little restrictive given our interaction with 3rd party products."
PHB: "There you go again. As stated in the document, ALL code used by the company will comply to our standards. What part of 'ALL' do you not understand?"

Was he bluffing about requiring 3rd party vendors complying with our standards? Heck no. That's a story for another day.

I never thought clean architecture concepts and low complicity, maintainable, readable, robust style of software was going to be such a difficult concept to get across seasoned engineers on my team... You’d think they would understand how their current style isn’t portable, nor reusable, and a pain in the ass to maintain. Compared to what I was proposing.

I even walked them thru one of projects I rewrote.. and the biggest complaint was too many files to maintain.. coming from the guy who literally puts everything in main.c and almost the entire application in the main function....

Arguing with me telling me “main is the application... it’s where all the application code goes... if you don’t put your entire application in main.. then you are doing it wrong.. wtf else would main be for then..”....

Dude ... main is just the default entry point from the linker/startup assembly file... fucken name it bananas it will still work.. it’s just a god damn entry point.

Trying to reiterate to him to stop arrow head programming / enormous nested ifs is unacceptable...

Also trying to explain to him, his code is a good “get it working” first draft system.... but for production it should be refactored for maintainability.

Uggghhhh these “veteran” engineers think because nobody has challenged their ways their style is they proper style.... and don’t understand how their code doesn’t meet certain audit-able standards .

You’d also think the resent software audit would have shed some light..... noooo to them the auditor “doesn’t know what he’s talking about” ... BULLSHIT!

Fuck you google android IME team and fuck their open source policy..

So recently i had a chance to work with AOSP LatinIME code, basically our Android keyboard was forked from very old code base of LatinIME and my job was to change its base version to latest Version available on AOSP repository. Downloaded latest Android 8 codebase. Did 2 weeks of deep investigation of what improvements we will get from upgraded code base.

And I came to know that those Google fucking cunt sucking dick heads deprecated that project and broke the whole thing to a pice of shit. Half of the code is broken with fucked up todo stuff and motherfucking missing method implementation with not implemented warnings. What those motherfucker did is that they abandoned the open-source project after they released Google GBoard, and fucked the stable code by adding quard gram support and dictionary download with multi account features which was never completed by those motherfuckers..

Those misguiding donkey shit fuckers kept a depreciated project in AOSP build tree which has not received a single fucking commit from shitty ass Google IME team, is said to be reference model of Android IME implementation..

What kind of fucking shit is going with open-source code in name of making competition high with thirt party Android keyboard developers ..

Fucking shit fucking ime team .. fuck you .. wasted my fucking time reading your shitty code base .. Fucking shit

Still dealing with the web department and their finger pointing after several thousand errors logged.

SeniorWebDev: “Looks like there were 250 database timeout errors at 11:02AM. DBAs might want to take a look.”

I look at the actual exceptions being logged (bulk of the over 1,600 logged errors)..

“Object reference not set to an instance of an object.”

Then I looked the email timestamp…11:00AM. We received the email notification *before* the database timeout errors occurred.

I gather some facts…when the exceptions started, when they ended, and used the stack trace to find the code not checking for null (maybe 10 minutes of junior dev detective work). Send the data to the ‘powers that be’ and carried on with my daily tasks.
I attached what I found (not the actual code, it was changed to protect the innocent)
Couple of hours later another WebDev replied…

WebDev: “These errors look like a database connectivity issue between the web site and the saleitem data service. Appears the logging framework doesn’t allow us to log any information about the database connection.”

FRACK!!...that Fracking lying piece of frack! Our team is responsible for the logging framework. I was typing up my response (having to calm down) then about a minute later the head DBA replies …

DBA: “Do you have any evidence of this? Our logs show no connectivity issues. The logging framework does have the ability to log an extensive amount of data regarding the database transaction. Database name, server, login, command text, and parameter values. Everything we need to troubleshoot. This is the link to the documentation …. If you implement the one line of code to gather the data, it will go a long way in helping us debug performance and connectivity issue. Thank you.”

DBA sends me a skype message “You’re welcome :)”

Ahh..nice to see someone else fed up with their lying bull...stuff.

Oh, $work.

Ticket: Support <shiny new feature> in <seriously dated code> to allow better “searching” (actually: generating reports, not searching)

UI: “Filter on” inputs above a dynamic JS table don’t update said table; they trigger generating a new report.

Seriously dated code: 12 years old. Rails v3-isms. Blocks access without appropriate role; role name buried in secrets configuration files. Code passes data round-trip between server/client/server/model that isn’t ever used. Has two identical reports with slightly different names, used interchangeably. Uh, I guess I’ll update both?

Reports: Heavily, heavily abstracted; zero visibility.

Shiny new feature: Some new magical abstraction layer with no documentation nor comments. Nobody in my team knows how it works. The author… won’t explain, but sent me her .ppt presentation on it (the .ppt, not a recording).

Useless specs for seriously dated code: Tests exclusively factory-generated data; not the controller, filters/lookups, UI, table data, etc.

Seriously dated code and useless spec author: the CISO.

The worst part: I’m not even surprised at any of this.

Today my boss decided to sit in the same table that his team works (me included) he said that he will take a call and apologized in advance because he will "rant". I didn't get it until I Google it and found the name meaning of this app.

Our IT-Class project: Mathematics trainer in Java
Day 1 (was monday)

TL;DR we didn't save.

So we formed groups and I landed in the UI team with, let's call him Mage and let's call her Goth.

We had an eclipse project folder on our desktop (they said it only works when put on desktop) Btw they didn't even want to use a cloud or something (I wish we'd use git and I'd finally learn it). We should take the changes by USB from computer to computer.

So me, Mage an Goth are making a basic GUI for this Mathematic-Training App. We use this thing from Eclipse but I forgot the name. It has not enough functionality on surface and I hate things that break complex things up to ease things but leave away so much.

So after a productive hour of building a GUI and centering shit by calculating the top and bottom distance and use margins (hurts me really but Mage was designing, Goth intensively calculating on paper), the bell rings.

Mage wants to save the project on my USB-Stick and bamm💥
A black screen.
I don't know how it happened but it sure had something to do with the USB-port looking like you fucked it with a way to huge🍆. It looked damn broken.

So because we have a nice App called HD-Guard, which fucking wipes the desktop on startup and resets all but the documents/images/videos/music folder —

It's all's gone. Today is day 2 of this project so let's see how today turns out.

When I started off working on this particular project under a new technical manager, I used to love working overtime because the work and the problem we were trying to solve was really interesting. My technical lead was also a really awesome dude and I was able to learn a lot of things under his guidance. A couple of times, I didn't even mind working on the weekends too in case we wanted to meet some strict deadlines. I wanted to make sure that my team's brand name does not get spoiled and we deliver on what we promise.

It was all good until all the management started taking our overtime and weekend work for granted. It took me some time to realize this. Now it almost became a part of standard expectations. It was getting irritating. Managers could see this uneasiness but chose to do nothing.

The work increased, so did the team and the communication channels. The newbies in the team now worked overtime and on weekends. And everybody started acting as if it was normal. That's when it stuck me that I am responsible for inculcating this unsustainable and life sucking culture in the team. I stopped working overtime and started questioning the set deadlines, often asking them to postpone things. Management got furious and changed their focus on the newbies who'd work overtime, often rewarding them to reinforce the behavior.

I tried undoing it, asking managers that the team will not work on weekends. There was friction and managers would agree but the old bad habited cultural spore would pop up tume and again and the team would go back to the regular overtime and working weekends thing. As more time passed, the managers would circumvent me and start talking to others in the team, giving them work and deadlines directly because I started to say 'No' when I felt the need to do so. I tried to protect some folks in the team who would not be able to speak up but were frustrated. I started caring less about the team's brand and more about colleagues who were suffering due to such unethical (and illegal?) practices being normalised in the team.

Trying again and again to get back to 'normal', I failed everytime. Unsure of how far I'll be able to go on with this without getting severly burnt in the process and seeing no respite, I decided to move on. I put in my resignation two weeks back and want to start a fresh in another company.

I feel I am responsible for bringing this into the team without realizing the repurcussions of my working overtime. Staying in the team for more than 3.5 years, I could actually feel how managers have no fucks about your personal life and work life balance (despite showing oh so much concern about the well being of my family) and would reward anyone who works as per their whims and fancies. I wish I never get to work for a management such as this.

Got demoted, got a pay raise and don't know how to feel about it. A story of how not to drink with your coworkers?

The story begins roughly 8-9 months ago. Me and this coworker (let's name him Tim) go out drinking after a Friday party at the office. We do some rounds and we're both smashed. Tim starts telling me how he's happy with life and that he's earning a nice salary right now. He told me his salary. It was the same as mine. Which was weird - He codes in a more hardcore languages than me and has almost double the time in the company as me. I think after some more drinking I've confessed that I make the same as him. This part is sort of a blur (drinking). I've gotten a pay raise(+30-40%) roughly a few months ago from that point backwards because another company gave be a much higher offer. The company I work for matched to keep me. Anyway, 3 months or so after the drinking,Tim is promoted to team lead, and me and a few other people are added to his team. Conversation slips and he told me his new salary - quite a bit more than me.I think it's safe to assume what happened.

The problem with that is that I was a team lead of 1 person (me) at that time, and I was managing my own time and my own tasks, was working with people individually. I was part of the weekly meetings with the CEO and other team leads. Being stripped of this title wasn't a problem at the beginning, as people still contacted me because of their problems, suggestions, whatever. A few more months pass (to now) and less and less people are contacting me - instead they are talking with Tim, and are asking of his opinion on tasks I should do, where he has no experience and roughly 0 lines in the programming language I code in. This is starting to piss me off.

There are a couple other things to take into consideration as well - The company is hiring a lot of people right now. The whole structure for team leads changed a bit, more team leads then ever right now and new roles added pretty fast.

I've gotten a pay raise a few weeks ago though(10%~).

I'm not sure on how to react to this. Should I comply and just keep on working on these tasks? Or should I still keep contacting people directly on their requests and talk to them directly, take credit for the projects I complete publicly and the stuff I do as I was previously doing? Part of me wants to reroute all of the stupids questions people have to Tim, as he is now responsible for these tasks and get this weight off my shoulders.

I'm starting to shift to learning a new programming language and thinking of jumping ship. Thoughts?

Customer complains that the deployed desktop app is slow at site x.
I check it out with users at site x, and indeed, it does have a delay when trying to connect to a share on a server.
Checks with users at site y and z, no issues.
After a bit of digging, the resolve of a DNS record is most likely the culprit.
Send the ticket to the customer network team to investigate.
Get it back after an hour.

"We have pinged the DNS name, and it responds fine, there must be a bug in the application".

Oh and also, I wrote this rant at work, in my head, with a lot more cursewords involed.

So when I joined the company 2 months ago I was told they offered flexible working, today I received this email. (I can't help but think it is aimed at me given I often arrive between 9 and 10....I'm always the last to go home)

Oh and yes they have named some of the team DevOps and others just Developers, they haven't quite grasped the concept!
-----------------------------------------------------

Morning All,

I have been noticing the start time for all the team members. Some like to start early while some likes the late start. So before Senior management raises any questions below is the shift pattern I would like everyone to stick to it.

I have assigned name against each of the shift which I am aware of. If you would like to change it please let me know. We need at least one Developer between 08:00- 17:30 and at least one Devops between 07:00 – 17:30.

If we have any emergency issues and takes longer to fix it , I would appreciate if you guys can work after your shift. We can adjust this overtime by leaving early next day or whenever possible.

7:00 – 15:30 - @Michael Smith
7:30 – 16:00 - @Sarah Twist @Jim Bob
8:00 – 16:30 - @Lesley Matthews
8:30 – 17:00 - @Bill Best
9:00 – 17:30- @Jennifer Rowe @me!
9:30 – 18:00

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.

"Hey {name}",

I see you did this raspberry pi project and this is why we called you in for an interview.

Have you done any projects that's relevant to the company? Because your pi project isn't exactly what we're looking for

I know we advertised back end and front end roles for this position. You would be ideal for the front end position ...but our team is backend and the front end position would be at another office

I am so frustrated with companies like these

I want to share this story and need your advise.

When I was teaching exisiting team members about git and new iOS development ecosystem. I was changing the whole ios development practices and processes that time. One of my teammates wasn’t listening, when implementing the new ios development practices and standards, he actually screwed all of the projects.

He’s been with us for 2 years and he even don’t know how to use git. He forcefully push his changes without pulling our changes first. I was so angry that I reported him to my manager to address this matter. And then my manager told me, he is aware of my teammate’s incapabilities. He said he was planning to terminate him, and he is been thinking about it for 3 months.

When the judgement day came, we were in the meeting room. My manager told us the bad news that one of us will be terminated. During the meeting he said, “I am sorry, {my teammate’s name}. You will be out of the team due to {reason of termination}. {my name} reported to me that you dont meet the deadline, you are always late with 2 weekly sprint to your tickets”. As my manager keeps talking, my teammate look at me with his eyes so angry together with his girlfriend (her girlfriend is part of mobile team, but she is focused on UI/UX).

After my manager stops talking, her girlfriend started crying and said I was the one who should be terminated. Her reason was that I keep on giving difficult tasks to his boyfriend, that’s why he is always late to report. In my defense, those tasks are not difficult, most of his tasks is just changing the color of labels, changing layouts. If you are an iOS developer you know how easy it is to change font colors, changing the layouts using storyboards. Her girlfriend keeps on rambling that I should be the one needs to be terminated.

After few days, he left the team and surprisingly his girlfriend stayed and we never talk to each other except anything about work.

I am really pissed guys. Now my teammates think I am the bad guy asking my manager to terminate anyone in the team if I feel to. I feel very very not good in my work now. I can’t function what I used to. The termination of my teammate was already planned why am I should take the blame?

So lets start here, as i have been preparing myself for a while for that rant. I have been putting it off for a while, but today I had enough.
Fuck react-native and fuck facebook react-native team. Bunch of lazy incompetent twats.
The all amazing framework that suppose to be speed up your development process, since you don't have to compile your code after each change. SO FUCKING WHAT if the god damned framework is so fucking buggy and so fucking shit that you constantly have to fix build, dependancies etc issues. Every day since I work on this project that is using react-native I have to deal with some of the react fucked up behaviour. You got an issue ? don't worry google it just to find out that 100 other people had the same issue. Scroll through down the bottom of the page just to find out that facebook devs have closed the issue as resolved (without fucking fixing it) because there wasnt recent replies to the post. Are you fucking kidding me? It's ok thou, create a new issue just to get an automatic reply from the bot that locks the thread and keeps it locked till you update your React-native version to the newest one. You do that and guess fucking what? Their newest version fucks up remote debugging on iOS(fucking android been broke for over a year) so say good bye to debugging your js code. Documentation is fucking trash. You found a nice function like autoCaptialise on your text input? Great! Ah wait, its not fucking working, what is wrong? You google this just to fucking found out it, function never worked on android, so why the fuck you still have it exposed and still have it in your docs? You want to add package? So fucking ez, just type npm install <name of the package>. Ha! fuck you, you still have to go and add them fucking manually in gradle in android and in pod in xcode, because obviously react-native is a one big fucking bullshit. Oh and a scroll view is a fucking glorious highlight of that framework, try add some styling to it, you gonna have loads of fun. Fuck react-native. And fuck the fucking idiot who convinced my boss that framework is so fucking great and now I have to work on this shit. Sincerely Xamarin Developer.

Founder : You have been appointed as intern and will be working with our web and Backend engineering team.
Me:(excited)updates LinkedIn profile to 'web developer intern at {{name}}'
Founder: You have misrepresented your internship, pls remove web developer intern.
Me: (What? confused) Updates LinkedIn to 'Intern at {{name}}'
LinkedIn : Congratulate {{me}} for been promoted as intern at {{name}}.
Everyone's congratulating me now.
Me: Shut up everyone.!! And first you LinkedIn.

Use this as a template to send rejection letter to your recruiter as a revenge.

"Dear Recruiter,

Thank you for considering me for the software engineering position at your company. After careful consideration, I regret to inform you that I am unable to accept your offer.

As a highly qualified and skilled software engineer, I am confident that I could bring a great deal of value to your organization. However, after reading the job description and learning more about your company, I have come to the realization that I am simply too good for the position. I have no interest in joining a team where my talents and abilities would be underutilized and unappreciated.

Furthermore, I am a bit concerned about the working environment at your company. I have heard rumors that the office is dingy, the cafeteria food is subpar, and the company culture is lacking. I am a true perfectionist, and I refuse to settle for anything less than the best.

In conclusion, I must decline your offer. I wish you and your company the best of luck in finding a candidate who is worthy of the position.

Sincerely,
[Your Name]"

We may have lost quizzo, but we won best team name with "404 Error: Team Name Not Found" 😎

story time:
I use onedrive for sharing some files and shit. So one day one of my folders, which I got from a downloaded zip, caused an error "files couldn't be synced because of unallowed character in the title".
Turns out there was a space at the end of the folder title. I change the name, I get some error.
"Okay, no problem, I don't need that folder anymore anyway" So I delete it, doesn't work, the error message reads "Can't delete folder because it no longer exists.". "What the hell" try deleting it some more. Emptying it before deleting. Deleting the parent folder. I try formatting it before deleting. Nothing works.
Deleting from the online onedrive client causes it to briefly disappears but refreshing places it back right where it came from.

So I resort to my last hope, customer support.
I explain the whole thing.

I get a reply. Oh boy.

I get explained that if the recycle bin is full, the file will be placed back.
After that, I get an explanation on how to remove a file xD

Thanks OneDrive Team, really helpful.

SharePoint things that I get yelled at by customers for:

Setting up page permissions wrong (even though the real problem is that a coworker didn’t check the page in)

Writing the workflow wrong and nobody is getting emailed (even though they didn’t select who to send the email to)

Not magically knowing that they wanted the new intern (who started Tuesday) to be given full design rights on their page

Not magically knowing that their discussion mod quit a year ago (before I started here) and now nobody can feature a post

Not spinning up an entire new site so that they could post a link to a single sign up sheet for their team (of 10 people) barbecue

Somehow making it so MS Edge can’t handle high res images correctly (because I totally created Edge (which isn’t even a supported browser here))

Not responding immediately when they submitted a ticket at 7:00pm (I’m off at 5) asking me to change one word on a page they have edit rights to

Not giving their admin assistant global design rights for our entire organization

Not giving them access to a confidential folder that has nothing to do with their job

Telling the owner of aforementioned folder that they’re not allowed to store confidential data in SharePoint

Making workflows too confusing for them to figure out

Fixing shit workflows that their ex coworker built wrong

Generally having the word SharePoint associated with my name

Fuck the managers !! Fucking Fuck Fuck !!!
I am in manual testing for 3 years. Wanted to move in to automation since 2016 January !
They kept delaying.
While waiting I kept autating stuffs and making utilities to use for everyone.
Recently automated a 5 yr old manual process.
Made an utility that can perform a 5 hours manual activity in 5 mins.
Our automation team had a vacancy.
The managers were asked to nominate names who could fill the spot from the current manual team.
They didn't suggested my name.
I am not bragging but I am the only person in the team who nows Selenium , UFT , Java , Python even though being in the manual testers.
The team is going to hire someone from the outside.
I just got to know it all this today.

These bastards should die in hell !!!!
I hate these bastards !!!!

What's the best scrum team name that you've heard?

My favorite is "Colonel Panic" (Kernel panic)

"We need to have a meeting to clarify your role"

My head: Just give me a raise and then leave me alone

My mouth: Yea, sure. When works for you

Context:
My job is a little confusing.
My title on paper is support technician and I'm on the DevOps team but I have my own project to automate health checks. So most the accurate title for me would actually be Automation Developer Attached To [department name] DevOps

I used to be in an infrastructure maintenance team, and I worked with an old guy. We had a jump box we all used. This guy would work weekend maintenance windows and still be trying to get changes done at 7am, three hours after the end of the window. He was glacially slow. I remember watching him login to a prod weblogic server. He would open the Windows start menu, move his fucking mouse through two or three submenus, and finally click putty. Then, he would type out the FQDN of the jump server, and move his mouse to the connect/ok button. Then it would prompt him for his username and password, both of which took him about 90 seconds to single-finger type. Then, once loved into the jump box, he would then type ssh user@server.fqdn, rather than copying and pasting the server name.

It took him fully five minutes to get logged into the weblogic server. I could not take it. It would have taken me about ten seconds.

In flutter , there’s something called TextButton.icon. Which render a button look like this :

(👍🏼 Like Button)

But there’s this tiny twat decided to use countless of nested column in a nested row and containers just to create a fucking button! This particular class contains 1438 lines of code! Most of the code are redundant and nested fucking shit.

I want to punch this guy so hard but I do not intend to start a ww3 with china.

That means I have no choice but refactor it as I implement a feature requested by the product team, every components break. It is like a land mine field here. One changes , the entire application crash.

So there are useless mother fucking Sherlock fucking holmes kept telling me that “don’t worry about refactoring now , just complete the task.” , like seriously “how in the name of mother fucking god of all arseholes can I complete my task when I can’t change even one component?”

These people are fucking genius. Their intelligence resurrected Einstein and made him die the second time.

Why do marketers always tarnish the name of new concepts by turning them into buzzwords?

For example, "Cloud" is one of the most misused and overused words on the internet. If something has anything to do with the internet, it's likely to be plastered with the word "Cloud".

It's like "App" all over again. Anything remotely related to technology is called an "App" by it's marketing team and layman users.

My lead always steal my work and showcase it has his work to the manager. I always look for a chance to trap him in front of Manager.

One fine day, He gave me an work which has to completed on Monday, I sit over the weekend and finished it’s but partially committed it.

He is a blind thief, As always he says that he himself completed over the weekend.

While running in front of the manager they face huge issues because it’s a half cooked product. Manager purposely sent an email to our team without mentioning the name of my lead.

After few days my lead silently put paper and left the team.

Fresh internship story (Part 3)

Turns out my coworker with a mental disorder(adhs and idk what you call it. He is 24 years old, but is mentally between 16 and 18) is gay.

ATTENTION: DO NOT READ ANY FURTHER SINCE THIS IS GOING TO GET DISGUSTING!

My cheap coworker's name is Justin btw. I felt a weird atmosphere when I joined the team. Justin seemed to be a hetero guy. (I am generally assuming that every guy and girl I met is hetero). But he had his slightly "gay moves".

Yesterday, I was curious about it and asked him about why he was afraid about the police to identify him on a video to start the conversation. He told me that his ex did cheat on him. Since I assumed that he was hetero I asked if the girl was cheating on him. He got embarrassed.
him:"I uhmm... am... not hetero. I am...*stops talking*"
me:"What? Are you bi? Are you gay? What are you?"
him:"I am gay."
me:"Oh... *tries to hide the shock* I see.*silence for a minute*"
me:"What is the name of your ex?"
Justin:"Fabian. Fabian had a video and pictures of me and he put them online and did spread them with everyone. After that I got punched by some dudes. Now I want to take my revenge."
me:"... well... now that makes sense.*silence*"

I felt sorry for him and decided to keep listening. I made a wrong decision there.

2 hours later he told me how he got gay, because I wanted to know if he was born gay or if he became gay.
He told me his whole life was full of sex.
He found a sextape of his parents and jerked off to it without cuming since he did not even hit puberty yet. Then he had sex with a 6 year old girl and then with a 12 year old girl when he was 8 or something in both cases.

Later he got into a place full of guys.
He first started jerking off to hetero porn among the dudes. I wonder how he got no shame while doing it. Anyways, after that he began to feel something for boys and less for girls since boys were able to understand him more than girls. Then he became gay and his sex life with boys started.
It was very disgusting, but I wanted to know it.

next morning:
*he keeps talking about how Fabian fucked him outside in the bushes and I keep ignoring him*

i was hired to join a team of old devs (40+) in an unnamed European country "yay goodbye 3rd world it's time to enjoy the quality of life" assist with enhancing already existing software and creating new solutions.
prior to my arrival most things were slow and super buggy, looking at the code base it shouldn't be a surprise, amateur hour everyone, logic implemented that is not needed, comment driven development, last time code review was done back in 1996. lots of anti patterns.
i swear there is a for loop that does nothing but it loops through a 100+ elements list, trunk based development with tfs since git is "not really needed"
test projects are not there.
>enter me an educated fool, with genuine passion for the craft and somehow a decent amount of knowledge.
>spent the last year fixing stuff educating people on principles and qualities.
> countless hours of training and explaining. team is showing cooperation, a new requirement comes in to develop with react.
> tear my ass creating reusable shit and self explanatory code with proper naming etc using git with feature branching, monday is first deployment day.
> today a colleague was working on an item submit a pull request and self approve it
> look at the code..... WTF the dumb fuck copied and pasted the whole code from different kendo components but somehow managed to refractor the name to test component, commented out all the code that he didn't use did the api call directly from the component, has 2 useeffects that depends on the a fucking text box changes for no reason, no redux implementation, the acceptance criteria is not achieved, and it doesn't work it just look right.
> first world country shit cannot scold, cannot complain, lead by example.
>asked him why you did this, the response was yeah probably i shouldn't have done that, i really didn't understand anything in the training but didn't want to waste time!!!!
> rest of the team created a different styled disaster with different flavors they don't even name their shit the same way.

fellow developers I'm stuck in a spaceship with a bunch of imposters, seriously i never cried in my entire life now I'm teary and on the verge of a break down.
talk with management "improving needs time" and offers me to join a yoga session to release the stress as if reaching nirvana would deliver shit on monday.
i really don't know what do is this a rant, is this a cry for help, I'm not sure, any advice is welcomed.

So today I found a file share containing some super super sensitive information accessible to what I think was our entire user base (6,500 users) if you knew the server name and had an interest in nosing around.

I reported it to our head of IT and heard nothing after, although 5 mins after reporting I could no longer access...

I suspect the infrastructure lead is going to be a dick (because his one of them awkward non team player kind of guys) and not thank me for preventing our company from being in national news papers... but try to spin it on why am I nosing around his servers in the first place..

I actually feel 50/50 about if I should of told or not.. but on flip side, I guess the access logs of me listing the files as I flick through to confirm my suspicions would of caused s bigger headache.

Fucking useless infrastructure engineers!

High paying unstable job at a startup vs. Low paying stable job at a huge company.

I'm currently at the latter and I'm expecting a job offer (hopefully!) from the other one today.

Low paying job:

Pros:
1) big name. (their stock has recently gone down tho)
2) insurance and stuff.
3) quite stable.
4) can re-skill and move to another team.
5) work from home.

Cons:
1) shit technologies.
2) lots of fake "we are a family" kinda crap.
3) shit pay for a huge company.
4) boring. I feel very unmotivated.
5) obsolete systems and management processes.
6) it would take years to save for a car even with my upcoming promotion pay raise.

High paying job:

Pros:
1) awesome salary. Like 6x my current.
2) up-to-date technologies. Something I'm passionate about.
3) team lead position.
4) I can buy a car in a couple of months.
5) might get a visa sponsorship in the future.
6) small team, my voice will be heard.

Cons:
1) it's a startup so it can go down anytime.
2) no insurance or any kinda benefits.
3) no work laptop.

I'm kinda in the beginning of my career, so my gut is telling me to risk it and go for the unstable job.
It will be my first time to be an "official" team lead and honestly idk how I'll go about it yet.

Which one would you go for?
And wish me luck! The interview went pretty well but I'm dreading for some reason.

Need a new name for my dev team. Any suggestions?

A dev found a bug I created where I set a SQL parameter name to @OrderID instead of the expected @Order. The standard is @OrderID, there is one stored proc where it's @Order.
Oops...I didn't catch it because the integration test didn't cover that area of the code. My mistake...I should have checked...I take complete responsibility for the screw up.

He let me know by email..
"When refactoring, from now on check the stored procedure parameters, there are a few that don't follow the standard."

I was like "from now on..."? ...wow....bold comment from someone responsible for code that doesn't check for nulls, doesn't log errors, and relies on exceptions for flow control. You wouldn't even have known about the error if I didn't modify your code to log the error (the try..except returned false)

I really wanted to reply ...

"Fixed. From now on, when you come across those easily found bugs, go head and fix it, write a test, and move on. Don't send a condescending email to me, my boss, your boss, all the DBAs, and the entire fracking order processing team. Thanks."

But..I thanked him for finding and letting me know...we're a team..blah blah blah..

Frack..people suck.

We rewrote the whole thing, except for iFraming some old pages in. We had to, the system was fucking awful and couldn't cope with any of the new mission critical requirements.

Client didn't understand the scope. Our project leader somehow snuck it in and we worked on it for months. We were sure we'd be kicked off the whole project... Somehow things didn't crash and burn. How it didn't blow up defies rational thought and the laws of physics. The new system worked, the client was happy, and boss made a lot of money.

Lead dev worked weekends for what feels like an eternity, it really was his baby and no one else on our company could have done it. It's where I finally learned how to do things the proper way; DDD, unit testing and TDD, architecture, building strong components in front-end, you name it. Before that I had a great nose for code smells and how not to do stuff, but now I got to see a proper system for the first time. It was glorious.

Then lead dev left and the system degraded quite a bit because new team didn't keep to the architectural patterns or general best practices. But we had a good run.

2 hour meeting to brainstorm ideas to improve our system health monitoring (logging, alerting, monitoring, and metrics)

Never got past the alerting part. Piss poor excuses for human being managers kept 'blaming' our logging infrastructure for allowing them to log exceptions as 'Warnings', purposely by-passing the alerting system.

Then the d-head tried to 'educate' everyone the difference between error and exception …frack-wad…the difference isn't philosophical…shut up.

The B manager kept referring to our old logging system (like we stopped using it 5 years ago) and if it were written correctly, the legacy code would be easier to migrate. Fracking lying B….shut the frack up.

The fracking idiots then wanted to add direct-bypass of the alerting system (I purposely made the code to bypass alerting painful to write)

Mgr1: "The only way this will work is if you, by default, allow errors to bypass the alerting system. When all of our code is migrated, we'll change a config or something to enable alerting. That shouldn't be too hard."
Me: "Not going to happen. I made by-passing the alert system painful on purpose. If I make it easy, you'll never go back and change code."
Mgr2: "Oh, yes we will. Just mark that method as obsolete. That way, it will force us to fix the code."
Me: "The by-pass method is already obsolete and the teams are already ignoring the build warnings."
Mgr1: "No, that is not correct. We have a process to fix all build warnings related to obsolete methods."
Mgr2: "Yes. It won't be like the old system. We just never had time to go back and fix that code."
Me: "The method has been obsolete for almost a year. If your teams haven't fixed their code by now, it's not going to be fixed."
Mgr1: "You're expecting everything to be changed in one day. Our code base is way too big and there are too many changes to make. All we are asking for is a simple change that will give us the time we need to make the system better. We all want to make the system better…right?"
Me: "We made the changes to the core system over two years ago, and we had this same conversation, remember? If your team hasn't made any changes by now, they aren't going to. The only way they will change code to the new standard is if we make the old way painful. Sorry, that's the truth."
Mgr2: "Why did we make changes to the logging system? Why weren't any of us involved? If there were going to be all these changes, our team should have been part of the process."
Me: "You were and declined every meeting and every attempt to include your area. Considering the massive amount of infrastructure changes there was zero code changes required by your team. The new system simply worked. You can't take advantage of the new features which is why we're here today. I'm here to offer my help in any way I can with the transition."
Mgr1: "The new logging doesn't support logging of the different web page areas. Until you can make that change, we can't begin changing our code."
Me: "Logging properties is just a name+value pair dictionary. All you need to do is standardize on a name and how you add it to the collection."
Mgr2: "So, it's not a standard field? How difficult would it be to change the core assembly? This has to be standard across all our areas and shouldn't be up to the developers to type in anything they want."
- Frack wads smile and nod to each other like fracking chickens in a feeding frenzy
Me: "It can, but what will you call this property? What controls its value?"
- The look I got from both the d-bags I could tell a blood vessel popped.
Mgr1: "Oh…um….I don't know…Area? Yea … Area."
Mgr2: "Um…that's not specific enough. How about Page?"
Mgr1: "Well, pages can cross different areas, and areas cross different pages…what do you think?"
Me: "Don't know, don't care. It's up to you. I just need a name."
Mgr2: "Modules! Our MVC framework is broken up in Modules."
DevMgr: "We already have a field for Module. It's how we're segmenting the different business processes"
Mgr1: "Doesn't matter, we'll come up with a name later. Until then, we won't make any changes until there is a name."
DevMgr: "So what did we accomplish?"
Me: "That we need to review the web's logging and alerting process and make sure we're capturing errors being hidden as warnings."
Mgr1: "Nooo….we didn't accomplish anything. This meeting had no agenda and no purpose. We should have been included in the logging process changes from day one."
Mgr2: "I agree, I'm not sure why we're here"
Me: "This was a brainstorming meeting as listed in the agenda. We've accomplished 2 of the 4 items. I think we've established your commitment to making the system better. Thank you all for coming."

- Mgr1 and 2 left without looking at me or saying a word.

Hello all,

I am an apprentice, 19. I joined this software developer apprenticeship to leave college as it was not particularly great for my mental health, and programming is the only thing I can do reasonably well.

The company that I find myself in is a strange one. It has about twenty or so employees, but we all instructed to operate as if we are a giant company—our sales person, for example, will tell our clients that we have hundreds.

The development team is a collection of software developers. There is no database administrator, network administrator, software engineer (not in name only), test engineer, requirements engineer, etc. There are just several software developers. Of these developers, one has left by now. When he joined, he was promised to be working on a new system: he left after spending seven years on an old system. A new developer has just arrived to replace him: he was told he would be working with Raspberry Pis; it was interesting to see his face after we informed him that we do not use Raspberry Pis.

The codebase is fourty-years-old and written in Delphi, which is some kind of cousin of pascal, from what I understand. Code is not peer-reviewed. Instead, it is self-reviewed, and you just push whatever changes you make. The code is very much spaghetti, and there is a whole array of bugs that, at least to me, look impossible to track down and fix. I have a bug assigned to me at the moment were someone appears somewhere when they are not supposed to. After asking seniors about this, I learn of this huge checking mechanism and all of its flaws: a huge, flawed checking mechanism... for toggling a single boolean value. This isn't a complicated boolean value, by the way, this is just a value to say whether someone has clocked in or clocked out of a building, via a button.

In terms of versioning, we have several releases, and we often do development work in older releases (or new releases and then write them into older releases) because our clients are larger than us and often refuse to upgrade, and the boss does not want to lose any contracts. We also essentially have multiple master branches.

With the lack of testers, bizarre version control, what appears to be unfiffled promises to staff, etc. I must ask that, since this is my first gig as a software developer, is any of this normal?

Does anyone have a good (preferably funny) name for a competitive programming team?

I was thinking "it compiles; submit it" but that is slightly unoriginal...

Just got reminded in the comments of another rant, that theres a .se domain, so my first thought was to register per.se (torilla tavataan) - sadly it wasn't available, since some football club/team is owning it, what a nice domain name 😂

Dear managers:

Don't rush developers when they're reviewing code - telling them to cut corners.

You're not a dev (anymore). This shit is important if you want a system that doesn't blow up / takes months to make a simple change.

It's my name going against this approval and I (and the team) have to live with the code every day

One stubborn (but not very good) dev working on one part of new project (Windows desktop application with C# underneath) decided he didn’t like the interfaces we were agreeing for the algorithmic code.

Instead of discussing with the team (we were still very much in design phase), he made his own interfaces with the same name but in a different namespace, and in his assembly rather than in the base library. He was senior to the rest of the dev team, so when we raised our concerns he pulled rank and just carried on.

I resigned not long after that.

It happens some times. not actualy their fault.

Today i reached office on almost lunch time. and i saw our new intern(3 members) team trying something on same PC, something in like css file. (Helping each eachother).

Yes i Forgot to mention that they were supposed to finish that page-task yesterday (in angular app).

When i asked them about issue.On which i got to know that they were trying to apply css on class name. But could not since Morning.And when i saw code, It was something like this....

Yes "cls_model" is css class

MICROMANAGEMENT

I got assigned a milestone we had delayed twice already. It needs to be ready for tomorrow, it's harsh but doable.

Guy from another team, looks at my folder system during the presentation, something like
"src/views/users/view-all/view-all.template.html" and starts whining "hurr durr this isn't good tho, you should have chosen a significant name, it's impossible to understand what this file does".

Honest thought: if you can't navigate through folders, you shouldn't be writing code in the first place.

I just heard someone quote this
"To complain about a problem without proposing a solution is called nagging."

I know the perfect name for QA team now. 😁😁😂

The 'farewell great manager Jim' party on Monday.

The [insert name of a department] Christmas party on Wednesday, which you shouldn't miss because they want the company to be more integrated.

The [insert name of your department] Christmas party on Friday, which is separate from the other party because they want the company to be more inte... wait.

The hackathon on Saturday and Sunday, because coding all night for free to create buzz around the company's name is always fun.

The team meeting where the product manager presents all the shinny new things they're thinking about presenting to the client while our deadline is still a couple of weeks away. "And the engineering team knows exactly what to do, right?" Yeah, sure, if you say so.

I can't convince my team that a good database model promotes a good API design and a good UI/UX experience.

Instead, I have to work with a ridiculous table setup.

Imagine, if you will, a table (table B) that references another table (table A) via a foreign key. The FK is a string in both tables. And table A only has one column, which is labeled as "name".

The schema i have to look at it kind of like this:

Table parent
Name varchar(10) primary key

Table child
Name varchar (10),
parent_name varchar(10),
Foreign key (parent_name) references parent (name)

Sorry if the syntax is wrong, a little frustrated having to look at it...

Am I crazy to want to change this table design? Am I missing something? I feel like I'm taking crazy pills, because this is just scratching the surface of the problems I have to deal with.

Renaming a file is just too difficult for this piece of shit software.

Fixing bugs? Fuck no.

Fixing crashes? Fuck no.

Fixing the unnavigable IDE settings? Fuck no.

The IntelliJ platform is a bloated piece of shit at every level.

JetBrains cannot produce software that isn't held together by duct tape.

I can't name a single item of software they've ever produced that isn't a bloated piece of shit.

Even if you are prepared to waste a lot of time trying to file a bug report – which they usually just ignore or pretend not to be reproducible – you have to use another in-house heap of shit called YouTrack.

Have you tried using this piece of trash that masquerades as a bug tracker?

These people are fucking clinically insane.

While your IDE becomes unresponsive and crashes without warning, or your keyboard shortcuts just mysteriously stop working in the IDE, or indexing just stops working for no reason, why not check out their TikTok and Twitter accounts?

They've got an excellent PR team that knows how to polish a turd for public consumption, and to make money out of it.

I need guidance about my current situation.
I am perfectionist believing in OOP, preventing memory leak in advance, following clean code, best practices, constantly learning about new libraries to reduce custom implementation & improve efficiency.
So even a single bad variable name can trigger my nerves.

I am currently working in a half billion $ IT service company on a maintenance project of 8 year old Android app of security domain product of 1 of the top enterprise company of the world, which sold it to the many leading companies in the world in Govt service, banking, insurance sectors.

It's code quality is such a bad that I get panic attacks & nightmares daily.

Issues are like
- No apk obfuscation, source's everything is openbook, anybody can just unzip apk & open it in Android Studio to see the source.
- logs everywhere about method name invoked,
- static IV & salt for encryption.
- thousands of line code in God classes.
- Irrelevant method names compared to it's functionality.
- Even single item having list takes 2-3 seconds to load
- Lag in navigation between different features' screens.
- For even single thing like different dimension values for different density whole 100+ lines separate layout files for 6 types of densities are written.
- No modularized packages, every class is in single package & there are around 100+ classes.

Owner of the code, my team lead, is too terrified to change even single thing as he don't have coding maturity & no understanding of memory leak, clean code, OOP, in short typical IT 'service' company mentality.

Client is ill-informed or cost-cutting centric so no code review done by them in 8 years.

Feeling much frustrated as I can see it's like a bomb is waiting to blast anytime when some blackhat cracker will take advantage of this.

Need suggestions about this to tackle the situation.

Boy oh boy.. Reminds me of good ol college days. I was in my final sem when Amazon came to our university for campus hiring. I was very confident that I will get selected. Funnily enough I went till the final round and I had a feeling that it went well if not excellent. It was a Friday night and we had to wait two excruciating days for the final shortlisted result to come. On the evening of Monday my friend T called me and told me my name is not on the list. I was heartbroken. I asked him who all got selected and he said our friend A did. A was, and still is a good friend of ours and I was happy for him. That night we sat down for drinks and as the night progressed I anguished over my selection. I still remember solving a binary tree problem holding a glass of whiskey in my one hand. The next morning I woke up at 6, detoxed myself with fruit juices and sat in front of my laptop feeling full rage from last night. I sat till lunch and hacked a chrome extension in one sitting. Mind you I had no existing knowledge of extensions at that point of time. I sometimes look how my life has turned since that time and now I am one of the devs in a team which work on a product that itself is a browser extension. :)

First-time goona work on frontend(my worst nightmare).
That too Angular.
That too on a file containing 900 LOC.
That too with no proper naming, variable names x,e, obj.
That too with no comment.
Cant take help as I am the lead(name-sake, small team, I have 6month more experience than others)

I have 2 days(thank god for the weekends).

Fuck...Fuck...I missed writing CLI apps.

My FIRST robotics team 5024 is ordering sweaters and I can put anything I want on the back as my code name sortof thing. What is witty that I can put on it?

I want to get your take on an icebreaker I was subjected to recently. For a 9 a.m. Monday morning training last week, the facilitator opened with, “Tell us your name, your team, how long you’ve been with the company, and a ‘scar story’. Pick a scar on your body and tell us how you got it. If you prefer not to talk about a physical scar, you can tell us about an emotional scar.” I am not joking.

As we went around the room, there were lots of blood and guts stories (gross) but people also shared really traumatizing tales, like an infant daughter being diagnosed with leukemia. The whole thing took 30 minutes of a 90-minute session. I was very turned off by the activity in the moment and even more so later after reflecting a bit.

Besides this one being in very bad taste, I find myself turned off by icebreakers in general. They feel forced and never seem to give you a useful introduction to your colleagues. I’m wondering if your readers have ever participated in an icebreaker they think was particularly effective or are these just a reality of office life we need to endure?

Everyone in this team calls everything a team effort, but once I start offering my help, they be like "no, I can do it. I know more than you".

Hmm. yeah, but you (sysadmin) use jQuery and vanillajs mixed. For example: $('#hello') and document.getElementById('hello').
Also you put console.logs everywhere, I don't mind putting console.logs in development, but not in production.
Oh and he copies the libraries to every folder that needs it, so there are at least 12 jquery libs in this project and the version is not even the same. Lol.... Please slap me to death.

There is another networkadmin that calls himself a (python) developer. He doesn't agree with my simplicity.

His work (just an example, changed names but you get the idea)
"A notebook that is used by x-department"

Model: Notebook
endpoint: department-notebooks

Model: DepartmentConfigs
Endpoint: notebook-department-configs
You won't believe what he put in 'department'configs, it's literally hardware vendor, model, versions.

Like... really? What the hell you doing man?!
Just have these models for example: device, department, vendor, product, category

We do not only have notebooks, but also servers, routers, switches and more.

His argument of having configs in the name is that they do more complex things. Hmm, I don't see it in the code and the data is messed up:
Microsoft, microsoft, micro soft.

He fixed it by hardcoding it in a select box. Mickysoft isn't the only vendor, fuck you!

fuck this team, fuck these people

Another fucking rant, a story was assigned to me. But that stupid fake developer worked on it immediately and message me he fixed it already. I guess he won't let me touch his baby.

Everything is just piling up. This team and people aren't fun at all.

We are researching enhancing our current alerting system (we use Splunk) to be 'smarter' about who is emailed/texted/whatever when there are problems in our applications.

Currently, if there are over 50 errors logged within a 15 minute period, a email/phone/text blast to nearly 100 individuals ranging from developers, network admins, DBAs, and vice presidents.

Our plan is to group errors by team and let each team manage their own applications. Alert on 1 error, 5, 500...we don't care, let the team work out the particulars.

The trick was interfacing with Splunk's API (that's a long rant by itself)

In about a day or so I was able to use Splunk's WebHook feature to notify a WebAPI service I threw together to send myself an email with details about the underlying data (simulating the kind of alert we would send to the team)

I thought ...cool... it worked. Show it off to the team, most thought it was a good start, except one:

Dev: "The errors are not grouped by team."
Me: "No, I threw the webapi service together to demonstrate how we can extract the splunk bits to get access to the teams"
Dev: "Well...this won't work at all."
Me: "Um..what?"
Dev: "The specification c l e a r l y states the email will be team based. This email was only sent to you and has all the teams and their applications"
Me: "Um...uh...the service can, if we want to go using a service route. Grouping by team name is easy using a LINQ query. I just through this service together yesterday."
Dev: "I don't know. Sounds like I need to schedule a meeting to discuss what you are proposing. I don't think emailing all that to everyone is a good idea."

WTF! Did you not listen to what I said?!!!

Oh well..the dev's proposal is to use splunk's email notification and custom Exchange rules with callbacks into splunk that resend...oh good lord ...a fracking rube goldberg of a config nightmare ...

I suspect we'll go the service route once I finish the service before the meeting.

I am working for one of the FAANGs. I will soon be completing 4 years in industry. For me I should be an level 2 developer or at least working for level 2.
In my current company I don't think I will get promoted this soon and also, switching internally might now benefit as if I will switch my work at the company won't give me enough feedback to get promoted soon in the new team.
I am thinking of switching to some other company with a level 2 position and work at that level.
Should I continue working at FAANG as it has a nice name and all or switch to some other company with a promotion to grow my skills.

Even at my current company I am. learning a lot but the promotion is an issue.

So we have this team that deploys some code. We had a change in that code that "we" forgot about. Turns out, a dev on our team decided it would be cool to rename an endpoint. Why? Great question. Because. So this code gets deployed, but the call to that endpoint didn't get deployed. System 2 tries to call the endpoint, 404. We roll back, we're searching, after like an hour, we find it. We go to TFS to see who did it. The dev grabs my keyboard and starts checking diffs, somehow managing to skip their commit (from 5 months earlier). I take back my keyboard and *surprise* it was the commit that was skipped. WTF? Why did you rename that endpoint? What do you mean you didn't do it? It has your name right there!

!devrant.

More like 'relationship' rant.

The following is gonna be kinda crude and not work appropriate just fyi.

First, whats with this trend of 'shave your pussy", and small tits? Shit just a few years ago it was the opposite! Who wants to fuck a women who looks like an undeveloped boy. Give me a good medium pair of knockers and a (slightly) hairy pussy anyday and I'm in heaven.

On that note, all these guys whining and fucking whinging about "fat" women. Like I'm not chasing deathfat women or anything, but come on dudes. If you're gonna demand 'thin beautiful women' put in the fucking work! Just saying it now. Kinda pudgy, not a deal breaker for me. She have a pretty face, looks good in make up? Fuck it, I'll give her the time of day. Don't come at me with "hurrr...fat is unhealthy! Wheres your standards?"

Wheres YOUR fucking standards? Shit, I could take a 'heavy' girl and in a few months time have her trim. Its about the WORK you put in. All these fucking guys, all these fucking guys man, they all want something for nothing and chicks for free. No one wants to put in the fucking EFFORT anymore. I can't name on one hand the number of 'fat ugly chicks' everyone ignored from school (well except for me), who are now bombshells. If I stayed connected with people maybe I'd be with one of em right now, but I just get tired of this attitude that no one invests any time in others any more. It's all about 'me me me'.

Shes fat, maybe only a few extra pounds? Fat and 'not beautiful'? Fucking DO THE WORK and make her beautiful you bitch! Be her coach, like those fucking instagram couples you see sweating it out. Make her sexy. Become sexy, together.
Get her a fucking treadmill. Get her two. And jog together. Make her *feel* sexy.

More importantly get to *know* her. Why does she get out of bed in the morning? What drive her NOT to get out of bed? When does she feel lousy? What makes her feel that way? In addition to all the other shit men should know how to do, you should learn to play doctor phil, because every girl needs one. Women bond by talking, men bond by doing things together. Relationships should involve both.

Jesus fucking christ, this is basic bitch advice, and it annoys me I keep on coming across these spergs that don't fucking get it. Women are not cars you can stick your key in and just go 'vroom'.

They require maintenance, same as anything, any 'relationship' (because really, what are relationships in 2020, with instagram and fucking tinder and antisocial distancing?). You're a *team*, and i don't mean that in an inspirational way. You're a literal team. And far too many people prioritize the well being and success and concern of 'I' over' 'us'.

In short, if she ain't coming, you shouldn't be either. And if you expect her to on-the-regular put sharp objects on her fucking nether regions, don't expect any blowjobs unless you're doing the same thing for yourself!

Ideally you should be doing it to each other.
After all, you're partners. You trust her to put sharp objects near your groin, right?
Aren't relationships supposed to be about mutual trust?

So I work for an IT consulting firm (web development) and was hired by a customer 7 months ago for coaching Git, implementation of VueJS on the front-end and fostering teamwork with devs who'd been in their solo comfort zone for the last 15 years.
I asked for confirmation multiple times on whether they were sure they wanted to go through with a bigger investment in front-end. Confirm they did, multiple times.

After half the team's initial enthusiasm faded (after 1 month), the 'senior' of them who's worked there for 18 years on a single -in the end, failed- project got a burn-out after half a week of showing up (without doing actual work) from the stress, and started whining about it with management that has no technical clue whatsoever. This and other petty office politics lead to the dumbest organizational and technical decisions I've seen in my short 5-year career (splitting a Laravel app that uses the same database in two, replacing docker container deployment with manual ssh'ing and symlinking, duplicating all the models, controllers, splitting a team in two, decreasing productivity, replacing project management dashboards with ad-hoc mail instructions and direct requests).

Out of curiosity I did a git log --author --no-merges with the senior's name on the 2 projects he was supposed to help on, and that turned up... ZERO commits. Now the dept. hired 3 new developers with no prior experience, and it's sad to see the seniors teach them "copy paste" as the developer's main reflex.

Through these 7 months I had to endure increasingly vicious sneers from the IT architect -in name only- who gets offended and hysterical at every person who dares offer suggestions. Her not-so-implicit insinuation is that it's all my fault because I implemented Vue front-end (as they requested), she has been doing this for months, every meeting at least once (and she makes sure other attendees notice). Extra background: She's already had 2 official complaints for verbal abuse in the past, and she just stressed another good developer into smoking again.

Now I present her my timesheet for January, she abuses her power by refusing to sign it unless I remove a day of work.
Earlier this week I asked her politely to please stop her unjust guilt-tripping to which she shouted "You'll just have to cope with that!", and I walked out of the room calmly (in order to avoid losing my nerves). She does this purely as a statement, and I know she does it out of bad faith (she doesn't actually care, as she doesn't manage the budgets). She knows she wields more power over me than the internal devs (I am consultant, so negative reviews for me could delay further salary raises).

I just don't know how to handle this person: I can't get a word in with her, or she starts shouting, and it's impossible to change her (completely inaccurate technological) perception.

Funny team names? A team at my comapany cant call themselves the "super high intensity team" so they gotta find a new name.

Sus!
yesterday I bought a cool domain in namecheap, I was very lucky to find short and good one for my case.

Today (at weekends!!!!) I receive a letter:
>Hello **redacted name**,
>
>We are contacting you from the Namecheap Risk Management Team regarding your '**redacted name account**' account.
>
>Unfortunately, your Namecheap account was flagged by our fraud screening system as requiring verification and was locked.
>
>Please follow the instructions below to get your account verified:
>
>- take a color photo of the credit card used for the payment at **redacted link**
>
>Please make sure all of the edges of the credit card are visible, and that we can clearly see the card holder's name, expiration, and last four digits of the card number. The screenshots or images of the card cannot be accepted for verification. >If the submission does not meet these requirements, we can either request to submit the details again or permanently suspend your account.
>
>- provide a valid phone number and the best time to call you (within normal business hours, US Pacific time).
>
>If we do not hear back from you within 24 hours, we will be forced to cancel your orders.
>
>We apologize for any inconvenience that may result from this process. This extra verification is done for your security and to ensure that orders are legitimate. This industry, unfortunately, has a high rate of fraudulent orders, and this sort of >verification helps us drastically reduce fraud and ensure our customers remain secure. Such documents are used for verification only and are not provided to third parties in any way. Account verification is a one-time procedure, after your account >is verified, you will never face this issue again.
>
>Looking forward to your reply.
>
>---------------
>Dmitriy K.
>Risk Management
> Namecheap, Inc.

what if I did not notice it in 24 hours? It is the weekend for god's sake! People usually rest until monday.
They would what, cancel order and scalpel it to super high price?!
I have some doubts if the request is trully having anti fraudulent origins.

What if I used digital visa card? How was I supposed to photo it?

And the service they provided for photoing accepts only photos from web camera. I was lucky that I bought recently web camera with high enough amount of pixel power and manual focus. What if I did not?

That's all really SUS!
The person can not notice the letter within 24 hours time frame until the morning, when it would be already too late.

End of my rant about 35 day recruitment process for anyone interested to hear the ending.

Just got rejected by a company (name Swenson He) for a remote Android Engineer SWE role after wasting 35 days for the recruitment process.

First intro interview went good, then I did an assignment that had 72 hours deadline (asked for couple days longer to do this task, did it in around 40 hours, it was purely an assignment not free work, I could have done it in a day but I choose to overeenginer it so I could use the project as a portfolio piece, no regrets there and I learned some new things). After that It took them 2 weeks just to organize the technical interview.

2 days after the technical interview I received an offer from a second company with 1 week to decide. I immediately informed the Swenson He about it and politely asked whether they could speed up their decision process.

Now I know that I could just sign with the second company and if the big Swenson He would decide to bless me with and offer I could jump ship. But out of principle I never did that for 7 years of my career. If Im in a situation with multiple offers I always inform all parties (it's kinda a test for them so I could see which one is more serious and wants me to work for them more). Swenson He didnt pass the test.

6 days of silence. I pinged the techlead I interviewed with on LinkedIn about my situation, he assured me that he'l ask his hiring team to get back to me with feedback that day.

2 days of silence. I had to decide to sign or not to sign with a second company. I pinged the techlead again regarding their decision and 10min after received a rejection letter. There was no feedback.

I guess they got pissed off or something. Idk what were they thinking, maybe something along the lines of "Candidate trying to force our 35day recruitment process to go faster? Pinging us so much? Has another offer? What an asshole! ".

Didnt even receive any feedback in the end. Pinged their techlead regarding that but no response. Anyways fuck them. I felt during entire process that they are disrespecting me, I just wanted do see how it ends. Techlead was cool and knowledgeable but recruitment team was incompetent and couldn't even stay in touch properly during entire process. Had I didn't force their hand I bet they would have just ghosted me like they did with others according to their Glassdoor reviews.

Glad I continued to interview for other places, tomorrow Im signing an offer. Fuck Swenson He.

P.S. From my experience as a remote B2B contractor if a company is serious the entire process shouldn't take longer than max 2 weeks. Anything outside of that is pure incompetence. Even more serious companies can organize the required 2-3 meetings in a week if they have to and if they are interested. Hiring process shouldnt take longer than MAX 3 weeks unless you are applying for some fancy slow picky corporate company or a FAANG, which is out of topic for this post.

Need a team name for Google Hashcode, please suggest something bad.

So I came from the Portal modding scene. And I know most other ones who did similar stuff.
Now there was a cool looking upcoming free mod and I somehow came in touch with the lead Dev. Now somehow I managed to get into the developer team and me and my girlfriend we're part of it. We got a level name and should start mapping it (TL;DR, we never finished one because we didn't know what to do).

I actually made a website for the mod. But sometime later we both left the team because the lead Dev (12 yo btw) was "hiring" (working for passion not money btw, that's fine in this case) everyone he got in touch with. They had no team structure just a huge list of people and a long story script. I'd guess the mod won't ever be done, although it has made it through steam greenlight (R.I.P greenlight). Just because they're not working on a team.

Things I learned in this 2 month training in an IT company ;
- the way @marcerisson wanted me and my group project team to use Git (and kept yelling at us about ) is actually the proper, professional way of using Git
- there is a difference between an MVC model and a fucking pack of overcomplicated spaghetti code
- commenting your code and naming your variables properly IS IMPORTANT especially when another dev might read it 15 years later (i see you Mr I Name All my Variables With the Name Of the Function and A Number)
- « if it worls it ain’t stupid » also apply in a professional area
- where ´s my fucking rubber duck

When the team lead announces you have to pick a team name for the mobile software devs. No seriously I have until tomorrow otherwise we get called team Poloni because of a poorly chosen color once. Ideas please! So far we have hackslash, A-team (Android Apple) or Swifty Java 😜

I don't at all like when few team mates just put their name on top of the file they are adding to the project.

Gets on my nerves every time.

Usually, when I programme for myself or in a German-only team and they agree, I/we do it in German because it makes naming things much simpler (no naming conflicts, never, and a strict visible separation between your code and libraries).
This time, I thought: "Nooo, let's do it in English, because, you know, reasons and it fits into the situation"...
Booom, stack overflow!
"How in the hell did that happen?" I never had a stack overflow before outside of recursive programming.
And what was it? I had made a class to encapsulate an API, added a property with getter and setter, naming in English and similar to the said API... very similar... in fact, the property had the same name as the API function, resulting in a getter calling itself over and over again.

This was a harmless mistake, and found very quickly, but it's interesting so see how a habit (or working method) probably prevented similar or worse sources of error in the past.

It's just that your team doesn't have experience in "insert platform name here" so we want to use a third party to move "insert product name here" into it.

My first thought: why don't you just train the team with the product knowledge in the new platform rather than the other way around? Does anyone else see this happen and want to eat glass every time it does?

TL;DR Shit programer trying pass off stealing code as "Recycling"

Backstory:
Client hires senior dev. He lied and knows nothing. Has been causing havoc in production since day 1. My crusades to defend production have been without much success.

Since he wants to LITERALLY put his name on every big project, he finds any reason to make a new version of it (or make a slight astetic modification) to say he did something.

The client doesn't know or care about the programming side of things. Which means it is incredibly difficult to get him to understand the issues this brings. Not to mention that the "senior dev" is acting as a consultant to the client, altering the facts.

Story:
The piece of shit, is trying to make a new version of a big project. It was originally made by my mentor. Again, if you are using someone else's work to complete your own, I don't care. But if you take 99% of another person's work and then say...

"I took and existing project, which was similar to what I'm trying to make. Then I modified it to fit our needs."

Fuck you man!

You took someone else's work. Now you're trying to present it as your own. No references to our team. Again, there is literally nothing new about this project. It's exactly like the original. The client didn't even ask for this.

I had a complaint about a product I bought from a store a while back. I was resistant to taking into the store because the people there make you feel like you are stealing when trying to return a defective DVD. So I contacted the store via their website. I put in my first and last name and my email in the message to them. This is an excerpt of what I got back:

---

Response By Email (Triston) (12/12/2019 03:56 AM)
Hi Phuckin,

Your satisfaction is our top priority and your comments have been forwarded to your local Store. The management team there will take appropriate action and you can expect a response from them within three business days.
<store specific info>

Customer By (Phuckin Chit) (12/11/2019 03:40 PM)
<details of my complaint, etc>

---

Apparently I had created an account with this store a while back when I was angry. Hence my name being reported as Phuckin Chit. Even though I entered my name in the form it used the stored name associated with my email. At this point I am not sure they are going to help me.

Being victim of an arbitrary worplace's culture on dev experience and documentation makes me a very frustrated dev.

Often I do want to document, and by that, I don't mean laying an inline comment that is exactly the function's name, I mean going full technical writer on steroids. I can and WILL get very verbose, yes, explaining every single way you can use a service - no matter how self explanatory the code might look.
I know developers (and me included) can, and sometimes will, write the best variable and function names at the time, wondering if they reached the peak of clean, DRY code that would make Robert Martin have a seizure and piss himself, only to find weeks later after working on something else that their work is unreadable. Of course.
I know the doc's public, it's me, and I've done this.

But then again explain for the people in the back how the FUUUUCK are we meant to suggest improvements, when we are not the ones who are prioritising features and shit WITH the business?

Just email me when the fucking team recycles, and no new team member knows how to even setup the IDEs because this huge piece of monumental shit called CompanyTM is also run by VPN. Fuck, no one wants to access that garbage, you have no docs.

I once tried setting up a culture for documentation. I did an herculean amount of work studying what solutions were internally homologated, how steep the learning curve would be from what we had at the moment (NOTHING, WE HAD FUCKING NOTHING, jesus christ, I even interviewed SEVENTEEN other squads to PROVE they FUCKING NEED
DOCS
TO WORK

You know what happened to that effort?
It had a few "clap" reactions on a Teams meeting and it never reached the kanban.
It didn't even made it to backlog.

I honestly hope that, someday, an alien fenomenon affects the whole company, making their memories completely reset, only to have the first one - after the whole public ordeal on why our brains became milkshake -, to say: "oh, boy, I wish we had documented this".
Then I will bring them to the back and shoot them.

Suggest me some good team name for a Hackathon,

Should not be too edgy as I want to show it to my College HOD : P

So I just noticed while looking at our release notes, we got some new members of our Shanghai team. Their English names are:

Paul, Jonas, and ....
...
...
...
...
Elvis

Every time I see his name I sort of chuckle...

When your IT VP starts speaking blasphemy:

"Team,
We all know what’s going on with the API. Next week we may see 6x order volumes.

We need to do everything possible to minimize the load on our prod database server.

Here are some guidelines we’re implementing immediately:

· I’m revoking most direct production SQL access. (even read only). You should be running analysis queries and data pulls out of the replication server anyway.
· No User Management activities are allowed between 9AM and 9PM EST. If you’re going to run a large amount of updates, please coordinate with a DBA to have someone monitoring.
· No checklist setup/maintenance activities are allowed at all. If this causes business impact please let me know.
· If you see are doing anything in [App Name] that’s running long, kill it and get a DBA involved.

Please keep the communication level high and stay vigilant in protecting our prod environment!"

RIP most of what I do at work.

Today I had a full-day job interview for a junior data scientist position.

First I met the team which was only like half of everyone because apparently everyone was gone on Fridays. However the few there were really nice.

First task is to do some basic data analysis stuff even though I already spent a week on the coding challenge and sent them all my code/tasks. I log into my machine and create a new virtual environment but can't for the life of me figure out how to use the command line in windows to install packages. Turns out there is some problem with their proxy and they have to log me in on that. Then I am struggling on the keyboard because it's for a language different that my mother tongue and it takes me 3x as long to so the most simple things. All my shortcuts are out the window. Haven't a hard time typing parentheses and brackets. Start freaking out and have a panic attack mid task. I'm sweating bullets. I didn't even make it to the simple visualization tasks much less the models at the end. Time gets called and we all go to lunch and I'm freaking out on the inside the entire time. Angry at myself because I know I am better and just couldn't think.

After lunch I present my code and results from a coding challenge I did weeks prior. People from other teams get invited and I end up getting grilled for 2 hours by 15 people. Questions are flying in from all sides. They ask me almost everything I know about machine learning and some more. Under stress I forgot the name of the optimizer I used and couldn't answer some easy stuff because my mind was racing.

Right now I am on the train home and my body physically hurts. I am disappointed with myself and wish I could have shown up better. Never really froze up like this before.

Our team uses story format titles for JIRAS like As a ..., I want...

But in our git repo, a lot of people create branches using the same name:

{JIRA-ID}-as-a-...

And I'm always like why the fuck can't you take 5s to name your branches more descriptively? I usually name mines using some keywords from the Jira Title

But wondering now what do you all think/do?

HELP, ITS A MESS!!

Here is a thing : 30 hours ago, i was completely free nd useless .Had a lot of reminders to open source & learn new techs for upcoming summer vacations .

But day before yesterday my friend called me to say that he got a 6 month internship in web from some (not so big) startup and they were looking for some Android dev too, so he gave my name and wanted me to mail him my resume.

I did, and within half an hour he called, discussed about the work and wanted to test me.(as i said i didn't had plans for internship , leave alone a sudden test, but the company was work from home so i didn't denied ) The test was a big one but easy, he wanted me to design 15 UI activities for an app by looking at the wireframe. I asked for next 6 hours, did it in 4.5 and submitted him the repo...

THE TROUBLE STARTS NOW...
1) He seemed impressed i guess, coz the next day when he saw my message, he Created a group of 5 people within a few minutes and started assigning tasks(?!) And in the personal chat what he said was just weird : "You are the lead for this project" (WTF??!?)

2)I had already mentioned him that i currently had exams so won't be doing any much of practical work but after every few grp messages, he was trying to assign me some task and a deadline. Weirdly, the test was actually a wireframe based on the project idea from some of their client , and just to show my skills, i have designed layouts of 15 of their activities of their app.

3) The negetive part comes like this: THERE IS NO MONEY AND ITS A 6 MONTH INTERNSHIP !! Fed up of this continues indirect deadlines, i asked him What's my responsibilities as a team dev, what will be my tenure and what will be the pay to which he replies that:

"there is no stipend for this, we have multiple projects lined up in which you can contribute and your internship period is 6 months which could be increased/decreased on the basis of your performance. You will get a PPO, Internship certificate , mentor support and intellectual code rights (which i am guessing means my 2 word name in the about pages of the apps i develop for them ) .And as a lead , you will be getting an experience in leadership skills "

I am really confused. Work from home seems like a relaxing thing , and being a team lead for the first time definitely would make me a little more confident. But why does it feel to be kind of fraud plan? Plus there is no pay and i would be ignoring my creativity ideas for this (not completely but i am sure anyone giving a job would expect some work from me eceryday ).

WHAT SHOULD I DO???

A few months back, I was having the last few days of my college / university. Already had a job offer, wasn't fond of attending classes, so I had not much to do. I had been a student placement coordinator, and a few of other student coordinators along with the University Placement Cell decided to overhaul the current placement structure with a new, more efficient one. So, they asked whether I could take interviews (along with a few others) for new placement coordinators, who'd take over the following year, making the existing posts null and void.

So, I was interviewing a 2nd year girl for the technical team. In her form, she had mentioned that she'd been an executive member of the programming club of our University, founded the previous year, was peaking in terms of popularity among other clubs.

I found it strange, and during the interview, I kept pushing it until she accepted that she was just a member and not an executive member.

Then, I asked, do you know Bugs Buggy (name changed)... She said, yes, he is the founder of that club. I said, I am, Bugs Buggy.

Felt thug life B)

Revision to the Peter/Dilbert Principle, the ProjektAquarius principle: a company will systematically shift the least competent employee on to the assignments the competent employees can't be bothered to do until they become an integral part of the team and drag you down with them. (E.g. eventually they completely fuck up your delivery process, although it's probably still cheaper and quicker than having them do anything else.)

ProjektAquarius principle: A Case Study

We have an engineer who is getting paid quite a bit more than me. Over time his responsibilities have gradually been reduced to documentation and running our almost entirely automated build. Well today the build failed. He pulls me over to tell me, and says he's confused because there is a file there he has never seen before in there and a file he always has seen that isn't there (basically a file got renamed. It was not non-obvious). Answer: change the file name.

Then he comes over and tells us that it's failing again because the script is not finding a file. So a coworker of mine and I go over. He explains the whole build process to us when we ask if there is any point in the script that would help us identify where the script is looking for the file and failing (there wasn't but that's besides the point).

Turns out, he had decided to put the assembly list in order. Normally no problem, but the list is in source destination pairs. So the fucking file was being put in a different directory than the one the script was looking for it in and failing. And that's the story about how my company just paid 3 engineers a quarter of a man hour each for something that would have been resolved in 30 seconds via file search/copying and pasting a file path. Related note: our process for building an install is now about 4 hours long with no change on process besides the BCAK.

At school during my first Java project we had to make a simulation of a parking garage and what effects price changes would have in order to find the most optimal business model from some company.

At the project kick off.

School: "we will be checking your code for plagiarism. if you use code from the internet, even if its 2 lines you need to mention the source. otherwise you will fail this cource."

We go on to do the project.

Friend of mine who was in another class sees a group presenting a 2 days old version of my teams application. theres literaly a credits button that displays the names of the people that worked on it in a popup.

Me: mentions to a teacher that my project was stolen.

They literaly didnt even change the name and pulled the entire repository from github and handed it in.

The fucking teacher doesnt even check the code / git logs after i mentioned that the entire codebase was stolen from a public github repository.

There was an endless mountain of proof to support my claim such as our team members names hard coded in the code they handed in and about 500 commits from our accounts.

I will from now on NEVER EVER mention sources when i hand in code at school.

When Do You Stop Taking Responsibility?

Let me clarify by describing four scenarios in which you are tasked with some software development. It could be a large or small task. The fourth scenario is the one I'm interested in. The first three are just for contrast.

1. You either decide how to implement the requirements, or you're given directions or constraints you agree with. (If you hadn't been given those specific directions you probably would have done the same thing anyway.) **You feel accountable for the outcome**, such as whether it works correctly or is delivered on time. And, of course, the team feels collectively accountable. (We could call this the "happy path.")

2. You would prefer to do the work one way, but you're instructed to do it a different way, either by a manager, team lead, or team consensus. You disagree with the approach, but you're not a stubborn know-it-all. You understand that their way is valid, or you don't fully understand it but you trust that someone else does. You're probably going to learn something. **You feel accountable for the outcome** in a normal, non-blaming sort of way.

3. You're instructed to do something so horribly wrong that it's guaranteed to fail badly. You're in a position to refuse or push back, and you do.

4. You're given instructions that you know are bad, you raise your objections, and then you follow them anyway. It could be a really awful technical approach, use of copy-pasted code, the wrong tools, wrong library, no unit testing, or anything similar. The negative consequences you expect could include technical failure, technical debt, or significant delays. **You do not feel accountable for the outcome.** If it doesn't work, takes too long, or the users hate it, you expect the individual(s) who gave you instructions to take full responsibility. It's not that you want to point fingers, but you will if it comes to that.

---

That fourth scenario could provoke all sorts of reactions. I'm interested in it for what you might call research purposes.

The final outcome is irrelevant. If it failed, whether someone else ultimately took responsibility or you were blamed is irrelevant. That it is the opposite of team accountability is obvious and also irrelevant.

Here is the question (finally!)

Have you experienced scenario number four, in which you develop software (big as an application, small as a class or method) in a way you believe to be so incorrect that it will have consequences, because someone required you to do so, and you complied *with the expectation that they, not you, would be accountable for the outcome?*

Emphasis is not on the outcome or who was held accountable, but on whether you *felt* accountable when you developed the software.

If you just want to answer yes or no, or "yes, several times," that's great. If you'd like to describe the scenario with any amount of detail, that's great too. If it's something you'd rather not share publicly you can contact me privately - my profile name at gmail.com.

The point is not judgment. I'll go first. My answer is yes, I have experienced scenario #4. For example, I've been told to copy/paste/edit code which I know will be incomprehensible, unmaintainable, buggy, and give future developers nightmares. I've had to build features I know users will hate. Sometimes I've been wrong. I usually raised objections or shared concerns with the team. Sometimes the environment made that impractical. If the problems persisted I looked for other work. But the point is that sometimes I did what I was told, and I felt that if it went horribly wrong I could say, "Yes, I understand, but this was not my decision." *I did not feel accountable.*.

I plan on writing more about this, but I'd like to start by gathering some perspective and understanding beyond just my own experience.

Thanks