I hired a woman for senior quality assurance two weeks ago. Impressive resume, great interview, but I was met with some pseudo-sexist puzzled looks in the dev team.

Meeting today. Boss: "Why is the database cluster not working properly?"

Team devs: "We've tried diagnosing the problem, but we can't really find it. It keeps being under high load."

New QA: "It might have something to do with the way you developers write queries".

She pulls up a bunch of code examples with dozens of joins and orderings on unindexed columns, explains that you shouldn't call queries from within looping constructs, that it's smart to limit the data with constraints and aggregations, hints at where to actually place indexes, how not to drag the whole DB to the frontend and process it in VueJS, etc...

New QA: "I've already put the tasks for refactoring the queries in Asana"

I'm grinning, because finally... finally I'm not alone in my crusade anymore.

Boss: "Yeah but that's just that code quality nonsense Bittersweet always keeps nagging about. Why is the database not working? Can't we just add more thingies to the cluster? That would be easier than rewriting the code, right?"

Dev team: "Yes... yes. We could try a few more of these aws rds db.m4.10xlarge thingies. That will solve it."

QA looks pissed off, stands up: "No. These queries... they touch the database in so many places, and so violently, that it has to go to therapy. That's why it's down. It just can't take the abuse anymore. You could add more little brothers and sisters to the equation, but damn that would be cruel right? Not to mention that therapy isn't exactly cheap!"

Dev team looks annoyed at me. My boss looks even more annoyed at me. "You hired this one?"

I keep grinning, and I nod.

"I might have offered her a permanent contract"

TL;DR: One of my coworkers is a genius engineer and doesn't get as much recognition as he deserves, whereas another extremely mediocre engineer on the team gets praised for his crappy applications.

We have one engineer on our team (let's call him Hank) who started with me at the company when we were interns, and man is he a freaking genius. I swear, you could give this guy any language/library/framework, and he'll be fluent in it in less than a week. He's singlehandedly written two of our most complex applications by himself, and has a great sense of UX as well. All of his apps look fantastic.

The problem is, I feel like he doesn't get anywhere near as much recognition as he should. I try to talk him up to our manager, and our manager knows that Hank is smart, but he also overlooks him for promotions and praise because he's a little spacey (he's got quite the case of ADD) and doesn't speak up very often. He's got trouble focusing sometimes, but when he's in the zone, he can write an exponentially better and more complex application in 2 days than some of our other engineers can do in 4 months.

For example, we have another engineer on our team (let's call him Phil,) and the entire team has their heads so far up Phil's butt that I'm surprised they haven't suffocated yet. Don't get me wrong, he's a smart guy. He's great with the more basic aspects of our job, but when it comes to writing an application, he has no idea what he's doing, and he takes months to write something that should have taken him days. Then when he finally releases it, it's riddled with bugs. But everybody praises and bows down to him for it. "Oh Phil, this app is amazing. You're a genius, you deserve to be a Lead." Then we have Hank sitting quietly at his desk, banging out his 3rd big application of the month, and people say "Eh, nobody's going to use those apps anyway. He's wasting time." And I'm standing there thinking, "You asshats, we already have a solution for the app that Phil wrote, and the entire company is already using it. It's exponentially better, why did you let him waste time writing this when there's already an existing solution?!"

Oh well, I hope Hank gets some recognition soon. He certainly deserves it.

I want Gordon Ramsey to start a IT program in the same fashion as Hotel Hell and Kitchen Nightmares

He'll sit at a desk with a laptop, examining code as if he's eating food, venting frustrations and screaming insults out loud

Then he'll have a talk with the team and see how they work on a day

After that he'll go into the freezer (server room) and scream at mold and cockroaches

Then comes the intervention where we discover that the PM is still grieving about the death of his original programming language and the team loves him but thinks he should move on

The next day the development studio is modernised and has a candy bar, tennis table and everyone is forced to use linux on their new macbooks

Then we experience a good day where everything is great and velocity is through the roof

Then Gordon leaves and everything is shit again

An interview via Skype
HR: (ask some technical questions)
Me: (give some technical answers)
HR: Great! I will send your answers to technical team and let you know asap. Have a nice day!

Suddenly I lost all my interests on that company.

1. Humans perform best if they have ownership over a slice of responsibility. Find roles and positions within the company which give you energy. Being "just another intern/junior" is unacceptable, you must strive to be head of photography, chief of data security, master of updating packages, whatever makes you want to jump out of bed in the morning. Management has only one metric to perform on, only one right to exist: Coaching people to find their optimal role. Productivity and growth will inevitably emerge if you do what you love. — Boss at current company

2. Don't jump to the newest technology just because it's popular or shiny. Don't cling to old technology just because it's proven. — Team lead at the Arianespace contractor I worked for.

4. "Developing a product you wouldn't like to use as an end user, is unsustainable. You can try to convince yourself and others that cancer is great for weight loss, but you're still gonna die if you don't try to cure it. You can keep ignoring the disease here to fill your wallet for a while, but it's worse for your health than smoking a pack of cigs a day." — my team supervisor, heavy smoker, and possibly the only sane person at Microsoft.

5. Never trust documentation, never trust comments, never trust untested code, never trust tests, never trust commit messages, never trust bug reports, never trust numbered lists or graphs without clearly labeled axes. You never know what is missing from them, what was redacted away. — Coworker at current company.

Boss: Great news, we are getting another backend dev from another team to help us out.

Me: Cool, hopefully we don’t have the same trouble as the others, not replying, never writing anything down etc.

Boss: No, I’ve worked with her before. She’s much more passionate about doing things right, using best practices and all that stuff.

Me: Oh that’s perfect, great news!

Boss: Yep! ... just be aware she has a tendency to get very easily confused. She delivers the wrong thing from time to time and might need to redo stuff semi-regularly.

Me: ... ... ...

Boss: It’ll all work out. Don’t worry. Ok gotta run.

*deep breath*

Remain calm, don’t freak out, remain calm, don’t freak out.

*deep breath*

Ok, so my sort of new manager (had a slightly different manger-ish role on the team), has for the third time in as many months, just sent an email criticizing the dev team for our working from home-ness (which for the record has not been that bad, 2/3 or 3/3 have been in everyday for the past month)

In this same period, there has been late nights, weekends, successful releases, I’ve been invited to talk at a conference about my work (not a particularly big one, but still). Point is, everything is going well, very well in fact.

There has been no emails discussing our great work, thanking us for extra work, thanking us for picking up slack from other teams who are down a few people etc. no our major concern it seems is the “optics” of our team not being present in the open space.

Our contracts list flexible working hours, and his boss has frequently told us WFH is fine when things are too busy. But no he is complaining for us to get our hours in the office in line and make sure we are in the office more.

It’s been a particularly long and frustrating week, and I’m very tempted to inform him that if he is concerned about my chair and desk looking empty, that I can put them somewhere for him where they will always be occupied until a surgeon can remove them.

However, thanks to the deep breaths, I’ve managed to restrain myself long enough to run this past you all first and ask advice.

Please help,
Sincerely,
My sanity

Manager: So great news, we will also be building a new app this year!!

Dev: We only have 2 devs and we already struggling to maintain/build our current portfolio of applications. I don’t think we have the resources to support another.

Manager: Nonsense, this is a very small project management app that was requested by the CEO himself!

Dev: …We already have MS project, why can’t they just use that?

Manager: The executive team isn’t interested in learning MS Project, it’s way too complicated. They want us to build an internal version of MS Project one feature at a time so they can pick it up over time instead of getting overwhelmed with learning MS Project all at once. It also needs to have loads of customizable automation features so leadership doesn’t ever have to get “in the weeds” having to work with it. It needs to basically run itself!

Dev: …What about this is small?

Manager: Well that is the requirement.

Dev: …

Team: Finishes SudoCode.

PM: Great, now let’s convert our sudo code to python.

Team: SudoCode.py

Dev manager: great news guys. We’ve built a new tool to do automated testing on apps. We’ve gotten rid of the old Appium solution we were using and built this new one.

Me: why not just use the inbuilt native stuff? Click to record works really well.

Manager: nah we thought it would be more flexible to build it ourself.

Me: ... ok ... moving on ... how does it work?

Manager: well this new .jar, you download it, pass in a config file, setup up your simulator and appium and the jar will do everything for you.

Me: ... wait you said you hate Appium? Now you’ve built a wrapper around it? And it doesn’t even set everything up, you’ve to do it all by hand?

Manager: oh we had too, would be too much effort to replace it. Don’t worry we can now write all our tests in .yaml config files instead of using Appium.

Me: so we’ve lost the ability of auto-complete and type ahead, everyone has to upskill on a new tool, it offers no new features over what’s available out of the box and we’ll have to deal with new bugs and maintenance and stuff our self ... because we need more flexibility?

Manager: oh don’t worry. The guy who built it is staying here. He’s going to deal with bug fixes and add features. He’s only one guy, but he’s really sharp, it’ll be great for us and the team.

Me: ... ... ...

*audible noise of soul breaking*

Me: ... ok thank you. I’ll look into this new tool

Once we were going to present a web service to governmental firm. All is going well so far and my boss asks me to host the web application the day before the presentation.

I hosted it and all was good with demo production tests, but I had a bad feeling.

While it was running on our server, I also ran it locally with a reverse proxy just in case.

* Meeting starts *

* Ice broken and down to business *

"And now our developer will run the demo for you..."

* Run the demo from my laptop to double check --> 500 Internal Server Error *

Holy shit!!!

* Opens reverse proxy link on my laptop. Present demo during meeting. Demo works like a charm. *

Firm representative: "Great! Looking forward to go live."

*Our team walks out*

GM: "Good job guys"

ME:

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.

Had a team with

1 entrepreneur who has this great billion dollar Idea and want me to sign an NDA before he can share the idea

1 newb who thinks that X language is the coolest because that's what everyone on Hacker news says

1 person who spends more time with other team than yours. I'll be fortunate to even spot him during the hackathon. Aka, "networking guy"

And then there's me, wondering why was I even here in the first place

Oh wait, that's the every hackathon I've been to.

A recruiter called today.

A new job proposal. Higher salary, manage some 5 men team, DevOps buzzwords, cool product, great conditions but then she says "and we're working only in Windows environment".

My ears ringed "only in windows env".. "only windows"... "windooowwssss".

"Nope, thanks, have a good day!" - hung up.

Ahhhhh devrant... long time no see.

I just need to get something off my heart. The past two years, I worked for the same ISP in Germany, but now as a devops engineer. Well, popo hit the fan really quick lately..

First a good friend, team lead for one of five areas in Germany, quit his job. He was one of the nicest persons I knew, and he believed that all that five areas should work together and share dev resources. Thats why I work mostly in other areas as developer.

Shortly after, his deputy quit as well. I heard that this specific area, the management were a bunch of dicks, but wow!

A short while later, I learnd the hard truth, why those two good friends quit, and that brings me to this story. In a meeting I readied myself up to present my new plattform - a social room - to management. I got a lot of positive feedback from others and we thaught managment would approve of the project. But nope. "We can buy from external, we dont need to program ourselfs. In fact lets stop spending money on internal programming, we should outsource everything!"

I was baffeld... Wtf did i just witness? My team lead didn't say anything, and afterwards I didn't dare to question it, but I told most of my close dev friends and we all realizied, that the rumors were true... We will be shifting into project managment.

At this point, I realized that I wasnt having it, and made a linkedIn account, not because I wanted to switch jobs, but because, meh you never know.

One week ago, one of my bestest buddies said he will quit and join his team lead that left eariler this year, I was heartbroken. Me and our other buddy are devestated, because now we have to do everything he had done. Management didn't listen as we told them that nobody can maintain his code. I have so many projects, I can bearly keep up with them. Now I got a lead role for creating the server infrastucture for a huge project my buddy was working on. Only as specialist and not PM, but his Team Lead thinks I am replacing him!

Last week I got a message on LinkedIn, a consulting firm reached out to me to aquire me as a new consultant or devops engineer. They look great, only less vacation (26 instead of 30 days), 40h shifts instead of 38h and only slightly more base payment. I currently receive about 53.000€ a year, the new firm only grants up to 60.000€ a year for anyone. Otherwise, they look great.

With all my buddies quitting around me, work getting more while time developing decreasing, I don't know what the right thing to do is... There is no way I can get a payment increase in my current position. I always say "my workplace is save, but my work isnt". I don't want to do project managment.

Today I have a meeting with my team lead, she is really nice btw. This is an annual meeting where we discuss my future in the company etc. Shortly after, I have a meeting with the new firm to discuss a bunch of questions I have.

I dont know what to do...

Edit: I missed you, devrant

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.

One of my previous managers would constantly make promises our team couldn't keep. "You want it in a week? Sure, we can finish it in a week! You want it tomorrow? Sure, we can do that!"

It got so bad that our team basically had to stage an intervention. At one of our standups, we flat-out told him that even if the entire team dropped all of our other tasks to focus on the one big project, we still would not be able to meet the deadline he'd promised the client.

And that fucker actually said, "Well, if you want to come in on the weekend to work some overtime, I don't mind." as if he was offering to do us a favor by "allowing" us to work more.

No overtime pay because we had salaries.

So glad I don't work for him any more. Of course, my next manager wasn't great either, it just took longer for us to figure it out because she wasn't nearly as blatant about it.

When a great developer in your team decides to leave for a bigger company and then half of his last day is for him to share all the knowledge he can to the team.

I'm a little sad about our loss, but really glad for him and for all the things I just learned.

Blender.

3D modelling, UVs, texturing, animation, video editing, compositing, motion graphics, motion tracking, 2D animation, and a fucking powerful render engine? Check.
Great community? Check.
Powerful and easy scripting system? Check.
A well organized dev team? Check.
People who care about UI/UX? Check (look at Blender 2.8).
Does it compete with a major corporation that would go into sloth otherwise? Check. (If you thought M$ was shaftware wait till you see Autodesk)

There are other FOSS projects that I really like, but my vote definitely goes to Blender.

We have no more time for all this Agile stuff!

Half of our developers might have been injured when we built the Great Wall of China, but no worries, we've listened to your complaints about feeling overworked!

You can take 3 extra days off this year. Meanwhile, we're starting the next project.

We're building some pyramids.

What? You want Scrum and sprints? Sure, do sprints, whatever helps us build those pyramids!

Requirements? Refinements? What requirements are there to refine?

We require a giant pyramid.

For v1, you can build the foundation out of wet mud. It must be 500 meters. Wide, or high, we're not sure yet, we'll get back to you on that. It must have less than 4 sides, but certainly more than 3.

The Frontend team has already built a part of the entrance using 60 semi trucks filled with papier-mâché, pipe cleaners and glitter.

Now go build already!

Yesterday I had my performance review discussion with my manager after about 6 months into the job, which is my first dev job. Before this, I had spent about 2 years in a support role after graduation, but always yearned to build something cool and be a full time developer. Hence I had made the lunge in spite of a pay cut into a development role.

For the past 6 months I was asked to develop a bunch of features on top of legacy code which is ~15 years old. I did my best and brought in the best ideas and practices onto the table and delivered on time. The features turned out great. I enjoyed working with the team and the team loved me back!

But at the back of my mind, I was hoping that I would get to work on something new and relevant. To quench this thirst, I used to spend my personal time on side projects.

The managers and the leads who have been observing me all along, told me yesterday that my manager got AMAZINGLY positive feedback from the leads and my teammates (who are like 10 years senior to me). Going forward, I get to work on any CRAZY idea and pick up any technology I like with the goal of revamping our product. Essentially I get to work on my side projects full time as long as it adds value to the company.

Ohhhhhh YEAH!

Wish me luck. 😎

PM: I spoke with x client, they really like x feature and want to continue.
Me: great, I'll let the team know.
PM: Yeah, I told your team already.
Me: Oh. What did they say?
PM: They all told me to tell you first, so you can tell them.
Me: 😏

I got laid off from my previous position as a Software Engineer at the end of June, and since then it was a struggle to find a new position. I have a good resume, about 4 years of professional dev experience and 5 years of experience in the tech industry all together, and great references.

As soon as I got laid off, I talked to my old manager at my previous company, and he said that he'd love to hire me back, but he just filled his last open spot.

In order to prepare, I had my resume reviewed by a specialist at the Department of Labor, and she said that it was one of the better resumes that she had seen.

There aren't a huge amount of dev jobs in my area, and I got a TON of recruiter emails. But they were all in other states, and I wasn't interested in moving.

I applied to all the remote and local positions I could find (the ones that I was qualified for,) and I just got a bunch of silence and denials from all my applications. I had a few interviews that went great, but of course, those companies decided to put the position on hold so they could use the budget for other things.

The silence and denials were really disconcerting, and make you think that something might be wrong with you or your interviewing abilities.

And then suddenly, as if the floodgates had opened, I started getting a ton of callbacks and interviews for both local and remote opportunities. I don't know if the end-of-year budget surpluses opened up more positions, but I was getting a lot of interest and it felt amazing.

Another dev position opened up at my previous company, and I got a great recommendation for that from my former manager and co-workers. I got a bunch of other interviews, and was moved onto the next rounds in most of them.

And finally, I got reached out to regarding a remote position I applied for a while ago, and the company was great about making the interview process quick and efficient. Within 2 weeks, I went from the screening call, to the tech call, and to the final call with the CTO. The CTO and I just hung out and talked about cars/boats/motorcycles for half the interview, and he was an awesome guy. AND THEN I GOT AN OFFER THE NEXT DAY!

The offer was originally for about the same amount as I made at my previous job, but I counteroffered up a good amount and they accepted my counteroffer!

It's a great company with offices all over the world, and they offer the option to travel to all those offices for visits if you want. So if you're working on a project with the France team and you think that it'd be easier to just work with them face-to-face, then the company will pay to fly you out to Paris for the week. Or you can work completely remotely. They don't mind either way.

I'm super excited to work with them and it feels great to be back in the job world.

Sorry about the long post, but I just wanted to tell my story and help encourage anybody out there who's going through the same thing right now.

Don't get discouraged, because you WILL find an awesome opportunity that's right for you. Get somebody to go over your resume and give you improvement recommendations. Brush up on your interviewing skills. Be sure to talk about all the projects you've worked on and how they positively impacted people and/or companies.

This is what I found interviewers responded the best to: Be sure to emphasize that you love learning new things and that you love passing along that knowledge to other people, and that your goal is to be an approachable and reliable source of knowledge for the company and to be as helpful as possible. It's important to be in a position that encourages both knowledge growth and knowledge sharing, and I think that companies really appreciate that mindset in a team member.

Moral of the story: YOU GOT THIS!

Not laughing.

Not cursing.

Both for interviewing and being interviewed.

Some interviews could have been taken straight from a mexican telenovela.......

"Yeah, I worked for a year in the Walmart IT administration."

"Ok, what did you do?"

"Oh I had the high responsibility of taking care of swapping printer cartridges, programming the registers, stuff like that..."

"You apply for a senior database management role, you're aware of that?"

"Yeah. I took a bootcamp for 3 months in the evening after work. I'm up for the job and expect a payment of <lol, even having a stroke while writing a payment check that number will never happen>".

I made that up - but we had these cases... The story is just rewritten and mixed up for obvious reasons.

When I'm being interviewed, the same thing can happen by the way, too.

IMHO a interview is made not only for the company, but for me as an employee, too. I don't sugar coat it. I want to know what type of shit I'm getting into and how much I'm drowning in it.

Some "types" of interviewers react kinda funny when I start roasting them with questions...

For example, the authoritarian type usually reacts with disrespect. How dare u piss on my front lawn.... Kind of reaction. Which makes it hard not too laugh, because who wants to work for someone who throws a tamper tantrum during a interview? Even harder when the same guy promised you heaveb before (the flowery kind of bullshit, like everything's peaceful and fine and teams great and they have such a great leadership...)

Even worse is the patsy.

When you're sitting in an interview and the only answers you get are:

- Sorry, I don't know.
- I'm not allowed to ....
- Not in my area of expertise....

All just nice ways of saying: I will say nothing cause then I'd need to take some responsibility.

:)

The most Mexican telenovela stuff though in being interviewed is when I managed to divide a team of interviewers and it starts to become a "Judge Judy" or similar freaked out justice show...

A: "No, our team doesn't work that way".
B: "But you will in the short future, WE committed to it".
C: "Not that I'm aware of".

And me, an obvious sinner and person who enjoys entertainment and schadenfreude, just keeps adding kerosene to the fire.

"So, it seems like the team of A has its own rules which do not apply to B and C, do they also have greater funding?".

Oh it makes just fun to spur a good blood bath.

At Uni, I went from being the only programmer, to the programmer, designer, scene builder, main script writer, minigame designer, project manager, music composer, UI designer and fucking everything else.

We had a team of 4 people. The artist was great and dedicated, the production person was motivated, but lacked any technical skills and my useless fuckwit of a friend wrote literally 3, 2 note midi sound effects in 6 fucking weeks.

Thank fucking god the coordinator and a mate of mine who we got to do the animations, saw the amount I had carried and both led me to getting 2 jobs in the industry right after graduating.

Ugh, fxk. I got a promotion, I'm now a team lead for 4 developers, and I fxking hate it.

They never asked me if I wanted the position, they just threw me into it this week. They ripped me away from the team I had great chemistry with and put me on this other team with people I have no connection with.

To make matters worse, I'm also responsible for production servers of the clients of this team, one has malware even.

On top of all of this, they made me move desks for a new developer to fill my spot.

How do you demote yourself? Why would a company want someone to perform poorly (on purpose, I don't care) than to just keep their employee happy?

/end rant

Once, I overheard a conversation between my former PM and a client during a phone call.

Client: I will send the final draft of the project by Thursday.

PM: That's great to hear!

Client: When can I expect the updates to review the changes after the draft is sent? I need to present it at a meeting this weekend.

PM: It should be ready by Friday without fail!

Client: Excellent! Thank you. I will be expecting it.

PM: Sure, goodbye.

(After the call, PM joined the team.)

PM: So, team, the client for Project-A will be sending us a new draft for review and updates. They are putting a lot of pressure on us and need it to be ready by Friday at the latest. We need to treat this with a sense of urgency.

(After hearing this, we felt compelled to respond.)

Me: There's no way they would expect us to deliver an unseen draft within a day. Both the backend and Figma team members were forced to work last weekend, on Saturday, because you mentioned that Project B was behind schedule and the client needed an update by Monday. We simply can't continue working like this.

Backend guy 2: I also worked last Sunday on Project B.

Me: We overheard you telling the client that they should expect an update by Friday. It seems like you're the one directly putting the team under pressure, even though we still have three ongoing projects with tight deadlines.

(The office fell into an uncomfortable silence.)
(PM left the office without saying a word.)

Later on, I heard that he contacted the client to reschedule the expected time of arrival (ETA) after receiving the draft.

This is in one of the big 5 (not specifying which for some anonymity)

I apply for an internship.
I get an interview.
I pass the interview and get the internship.
I do great in the internship. Get an exceeds expectations.
I apply for conversion.
I ace the two interviews.
I am told that the hiring committee gave me a yes.
I enter host matching (ie to find a team to join).
...
And that's it. I never get matched (I only met 1 team that had UI focus and I had previously asked to not be put on a UI team so the TL rejected me). 1 year later I'm told sorry the offer is no longer valid.

The annoying bit is that I decided not to apply to grad school and refused all other offers under the assumption that it was a guaranteed spot.

I had a co worker who was a bit of a robot with little to none tact or social skills (let's call him Bob Bot). Once, we had one of those company events where pointy haired boss had the cringe worthy idea of having everyone share an "unusual secret" about themselves as a team building exercise.

"So Bob Bot, what is your secret?"

Bob (in the same tone you would use to deliver the weather forecast): "So for those who don't know yet, I am polyamorous. This means that I have multiple sex partners at the same time."

(Dead silence in the room)

Bob: "Oh but wait...she gets to have multiple sex partners as well!"

And that kids, was a great example of gender equality!

Was asked to help a team of interns in a remote country, finish an app. Not only were they terrible at literally every aspect of development, but were arrogant and argued their "new" ways were right.

Spent weeks on the project being nice, trying to help them, sending them links to standards and documents, pointing out unit tests shouldn't be failing, everyone needs to have the same versions of the tools etc. You know, basic shit.

Things got quite heated a few weeks in when they started completely ignoring me. Shit was breaking all over the place and crashing, as I thought we were going to build it one way, and they went and built it another.

Was practically begging the team architect and my manager for help dealing with them. Only reply I got was the usual "were aware of the problem and looking into it" bullshit.

Eventually after the app was done, a mutual agreement was reached that the 2 teams would split (I maintain they were kicked out). All the local devs were happy, managers had mentioned how difficult they were and it would be great for us to finally work on our own.

So I thought everything was fine ... until my end of year performance review came along.

Seems I'm quite poor at "working with others" and I "don't try hard enough with others", it was clear I was struggling with the remote team and "made no effort".

WELL FUCK RIGHT OFF

Not being cocky, but I've never had anything like that in a performance review for the past 7 years. I'm a hard worker, and never have trouble making friends with colleagues. Everyone in the country complained about these remote fuckers, even the manager, who I begged for help. And the end result is I need to work harder.

I came in early, stayed late to fit their timezone, took extra tasks, did research for them, wrote docs. And I was told to work harder.

Only reason I didn't quit, was my internal transfer request was approved lol. New team is looking at projects orders of magnitude more impressive, never been happier.

Have you read the devRant update? @dfox and @trogus have done an amazing job of building a great community, keeping us informed of upcoming features AND asking for our input.
The upcoming features are 10x.
I can't wait for the store to open. Please tell me killer polo shirts and unique gifts just for devs make in before the holidays. Sending my wife up to buy me stuff.
All I can say is thanks to the devRant team and all of the community for the informative, funny and get it off my chest rants. I start and end my day with devRant and enjoy every rant.

CEO calls the Android team in for a congratulatory speech. Likens us to tower builders in the age of cellular tech, building the infrastructure of something great. Then finishes his talk with “and when they were finished, they fired all the tower builders”

I think he was trying to joke, but it sure as hell didn’t feel like it.

A few years ago, I used to work at a very small company. It was a compact team, we all got along quite nicely and work was very good too, but the salary was very low.

Then I got an offer from a big company in the big city for thrice the pay, and I understood how great an opportunity this is, and I knew I would get a lot to learn from this. So, I decided to take it.

So, when I went to my boss to hand in the resignation, he turned red and started tearing into at me and threatening me. And I was taken aback, because, he was usually so nice. He even threatened to have me kidnapped, and I was so dumbstruck, I couldn't even understand what the heck was going on.

I didn't even finish my notice period. I just went home after that, and never went back.

Today is my first day at work, I hope the team will be great 😁

Currently in the middle of quarterly planning (its been fun so far). Needs to be signed off by business today.

- My team has ~25 man weeks available in terms of capacity.
- Looking at only priority 0 tasks, last night we calculated the ask from product stands at 64.
- Including P1's, P2's etc. its well over 100 man weeks.
- Email was sent around from business with a list of tasks, asking which can be dropped, de-scoped etc.

Product (non technical) response this morning:
- This one can't take 2 weeks, its not that complicated.
- This one needs to stay, It was originally a Q1 task.
- Can we make this one smaller? (currently only a 3 week task)
- 14 comments on other teams items.

<extreme-sarcasm>
... ah perfect, that cut down the items by less than half. We are now ready for the deadline in 4 hours to have all this signed off on. Great job everyone. Thanks for all the insightful discussions. Go team!
</extreme-sarcasm>

Hiring junior devs is a game of Russian roulette.

You can get some one who is smart and loves coding. In this case stack, limitations etc don’t matter and experience will be great for junior and the rest of the team

Or it will be a lazy person who watched 5 videos and think to be better than everyone else. 95% of juniors are these fuckers. Takes about 1 week to find out and fire… which starts the 3 months recruiting loop again.

So recently we re-orged to a product vs engineering (yes, I meant vs, it’s contentious) organizational structure. One of the former dev leads got picked for product and went on this lovely ass-kissing spiel about how great this was in front of our new bosses. The next day(!) he was telling his old team what to do directly to his buddy the scrum master, who works for me and casually mentioned it. How am I supposed to run engineering and deliver if every P.O. can end run around the structure? I hate all this.

Also, if the new PE tells me one more time all my problems can be solved with SQS, I’m gonna explode. Not all dev problems are a nail to fix with an sns hammer. Asynch comms has its uses, it is not the *only solution.

I feel like I’m over reacting, and yet, I still feel rage…and happy to find an anonymous place to rant about it.

I'm so over the politics....

System team: So, we've rewritten the entire site and the stats are looking pretty great. We're more than a year into the two-month transition period, and hey, that's cool, no judgement. But now we're gonna hit a license expiration on the old site, so we need to shut it down, or otherwise pay a ridiculously big amount to renew the license.

Business: nooooooooo you can't shut down the old site!

Systems: but nobody is using it

Business: yes, they are

Systems: no, they're really not, we checked and everything

Business: ...........

Systems: ok, well are you gonna pay for the license renewal?

Business: oh hell no

Systems: ok then we're shutting it down

Business: ..............

Systems: ok, it's down

Business: how dare you! We didn't sign off on that! Bring it back immediately!

Systems: are you gonna pay the license?

Business: no! now bring it back!

FML.

We have 2 layers of testing environments and production.

I tested the changes on the 1st layer, bud since it was 5min to lunch i did not test on 2nd layer which is connected to the production DB. I pushed to production and caused 5+ websites to go full retard and went to lunch.

Came back to 19emails and 3+ skype msgs about "why the fck would you do that..."

Estimated damages nearly 20k EUR and i lost some permissions for two weeks, but my great boss helped me out and cheered me up by telling stories how he took down multiple servers too

plot twist: im the team leader of our office now :)

Background: I work at a small startup company in Canada who makes simple FAQ Chatbots for companies who waste a lot of resources on the same Customer questions over and over.

So we were making this one bot for a provincial government who wanted a bot for students to be able to ask questions regarding the upcoming election and how to vote, etc. and get the answers they were looking for. Since it's Canada and a government bot, it had to be in both English AND French.

These bots take some time to train (we use Wit.ai mostly) in english so it was a challenge to train it in French. However I am bilingual (not very strong in French but can manage) so I did my best and the bot didn't turn out too bad. (English was great, French was, Id say, "not terrible").

HOWEVER, now that it is done (The company loved it, even with the less than perfect french version). The sales team (who know nothing of the process of making/training these bots) is now telling companies we support "SEVERAL LANGUAGES" and are currently about to sign a contract with a company overseas that wants a bot done IN JAPANESE!!.

To make matters worse.. when we (the dev team) brought up that it would be EXTREMELY difficult to do this, their answer was ... "You did it in French so you can just do the same but in Japanese"

HOW DOES THAT EVEN MAKE SENSE.

Oh well, Rosetta Stone here I come, I guess it's time to learn Japanese.

I am tired of toxic politics at work.

Signs of a toxic workplace:

* (good) decisions are discouraged rather than encouraged.
Someone wants to introduce a great optimization and guess what the reply is (often from someone IT-ignorant): wait a minute, you can't do that because we have all these nifty little hacks and if you dare to suggest change to our shitty system, we could not allow that! We want to stay in our comfy zone, no no!

* no one can make a decision unless Mr. favorite-developer-everyone-likes says it's a good idea. And even if he's wrong, no one cares to listen to anyone else's idea on it. Stupid Feudalism. One man decides over the entire codebase. That's just idiocy. Where's TEAM in there?

* thinking years of experience equals intellectual capacity. It certainly does not! There are senior developers with 15 years of experience who don't even know how to open commandline, or they didn't even know about Chrome developer tools, or how the HTTP spec is built. That shit just makes me cry inside. How can you give these peoples the title of senior when they know less than a freshman year kid?!

* ignoring people's education and/or capacities. "You just graduated, so you're a noob". Right, I know more than you, you idiot. You've demonstrated your ignorance often enough. Stupid ignorant colleagues.

* blaming politics (every team blames the other team and there's constant tension)

* roaming ignorance (no one in the company, and I mean no one, besides me, knows enough about Information Technology to make competent decisions or analysis)

Politics:
What gives testers the idea that they know more than other members of the team? Why do they treat devs like they are mentally challenged?
What gives PO's that same idea?
What gives managers the idea that they can just yell at developers and threaten them with time pressure? Yeah, because the customers are breathing down their neck.

Just because I am a Junior Developer, that makes me stupid? I am tired of no one caring to listen to my ideas. I could save the company at the snap of a finger but everyone ignores my opinion (and often facts) on things.
People come in and instead of asking me for help, they ask everyone else for help, including the people who don't know shit about IT; now that's insulting.

Anyway, toxic politics.

They make a great addition to the team :D thanks @dfox

CEO : this Facebook app has this great feature .

Me: yep, it’s really useful

CEO : can we make something like this in ours too ?

Me : we can sure try using this(x) method.

CEO : cool, I’ll add this into the sales team memo , and btw, it needs to be done in 2 days,
Me : but... but ...

My team is quite international and although we speak English among ourselves, most people still comment their code in their mother tongue.
I have learn a lot from reading my colleagues code. Mainly curse words from all over the world. It's great.

Me: Hey boss, if you ever need someone to get into doing DevOps related tasks for the team, I'd be more than happy to take that on.

Boss: We don't really need any dedicated person to work on that, but if we do in the future, I'll let you know.

Fast forward a few days: I am now unable to deploy bug fixes to our testing environment, now in the cloud, because all access has been blocked for everyone except the two numbskulls who thought it'd be a great idea to move EVERYTHING over (apps, configuration manager, proxies, etc) first.

Oh, and this bug is affecting production.

It was my first ever hackathon. Initially, I registered with my friend who is a non coder but want to experience the thrill of joining a hackathon. But when we arrived at the event, someone older than us was added to our team because he was solo at that time. Eventually, this old guy (not too old, around his 20s) ( and let’s call him A) and I got close.
We chose the problem where one is tasked to create an ML model that can predict the phenotype of a plant based on genotypic data. Before the event, I didn’t have any background in machine learning, but A was so kind to teach me.
I learned key terms in ML, was able to train different models, and we ended up using my models as the final product. Though the highest accuracy I got for one of my model was 52%, but it didn’t discouraged me.
We didn’t won, however. But it was a great first time experience for me.
Also, he gave me an idea in pitching, because he was also taking MS in Data Science ( I think ) and he had a great background in sales as well, so yeah I got that too.

Boss : going to up you as a project manager!
Coworker1 : well done bro
Boss : with all you knowledges, you'll be able to make great diagnotics, evaluate time for each task and lead the team
Coworker2 : you're wrong..

Me : hell no, doing stats and evaluate your shit ? Overcomunicating ?

Boss : you don't accept ?

Me : of course no! Opening my ide twice a week ? I need more fun .

Debugging a system error with a good team of fellow developers/devops people is fun.

We had an issue on Friday where we were getting a pretty cryptic error in our error reporting system. A couple of developers and I got together with a couple of devops people and we worked it out well as a team and figured out a pretty complex issue in a reasonable amount of time with everyone playing a solid role.

Nobody tried to steal the show and everyone listened to each other's ideas on what the problem might be. Through and through a great debugging session and made me think about bad ones and good ones I've had in the past.

Transport management system support team:

Me: Good day, how may i assist?

Client: Hi, Can you help me setup my printer?

Me:* Sighs deeply with great discretion*

Me: Sorry mam but we don't do that here, we
only deal with issues regarding the TMS.
You would have to contact your IT guy

Client: but you are our IT guys

Me: *Sighs even deeper*

Me: Unfortunately mam we are not your "IT
guys"

Client: Well, This issue needs to be fixed

Me: Yes mam, yes it does *Hangs up phone*

When new developers join in your team, please make a time and help them to get confidence with the project they will work on. Besides the project's documentation there is a human factor that can make the difference between a just another dev team and a great one.

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

It was my first time in Berlin. I came as a tourist but started looking for a workplace, with hopes of getting a blue card and continuing work.

I searched online, going through some hiring platforms, and sent out a few messages around. I felt a special connection (I thought I was exactly who they needed), and wrote them a carefully crafted letter of intention alongside my lavish CV.
They got back to me, and I was given this task, to do while at home. I completed it, had a phone interview, and was invited on-site for a face to face interview. Everybody felt warm, I felt a connection. We already talked salary expectations, and all was going great.

They told me they'd get back to me for the next stage. ...
and they actually DID. Yes, they did!
They invited me for a second interview, but this time to prepare a technical topic to present. So I did. I picked one of the 3 topics they offered, which was about performance optimization. I had recently read materials about that, so I felt really empowered.
So far nobody told me what I was supposed to be doing at the new job, I only knew the technologies required, and what the company did for money.
I prepared a thorough presentation, with practical demos of why some things are bad for performance. While I was showing it, many people in the room were learning about this for the first time, which means I did good. The team lead had some extra questions that I wasn't able to answer in full (needed some research), but otherwise it was great.

The CTO then asked me out to lunch, to talk over some more stuff, and we had a general discussion about what drives us, our life story, etc. He said that he'd really like me to be part of the team, and that he's looking forward to working with me.

So I've been at it for almost a month. I've met everyone, got acquainted with the team, knew the biography of some of them, proven my worth, etc. I was ensured with body language, and verbal language that everything was going great. As careful as I was with this kind of stuff, I was positive that I'd get the job. I even started planning my trips, to get the documents ready.

And then I got a message stating the usual stuff "Thank you bla bla bla we don't think we'll need your services". I was shocked, but in good faith I wanted to reply something along the lines "I'm sorry it didn't work out, all the best in finding what you're looking for", but I found out that I was blocked from contacting them.

That's right. Rejected + blocked. After a month of fucking foreplay. I get rejection, even though it hurts. But being blocked?! That's just insane!

Manager: Hey, what you working on?
Me: cough-finding another team-cough.
Manager: I didn't catch that.
Me: Sorry my throat is acting up today, i've been bug fixing all day.
Manager: Ah great, thanks.

I spent the last 3 months trying to hire new developers for my team. I found someone experienced who is great and a graduate, who is, well, a graduate.

For some reason he thinks he knows everything about our framework he has never used and seems to think he knows how everything works in our codebase which he has never seen.

That’s fine. I’ve had my share of cocky developers.

But what confuses me is that when I ask him what critical bugs are left, he reels off two significant ones. I ask what it will take to fix it. Of course he says he knows how to fix it. So I say great. Then fix it and let’s move on to a more fun part of our project.

Suddenly he didn’t know where he problem was and so I told him he had to investigate and come back with something concrete.

It’s just frustrating managing this developer who is deceitful.

After two years... I finally was able to quit my job.
I'm finally in a cool job, with a great team, with a cool project (from scratch! )
I have to learn Spring and Vue.js, knowing that I never tried any framework of these languages. But I really want to make it, I didn't suffer for two years, just to be beaten by a stack :p

Thanks for the ones who commented on my rant a few months ago, telling me to keep hoping for a better job. I got hired three days after the end of my previous contract, and I couldn't feel better now!

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

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

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

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

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

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

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

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

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

Frankly, fuck those guys.

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

Let's see how this whole thing goes.

I had a meeting today with some high level technical executives from IBM and I showed them our architecture and they were impressed and said it was rare that they saw start-ups with such great architecture. As a dev with no formal education and one year experience this makes me so proud and also very proud of my team

My boss once decided to employ a team of developers from Ukraine because it was cheap.

I worked with these people (remote) for years and their humuor, hard work mentality and intelligence impressed me.

They became my friends and i have visited them in Poltava many time since.

Please fight for Ukraine! A lot of great devs are there!

Christmas reminds me of my favourite development team ever. I first visited the team for a quick hello, before I started working with them, at Christmas time. Unlike the rest of the the company they had decorations and Christmas treats and the radio was on with Christmas songs. This set a very good impression.

When I did come to join them after the holidays I discovered that this team like having treats, would often sing songs together randomly and even make up new ones about their code on the spot. They had a great attitude to work and made the working environment a fun place to be. We did get lots done but I also learned so much being with them. When I left they wrote me a card filled with raps they had come up with reflecting my time with them. I still have that card.

I miss you guys dearly. Merry Christmas xxx

Me: soooo can you get this done by next week?
Other dev: well who knows what rabbit hole I'll fall down. There's no way to tell.
Me: can you just avoid falling down a rabbit hole? We have a deadline.
Other dev: oh ya there's no way to know for sure.
Me: ....... Can you please try harder
Other dev: I'm trying I can't.
Me: ................

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.

Conversing with developers can be frustrating.

Here is a good one from today. 2 people 1 women (let’s call her W) and one man (let’s call him M)

W: “Hey guys! Our team is looking for lots of great developers. Front end, back end, data, dev ops. At above market salaries with a great team! Reach out to me is you want to chat. I would love to hear from you.”

Translation: I have a great offer and want to help others achieve and strive in their careers.

M: “also, guys/less-gendered-alternative plz” proceeds to chastise this women about using the word guys.

Translation: I have no level of social awareness, but I have a need to feel big and important. So I’ll take offence for those who aren’t offended to make me feel better about my lack of fucking personality.

————

I’m not really concerned about opinions about the gender issue. It isn’t about that.

It’s just tiring dealing with these people’s bullshit.

It’s time to grow up folks, stop arguing on the fucking internet.

————

I also once saw a developer chastise 2 women we worked with while we were out for drinks for the exact same thing; using the word guys.

He was so busy “defending” them from themselves that he ended up making them uncomfortable and then they left.

He was saying “don’t exclude women” while fucking excluding the only women there.

What a fucking douche.

it was 12am when we are ready to launch our new web design which requires a lot of hardwork and routing processes. my team lead was the one who pushes the button to production using "cap production deploy" command. everyone in the room (including PM) was like counting down like launching a rocket to space. the feeling is great knowing that everyone was sleepy at that time. im glad it went smooth and everyone congratulates each other.

Microsoft Teams can burn.

Who the fuck thought it would be an excellent workflow, when you want to COLLABORATE IN TEAMS between users in different domains, that each sorry bastard needs to manually log in to a second Teams tenant and loose all the context from their main Teams tenant !?

On random occasions the fucking authentication token expires. I send messages to my team mate in another domain. Three days later I am pissed off because they don't answer. It turns out their authentication token has expired so when they are on their main tenant they don't get any notifications before they manually log in to our tenant as a guest. HOW FUCKING GREAT IS THAT AS A NOTIFICATION SYSTEM ??!

Would it be that fucking difficult to maintain a notification bar with all tenants and note with an exclamation mark or something REALLY FUCKING SIMPLE to hint about an expired token ? It's not like this is magic, Slack does it already.

FUCK !

Slack culture.

Yes, the chat application.

Fuck it, fuck mattermost, HipChat, Skype, and whatever other digital text medium for team communication.

These are great applications, but used for great evil. They feed cliques and passive aggressive "side" conversations. Every team I've been on has something like this, and it allows people to cultivate hate for one another even though they're sitting in the same room.

Texting allows you to complain about a coworker to your clique. Each clique can have it's own thread. This empowers people to silently rip into other team members. It prevents rational adult conversations and builds stupid little secret societies.

Soft rant...
So I'm working at the company for 8 months now. Best 8 months in my career, great team mates, great work, the best - a team leader who is one of the best developers I've ever worked with, but more importantly he is a good friend, brother like. We had great time, from the interview we understood there is a bro-mance there.

So why am I ranting? He got promoted and became a group leader, not even of my group. Now we don't have a TL and we're afraid they won't be able to get a swell guy like our exTL

I've been working with some new programmers now, trying to make this a place where people actually like working at. In my experience, most workplaces are bottom of the barrel shit, so I really wanted to try and make this the opposite, at least for the engineering team. When I hear them say how much they like working here, and how jealous their friends or family are at how much they are enjoying themselves and chilling with their coworkers and even their boss, it makes me feel so nice.

It might be a tiny company, but spreading happiness is great.

The best memories are always when the team works well and we achieve something great together.

So my colleagues and I are somewhat great friends. (As in my first rant, I'm a practical evil joke guy). Since our boss thinks we are working on the production server (in reality, he commissioned it to be done in 4 months time. We all got it done in a month.), we get our own little room in the building, each time one of us walks in, we greet each other with a nice "go fuck yourself". Not to be mean, but just as a joke.

I decide to leave the room to go get a drink and I said I would be back. Guess who wants to see the dev team to see where they are on production? Not our boss, the fucking CEO. This isn't a big company, but this definitely was not expected.

So, he walks in and greets the team. He gets greeted with "Go fuck yourself".

I come back to see my team outside, and the CEO asking me why they said that. So after 15 minutes of ass ripping, the CEO leaves, our jobs barely intact, and I get to talk with the team about why we have to be nice to our superiors.

I am the manager of a customer service team of about 10-12 members. Most of the team members are right out of school and this is their first professional job and their ages range from 22-24. I am about 10 years older than all of my employees. We have a great team and great working relationships. They all do great work and we have established a great team culture.

Well, a couple of months ago, I noticed something odd that my team (and other employees in the building) started doing. They would see each other in the hallways or break room and say “quack quack” like a duck. I assumed this was an inside joke and thought nothing of it and wrote it off as playful silliness or thought I perhaps missed a moment in a recent movie or TV show to which the quacks were referring.

Fast forward a few months. I needed to do some printing and our printer is in a room that can be locked by anyone when it is in use (our team often has large volumes of printing they need to do and it helps to be able to sort things in there by yourself, as multiple people can get their pages mixed up and it turns into a mess). The door had been locked the entire day and this was around noon, and the manager I have the key to the door in case someone forgot to unlock it when they left. I walked in, and there were two of my employees on the couch in the copier room having sex. I immediately closed the door and left.

This was last week and as you can imagine things are very awkward between the three of us. I haven’t addressed the situation yet because of a few factors: This was during both of their lunch hours. They were not doing this on the clock (they had both clocked out, I immediately checked). We have an understanding that you can go or do anything on your lunch that you want, as long as you’re back after an hour. Also, as you mentioned in your answer last week to the person who overheard their coworker involved in “adult activities,” these people are adults and old enough to make their own choices.

But that’s not the end of the story. That same day, after my team had left, I was wrapping up and putting a meeting agenda on each of their desks for our meeting the next day. Out in broad daylight on the guys desk (one of the employees I had caught in the printing room) was a piece of paper at the top that said “Duck Club.” Underneath it, it had a list of locations of places in and around the office followed by “points.” 25 points – president’s desk, 10 points – car in the parking lot, 20 points – copier room, etc.

So here is my theory about what is going on (and I think I am right). This “Duck Club” is a club people at work where people get “points” for having sex in these locations around the office. I think that is also where the quacking comes into play. Perhaps this is some weird mating call between members to let them know they want to get some “points” with the other person, and if they quack back, they meet up somewhere to “score.” The two I caught in the copier room I have heard “quacking” before.

I know this is all extremely weird. I wasn’t even sure I wanted to write you because of how weird this seems (plus I was a little embarrassed). I have no idea what to do. As I mentioned above, they weren’t on the clock when this happened, they’re all adults, and technically I broke a rule by entering the copier room when it was locked, and would have never caught them if I had obeyed that rule. The only company rule I can think of that these two broke is using the copier room for other purposes, preventing someone else from using it.

I would love to know your opinion on this. I tend to want to sweep it under the rug because I’m kind of a shy person and would be extremely embarrassed to bring it up.

When I landed my dream job in 2009 (which is also be my first job in the industry), I had no clue about python. The company just asked me three months after starting with them for something related if I'd like to join the automation team. It sounded like fun to me, so the company paid for me a private remote instructor for a week. Then I went across the world to the main office to work directly with our automation team for two weeks. I picked it up quickly and well (or so I thought) and was churning out scripts for a few years.

Through a series of unfortunate events, I and many others no longer work there. Five years later, I have a renewed interest in Python so I take online courses to relearn it. Why is it so much harder this time around? I do remember it, but not in great detail nor as well as I did, but I'm baffled that I'm struggling so much the second time around.

It's only Python! Still getting enjoyment out of it as I did before though.

So there's a new team member in the project (me & him), he's assigned to make the frontend, which is great since I'm so proficient doing back. But he starts by doing backend tasks and the fucking frontend which is the most delayed part of the project is still untouched.

Former boss taught me to care about the place where you work and how to think always as a team and not just to improve my skill.

Current boss taught me that you can be excellent designing and writing code, bur if you don't know how to transmit your ideas to others in a way that they understand, you're pretty much stuck.

Great bosses so far...

Ever fuckinn "townhall meeting" at previous workplace. It was such an utter waste of time that even after leaving that place I still rage when thinking about it.

Every 4-6 months they would setup this useless crap of a meeting that drags on for over 1-1.5 hours of execs talking themselves up and trying to convince how great they are. And since they were cheapskates they would send out an email asking everyone to not join from their desks but congregate in the conference rooms to save on the dial-in. The conference rooms didn't have adequate chairs, vantilation or good enough aircon to handle twice/thrice the capacity of people standing in the room.

The marketing exec would go on and on about how great the media visibility is, how many views/likes they had on a linkedin post last month. The sales exec would blabber on about how their team is great and that the customers themselves are lining up and there is no competitor. Straight after the CFO would lecture on how the year is still difficult financially (in disguise justifying the peanuts of pay). The last exec, no matter who that is would specifically raise a point that the previous speakers didn't mention his/her team while thanking others.

This is also not a small company, the total headcount was just over 900 and roughly 500-700 people would be attending these townhalls. Imagine the amount of man hours wasted on that shitshow.

Our team spent 2 continues weeks working on deadline, without going home, doing all our activities in the company, learning from each other, nd developing great apps. Once upon a time.

It's not that my work is hard. Basically, all the work I do these days is something I've done before with a slight twist on it.

I just feel underappreciated.

"bUt u mAkE sO mUcH mOnEy dO uR jObBbb!!"

How much money I make should not suppress how I feel at a company. Two years without a raise, every company meeting is a circle jerk for the sales team, and whenever our work is mentioned it's "Great job to the PMs for getting this to our clients."

Fuck you guys. Lol. This is a team effort from all sides, but to put engineers last on the "kudos" ladder is just so shitty.

The Return of Mr. Gitmaster:
So there is this colleague I already ranted about several times. After my previous team lead had confronted him about not doing much work, there was some irritation because he showed not up at work, but it turned out the external training he did was just a week earlier. Then he was ill a week, another week vacation so we didn't see him much. Not that his pre- or absence makes much difference to our repo: When his and my team lead looked at his commits of the past three months they found like the one copy-pasted HTML-form that wouldn't even show.
Fast forward to now, where we have a new team lead and we were going to lunch with Mr. gitmaster. So we got some more hero stories from the great work he was doing in the previous company. How he was graphically monitoring the heap fragmentation that stupid glibc was causing to their search engine, and how much better it became with tcmalloc.
I still don't understand how he bridges that cognitive dissonance from all the superior tech knowledge he displays to not actually writing any code at all. Not that I would not have experienced some states of feeling low, in paralysis unable to write a single line of code... but he seems so full of confidence, always commenting how trivial and easy all these tasks would be, as if it's all so lightyears below his abilities. Maybe he should just become a manager - but not mine.

Dev team: This part of the app has a shitty ux. We want to fix it after we finish this feature.
Business: hey guys we think we lack data so we got some users to check our page with shitty ux and see if they think it is shit
User: yeah it’s shit

Great use of resources you chucklefucks

> Advice to new coders

Don't worry over picking language A or B.
Just pick A, use it for a month, then move on to B.
In a normal 3 year college degree you'll try multiple languages, some of which you'll never use again, and they'll each teach you something.

I had classes in Java, C, C++, C#, Prolog, Assembler, F#, JS.

Never used F# again and no one uses Prolog. But they were great for learning recursion and logic.

It's not like you take "a step down a bad path" if you pick a language you're never gonna use again.

You'll also learn new stuff on the job. We have one team that uses Go and one that uses Rust. None of the devs ever studied those languages. They were mostly former Java devs who leaned on the job.

I got cut from a contracting job yesterday I have 3 weeks left in the contract. They said I worked well with the team, had a great work ethic but didn't think I had strong enough tech skills. In the past this would have hurt my feelings and it does a little but I think my tech skills are fairly high. There were three devs working on 66 apps with no tests, some source control but most of the code in source control was older than code deployed in prod, no automatic builds, people would wait a week before checking in code, others would check in code that would not build. Today the boss asked if I had messed with app pools on the prod iIs server because something was wrong. I said no because never remote into the server. Anyway it is the end of the world and I feel fine.

So, 9months ago my scrum master came to me and asked me to spearhead a "little" API... 2months work, no worries... I started the analysis and quickly discovered that that estimation was grossly understimated...

I convinced them that it was not 3 months but 4. I alerted to the design mistakes that were made, I pushed changes and made sure the entire project worked, was stable and the best it could be... 4 months passed, target proposition donne... Several change requests since then and we have been implementing braindead CR after CR for 5 months... Most CRs came from design issued I raised but we're ignored at the time just to come back and bite them on the ass...

Horrible design, bad documentation, amateur requirements analysis... However, delivered successfully with great acceptance...

What was my reward? They rearranged my team, removing virtually every good performer.

Never did I receive a "good work" or a "thank you"... I don't want one, I am just doing my job... However can you please not fuck me in the ass!? I now have 2 projects to spearhead at the same time and virtually no team... I can only handle so much!!!

Some good news? Ok, just announced I'm the project owner of a new project, that we will take advantage and make a 2 in one.... Great! Some more work for my lap! Thank you for the workload raise!... Ok, timewise? One month! And I still don't if that includes implementation....

TL DR; did my job, got fucked with more work...

Sorry for the vent, just wandering if I should try and not do my job...

Sprint planning:
PO: I have a great idea for a new game changing feature
Team: cool, let’s talk requirements, etc
PO: nah, I trust you can come up with the best implementation possible
Sprint demo:
Team: presents the feature
PO: Why are you guys always doing it your way, instead of following my vision?!

Every single sprint...

Junior engineer asking managers on Slack about prioritisation..

Junior eng: Hey managers, I have these tasks A & B lined up and some other type of work... Is it ok if I finish A by Weds and B by the end of week or should it be done sooner? Also, is the order fine or should I prio B first?

*silence for hours*

Random dev feeling bad for junior getting no response chips in: Hey, you are doing great, that order makes sense to me and let me know if you need any guidance or have questions!

Junior dev: Thaanks and will do!

*another hour goes by*

Manager: Hi team. I have asked other engineer X to do task B tomorrow.

what the fuck. at least answer the fucking question and say it needs to be done sooner. felt bad for poor junior here. :/

My very first rant here was about the mess of ticket submission and ticket tracking applications we use, and about how we were moving to a single unified system some day.

Well, that day is today. And, predictably, it went horribly wrong.

So the way it's supposed to work is people login to the portal, search for what they want to request, then fill in details and submit. It creates a request ticket assigned to the appropriate team. (The old way involved a bunch of nonsense that you can see in my first rant).

The thing is, I found out about this today, when I got a company-wide email saying the new system was live as of this morning. None of us knew it would happen today. Not that I could've foreseen any issues just by getting the announcement early, but still, usually people find out about these things beforehand.

So, ecstatic to finally be rid of the old ticket tracking system, I log into the new system and look for our request form, which is, of course, not there. I check the old system and see that they combined every single "general request" into a single request where you pick which team the request goes to.

So I finally find the right request, pick the right department from the drop-down, and see that the request looks much better than it did on the old system. Out of curiosity, I look at the list of people who are part of that department.

I am not on the list.

My ENTIRE TEAM is not on the list.

Because they migrated the team data to the new system a year ago, when the issue tracking/reporting portion of it went live. My current team was hired approximately six months after that and apparently updating the team data in the new system isn't part of our Onboarding process yet.

So... Bright side is I guess I will have a lot of free time soon since nobody can submit new project work to my team?

tl;dr: they took a great software product and implemented it so poorly that our team can't use it.

Okay, I'm interning at a government institution & boy let me just tell you... mmmh... A FUCKING MESS!

So I'm tasked with developing a HR system that the whole company should eventually use. I tell them I'm not familiar with the open source technologies they'd like me to use, they tell me no worries, you can develop a prototype with a tech stack that you're familiar with. Also, they tell me that they don't quite have the requirements from HR so what I can do for my prototype is just develop something "general" that works according to their "idea".

Being the good intern I am, I develop quite a good functioning prototype & present it to the team who then present it to the managers.

Finally we're all called in for a final meeting with the managers & HR, and guess what? The requirements for the system are different. Almost 90% of the features we built into the prototype need to change. Also, the system must use open source technologies. The managers promise to send a detailed requirements specification document, with sample data. I think this is a great idea as there's still a lot I don't understand. I expected this to happen, so I soon start to redesign afresh, this time trying as hard as possible to consider open source technologies within my plans.

But noooo... My team wants me to "finish" the system!

"Finish" what system, I ask? That was a prototype!

"Just tweak the functionality you built to meet the new requirements".

WTF!

We don't even have the actual requirements specification document, so I'll still be coding blindly. Also, the whole system needs to be re-built using open source technology!

Instead of pushing me to develop a system blindly, with no requirements, how about you push HR to tell you exactly what they need and how it should work first!?

I'm honestly exhausted with the false sense of urgency from my team!!

Microsft (before Win 8 ): we have to fix the blue screen of death! People are pissed off seeing it appear again and again.

Windows: We will do something

*In its remastered blue screen - adds a sad face emoji, changes the shade of blue, and inserts a QRCode for the user to play with in the meantime*

Microsoft ( after win 8) :Good Job Team, it looks great now, people are gonna love it, especially the QRCode feature!

Damn! I never thought resigning from first company is not easy.
The team was amazing, overall culture was great. But after working for 2 years and making product stable enough, the learning curve started to flatten.
Decided to move on, last day was most painful. Sitting on the chair, wondering whether I did the right thing. All the memories flash black on that day. Nervous but little bit excited. Kinda mixed feelings

But turned out that job switch was even better. Good pay + one hell of learning to build product from scratch.

.net 1.1 had the best documentation ever written. Microsoft spent an enormous amount of money and a dedicated team of skilled engineers just to write them. It was kind of a great time to be a developer, even though the technology is much better now. The current reliance on community docs doesn't hold up as well.

dear female devs / haecksen, how many other female devs do you have in your team?
if not so many, how do you feel about it?
and do you get a lot of sexist bullshit or not so much?

would be great to hear your experiences.

the female quota among our devs is < 3% 😅
most of the time i don't think about it and just do my job and it's fine, but sometimes i think, it's a bit weird. also, there is this fear that people might not have trust in my skills. it can be good and bad to be "special"... anyway, having more female rolemodels / mentors / colleagues to have technical discussions with would be awesome.

Yesterday, I and my team built a good hospital management system for Trauma centers containing two apps and two websites.So that the system should contain transparency. But unfortunately, we didn't made a place in top 3 but it was a great experience to build this project with my team.

Can't stand it when devs who never bother to do anything / don't pull their weight etc. suddenly come out with:

"Ooh I'm really feeling the imposter syndrome right now, I feel like everyone around me is just leagues ahead of me and I shouldn't be here"

...then wait for everyone to tell them how amazing they are, how they're a critical part of the team etc.

No mate, imposter syndrome is a thing, but so is being a genuine waste of everyone's time. I'm not talking about having bad days, I'm talking about your work output being practically zilch for the past half a year or so because you're "not too familiar with the framework", then going after this pity party approach. As a senior dev, it's kinda insulting to all the great junior and mid level devs who do a better job while being paid considerably less.

A good boss gives you a few clear instructions and then doesn't meddle in your work.
A great boss does that, and also spends most of their time protecting the team from corporate fuckery.

99% of all bosses, though? You can't make heads or tails of their blabber, and the only way they can handle problems is throwing their team under the bus.

Being called into a meeting where you get fired for an argument you had with your CTO. But the CTO left 6 months ago and the sales department are suspiciously low on deals in the pipeline...

Shame really, I loved that job and the Dev team was great, shame the directors were bastards.

Just finished a rant about rererereinstalling windows (sorry, in a ranty mood), and now I have another reason to rant. Not the 10 new and exciting bloatware apps. Again. Lovely. No, this rant is about Edge.
You know, the new browser Microsoft is soo excited about (or was when it came out)? Just found out that it won't connect to Googles links to download chrome (tried 4-5). Because, you know, I might need to develop something. Incredible. That's some pretty high level *insertSpecialWords* from the Microsoft Edge team. "uhhhhh so your Highness, sir customer destructinator sir, our browser isn't that great. Everyone is still using chrome."
"how about we stop them from downloading that freaking amazing browser. That should stump them."
"wonderful sir! Amazing. We'll implement that straight away."
>:(
There's even a try this list of "suggestions" to fix this "problem". Including:
> Make sure you've got the right web address.
And my personal favorite, is less subtle:
>search for what you want!
Umm, I did. And then you blocked me from doing the one thing that I would realistically use this browser for. Aaand after the windows 10 forced update debacle, I'm not feeling especially "friendly" towards windows' "suggestions".
No worries though. I installed Firefox (not blocked) just to install chrome. Great job Microsoft.
10/10

Just learned the previous dev team thought a db column with a value of NULL or "Y" was a great way to handle boolean values.

devRant keeps getting better and better! Collabs are great and the new avatar pets rock! Thanks devRant team.
What do you guys think of my new pets?

The first thing that matters to me for applying for a job is how their project that I am going to work on will improve me. I have refused a job position with a higher salary just because they want me as their only developers for their website and other things. Instead, I applied for another job with lower salary but now I am a backend developer of a team of 15 developers making a great product and I have learned many experiences.

So a team of 3 went to a hackathon. One of us didn't know how to code, the other just front end and I back end.
So we started with some ideas and choose one, starting to code it.
After we were about 80 precent into it at the end of day 2 (the event had 3 days) one of the coaches came to us, saying our idea is already a launched startup out there and we had to have a change of idea at the beginning of the third day.
Other two completed the simple front-end of the new idea about 7am and went to sleep.
And I, while was awake for 50 hours already, had to code backend of a minipay app from scratch in 10 hours.
That was HARD for a newbie like me, but in the end I did it.
We didn't win anything. But that was a really great experience for me. Plus coffee was provided infinitely there ;)

Have good coworkers and be a great team.

Not too terrible but it was pretty discouraging. Spent the majority of the interview having a great back and forth with 2 devs. Finally the boss shows up 30 minutes late and very bluntly/rudely asks me the largest team I've worked on. After he found out I've only worked at small companies, he said that he had heard enough and the interview ended.

// Probably dodged a bullet anyway.

I am beyond fucking frustrated at this point. I feel pretty confident that I was just blocked from getting a position at work because they believe the current team I am on will fall a part without me. I’ve asked for a backup for years but they never got one for me. I have great folks on my team but despite knowledge transfers, they just don’t get it. I am ready to grow within the company, develop better soft skills, learn more about the other groups etc. but I don’t have the opportunity to. Also, I was passed up for someone outside of our group to manage our team a few years back despite being the lead since day 1. That’s two promotions I’ve been denied despite getting exceeds on every review I’ve ever had. I am so pissed that they would do that to me.

At some point, someone on the visual studio team thought: what people need is a clicky-draggy gui for editing yaml files for github actions.

And instead of throwing him unceremoniously out of the window, the rest of the team agreed, and said: yes, that's a great idea, it will be almost as useful as that clicky-draggy gui for editing sql commands.

introductory rant

So I am new here, hi! :)

So the devRant android app does not seem to support this mail format:
user+devrant@domain
(the important part being the "+devrant" thing)

Now I waited 2 days for a confirmation mail that wouldn't arrive and was greeted with the "please confirm your fucking mail" popup every damn time.

"Okay, let's just change my mail to user@domain and deal with it", I thought. Guess what: You can't!

So I contacted the devrant team via e-mail.
And I waited.
2 days.
No answer.

Okay.

Delete account, recreate with other mail, be happy.

Don't worry, I'm not mad. It's just really fucking ironic.

Looking forward to a great community! :)

A few years ago my boss held a brainstorming meeting to go over features for an internal reporting app. I brought up we should have related business news stories scroll on the page header like Fox business or something. He laughed and said sure. Two things happened after that.

1. Found out the marquee tag still works in chrome.
2. Yeah you bet I put that shit in there.

Anyways a meeting was held a few days after where my boss chewed me out for actually doing it. He showed the app to his boss and got laughed at by his leadership team when they saw news headlines scroll over analytics graphs.

After writing this I realize this is more his embarrassment than mine. Have a great Tuesday fam.

The new devRant vote info is great! Improvements like this is one reason we all love devRant! Thanks devRant team for implementing this.

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

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

(shortened)

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

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

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

Today Gizmo presented a new solution.

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

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

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

Things story points are great for:
- Helping the team estimate their workload for a sprint
- Discussing the relative complexity of a task / story

Things I will slap you for, hard:
- Arguing that all the easy stories you plan to pick are actually infinite story points to make you look better
- Going "yeahhhh look at me I did 5 more story points this sprint than Bob, I'm amazinggggg"
- Trying to subtly change the story point assignment after you pick a task so you can do the above while doing sod all work
- "Hmm your team only did x story points this sprint, but team poopoo over there did x+10, what's going on?!"

It would be great if CS students graduated and emoloyers could plug them in anywhere knowing that they can do their job without anymore training.

There for I think students sould have full on collaboration with high risk companies. Deadlines with serious consequences if they aren't met (i.e bad reviews on your profile). Computer science and programming really needs deep thought and concentration. Being able to work in a team to deal with issues as fast as possible.

These days you don't need to know a lot of theory to get started. Knowing it all helps, but being able to figure it out and then finding beter ways to slove the issues as you progress through becoming a master in your field really burns the knowledge and skill into your being.

Hi everyone

I'm currently an intern in a startup
I started 3 months ago and I will finish in 1-2 months

From the beginning, all the team is very nice with me and say that I do a really great job
I could learn many many things and I can say my ideas during the project

This is a message to CEO/CEO, you see, if you offer a really good internship with interesting tasks and technologies, student like me are really motivated, want to learn, want to really participe to the project even if I do more hours than I have to do
Because we, students, are like you : interested in new technologies and great ideas

Offer good internship and you will be happy to have good and motivate intern in your Company

Thank you!

Flexible schedule, remote options, good pay, great team, building something useful to humans

So I am interning at this company, and I am Coding in Go.
Now I don't have much exp with go so I'm learning it, and all of my team is cool cause they also had to learn Go. Anyways I am just petty intern-dev so everyone and everything is cool.

Migrating from python to go is quite hard.

Unlearn, You must.

What I have imagined Go, to be is:
While python has this top down approach to inheritance and polymorphism, Go has bottom up approach.
In Python child classes are derived from parent class but In Go child classes create a parent class. (this might be totally wrong, but that's how I've imagined golang)

Go is static wrt dynamic python.

I have coded in C for 1.5 years then I switched to python, so I feel that am familiar with static typing. The path that lies ahead of me shouldn't be too hard.

I would like to take a step further and say that Golang is C, but with modern syntax/semantics. It derives many of its features from newer langs like js, Python, etc while being a compiled language which translated directly to machine code.

That's all 😊

My team members are really great and supportive, I am about 10 years younger than them but we still connect and sync.

Everything is Great, Life is Good ❤️

The new devRant long story feature is great! Very nice to have them in one place. Thanks devRant team!

Our team is small but we pretty much always have fun times. Our bosses have been visiting us this week (they work in a different country) and we've been partying almost every evening, they even paid for it. Our new employee who starts officially next week was also invited. Such a great time!

User A: We need to do some check on our data. So you need to add in a new function for this, we can't use your system otherwise.
Me: Ok then.
Spends 2 days or so to get it working
Me: So this is the function we'll add. Can you confirm that its ok?
User A: Ohh...but now I'm not too sure about this. Let me confirm with my team lead on this.
User A: I just checked. Good news,we don't really need that function now. I think we can use it with the current one anyway haha. And I just confirmed this so no worries.
So I just wasted my time then. Great.

Taming a legacy system with the team using TDD and great refactoring techniques

I proposed agile training to my company.
I choose a well known coach around here, with good references.

First 3 days were great. After a month he came back for another session and check progress.

This time, he literally fell asleep during the workshop. Several times. He would ask questions, sit down and quietly fall asleep while waiting for our answers.

We were astonished and embarrassed.

He apparently had a very hard working period and could not cope with traveling and working so much. He apologized some day afterwards and didn't charge us for the day.

He never came back. The team didn't take it very well and my reputation was compromised, as well as trust in the methodology I think.

I kept saying that everybody can have a bad day, but it was probably just to defend myself and my fucking stupid idea of changing the world.

A real fucking shame. Still I can't believe when I remember this.

Great new subscribe feature! Subscribed @dfox first! Thanks devrant team, great going!

[UPDATE] on my newly joined internship

Considering how corporate the organisation is, I'm surprised how chill everyone is. My team consists of mostly millennials, which is great!
Everyone is super helpful, I honestly thought it'd be shitty experience joining in and it'd all be so formal but none!
First few days I got no work, so I went and asked my mentor and he just laughed and said go home, watch Netflix, which I definitely didn't expected cause corporates

I got web testing work twice (sad I didn't get more, but in time it will increase), got some research work currently which is cool too.

Honestly, I wasn't excited to join as I didn't know what kinda work would I even get(it was pretty vague) but I'm glad I got this.
I'll continue to update here, and sorry I couldn't update any sooner

Cheers my dudes

I am working with a team that's producing tons of new services..
And me being a fresher, reading new designs every other day with God knows complex implementations and business requirements and attending design review meetings(where I can barely understand anything)
having a great learning curve..
Hopefully, I survive this period and cope up with the inputs...
Note: Just don't ask what's my contribution.. I am gearing up for the D-Day to make my impact(not a negative one).. 😎

So the company decided to go agile. I am now a scrum master. And we have the local product owners and all. They made us do daily stand-ups.

I don't know what is a scrum master. Nobody knows what the hell is a stand-up. It seems to be an akward 30 minutes every day, when local product owner asks questions and demands status reports.

I did some googling and it seems that the scrum master is supposed to just support the team and solve problems. In our version the scrum master finds out the system architecture and requirements, fills the backlog, does the system design and reports to the project manager(s). Also reports to the clients about the general project status in an executive meetings. I also do the sprint planning, in which we fit the vague features that we are told into time tables with ready told dates.

Oh yeah, the team is just 2 guys. One of them is me. And the other guy relies completely on me to daily tell what to do, review the work and also answer all the project and company level questions that pop into his mind. He gets angry if he doesn't receive ready-thought solutions to all problems, since "you're the boss and it's your job to tell us what to do".

This is going to be a great year.

Alright, server got hacked a week ago. Bad enough on its own but okay, perfect time to change the server infrastucture completely instead of doing it later this year. Since Saturday we are working on setting everything up (game server, apache, etc.pp.) while making sure to configure everything correctly to be safer this time.

We are finally at the point where we could go back online. And what happens? One team member _now_ (6 days after the hack) suggests that it might be a good idea to format the hacked server and configure just what we need to patch the clients with it.

Great fucking idea, why didn't you have that idea 5 days earlier?! There was more than enough time already to format the old server and configure it. Another day delay, yay. X_X

Aaah, ranting really helps in those situations. Oh and Hi, I'm new here. Nice place, I like it. ^_^

My collaborator was always telling me what a great team we are, until it got serious.

Getting stabbed back in the butt and fired from your job. HAHA what great Teamwork...

After that steal all my ideas and projects and sell them as there own.

I hope that guys Flip-Flops will burn someday

Currently a lower manager (I lead a team but I report to a handful of uppers). In my line of work the holiday season means more work instead of vacation. My team consists of 4 other guys, 2 of which aren't worth their weight in shit, 1 guy who's leaving for the military soon, and 1 guy who's just okay. The first 2 are about to be fired for any number of reasons, and there's no plans to hire anyone else. The lady in charge of hiring is incompetent; should've been hiring anyways for the past several months and hasn't (not due to a lack of applicants either).

I consider myself the hardest worker of the team, and one of the best in the whole place. Well, instead of being rewarded with even so much as a peptalk, my superiors have seen fit to tell me that I'm not doing enough. Like holy shit really? Are they taking credit for my work or are they just retarded? Track record at this place isn't all that great to begin with. I'm not in a position to leave as I need the money to put myself through college, but I'm thinking about hopping on the minimum effort squad at this point.

!(isRant(thisPost));

Submitted my third pull request today in just a couple months as an intern, got told I'm doing a great job and already being considered to move to a more in depth dev team. Honestly a dream come true. Great company, great people, and I have a solid shot at a REAL full time dev position after college. I'm so happy man all that work finally paying off.

First dev job is my current one.

I'm a software engineer in test, writing automated UI tests for web and mobile apps.

Its pretty great. I work from home with flexible hours. I have a boss but he doesnt manage my dev team, he just checks in to make sure I'm getting support, training and have all my questions answered. My dev team is myself and 2 other people, both of which are cool, and all the work is dev-driven.

Might just stay here until retirement, that sounds easy.

When I was in University, there's a group project on web development. We decided to make a simple game.

Out of 5 students (including me), one was missing for the entire semester.

Another one don't know anything about any kind of programming. We asked him to write us a json file of characters' attributes. Taught him how and gave examples. Turns out that most data is missing.

Luckily the other two was great. Altogether, we covered frontend, backend and design. Finally we got the highest mark :P

Best (and worst) team ever

I work on many projects at work. There's divisions of teams and each team typically has one project. Each one of those projects have weekly Sprint meetings.

That's great! For the team. That means each team has one meeting a week so it's not too disruptive for those individuals.

Me on the other hand? I've got my hand in all the buckets. I'm on every team. I'm the only person on every team. This means I get to go to every meeting.

Let me rephrase that:
This means I -have- to go to every. Single. Meeting.

Which means I have a meeting every. Single. Day. Even if I didn't touch that project that week.

It is literally THE biggest waste of time. I sit there in a 1-2 hour long meeting saying absolutely nothing, not even being spoken to. I could be working on other projects.

And these meetings normally interrupt something I'm working on. Conveniently in the middle of me being in my zone. It makes me completely un-motivated to work for the hour before the meeting because why bother if I'm just going to get interrupted? And then it takes an hour to get back into everything after the meeting because everyone is fooling around or complaining about the meeting.

So that's three hours of my 8 hour work day completely wasted.

Looking at my reflection on the laptop screen while it is being upgraded, and thinking that the career choice i made 11 years back was probably not a great idea.
I don't understand amazon-cloud, very little knowledge of DBs, can't write a single JS class without googling, block chain are meh, don't even know python, working with a team that abuses my framework in front of me, working 12 hour shifts for last 3 years... What is my life's purpose?

!rant

Part of my job involves researching a shitload of documentation and tutorials in order to have an established and well tested point of refference for the rest of the team. As a Django guy, I have always been happy with the plethora of tutorials and what not made available for this amazing framework. Until recently I had absolutely no clue that MDN had their own Django tutorial and I must say....I am impressed! I seldom recommend something over the already great tutorial made available by the Django page itself, but this one by MDN really is worth considerind for people starting into the framework. One can even see the love that they have for the framework just by reading the tutorials.

Kudos to MDN for creating such a great resource!

Just got to test the app from the frontend team... Oh God why!!
5 minutes, found 5 bugs (c'mon testers!!)

Worst (and now it's a rant) why do designers insist on working with big screens and don't test it on a standard screen? You know? Those typical screens your users are using?

So, it looks great in a 24" screen but the focus is terrible in a 15.6" screen... No time to fix it... What should I tell the users? Works better at 85% zoom out? -_-

You just fucked up the main feature of the app! Congrats!!! The rest looks okay I guess

Our PM just send a mail to our team, that after testing the latest extension we made to the project, he could not find a single issue or bug (usually there are some minor UI problems or some edge case bugs we did not think about or know existed)
and what a incredibly great job we did, and he also forwarded the mail to all our managers up the hierarchy right under the CEO.
The appreciation is a nice change to the self-hatred I feel while coding

1-hour downtime window. Finished in 37 minutes. Yah!

Got transferred on to a new team. The team I was on previously was successful, had great processes, and very smart people. New team was floundering, very late, no processes, and crotchety. Did my best with the (lack of) expectations and information given to me. No one gave me any feedback. Get called into a meeting to discuss my lack of performance and failure to meet goals. If I hadn't needed the money I would have walked out. Transferred teams a month later.

I’ve gave my two week notice a week ago, and my boss it’s just avoiding to announce it to the team, people in other areas, and of course to the teammates that will take my responsibilities. What’s wrong with him? He asked me not to tell people so they can “elaborate a plan to make my exit softer for the team” and that’s great but dude, I have one week left and people is still asking me for things that I’ll not handle in a week, I feel sad about the guy that will take that shot.

Those days where you start to think of leaving a good job and a great team because of one insufferable cunt.

Your "feature" just became my problem. Your "great idea" is now my migraine. What you did in 300 lines, another team was already doing in 5.

The next time you `brew install...` on your laptop, you should fucking think that the infra team has to install those dependencies, on every server, too.

In less time than it took you to create your code, I could have given you several functions to call. I could have saved all of us weeks of work. Fucking ask cross-team before you cowboy code your next big idea please.

Got a problem you need to be solved, somebody else probably solved it, just fucking ask.

I worked for a neutriceuticals company that I thought was going to be a crap job. Turned out to be the best employer I ever had. No micromanagement. Great team.

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.

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!

Every single time I present a tool for data visualization:

"Oh that's great! Have you considered integrating it with service XYZ? It would be great to see the data from XYZ alongside this."

The answer I would like to give:

"No, you retard! Nobody gives a fuck about your crappy service! Nobody uses it, not even your own team! This is the 10th service that I've been asked to integrate and I don't have time to dig into the details of yet-another-shit. If you have time to waste, please go ahead but don't bother me."

Worst: being forced back into the loud distracting office, to add on to the badness the covid restrictions were not taken very seriously

Best: getting a new full time remote job and an awesome company with some awesome team mates

Bonus is I now work from home fully but can still hang out with my great former coworkers

My team lead at my summer internship hailed from an MFC background.
I was able to dictate a whole block of jQuery code to her orally while I was in a hurry to go for lunch, and she typed it in. And it ran perfectly in the first time itself.
jQuery isn't a great deal, but it was a confidence booster for a guy who had only worked with JS for a week.

So I fix a bug and I create a PR, someone reviews it and leaves a couple of comments, I address those comments and push up my updated code thinking “great I should be ok to move onto this big story waiting for me”
Then some Expletive.random(); from a totally different team who has no context of my change comes in and starts leaving petty comments. He literally pointed out 3 different things that could be made private/package-private.
Bugger off and focus on your own team’s work instead of leaving comments about relatively trivial things on my PRs.
Apparently he is well known for this. I can tell we are gonna have some fun encounters...

If you feel it’s time to change I have a great job offer for you…
proceeds with offer with maximum wage that is half what you earn and by the way you need to know React, TypeScript, NextJS, Redux, NodeJS, ES6, Webpack, RESTful i GraphQL API
Nice to have is Python and Go

Girl you need to decide if it’s great offer or technology mishmash.
Hell no, glad you didn’t mentioned young and dynamic team cause I clearly see some dynamic technology stack there.

Company helps people find medical treatment clearly forgot about treatment on their stack.

Someone needs to tell them their tech leads are complete morons but since you’re not looking for head of technology it won’t be me lol.

First job was as a student, but paid, which was great! Started with some training which taught me more about programming in 7 weeks than I'd learned in 4 years at school/college. Started with some proprietary systems, then moved on to proper web dev/browser based apps using tech you're all far too young to remember. I was instantly at home. So became my career (with lots of full stack experience picked up along the way).

About 3 months in, my team lead said to me (the n00b student) "I'd ask and trust you to do things now that I wouldn't ask people who've worked here for years to do." Meant the world to me... (thanks DH!)

At the end of my time as a student I was invited straight back full time.

A client brought us a project once related to drones. Our team came up with a great solution for the problem and pitched it back to the client. After going back and forth and beating us up on the price, they ultimately got cold feet and stopped responding to us.

Flash forward several months and wouldn't you know it, NASA and Lockhead Martin have the same idea and file the patent. Could have been sitting pretty if the client just went through and filed our design first which would have barely cost anything.

In the “Qualities of Great Design” session at #WWDC2018. Really wish the Xcode team could be sitting in the front row so they couldn’t sleep thru the session...

oh i guess being the optimist I was thinking they would even be here. Silly me.

All the bugs that drive me effen crazy are clear and present in Xcode 10 beta. Stupid shit still rules at Xcode Central.

So i started an (8 month) internship in January. Team of 4 (2 senior/mid level devs + boss) plus 6 or so other people in our other office overseas. Everything was going really well IMHO. Boss's feedback for halfway through the internship was good too.

First 4/5 months were great: loved the team, got feedback and help when i needed it, wasn't stuck doing support too much, etc.

This all changed when both the devs moved to our other office. My boss works from home a lot and has frequent meetings, so i hardly see him. I have a 1 hour window first thing in the morning if i need help from the devs overseas. After that im on my own.

If i get stuck, even on something very small that a more senior dev could explain in 2 minutes, I'm stuck either unable to work or figuring it out (wasting hours of time) for the rest of the day.

On top of this, since I'm the only one around in our office, im stuck on support every week which takes hours of my time usually. Last week support ate up most of my week, which put me way behind schedule on my other work. (That was an unusually busy week of support.)

Feeling incredibly frustrated right now, just wanted to get this off my chest.

I went into interview last Friday and felt great. The recruiter said they needed people urgent, so I'll be hearing from him soon. On Monday he called me saying they liked me and would like me to join the team, so he will prepare a proposal for me.

It's been three days and I haven't received any information or contact with him about the proposal.

How much did it usually takes to create a contract proposal?

The worst of Agile and Sc(r)um: All those people knowing the right way(™) to do it. Endless discussion about useless tooling: the proper use of the custom workflow in Jira, on when and how to create sub tickets. The hour-less meta-discussions on what should be discussed where and when (what's subject of the backlog refinement, retro, etc), the roles: the PO's, what he should do, cannot, the PM's. Who is allowed to pull a ticket to the sprint or not. How many reviewers need to acknowledge a pull request. To and fro. Pointless, but fought with heart and blood, full of sound and fury, signifying nothing.

And everywhere I hear: "In my previous company, we did Scrum like.. and it worked perfectly!"

Some of you might remember my rants on Mr. Gitmaster, with whom I thought I'd made my peace. Guess what? He's now a team member and turning into Mr. Agile - a more severe reincarnation! As our company starts flogging that dead horse of Agility, he seems to feel strong tailwind. Our team lead would constantly cut his monologues, but he's now on holiday, so we have no escape from the never ending: "In my previous company..."

If it was so great, why didn't you stay?

We are not allowed to pull a ticket to the sprint unless every team member is notified? I don't fucking care. If our software fails on customer's machines and I can fix it, I will do if there is a ticket, if it's in the sprint or not. Screw Scrum, if it is getting in the way of it. You can waste your hours discussing horseshit, I want to sit at my desk, deep in the test-compile loop and ship some fucking code.

as much as i complain about work, I'm glad i have great colleagues in my team. they're a blast and they make this shitty job worthwhile. I've never been the type to make friends with coworkers, but they're really great people. i guess I'm really lucky

So I installed a new Linux distro, and since the DE is Gnome, I wanted to spice things up with a Conky file.

I download my conky theme, extract it, and try to run it.

And it's broken.

Apparently, the Conky development team decided it would be a great idea to switch over to an ENTIRELY FUCKING NEW SYNTAX, LEAVING EVERY CONKY THEME WRITTEN BEFORE AUTUMN THIS YEAR USELESS

Oh, no biggie, I think. After all, the development did very graciously publish a Lua file to convert old conky configs to the new syntax.

Except no.

The file used to convert conky configs uses the old loadstring function, for which support was dropped in Lua 5.4

So not only did Conky make every config written earlier than this Autumn obsolete, the FUCKING TOOL THEY DEVELOPED TO HELP WITH THAT IS ALSO FUCKING BROKEN

Fuck Conky. I wasted 2 hours screwing with this broken-ass piece of shit

Last day on my first job where I stayed for a year. I really enjoyed it, loved the team, we were always laughing and making jokes, even in the worst moments.

Had a leader who became a friend, I made some good friends in there.

But I was really unmotivated as a dev, we maintained a really old and complex software, with a poor infrastructure for the dev team.

The manager was a great guy, but couldn't handle much pressure, saw him about 3-4 times quarreling with someone when he should be talking with the team to solve the problem.

But as I said, he is a great guy.

Today the whole team will be making a happy hour as my farewell party. I love this guys.

After that, on monday, I'll be joining a new company, working with a whole new stack, studying a lot for this new challenge.

Wow! New devRant IOS upgrade released today has some really cool new features! They must have a team of 10 coders or 1 @dfox and 1 @trogus. Great work guys!

You know you have a great dev team when you signed them up on a codefight tourney and nobody even scored.
Seriously, did u guys even try? FML

Manager does nothing but give me more work. Can't code. doesn't even get git issues. Last in first out yet I'm first in last out. At end of meeting he says, "great job but one comment, you should say 'We' not 'I', cuz this is a team effort"

Are you fucking kidding me dude? Add it as another issue.... Oh wait

Demo

Backend Team : No one want to listen to technical details. A short 2 min demo what we have done.
Shareholders : Have you done anything?

Frontend Team : half an hour demo of validators and fields that sum values from other fields
Shareholders: Wow that is awesome, great job, nice to see, great value, lot of progress.

Found a reproduction to a bug that all the team tried to reproduce for 2 days. Damn this feels great!

We're using Slack for team communication.

After a lot of crappy slack apps I installed the snippetsbot today.

It's just great. Simple but really efficient. I love that damn little thing.

Product owner: when will you have that script written and submitted to DBAs?
Me: if nobody bugs me, hopefully COB today.
Product owner: great!
*user support*
*user support*
*user support*
*user support*
*user support*
Team lead: write this other script.
Me: I just finished user support, I have another script to write first. Does yours take priority?
Team lead: yes.
Me: ok....*sigh*
*writes 2nd script*
*submits 2nd script to DBAs*
Product Owner: you done?
Me: *face palm* ......NO!

I'm leaving my current job in a week. What is a great prank I can pull off on my team before/after leaving the company?

I'm more interested in a long con which plays out slowly after I leave (maybe on April fool's?) Please share if you got any cool ideas or experience.

Context: I designed and built a web app which is used to manage stuff (CRUD) related to my project internally.

I would really love to hear some funny and non-destructive suggestions.

!rant
Seeing some people posting stories about horrible internships so I thought let's post a good one.
At My current internship they treat an intern like an employee meaning having some great opportunities and rights. Having rights to ask anyone anything or question any decision or pointing that you are wrong.
Me: I don't want to work with this product.
Team lead: okay then there are some other options choose one of them.

And more cool stuffs

Hey, I have a cool idea about a new way to solve a problem our users are having!
Type type type, now I have a working prototype! Show it to the team, everyone loves it. Polish it a little, it works really great!
Now let's test it on an iPad like the ones our users have... Nope, nothing works, undefined is not a function.

F*CK YOU SAFARI, you're why we can't have nice things. 😤

Just taken on a new client through my own business. Great news! They pay well, everything seems to run smoothly and they're a great team.

They gave me access to their Gitlab repos and all looked well...until...no branches! They have zero branches to determine what is the current live distributed project, dev project or any of the various other reasons. I don't often use git but this really bugs me!

Startup needs app done for MVP at a money fair. Startup finds good team. Startup plans every little thing written and has most of the app screens ready. Team signs NDA to see screens and docs. Startup keeps working on docs. Startup postpones dev start to after the fair! Thank you for wasting team's time! FUCK YOU STARTUP! BTW, that's a great app you have there... on 'paper', though it is just useless piece of crap. Great job you headless fucks!

During the course of my career I've stumbled on like 6-7 people I've worked with and it was really great. Every now and then we meet up and chat how it'd be great to form a team again and work on something (we're all in different companies atm).

Lately we've been mentioning that even more and are considering whether to start working on a product/find clients and form an agency/join some other company.

We have experience with both outsource and products. Our profiles range from development, design, marketing, UX, HR, PM.

Any road we take has pros and cons. We're least fit to start on a product because we'd need more profiles, have to figure out finance and would probably have to work alongside our current jobs.

I've been thinking of writing a joint letter when I hear a company is opening up an office in our city. When that happens, usually whole teams are formed and most of the profiles I mentioned are needed.

Do you think that's even possible? Is there another way we're overseeing? Have you heard of or attempted something similar?

Any advice is truly appreciated.

First job while in college... Was working for web dev team lamp set up before lamp was lamp (year was 2000).

Had deadline one week after summer vacation. Worked non stop a couple of days to get shit done and didn't make it. Got in a conflict with my manager in front of the team and I blew my steam off. Quit on the spot.

Lessons learned:

1. Don't be a fucking idiot when estimating work.
2. Be cool with other teammates, nobody cares about drama and nobody has to feel sorry for you.
3. Uhm, plan? Had entire fucking vacation to get work done. I was a fucking moron.
4. Burning out is stupid and unproductive.
5. Your manager can be as poor in management as you are. Your job is to try to make them better at it, as they have less visibility in the details.

Next job in grad school. Worked for a security company. Direct manager had the bright idea to make execs sign the change requests. WTF. Code was in Perl/php, a mess. Team rewrote back end DB access , taking over six months, or more, failing twice the deadline. After a final 48 hour burn out, we ship and get laid off the week after.

Lessons learned:

1. Don't work for dicks.
2. Don't be a dick yourself.
3. Don't work for dicks.

Third job was in silicon valley. It was a great company, and I stayed there for five years.

Last week-end I went to a hackathon organized by Microsoft Innovation Center, that was great ! I didn't win anything unfortunately but the guy from there said to my team "we want your project" before we leave. So we didn't won anything but you want our project ? Wtf guy ?

The ones I have now! I have a team of great people I'm working with. We get good work done and have alot of laughs. And since we work for a huge fortune 500 company, we have plenty of people in the enterprise to complain to each other about!

If these aren't great mentors I don't know what is. They first took me into their company with no prior experience as an intern for six months working remotely a paying internship at that and they paid for my internet. Six months ends and they offer me a junior web developer position in the company, buy me a mac and and a second screen and still paying for my internet with an increased salary. And the team works like clock work all the time with everyone giving a hand to whoever is struggling with whatever not to mention they're very patient... I love this company FUCK!!!

!Rant

Tldr: great spike to solve deployment problem may be a wasted effort.

Deployments of an ancient electron application need to be done in CodeDeploy to deploy the latest build. Customer hour restrictions cause this to be done only after midnight, and manually checked.

The whole team knows this is the wrong method of deployment and that there are many other operational problems with the project.

A few other senior team members get together and decide to spike out a way to use electron auto-deployment to accomplish this without using code-deploy at all.

After a shallow dive into this subject, we all get pulled aside to handle a change in another part of the software ecosystem. It happens. We leave the spike behind.

A junior-intermediate developer on the team pics the project up and gets a good spike going in a day and a half! We are all high fives and beers. This is Friday.

By Monday there is a pull request in for code review and it looks solid. Seems like it will make deployments a lot better.

Preparing the last deployment (hopefully) with CodeDeploy ever...

Marketing team members inform us that they are running an add system on the customer devices and to do it they are using Linux.

The current application being deployed is using Windows 10 (yeah, another problem).

They say they have made plans to move our application over to Linux. This means we may not be able to launch the junior devs great spike and the old deployment method may stay for the time being.

Meetings soon to find out how all of this will hash out.

End of rant. I hope I'm doing this right