Big event. Massive traffic in production, so we were monitoring all night.

I was in a room with 2 devs of my team, a marketting girl, my boss and a designer... chilling.

Suddenly the production is down.

Boss: production is down, anyone can check?
Me: already on it
Dev1: it looks ok for me
Dev2: me too
Me: wait what? Impossible everything is down
Dev1: oh I refreshed the page it's not working
Me: don't stay on the page refreshing it like you are fucking monkeys. Give me useful intel or be quiet.
Market girl: is it working?
...
Guys is it working?
...
Hello?
Me: Not yet we are looking. Don't distract me.
Boss: client called us. They want it online now.
Dev1&2: he's looking
... 1 min later...
Boss: is it working?
Boss: is it working?
Boss: is it working?
Me: SHUT THE FUCK FOR FUCKING ONE SECOND. ALL OF YOU, OUT NOW. YOU ARE FUCKING MONKEYS WHO CAN'T DO SHIT. IF YOU CAN'T HELP JUST SHUT YOUR DAMN SHITHOLE. DEVS, LOOK WITH ME. MARKET GIRL PREPARE A FUCKING POST-MORTEM MAIL. BOSS GET THE CLIENT ON THE PHONE AND STALE. DO. YOUR. FUCKING. JOBS.

That's how I ended up screaming at everyone... the rest of the night went in complete silence and I fixed the issue 2min after the got quiet or busy.

isRant = true

Working in a team with no Business Analyst assigned, moment when you realize that you spend at-least 3 hours every week sending old emails as a proof to business users that what we have developed is exactly what they fuckin' asked for in the first place

I finally got a new job!! 😃
Actually i’v been working here for 3 months, but i was in trial mode so i didn’t want to post it yet but it looks like im staying 😃
They are the most talented team i ever met, they host all our local gamejams, have their own internal game engine and a gamer bar where the company’s devs have 30% off from the prices.
Their projects are exciting (even if i’m not currently on a game project) and my team lead is awesome!
I’v been wanting to work here for about a year 😃

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

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

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

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

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

*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

This is why I love working where I work. I worked extra hours until 9pm to get an ITest environment ready for one of my customer teams. I came in this morning to a little prezzie and a thank you card signed by the entire customer team. This is what awesome culture looks like.

What happens when you change the service call center to 100% AI

AI: Hello, this is the After Service center. How may I help you?

Angry customer: Hey! Do you count this as a product? Do you sell this to use it? F*** shit?! Bring the manager now!

AI: Thank you for your response. We will connect you to the Development team.

Angry customer: Uhhhhhh

AI: Hello, this is the development team. Please state your problems.

A bit relaxed customer: Umm, so this product you guys are selling stops working sometimes, so...

AI: We are sorry, but for the product misfunctions, please contact the After Service. We will connect you to After Service.

F***ed out customer: Wait, I just came from the After Service!

AI: Hello, this is the After Service center. How may I help you?

Angry customer who is ready to throw the phone: I said that the product is not working, and I asked to bring the freaking manager in the line!

AI: Thank you for your response. We will connect you to the Development team.

Customer throwing the phone and shouting: F*********************************************************************************************!

When you are on location (football stadium in this case) and you realize that some part of the algorithm isn't working quite right.

We are building a webapp for a little bet-game for our local football team and today was the first live test. I fixed the way the points are calculated in the half-time break.

You can edit code on mobile on gitlab. Doesn't mean you should, but you could. And I did.

🤣🤣🤣
Somehow, my boss got his son, 19, working in a team of developers last week.
Son: i got ton of money and i dont need to do this. i inherit lot of properties from my dad.(trying to sound funny, superior, and boasting of his inheritance knowledge he might have learned in school during java class probably.)

A guy in the team: No you dont. You are like us.😎😎😎
Son: minds his own business now.

Damn that line made my day.
🤗👏👏👏👏

++ for this dude for insulting morons like this at work.
I may have to remove it on boss request if he see it. But for now hit as many ++ to show that idiot no body likes people like him.

Today, I was telling a team member who joined recently to refer a GitHub repo, fork it and start working.

That person asks me, "Why GitHub, why should I access it etc". I blanked out after hearing the first question, so whatever said after that wasn't registered in my mind.

I asked that person "how did you do it in your previous org ?"

The response was, "we zip the code at end of everyday and store it as draft in our mailbox"

I stormed out of the workplace, even though it was just around mid of the day...

I was having dinner yesterday and I suddenly get a message from someone from another team.

Them: Hi
Me: Hi

(No response for 20 mins)

Them: I'm having some problem with your service. Its not working when I do <task>
Me: Okay, let me look into that.
Them: Also, <task2> is not working
Them: And <task3> has problems
Them: Could you also look into <task4>?
Me: (visibly sweating) Let's discuss this in detail in the morning.

[Next day, morning]
*convinced that the service has a major bug*
Me: Yeah, show me what is causing the problem.

They show me what they tried. Turns out they made an invalid call and got an error, AS THEY SHOULD, and reported that as a bug. And all the other tasks were because the first call didn't work.

:|

Professor in college: We have our fest coming up. We need some volunteers for technical team to build website and android app.

*She says that and looks towards guys. Some guys raise hands saying they were interested.*

She didn't look towards girls even though some girls were raising their hands too.

Then she looked at girls finally....and she said "Oh you girls are interested too? We have cultural and decoration team. You can join that. "

I was triggered to next level.

I stood up and asked "Can't girls be part of technical team?"

She said "oh...yeah sure...." With not much hope that I would get into technical team.

But I ended up passing the screening round and got into technical team. She realised at that time that I knew my shit.....

There was even a time when I was in HODs office and she pointed at me and went "She is my student." trying to take credit for me being so Awesome ;)

LOL!

She was my guide for final year project too. We ended up writing a research paper and won best project award as well.

This was a year back. I have graduated and now I am working....
Just remembered....

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

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

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

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

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.

Hai devs!
Team devRant here.

Some sad news, my teammate can't participate for reasons I don't need to disclose.
I'm not stopping though, I'm going in alone! (Or well, physically).

I'll post the link to the updates (and more) site later on but the important part:

It starts at 12pm EU/Amsterdam time and stops tomorrow at that same time!

Working on a livestream =)

Cheers!

Everyone in my company prefers solving git issues rather than `rm -rf` & `git clone`

Feels like I'm working with a team of geniuses. 😂

Every time I do a dirty fix and someone in my MR comments "have you investigated the root cause" I wanna kill myself.

No bro, I havent investigated the root cause because this ticket is 3 months old and was passed around like a hot potato from team to team until it got assigned to me.

If you want I can add a comment to refactor this in the future. As far as Im concerned any refactors are out of scope, also I atleast came up with some kind of solution that noone else was able to in 3 months. So im not gonna waste my time on refactoring this piece of shit code under immense pressure from management who thinks it was me who dragged this ticket for 3 months.

Its working, it doesnt cause any side effects, we all gonna die soon and nothing really matters, so fuck off.

I had an intern in for VBA programming on day one they realized that they were in need of an android dev, so the boss came to me and asked if I had any experience with android. I replied with yes a little, I had begun multiple projects but never finished only one of them. After 4 weeks of developing I presented my progress a pretty ugly but working app, after the meeting the boss told me that a other team of devs were building the same app but didn't made any progress in 1.5 years.
Ps: sry 4 my English.

Today is finally the day of my hackathon, have been working with my team for about a month on a personal assistant already. I think we may stand a chance to get in the finals this year, unlike last year, when we started working only on the day of the hackathon.

This just in everyone...

Android Dev: *sent and email to network admin* can you please unblock github for a few mins.

Network admin: *Replied* Can you take a screenshot whats the error your getting.

Android Dev: *Replied with screenshot* "Failed to load resource: the server responded with a status of 503 (Service Unavailable)"

Network admin: that is a known issue. *Replied with Wordpress Links.

Android Dev: why is github working outside our network then?

Network admin: there must be a problem with your code that needs to be tweaked.

Team: *FACE PALM*

Hey Root. Here’s a new ticket for you. It involves lots of things you’ve never seen before, and the only person you can ask is out this week.

Hey Root. Why haven’t you been making good progress every day? Why didn’t you reach out to the guy on FTO? Clearly you can’t communicate. Give me detailed status updates twice a day at specific times, covering <exhaustive list of topics> so I know you’re working. What do you mean “no”!?

Hey Root. Stop working on that ticket, and work on this other ticket. It’s the same thing, but different. High-priority!

Hey Root. You asking questions about that ticket pissed off a legendary golden boy principal dev, and he said it’s a bad idea and that we should have assigned it to a different team, too — you know, the team who usually works on these areas. But we might still have you do it. Please work on the previous ticket that’s in the exact same area until we decide.

Hey Root. Why haven’t you gotten anything done?

One of the dev in my team literally asked us (other student devs, professor, and a guy from the company we were working with) this question during a weekly scrum meeting:

"Who is this Jason you guys keep talking about? He never showed up to any of our meetings!".

A bit of context: we were 6 weeks (halfway) into our FINAL YEAR PROJECT for a bachelor in software engineering...

I thought at first he was joking...

!rant

So I have been recently hired at my current job for leading a product team. We're a small team working in a big company which have other teams working on other projects. I like my work and I have been appreciated for my work which I did since my stay here.
So I and my manager were discussing about how more can we automate our workflow to reduce the time to get the final builds. It was late in night. Suddenly someone asked, 'did I hear automation?'. We turned to see our CTO listening to our conversation. He told us that he's having trouble with automation in his project. I was new, so I didn't know what did he work on, so I asked.
Me: So what did you guys work on?
CTO: well, we work on automating stuff for clients and save them money. We earn 100x revenue than your product (In a more humble tone). I am currently looking for someone who can lead a team of developers for handling the automation scripting part. *Provides description of the candidate* Do you guys know someone like that?
Manager: (pointing towards me) It looks like his description.
CTO: I want him in my team then.
Manager: That can't happen, he's required in very important stuff and you're not allowed to poach.
CTO: I think I have the right to poach 😉
Me: OK, so how much raise am I going to get to switch teams (to the manager) and how much am I going to get to stay? Whoever gives me more I am theirs.
CTO: I like this guy

It's day three, I am still awaiting for one of them to tell me who won 🙁

PS: They both are friends with each other.

Client reads about MomgoDB ransomware attacks online.

Him: I heard that the MongoDB is not secure, we should use something else in our system.
Me: Those databases got attacked because security features were turned off. If you want you can have an external security team to test the system when it's done.
Him: I don't wana take any risk, so I we should use something else.

We have been working on this system for almost a year and the final stage was supposed to be delivered in a month.

He wants me to replace it with MySQL

Rant from my old company:

CEO decided he could cut costs by outsourcing to cheap devs in other countries.

Does this, the new hires are super incompetent. We're now paying for a whole team that is adding work cause they keep fucking up.

Leadership is super happy with the "savings" (which is basically just the team here working harder to fix everything).

All the smart people start leaving, leading to a downward spiral.

Last I heard, one of my junior co-workers had been promoted to senior (he hardly had any coding experience).

Fuck them all

Its so weird working in this company. No onboarding, no micromanaging, noone to track your progress or performance. U can basically do what u want and ask what u want and requests will be fulfilled.

Initially was assigned to a random team and started fixing stuff. I hated the scope so after 2 months in requested to switch teams, request approved.

3 months in realized I lowballed myself during the interview and actually am doing better than half of the team, so I asked for a 43% bump, request approved.

4 months in I realized that I did atleast 100hrs overtime in a month during crunchtime, burned out. Asked for a paid week off to recover, request approved.

5 months in realized that we have many MR's piling up in the team and I could help with approving some of them, but they grant MR approval rights only when u work here for a year or are a decent dev from the get go. Requested for MR approval rights, request approved.

Again it feels so weird working on a big product with 6-7 scrum teams. Its like there is no bullshit, just ask what you need you will get what you asked so you can continue working.

On the other hand its kinda weird to keep asking everything, in other companies a good teamlead/manager shows more initiative takes care of stuff like this without even asking.

Junior dude in my team: Started working with the expectation to get dirty and go deep into technology (he was in fact a mathematician). The first two months he was happy like a little puppy playing around. Then suddenly he started talking about getting more responsibilities and beeing more a manager than a dev (because development is too stressful). Then on his last day of the probation period he quit out of nowhere because he got a job offer from a place he really wanted to go. He bought one beer per person in my team, but haven't invited my boss to that event. We suddenly realize why: He talked real shit about him!

What a dick!

Action takes place during demo to the stakeholders.
Manager : During the demo we will show a working prototype of new functionality. In this sprint we focused on that feature not on UX. Please do not pay attention to UI and focus on business values
*Dev starts sharing screen*
*1 sec after*
Executive : This is unacceptable. It looks gross, why you don't use default controls.
Manager : We did, this is how they look like, but please do not pay attention to UI, it is not finished
*Dev continue presenting*
*1 sec after*
Executive : I see missing comma in that sentence. It is unacceptable to show features in that state, lets move on to another team.

It was really large feature working as a charm, but they focused entirely on unpolished UI :/

My manager is so cool at work that he doesn't care if I sleep during office hours or even skip working for a couple of days as long as I meet the deadlines. All he cares about is getting the work done and keeping his team happy.
I abso-frigging-lutely respect him very much and like him as a person.
Unlike my friends' managers in other departments, he wouldn't assign me more work if I finished a project before the deadline.
I wish all the managers in all the companies realise work-life balance is important and act like him.

PM was on vacation the whole sprint.
this sprint was so much more... convenient. i really liked what i was working on.
Also, team lost some of its bureaucratic discipline along the way.

colleague replacing him, in today's daily: since the sprint is basically almost over, i can really recommend to the whole team to wrap up your work of this sprint, so you have something *done* that you can deliver or show in next week's sprint review.
team: ...

oooohhh boy, let me get a shitload of popcorn for the sprint review when PM is back 🍿🍿🍿🍿🍿🍿🍿🍿

One thing I learnt after over two years of working as a programmer is that sometimes making your code DRY is less important than making your code readable, ESPECIALLY if you're working on a shared codebase. All those abstractions and metaprogramming may look good in your eyes, but might cause your teammates their coding time because they need to parse your mini-framework. So code wisely and choose the best approach that works FOR YOUR TEAM.

Recently, our team hired an arrogant trainee-junior to the team, who turned out to be mean towards the other developers and in a habit of publicly mocking their opinions and going as far as cursing at them. He steals credit and insults others. He openly admits he's an offensive person and not a team player. When someone from the team speaks, he might break into laughter and say demeaning sentences like "that's so irrelevant oh my god did you really say that? hahaha". Our team consists of polite and introverted engineers who cannot stand up to bullies. Normally this kind of behavior won't be suitable even if you work in a burger shop especially not from a trainee. Let alone trainee, the rude behavior of Linus Torvalds was not tolerated, despite him being in the top position and a recognized star talent in the IT field.

I personally no longer feel comfortable speaking up during teams meetings or in the slack team chat. I'm afraid my opinions will be ridiculed or ashamed - likely will be called "irrelevant". I respond only if I'm directly addressed. We have important features coming up, requested by the customer, but I feel discouraged to publicly ask questions - I sort of feel having to regress into contributing less for the product. I also witness that other younger developers speak less now in meetings and team chat. Feels like everyone is hiding under the bed. Our product team used to have friendly working atmosphere but now the atmosphere is a bit like we're not a team anymore but a knot.

Lesson I learnt from here is: There is a reason why some companies have personality tests and HR interviews. Our proud short boarding process was consisting of a single technical interview. Perhaps at least a team interview should be held before hiring a person to the team, or the new hire should at least be posed a question: are you a team player? Technical skills can be taught more easily than social skills. If some youngster is unable to communicate in a civilized manner for even five minutes, it should raise some red flags. Otherwise you will end up with people who got refused from other companies which knew better.

Rails 5 + Ruby + React learned in less than a month. Im so ffff tired, but have to keep moving to reach deadline for an app with already 2K hours in with team.

Still better than working on Wordpress.

So I am at the client's location for onsite consultation of their projects.
The HoD asked me to create an application to accept feedbacks from multiple points urgently. Although I was there just for consulting, I thought why not, I am anyway getting bored here.
So after explaining the functionality, she asked me, when can she accept a working app. I told her that it would depend upon a lot of factors, so give me till evening to figure it out.
When she insisted I told her, that it can take at least a month with all the APIs, logins, UI, QA etc. She was surprised and told me that she expected it in 4 days since the requirements can be fit into a single page of her notebook. (That's how she measures project duration).

I told her it's impossible, given that I am the only one working on it. So she told me that her team can do it in two days. I probably have more experience than her entire team combined, but still I thought they might know some simple magic or faster way, that I might not, so I asked her to discuss with the team and then decide.

After explaining the requirements, when she mentioned that it should be done in 2 days, everyone was kinda frozen. One of them said that it's going to take at least 4 months.

I couldn't hide my smirk 😉

Post Anger Rant (Beware, Long rant ahead)

So there is this project we have been working for months, most of the devs involved are jr students so I was leading them in the architecture and what to do and they were doing it, the progress was slow but safe and fun.

On the team there was this guy, someone I trusted and in who I had special interest for his skills, so I let him own the github repo.

So the day of the first demo I pull the backend changes ( I had been working on front end ) and I realize that the code was different, so I started using my super awesome forensic skills to find what happened,and when I say different I mean a totally different architecture different database connections, different service pirts, basically other project, so during my criminal investigation I found out this guy I trusted had never really worked with us, from the beginning he went solo working on his own project and changing everything because of some tutorial he found on the internet, so I decided to reset to the previous version just to find out that he had already deployed the code and that a lot of fixes that we should have were only on his version.

So I went and confront him telling him that he did wrong and he had to learn team work and that I was trying to teach them good practices and he waits and asks me "so, my code was wrong?" Seriously what da hell dude? I'm talking about team work and all you can think about is your code.

Finally he admitted his mistake and repented (I think), but seriously how arrogant must you be to ignore a whole team, specially when on your first real project.

Nowhere near my worst co-worker, but still funny.

The Dev team were all in a separate glass walled room with the business & support staff out in a bigger room outside. As is our wont, we wore headphones while working a lot.

One of the non technical folks asked me why and I said it helps me focus by keeping out distracting noises.

"Oh, I thought you were listening to code or something"

😮

It was kind of an eye-opener as to how little clue a person sitting just 4 meters away had of what I did or how I did it. And actually it helped explain some confusing interactions...

Got an email earlier this week. It went something like this:

"It looks like your team still hasn't delivered the logging and monitoring solution that we asked for. Can you get it done in time for our production deployment next Friday?"

Um, wait, excuse me, WHAT?

1. You never actually asked for the thing you claim we didn't deliver. In fact, when we brought up the fact that you should probably have some monitoring set up for your servers, you said it would be handled entirely by your own team.
2. I HAVE BEEN WORKING ON THIS PROJECT FOR SIX MONTHS WHY DIDN'T YOU TELL ME YOUR DEADLINE UNTIL NOW
3. I won't even have time to start working on this until the Monday after your prod deployment date. Sorrynotsorry.

I really shouldn't be surprised though. This project has been a clusterfuck from the very beginning so this is just par for the course.

So after a llllllloooooonnnnnnngggggg struggle with the team i've been working with, today is the day that my group move to a different org and start working with a different team.

This is a huge step in the right direction for us and we are so happy. This new team is much bigger, but has been around for a lot longer and has proper processes in place and works a lot smoother. Never going to be perfect, but still going to be much more workable and we are so ...... thats an interesting linter file, hhhmmm they have disabled all the checks for the stuff that will cause crashes, like force unwrapping ... but they've enabled the rule to make sure our imports are sorted alphabetically

... nope, cant do it, no sign of intelligent life in this company at all. linkedin here I come.

When 3/4 of my team gave up and left halfway through. I still don't understand how we ended up with a working prototype in the end.

So sometime back I was working as an android developer for a startup managed by a guy who wasn't much of a techie. The team wanted a share image to facebook option in the app, which required FB SDK integration into the app, which in turn will increase the app size and request more permissions. On discussing this with them and asking for the app secrets, they said that I'm being ridiculous, and denied me from giving the app secrets, citing the reason 'They're called secrets for a reason'.

WTF is with the entire Angular2 eco system and "half instructions". Started learning it and every inch is a struggle, out dated docs and code samples and then this style of shit:

Google: "Angular2 and bootstrap"
Result: "Install ng-bootstrap to get native bootstrap components written in Angular by the Angular UI team"
Me: Install != work

Google: "ng-bootstrap not working"
Result: "You also need to install bootstrap css, heres how"
Me: Install, plus try component
Error: "Bootstrap requires jQuery"

Google: "Installing jQuery in Angular 2"
Result: <Instructions>
Me: Install, still not working

Google "Angular2 ng-bootstrap bootstrap jQuery"
Result: "Don't forget to also include Tether"

WHY DID THE FUCKING "ANGULAR-UI" TEAM NOT MENTION ANY OF THIS

Man, most memorable has to be the lead devops engineer from the first startup I worked at. My immediate team/friends called him Mr. DW - DW being short for Done and Working.

You see, Mr. DW was a brilliant devops engineer. He came up with excellent solutions to a lot of release, deployment, and data storage problems faced at the company (small genetics firm that ships servers with our analysis software on them). I am still very impressed by some of the solutions he came up with, and wish I had more time to study and learn about them before I left that company.

BUT - despite his brilliance, Mr. DW ALWAYS shipped broken stuff. For some reason this guy thinks that only testing a single happiest of happy path scenarios for whatever he is developing constitutes "everything will work as expected!" As soon as he said it was "done", but golly for him was it "done". By fucking God was that never the truth.

So, let me provide a basic example of how things would go:
my team: "Hey DW, we have a problem with X, can you fix this?"
DW: "Oh, sure. I bet it's a problem with <insert long explanations we don't care about we just want it fixed>"
my team: "....uhh, cool! Looking forward to the fix!"
... however long later...
DW: "OK, it's done. Here you go!"
my team: "Thanks! We'll get the fix into the processing pipelines"
... another short time later...
my team: "DW, this thing is broken. Look at all these failures"
DW: "How can that be? It was done! I tested it and it worked!"
my team: "Well, the failures say otherwise. How did you test?"
DW: "I just did <insert super basic thing>"
my team: "...... you know that's, like, not how things actually work for this part of the pipeline. right?"
DW: "..... But I thought it was XYZ?"
my team: "uhhhh, no, not even close. Can you please fix and let us know when it's done and working?"
DW: "... I'll fix it..."

And rinse and repeat the "it's done.. oh wait, it's broken" a good half dozen times on average. But, anyways, the birth of Mr. Done and Working - very often stuff was done, but rarely did it ever work!

I'm still friends with my team mates, and whenever we're talking and someone says something is done, we just have to ask if it's done AND working. We always get a laugh, sadly at the excuse of Mr. DW, but he dug his own hole in this regard.

Little cherry on top: So, the above happened with one of my friends. Mr. DW created installation media for one of our servers that was deployed in China. He tested it and "it was done!" Well, my friend flies out to China for on-site installation. He plugs the install medium in and goes for the install and it crashes and burns in a fire. Thankfully my friend knew the system well enough to be able to get everything installed and configured correctly minus the broken install media, but definitely the most insane example of "it's done!" but sure as he'll "it doesn't work!" we had from Mr. DW.

Got the ideal job right now. Over market salary. 100% remote. Mornings to myself until the rest of the team in another time zone comes online. Working within my competency with just enough challenge to make it interesting. Free products for being an employee. Only wish it came with paid health insurance but I do get a partial reimbursement.

Backstory: Offering manager brings a project through a few months of requirements gathering / feasibility study etc. Project spends 8 months with a R&D team to flesh out. Our team gets 6 months to turn it into a ship able product. 4 months in, offering manager calls a meeting.

OM: ok so you are all working on project X, well I need your input on something

Team: Ok, go ahead

OM: what do you think the app needs to do?

Team: ... I'm sorry?

OM: well we've been looking at it, and we don't think it does very much compared to existing apps. We need a killer feature but we don't know what. Any ideas?

Team: well we were looking at project Y originally, which was a lot more advanced. But you pulled the plug in favour of this.

OM: yeah, believe me customers will want project X a lot more. It just needs to do something interesting ... you know what I mean?

Team: not really, if it doesn't have anything, why did we go for it?

OM: ok I don't think I'm being clear. Point is, if anyone has any ideas let me know, we need to ship it in 2 months and it needs to be killer

I handed in my notice that week and was asked why ... let's just say I told them.

Who in their right mind though it would be a good idea to move the web development team to a new office without checking that the internet is connected.

What a waste of three working days.

And of course the project needs to be delivered by Sunday...

**Me, while working on sql based project**

Manager: Does anyone knows java! Want a sample login screen written in java.

**I'm the only one in my team to know java, thus raised my hand**

Me: It's done. Mailed you the .java file.

Manager: I can see my password

Me: I fuckn hate myself. ***Forgot to set password field as password type***

Manager: you are no different than others.

Me: Yeah..😶 **f@#& you**

I am on a team of 2 currently at work.

I am assigned to build some custom code for a customer going live with our product soon.

Because my team mate is already working on another customers project I explained the work may not be done in time because we were not given sufficient notice for our team of two to plan for the project.

Sales team contact me later that day asking me why I told our customer we don't have enough resources.

He wanted me to find a better phrase to tell them like "We have half our team dedicated to your project."

Another reason to hate our sales team 🤪

New country, new company, new team, new projects.
I'm supposed to be the TL of a team working on a React project.

A guy in his late 40s celebrates himself as "the senior", he basically just finished watching a youtube thing, React 101 crash course or similar. The other two juniors who did only Wordpress so far venerate him like a god.

The code, of course, is one on the finest pieces of crap I ever had the pleasure to deal with in my life: naturally a bunch of JQuery plugins for everything, no tests, no state management, side effects everywhere, shared state and globals like hell, everything written in ES3/ES5 style, no types, no docs, build and deploy totally manual, deep props drilling at every level... and not to mention the console.log() shipped in prod.

First day, already headache.
Full rewrite start tomorrow.
Hiring real devs as well.

Me, being a lowly junior dev, had the honor of being in a same group chat with a big corporation devOps team.
Finally ready to play with the big boys!!

*opens chat*
DevOps 1: "so we need to remove the CSS cache from our clients computers."
DevOps 2: "ok, well... just delete the server cache"

*watching in awe as they all try to figure out why it's not working*

This continued on for a while...
Until my boss had enough laughs and giggles and put an end to this stupidity :D

This is how beautiful corporate is -

I talked to my cousin recently who works in an MNC. He told me about a team member who was assigned a Google Login integration task on the website. They already had a username/password combo working.

That team member took 2 months for it. Every week on the team wide meeting he took an off day and kept saying he was 'stuck' on the task and he's figuring it out.

2 months later, he completed the task and got compliments from the manager that he 'worked day and night' and overcame his struggles. Then he got a week off for his 'efforts'.

Just kill me at this point.

Bless the service APIs that don't charge you for failed requests, that fucking on-site team almost cost my client 7k$, just because of a typo and an endless loop, that they pushed to production, while bypassing the rate and resource limit I set in place, because it "wasn't working" - it was working, you fucking cunts, it was preventing your system running wild for a reason.

Took a bit of time, but yesterday I sent in my resignation letter, long and some wat detailed list of grievances against the guy running the project.

Gonna suck to leave the team, but working for that man was tantamount to torture.

He actually gave me a lecture on Monday for not forcing my team to work unesesarry over time, because he can do nothing but make changes. I was also trouble for not doing his job and not treating my team like shit, as he does. According to him, forced overtime, disrespect are just the way leadership is.

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.

For a large team project, I was working on the website. I implemented a log-in page that took me a bit of time since it was my first time.
He grade that process poorly saying he has seen log-in pages all the time and it was nothing new or exciting...
YOU ARE A PROFESSOR FOR AN INTRO CLASS! YOUR JOB IS TO LOOK AT THE EXACT SAME THING EVERY SEMESTER, SHITHEAD.

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

There is a company providing a very speciffic service. And it has a core application for that svc, supported by a core app team.
That company also has other services, which are derivations of the core one. So every svc depends on core.

Now that we're clear on that... I was working in a team of one of the subservices. We very strongly depended on core. In fact, our svc was useless if integration w/ core broke down.

The core team had an annoying habbit. They refused to version their webservices and they LOVED to push api updates w/o any warnings. Our prod, test, other envs used to fail bcz of core api changes quite often. Mgmt, IT head was aware of the problem and customers' complaints as well.

So as a result, once core api changes we're all in a panic mode: all prior priorities are lowered and revival of prod is to be our main focus. Core api is not docummented, the changes are not clear, so we have to reverse engineer the shit out of it. We manage to patch our prod up w/ hotfixes, but now we have tech debt. While working on the debt, core api changed again, in test env. Mgmt pushes debt back and reallocates us to hotfix test. Hotfix is 80% done when another core api breaks. Now mgmt asks us to drop wtv we're working on and fix that new break. By the time we're to deploy the hotfix, another api breaks in another env. The mgmt..... You get the picture :)

2 years go by, nothing has changed so far.

Why do people fucking do this? You're working in a team, ffs. Even if right now you're the only one working on that branch or whatever, that doesn't make it okay to have the most useless commit messages of all time.

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.

There comes that dreaded time in the life of a developer working in a conservative, borderline medieval corporate, where darkness sweeps over the land and the evil lords rummage through every peasant's hovel searching for the forbidden - AKA software audit.
So I made a list of all the unauthorized open source code we desperately rely on, and we decided as a team to go down in flames and gloriously fail the audit, a legend of sacrifice that shall be passed on in hushed voices.

I'm a backend (Java, Kotlin) developer and I mainly design & develop services and Android apps which consume these services.

My team in my current organization (I've been working here since past 2 years) just got merged with another team.

And now the new boss wants me to fix some fuck ups in their project which is written in C#, with some WCF and other stuff.

As this stuff is completely new for me, I asked for some time to get familiar with the environment. But the answer was a big NO.

As a result, "I've started looking out for a new job"
😡😠

Fuckin management screws up everything!

5 of us working for a larger team were tasked with doing some R&D, we blew everyone away and were given funding to start a new team and hire people to make the project come to life.

One of the high level sales / product managers we were reporting to, secretly had another team work on a similar idea because he needed it quicker (i.e. no time for research, just build it).

After forming new team, we were asked to work on his project instead because it was further along. 4 months later, big knob comes to a meeting and basically says "You know what, this doesn't look like we have enough features, we need more, but I don't know what".

Project blew up 2 months later, head of the unit kicked up a shit storm saying how badly everything was planned and canned everything. Now one of our clients is building nearly the same thing we were originally working on, the team no longer exists and i'm back on the R&D team.

Don't get me wrong, I LOVE the R&D team, actually didn't want to leave in the first place but was told I had to. But the sheer anger and frustration to see that walking cluster fuck strutting around like his shit doesn't stink, derailing entire teams, meanwhile we can't hire new staff due to lack of funding.

Heres an idea, fire the fucktards bleeding us dry ... then we'll have lots of funding.

I came first in a 48 hour 4x person gamejam with a game idea in 6 hours with 3x people.

Some info: I had an idea as soon as the topic went live, told the team this is the idea (button masher), we are going to do it in unity (at the time I was working at a studio that used UE4.x), and I'll also make a custom controller using an old keyboard to make it more fun. Ended up coming first place and won a nice bottle of champagne each, and at no point did we over stretch. Nice clean project with a good night's sleep in-between. The team was me (dev), an artist and a technical designer.

That was my first start to finish use of unity and C#, and now I exclusively use unity and make games for Xbox One and Steam.

What a shitty day.

3h sleep
Lead very pissed bcuz backend don't know specs
Boring meeting where everything is repeated like 6 times
In a few hours boss wants to talk with the whole team

My co-workers jokingly say they want to fire me.
I should be the "hero that will make things better"

Please just kill me instead...

Edit: started working there 3 weeks ago

Working on Python+Flask delpoyed on bluemix. The app failed to start. After 4 hours of debugging by all the 4 members of thr team, we together found that there was a tab in an otherwise space intended file, which was tripping bluemix.

This a during a hackathon
Resolved it 20 mins before submission
We won the hackathon!

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.

Me, two weeks ago, adding yet another function onto an increasingly complex webservice: "hey uh this is getting pretty confusing, why don't we structure the request this other way so at least it makes more sense."

Manager: "just leave it as is, let the other team worry about how confusing it is. It's their problem now, I want you to move on to a new assignment."

Now- the other team is confused by the webservice and does the requests wrong, resulting in failures. Does it become my problem again when they report that my webservice isn't working?

Yes, it does.

I am participating in a project i called "Game of Thrones"

We pretend that we are a team, but in reality everyone hate one another.
It took only 3 weeks for Team Leader to turn everyone against him.
He is constantly fighting for power with Architect who is terrible at his job, and doesn't listen to his advice even if they are good.
We hate Team Leader because he is an tyrant, who is ruling from high tower his peasants. His favorite task is to create various rules that everyone has to accept. You have to write "I accept" in a chat but this is the only choice. You cannot disagree.

Moreover there are developers from client side. They "committed" current project which is full of bugs and generally doesn't work. I don't know why they are still working there, but I presume every of them is working for 5+ years, so they are the only ones able to dig thru the spaghetti they made.
They constantly fight with us about the how code should be written, they commits are garbage but they are very peaky when it comes to ours PR.
They always drag our PR as long as they can. Even sometimes pointing they mistakes as ours.

The best dev team I have been with is during college where the three of us who were working at a maker space would go to various hackathon and stay up all night to build cool stuff! (We won prizes at quite a few hackathons too!) The other two are pursuing their masters in a different college now, I miss going to hackathons with them :( Hoping that we get to go to a hackathon together soon!

Working on a school project, a teammate created a git repo, gave us all the link, but no push access, told him about it, I gave up explaining.

I still dont have push access after half a day.

Also another team member doesnt know how to write code.

I assumed that people that got accepted in a master that has software development in the title have the basic knowledge or the background at least. Even though there is a separate master especially for that, to teach you software development.

Quick rant!!

Deadline in 2 days, working with a team.

Me: yo ! , How's the xyz feature? Is it working now?

Teammate: yah, made it work yesterday.

Me: epic! Can you present it to me?

Teammate: wtf, it's not working today!!

Me: no worries, you can sort it out!

Teammate: the latest release you worked on doesn't work properly.

Me: yah, merged code fucked up, I'm fixing that, I'll push a fix today.

And the cycle continues...

Yeah, So the principals of hackathons is shit and am about to braek down to fucking cry.All you do is waste 48hours of your life discussing your ideas with irrelevant startup managers who will just shatter your dreams with a single sentence "this is already in market, what have you creat new?" For fuck's sake, it's my first hackathon , you guys have given me just 10 hours ,i have a team of worlds most idiot devs and i am their equally idiot if not more leader... However my idea was 1000% real and authentic and worth finding... if not, then at least give me prize for creating 9000 lines of code with 2 IOT devices and a working , documented model which no other fuckin team could do.... AND even not this, then FUCKING GIVE THE PRIZE TO SOMEONE WHO DESERVE IT, AND NOT THE TEAM FROM THE COLLEGE THAT SPONSORED IT.. fucking politics -_-

During my internship.
Got wonderful opportunity to present a project to a senior Director of a different team.
And just moments before meeting, my project stopped working.
Was a disaster.
Later came to know there were internal issues in the service I was using in my project.
Though not my fault, but during the meeting, I managed to show a video of the project.
Let me know if folks wants to know what happened later..

Not sure if this is necessarily a prank, but I was working on a team that was split in 2. We had a group of senior devs in one country, and junior devs in another (god only knows why, and yes I complained about this a lot).

The "lead" of the juniors was very stubborn and refused to adhere to the official standards, as his way was better.

I was working on an app with him, I was fed up with how badly the app was working, how hard it was to find files etc. So I waited for him to be off on holidays and pulled some extra hours to completely re-do the folder structure, rip out his persistence layer and a few other things.

When he came back he lost his shit and complained to the architect. The architect (also fed up with his shit) told him that we don't have the time to invest in reverting back everything, and loosing all the new features I added on top, especially since the app is now adhering to standards.

Never felt such satisfaction in my life.

Teacher asks the class:
"How do you become a good developer?"

All the students starts talking about algorithms, problem solving or working in a team.

He nods and starts writing on the board. w w w. g o o g l e . c o m
He then leaves the classroom.

So here I am years later, a master googler and a expert stack overflower.

Please tell me something wrong with me, and whole world is working like that! It can't be right! Or could it, and I'm just one sad fuck who don't know shit?

So... We've got:
1. Jira reporting (agile style with cards and shit)
2. Task timers (via application integrated to Jira in order to count how much time we spent on a task)
3. End of the day email reporting with description of what we have done today (Jira is not enough?)
4. Daily morning meetings with a team leader to report what we're gonna do today
5. Git merge code reviews for each finished component (that lasts for hours)
6. Weekly status meetings
7. Working hours reporting with a fucking fingerprint

And on top of all of that, the developer is the one who just writes the code - team leader decides how this code is gonna look, what will be written first and what last, what libraries will be used and so on...

I work on a warehouse dev team. One day this past year, I was trying to deploy a new build to a QA server. Earlier that day I had been looking at the logs on the production server and had left the ssh session open. I had been working for less than a year out of college at this point and shouldn't have had access to deploy to the production server.

Long story short I deployed my QA build to the production server and saw there were problems connection to our production database. Then my heart dropped in my chest as I realized I had just brought down our production server.

I managed to get the server back up by rolling back in about 5 minutes and no one ever knew except some people on my team.

I felt horrible for the longest time. Later in the year another guy that joined my team that has about 20 years of experience under his belt did the exact same thing, but needed help rolling it back. Needless to say, that made me feel a lot better. 😂

Definitely the worst moment of my year.

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

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

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

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

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

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

!rant

My love for Clojure is so deep that I have invested the whole company. Over the past months just everyone came up to me and asked me, if I may teach them some Clojure programming. With everyone I mean literally everyone working in this company - fellow programmers, the ladies from HR, the Sales Team and even the CEO.

So today I gave a two hour introduction to the whole team on how to Clojure (in absolute basic terms).

The team has just voted that we will do that every friday starting next week for the rest of the year.

If you have passion, show it.

Working in a startup company acquired by some €^%€*^^ from singapore, second month no sallary(the first Local CEO) paid us.. now nothing...
I went to new interviews today.. HR and later 2 hours C# Coding test... definitely I was fucking good in the test, they called me hours later with positive feedback and new interview tomorrow , and they want me to team lead now 👍🏻👍🏻👍🏻👍🏻 positive vibrations guys🙌🏻🙌🏻🙌🏻🙌🏻

Started a new job and our tech lead doesn't know how to use GIT in a team environment, has only ever used it while working by himself on one person projects. Kinda worried...

dev, ~boring

This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.

I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:

1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by

I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.

At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:

"Hierarchy and structure should arise from an understanding of a problem domain"

As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.

In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.

Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).

I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:

1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth

Given that, I can devise a heuristic, organic framework for growing a team:

- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it

Last thing isn't derived from the train of thought, just things I feel are true:

- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy

/rant

So do you have any co-workers or teammates who horde tasks and don't share knowledge? I hate those kind of people. Everytime I bring it in team's retrospective and that one asshole remains quite during the whole meeting, agrees to everything and continues to horde tasks again in the future. That affects the team performance and causes to form a single point of failure and recovery which is bad when working in a team. Share your experiences.

Our smart and very professional sales guy strikes again,

I had to do some research on if I could print a pdf file directly from the server (be it php / nodejs)

When I told him I had found a solution he said, good job and went away, I was like...hmm k..

A few days later he came to my senior being mad that the project wasn't done in time.. And we were like.. Dude... What project!?

Apparently he made a deal to have a working demo in two weeks, but we (our dev team) never got that message...

The project which I took over from the previous team had exactly 1576 usages of an operator which I've never seen before after 10+ years of working in PHP.

Curiosity lead me to the php.net site to see what kind of advanced magic this operator does - only to discover that it's an error suppressing operator (@). They've simply used it as a default method for solving bugs and removing errors from the logs.

Just quit being in a team for an app i was working on on the side. I liked the app but i decided working 10 to 6 is enough work for a day, i deserve guilt free chilling in my free time.

This happened a couple months ago, but I wanted to share this one, since it still baffles me.

We were hiring and had this weird candidate. The team said no to the guy after the interview, management still hired him and pressured us to train him, which cost us tons of hours we had to somehow squeeze in during a hot phase of our project.

After almost 3.5 weeks training he had to hand in a small component. What he handed in was brainlessly duplicated, half of the stuff in there wasn't even used, the other half wasn't working properly. At the review we asked questions about the code he handed in - he could not answer one of them.
We then had a big argument with management to let the guy go, which they eventually unhappily agreed to.
The icing on that cake of a story: Turns out, the guy was hired as a senior dev with a way higher paycheck than most of the devs on the team. Wtf?!

Fuck, they updated the internal move policy in my company from 1 year 9 months to move to another team to be at least in the same team for 2 years.

I hope I can find a way to gtfo faster because I am honestly so tired of this shit, the tasks are getting too repetitive, my boss is useless, spends her time shopping instead of working and being stuck with a bunch of juniors means you only have the internet to learn something new.

I really want to start delving more into PAAS and start working with docker and kubernetes. Oh well, guess we'll have to wait and see.

Least fav part of remote work?

- When managers think you're in front of your laptop all day, they should be able to ping you ANY time of the day and expect you to respond.

"Well, you live and work at home and I'm paying you every month. So what if it's 3AM right now. Get the task done."

- When your team is remote and you leave a question to your teammate and they don't respond until night time - when they actually start working. Basically teams not letting each other know when they'd really be online.

- Too many meetings can be thing. It's not always though. So it's fine.

- Team level decisions take too long sometimes, so there's a chance you won't hear from your manager/team lead for a while.

I guess you gain something you lose something. Be it WFO or WFH.

Need to implement something huge on a app that I'm working on.
The design team is not from my company.

All the design that I have is in a PDF that I can't extract the images and they are low res.

How the actual fuck do they expect me to do a good job if I don't even have the design and assets to work with

Don't get stuck maintaining legacy stuff.

If you move to new, preferably greenfield dev every so often then you'll naturally keep with the times (at least if you're working in a vaguely decent team.) If you stick in one place too long and get stuck maintaining legacy crap, then that will be your focus, and that will be where your knowledge sticks.

Being a team leader some times sucks have to take responsibility for everyone's elses functionality that doesn't work or wasn't tested in production. Leads often ends up working overtime fixing everyone elses work :(

The most annoying co-worker(*team*) I have worked with just signed off a custom project that uses plain text passwords, hard coded into a file.. PLAIN TEXT!!! NO HASH!!! NOTHING!!! The same team also told me that working in feature branches cuts into their productivity, but they want CI/CD implemented NOW!

I'm a first year MSCS student, and working in a startup as a part-time engineer. The founder insisted to mark me as a "Senior Engineer" since I was leading a team of 3 student programmers. Deep in my heart I knew I'm at least 4 years away from competent enough to own this title... Today, I got an invitation from a well known company asking me to join their new team as a Senior SDE II, and I suspect this is the reason. I don't know what to do right now... Frankly I only want to ask the HR if he’d consider adding me as an intern instead LOL. I have no working experience in large professional companies before, and I think I will embarasse myself if they interview me about my experience as a "Senior Engineer" which in fact I was merely a Junior dev...

Last sprint is a mess.

Working on three products that are related one with another a little bit.

1. Bug reports are coming in;
2. We fix it and give for QA to test;
3. QA starts testing and it doesn’t work;
4. Because another team updated something in product A and product B depends on it.

Repeat for straight 14 days

I fckin love it when you start working on a new project in a new team and the 5000 lines of Angular code are acompanied by 0 documentation.

Being a junior and part of a small team at a startup, working with a new software architecture, even the team lead is a beginner in it. It feels like I'm at an echo chamber, there's nobody expert enough to look up to if stuck, decisions seem to be based on opinions rather than an architectural design kinda point of view.

Ugh, I hope I'm not the only here ever feeling this way.

Today was a SHIT day!

Working as ops for my customer, we are maintaining several tools in different environments. Today was the day my fucking Kubernetes Cluster made me rage quit, AGAIN!

We have a MongoDB running on Kubernetes with daily backups, the main node crashed due a full PVC on the cluster.

Full PVC => Pod doesn't start
Pod doesn't start => You can't get the live data
No live data? => Need Backup
Backup is in S3 => No Credentials
Got Backup from coworker
Restore Backup? => No connection to new MongoDB

3 FUCKING HOURS WASTED FOR NOTHING

Got it working at the end... Now we need to make an incident in the incident management software. Tbh that's the worst part.

And the team responsible for the cluster said monitoring wont be supported because it's unnecessary....

I get back from Christmas vacation. I read all the unread emails and team chats, then go to work on my assigned tickets. As far as I can tell, those tickets are all I need to work on.

Then my boss snaps at me during our team catchup that I'm supposed to be working on a different set of tickets. Which were not visible on the board. Which were not assigned to me. Which nobody on the fucking team bothered to update me on. Of course if I point those out it'll just be a pain to deal with (especially since my boss doesn't seem to have my back, unless he needs something).

I thought my vacation would help me re-energize and get motivated again for this job, but coming back I'm reminded how unhappy I am now here. I've started applying elsewhere, but I don't know if I can continue to put up with this bullshit until I find a new employer.

Any tips or advice from folks who've felt unhappy in their job in the last year?

What are your thoughts on working for a company that give their devs jira tickets that don't have any descriptions? I work for a big organisation (It's actually in the top 3 biggest companies in the country I live in) and I work in a team that has quite possibly the worst agile practice I've ever seen. We get tickets without any descriptions at all. The worst bit is then we get pressure from project management for not delivering things on time. Do they actually realise how difficult it is to deliver something without any business requirements? I have to have a million meetings before I even know wtf the ticket is about. It's incredibly annoying.

Why do some devs who work for corpos have a superiority complex?

“Oh I cannot imagine working on a small team of 3 people (2 devs, 1 designer) on a website”, saying it like if he was disgusted. “The team I work in has 40 people”, with a hint of superiority in his voice.

Bro, chill for a moment, it ain’t a race to the top.

note: it is already dec. 23 in here

testers and another integration team are working for an urgent deliverable.
they just called, asking if i can come to the office and complete my code so they can use it as a basis/reference to theirs.

wtf

Working with acutal BigData. Will be ''promoted'' to a new team where I will work on a system wrote in php+mysql with literal millions of requests and database rows. We are currently seeing server crashes around once a week on peak usage. Stack is a vps 64gb ram server + i dont know how many cpu/ cores. Apache, php, mysql.Best ways to optimise and adapt in this case? Kafka? Rabbitmq?ngnix? More hardware?

Have to present a school project I've been working in for three weeks with my team.

My part of the presentation is done, my part of the project is done.
The fucking sysadmin doesn't have his fucking part ready...

ALL HE HAD TO DO WAS SET UP A FUCKING WEBSERVER, IMPORT A DATABASE, EDIT THE HOST FILE AND WRITE A SMALL 2 PAGE DOCUMENT ON THE INFRASTRUCTURE.

Each of the 4 "roles" within the project need to present their own part, guess whose part of the presentation isn't there...

I am so fucking done with this guy and 2 others in the team...

I just don't get how you can spend 1000's of € per year on uni and then not take it seriously.

The best way to describe what I had to do today is I "Channeled Macgyver"... now production is working.

⚪Data wasn't flowing as expected.
⚪Component written by our team was blamed.
⚪Boss asked me to bypass the component so data can flow.

Sure, I can fix that... Give me a car battery, a roll of duck tape and a butter knife. Data will be flowing in production shortly.

Do you guys like working in a team or alone?

I hate those persons...

*sigh*

Don't do this.

Person does it.

Don't do it. We are currently overworked and this _must_ be a project every team agrees on. Otherwise it will end exactly like it is currently - a big mess that every team implemented differently.

2 hours later....

Person books time for said project.

Other team lead: Stop working on it. This makes no sense.

Person: yeah... But I needed to clean it up anyways, so I just started cause why not.

--

Me and the other team lead had a 5 min discussion about it shortly after...

Wasn't the first time said person has gone solo rogue *sigh*

Despite that this is driving me (and the other team lead) nuts...

WHY THE FRIGGING FUCK DOES HE ALWAYS DO IT WHEN WE ARE SO FUCKING OVERWORKED....

Really. Every fucking time this mother tugging bullshit kindergarten play.

I think it's the first time that I said: I don't care - I'll just trash his work when we start on the project as a team in 2 months (Yeah... That's realistic. 2 months minimum...).

The universe really has it's way to make me angry.

I hope he stops tomorrow, we really cannot deal with emotional bullshit at the moment.

*gooozfraba*

How can such fuckwads exist....

i am at the point of deep depression again as a CS student. a few weeks back and forward is a busy weeks with a lot of team projects/research. as always, team project never be as smooth as i expect, I always who be the one who work in the project with the rest of the team and they doesn't even care what the project does.

also a few week forward there will be a Leadership Training, and i just quit from it, why ? because i need sleep. why again ? BECAUSE I AM THE *ONLY* ONE WHO WORK ON THE PROJECT YOU FUCKING DIPSHIT, i am the one who can't sleep everyday working on the project scraping the deadline and class hour.

why i drop important thing (Leadership Training) just to keep me from depriving my sleep and to keep the project up while the team disregard me? am i being too humble yet i just rant about "don't be too humble".

..i...i just... I just can't take it anymore. :( god help me

Introduce Git - Promote Collaboration
In the real world they won't work alone. Instead of giving individual projects give them a module to work for.

Example project: Library System
Student 1: Sign-up module
Student 2: Log-in module
Student 3: Book sorting module
Student n: x module

Output: A working system

With this approach, students will learn to work with a team and communicate properly about the project they're working for.

No table and monitor, and having to work ALL THE TIME. Our team structure changed recently, and a coworker with 2 years of experience is my lead. He wakes up at 11-12 in the morning, starts working by around 2, takes enough breaks and sleeps at like 5 AM. He assigns tasks late in the evening and night. Expects people to finish it staying up late, because if he can, why can't we. Most of the time, it's like, hey, just push a little and finish it tonight, we have other things to do tomorrow.
And team mates who can NOT work without help from other people and text and call you every hour.

Well, the project I've been working on is now being terminated.

As the lead dev, I found out by one of the managers sending a public message to the staffing team in one of the channels unrelated to development, which I don't normally check.

Apparently at no point in their "very long discussion" did they think they should let me know of this decision.

Tbh I'm not even suprised, I was barely ever told anything. The others aren't either.

Just had a work review last day. They told I am meeting their expectations . Okay ,Nice..
Then at night , talking to a friend working in same company ,heard her review significantly exceeding expections and all she gets to do simple bug fixes or smaller user stories. No complaints for her.. But for my team, A little more appreciation would have been better..
When these corporate jobs will realise that sometimes an appreciation can make you work better?

When I wasn't a part of IT during the beginning I used to be working on Back office operations.

My team leader was such a motherfucking asshole!! He rarely ever worked, always came late and gave all his work to the asskissers in the team. He used to drink in his car during breaks and also leave before anyone. The only positive was he didn't give a shit about who took leaves and when.

Once he came to office drunk and warned me of getting me fired, which he never could. I probably felt like ripping him off then and there and escalating it to the HR.

I didn't. As Karma would have it, his manager changed and the moron had to get his team changed.

I work in a big corporate world where I felt really out of place at first. I didn’t enjoy working there, I could not understand why people would work so hard to keep all the systems happy. No one thanked them, no one gave the smart people maintaining the important systems any credits. I did not understand. Why did they care so much for these systems?

My team split. We were too many with too many systems to care for. After this my team was a lot smaller and therefore I ended up in a more important role. I was forced to do these tasks the more senior engineers had done before me, in the previous team. This was the greatest thing that could happen to me, and I started to like coming into work. Now our team is big again but I’m one of the senior people in it. Not senior as in years active in the industry but senior as in knows the most about our systems and our work environment. I work hard to constantly share my knowledge and try to put the newer members in situations where they also have to take responsibility.

Don’t be afraid to put important tasks on junior or new people. They might fuck up but they will learn, as will you. Don’t hog your knowledge and your team will thank you.

Optimization issue pops out with one of our queries.
> Team leader: You need to do this and that, it's a thing you know NOTHING about but don't worry, the DBA already performed all the preliminary analysis, it's tested and it should work. Just change these 2 lines of code and we're good to go
> ffwd 2 days, ticket gets sent back, it's not working
> Team leader: YOU WERE SUPPOSED TO TEST IT YOUR CHANGE IS NOT WORKING
> IHateForALiving: try it on our production machine and you'll see the exact same error, it's been there for years
> Team leader: BUT YOU WERE SUPPOSED TO TEST IT

Just so we're clear, when I perform a change in the code, I test the changes I made. I don't know in which universe I should be held accountable for tards breaking features 10 years ago, but you can't seriously expect me to test the whole fucking software from scratch every time I add an index to the db.

TL;DR: A new "process" for collaboration between teams was created in order to stonewall requests from my team.

A couple months ago, we created a new Dev team that specializes in writing internal tools. This team was staffed with internal developers, and got a separate manager. The whole point of this team was to collaborate with my dev team so we can both help each other develop tools that the company needs.

One of the developers that was on my team went over to this team while he and I were still working on a big application. For a few weeks, he still worked on this application as he normally would, and we'd sit with each other and work through features together whenever we needed a fresh set of eyes.

Well, eventually his new team got protective of him and created a new "process" for our teams to request assistance from one another. So now instead of just popping over to someone's desk to ask a quick question, you have to send an email to the team and request that you can borrow that particular developer for a question, and then the entire team sits down and discusses whether or not they're going to allow that person to answer your question. Then after a week of discussion, if they decide to allow it, they schedule a meeting for a week later, in which you will get the question answered.

So instead of just spending 2 minutes to ask and answer the question, you have to spend weeks in order to request assistance, and then schedule a meeting.

It's ridiculous, and it's all because his team got protective that he was working with another Dev team. Dev teams collaborate all the time, and work together. My team is constantly helping other teams, and we don't have this ridiculous process. We get asked a question, and we answer it. Simple as that.

Last week, I sent an email for assistance in completing a feature, and didn't hear back. I talked to the Product Owner for the team, and he said "Just send an email," to which I responded that I did and hadn't got a response. He said "Oh....." I then told my boss that this is an enormous bottleneck, and he seemed surprised hearing that this is a bottleneck.

A week passed and today I still hadn't got a response, so my boss reached out to the Product Owner to push him. Finally, I got a response and they scheduled a meeting to answer my question 3 days down the road. So it's going on 2 weeks to get this simple question answered.

Normally I'd just have the other developer come over and help, but apparently they yelled at him the last time he did that.

The issue is that the process was created with the assistance of our "senior" developers, who never work with this other team in this capacity, so they just nodded and smiled and let them put this ridiculous process in place.

Like, get off your high horses. You don't "own" him, he's allowed to collaborate with other teams. This question would've taken literally 10 minutes, but because of your new "process" you've turned it into a 2 week debacle and you've effectively delayed the app launch with your pettiness.

They say that this process isn't intended to prevent us from getting assistance, and that might not have been the original intention of the Product Owner/manager, but it's very clear that the developers on the other team are taking advantage of it and using it as a big stonewall so they can beat around the bush and avoid providing assistance when it's needed.

If this becomes a trend, I'm going to schedule a meeting (which apparently they love to do,) and we're going re-work this entire process, because it's extremely counterproductive and seems to only exist in order to create red tape.

I cannot work on my personal project this weekend.. because the fucking IT team gave me a fucking mac charger yesterday and it fuckin stopped working today.. FUCKING waste of a weekend!!!!

I guess I will be gaming for the next 48 hours.. on my windows PC..

(And please don't say Linux Rocks in the comments coz I had to work on an iOS app..)

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

So I need your advice guys. Our team is in crisis mode right now because of a vendor's attempt to extort money out of us. So for the next 6 months I am going to be taken off development and made to do sysadmin work...which I hate.

There is another team at work that was trying to woo me over to their team, working in security...which I love.

So would it be a dick move to leave my struggling team that is trying to use a hammer as a screwdriver and do what makes me happy? Or should I be a good person and do work that makes me miserable and go home and drink every night instead?

$rant = false;
Let say you guys are working in a team of 3 and need to share a database. All of you are in different locations.

I am currently hosting my database on online server, which is kind of slow for me because I have poor Internet in my country. How do you guys do it?

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

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

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.

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

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

I resigned not long after that.

The worst part of being a dev? Working in teams.

And I don't mean that in the "I'm the best ninja code wizard in the whole world and you're all holding me back" kinda way. I'm thinking more in the lines of someone who has to deal with that kind of attitude on a daily basis. As someone who recently was put in a leading position in a dev team, this is by far one of the worst experiences that came with it.

Some examples?
- One dev completely changed the naming scheme for variables in a class he worked on for one. single. bug fix. His reason? He just didn't like it!
- Another one noticed that data he was supplied with was not in the specified format. Instead of flagging this with the project leads, he just rewrote his parser to fit the data. A couple of weeks later the supplier noticed the error, fixed the format and suddenly everyone wondered why the software failed processing the data.
- Or that one senior dev, that just refuses to accept changes because "it was always done like this and it worked" No, it didn't. That's why it was changed!

Once a dev team reaches a certain size, people need to realize that stuff like coding rules and process guidelines are not there to annoy them but to help the whole team work as efficient as possible. I don't care how good a programmer you are, if you can't check your ego you don't belong in any kind of team-oriented development project!

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?

Ooh what a nice feeling it is when you come back from a short vacation and everything is in the gutter... My team is divided into the two other teams... (I said divided but I ment everyone got assigned into team X... And I am the only one who was put into team Y)

Besides the whole team fiasco, I think my legacy project decided to role around in the garbage... Because I have no idea where all those bugs came from...

One positive thing is that I won't be working alone on that legacy project anymore, at the start of next week I get help from my new team... Now let's hope they don't suck!

Working a month on college site, in a team of 10. Stay back after hours, work from home. Tons of fixing and patching. Student council member asked to demk the new site to a college trustee.

Trustee sees Snapchat icon in social media. Doesn't know college has Snapchat. Asks who authorized the icon (it was a sample icon!)

Orders site to be taken down.

We write our feature specifications in Gherkin, so it is clear to every member of the team (even nondevs GASP!) exactly what each feature should do.

SO WHY THE FUCK, AFTER BUILDING THE FEATURE, DO I GET REVIEWS FROM THE pRoDuCt MaNaGeRs, SHOWING ME THEY WANT SOMETHING DIFFERENT FOR THE FEATURE. YOU WROTE THE FUCKING FEATURE DID YOU HAVE A CHANGE OF HEART MID THOUGHT YOU IDIOT!!!!!! AAAAAAAAAAAAAAAAAAAAA I'M SO SICK OF IT I'M SICK OF WORKING 12 HOURS ON A FRIDAY FOR YOUR STUPID SHIT

Rant

I was given a project to lead and develop with 2 other team members by the co-founder, I was told that I will need to deliver an initial demo within 30 days, 20 days in the project and I was told yesterday that they need a final release ready within the next 10 days !! Not just that but the co founder decided to assign one of my team members to another project!!!

I've worked today till 4am.

Guess who's working from home in the morning!

I’m seriously considering leaving my current team or even resigning from the organization altogether. I don’t blame anyone— I understand that managers have their own deadlines to meet and have to answer to their superiors when things go south. I have indeed developed a thick skin by getting used to all this shouting/blaming the last 3 months. But yes, I seriously don’t think there is any point in taking this anymore. It’s not good for my mental health.

My question to all of you is, is working at smaller companies better in regards to this? (I’m working at a big corporation now). And are they more unstable than bigger companies? (especially in times of COVID)

I currently work for my college for the web team. We are working on a year long project which is to update the college's old website to one that is not only more user friendly, but is also mobile friendly (unlike the old one). My job for the past week (with another week to go) has been to simply delete all HTML attributes that were used in HTML3, and this entire site was written using it.

This literally happened in my current team, and I'm not even an experienced dev yet.
Incident happened like this :
Our team is working on a RCP based on eclipse plugins, which has a headless mode and a GUI mode. Now, in the GUI mode, my manager cum architect thought there are no need of user log files (long story) because the user can see the info on screen, whereas in the headless mode, she wanted me to print the logs onto the console and a log file as well.
Now it just so happened that our team had got a recent addition as a replacement to our lead developer (she left the company) who claimed she had 3 years of expertise and a masters degree, and she was assigned a task. The task was to format a custom file we were generating out of the product (basically dumping info in a file) in a human-readable format. Miss new-addition-masters-degree decided it would be a very good idea to redirect the standard java output stream to a file output stream ( which she used for generating the formatted file ) but somehow never realized that she needed to reset the output stream back to standard output.
Consequences were devastating. I wrote the logic for the logger ( yes, apparently any available logging mechanism won't do it, again, long story ) and had it printing to a file in tmp directory. The logs seemed to be working fine initially but after a few logs, specifically from the point where the formatter started working, all the logs got printed in the formatted file. And this file was supposed to be used by our clients to develop something on top of it. Naturally, I got the heat of it and then naturally, worried and nervous and curious and in a frenzied state of mind, I started debugging.
When I got to the actual fault, I seriously could not decide whether to cry or laugh or call up miss masters and scream at her. I decided to ask her about what the hell she had written and her answer was most of it was written by the developer she replaced, so she didn't know it would cause this much problem. Anyway, I fixed the leak after that and averted the catastrophe.
And that, fellow devs, is the story of how I solved a crisis in my first year at corporate.

My team lead had a history of being vindictive. After 1 engineer left she talked a lot of shit on him. After another left (who was extremely well liked), she surprisingly talked a lot of shit on her.

Well I put in my resignation and reached out to personally thank her for the years of working together. I said she could use me as a reference any time. She did not reciprocate. In fact, her entire demeanor was cold and confrontational.

No idea why I thought I would be any different, she's just a shitty person.

Working on a project needing to integrate java, jquery, SQL, various aspects of Android unix manipulation i.e. rotation, gps, music players, etc..needs to successfully build and after getting finally getting all needed repository files, work in android studio then be converted into an apk, compressed sent to instuctor's device for seemless use...this group project included 6 individuals teamed up like avengers to complete...my team mates either dropped the class or with drew.fml with a hammer sideways.

The actual struggle of working in a non-english team who prefers to keep their variables named in our native language. Currently trying to think of a better way to phrase 'sjaafoerAerend' as dropping any part of it makes it more vague.

Is this a thing in asian countries as well? I'm guessing it's more common to just stick to english naming there.

I figure it's safe to assume that anyone who will see the code are going to be proficient in english. If they aren't, natively named variables isn't going to make a difference. Hell I even write my personal reminder comments in english.

Yay finally summer started
Ye no fuck that
After being "migrated" into a newer smaller office and getting another team member we are now three people on about 5 square meters of space.

Another good thing is that we don't have an air conditioning unit in the new room and gained a few more PCs.
Oh and did I mention that we are on the sunny side of the building now.

Basically we are working in Satan's Asshole now. Good thing is that I am working on a thermometer now.
35 degrees Celsius is still alright isn't it?

Oh and our fan broke today.

I don't know how to feel about this: in the dev team I am the only one working with a dark theme.

Are they real developers? Where am I?

I think I joined the wrong crowd. After the recent Hackathon, I proposed that the team that I was working with, form a company in which we continue building apps, launch and try to profit. Y'know, the whole build fast and die slow kind of thing. Granted, I proposed it late November and we're all gearing up for the holidays. Now its January and everyone has this mindset of "if we don't meet, we don't get anything done" or "discuss face to face only". Guess they don't like the idea of working remotely.

I think I might just quit this venture after a couple of meetings with them before I lose my mind.

Job review time,
(just a random pick from the a list).
---
"Engineering Lead"
Translation: "Chief Calculator Officer"

"Anyone can design or spec a product, get it manufactured overseas and get it to market. But will it be good? Will people buy it?"
Translation: "We're looking for a miracle"

"Take on a top notch team that is going places in Electronics, R&D and advanced product development."
Translation: "Professional Excel engineer wanted"

"This company is a little-known success story that has been operating for over X years, making mission-critical electronic equipment for use by consumers, professionals, government and industry."
Translation: "Design weapons and tamagotchis."

"Working as part of the Senior Leadership team, you will have charge of the I.P. engine and product development team spinning up new ideas and throwing them out the door."
Translation: "You're success is our success. Your failure is your failure."

"The Role
- Generate New Ideas
- Push for new products
- Drive manufacturing
- Manage a cross disciplinary team that includes Electronics, Software and Mechanical
- Project Manage new projects to completion
- Interact with marketing and sales to drive results"
Translation: "We've never hired one person to be a whole team before but we think it will work."

"On your first day, we expect:
- Strong Leadership experience and skills
- Solid Engineering Fundamentals
- Experience taking new and existing products to market
- Experience with manufacturing high-tech, mission critical equipment
- Commercial Acumen
- Bachelors in Electrical or Electronic Engineering"
Translation: "We expect you know where to hide the drugs already."

"Nice to have:
- Experience with Defense or Medical Systems
- R&D background
- MBA, B. Commerce or similar"
Translation: "By clicking on this job ad your background check is already under way."

"In return:
- A loyal and oustanding team will be there to support you
- Extremely knowledgeable experts to guide you
- Incredibly smart founders to mentor you
- The opportunity to work on a real product
- Extremely generous salary package"
Translation: "Our last dev has removed the Warrant Canary. Can you pleeease put it back?!"

My first dev job :

Do a front-end in Joomla!. As an internship. Without being paid.
(In France, if you are here for >2 months, they can pay you, or not.)

At least, now I know why Joomla is a no-no when you want to do custom things. Heard that the team working on back-end had problems of PHP, like the PHP appearing and the one Joomla uses "is not the same" or something like this.

And now you know if you didn't. No problem.

Asked if I'll meet a July 15 deployment date for a payroll app that has been out in UAT since Jun 27th with no comments (6 working days and 2weekends)

Me "Well I smoke tested it and it worked but if I get a 20 item correction(/enhancement) list on the 12th from the customer rep again, then I won't"
m
Team Lead: "I'll try to play with (test) it some today"

Me :)

2 years back when I was onshore, we were in the bad situation due to the size and complexity of handling big webserivces simulators. A single change makes the build red hence the face of other developers too.

These simulators were created using J2EE and VM templates 5 years back. With the time, application and data size grown. We were supposed to maintain consistensy in dummy data accross the applications. But some programmers made a copy of these simulators to finish their applications fast and made the situation worst.

Finally one of the team member dare to use stubby4j to solve this problem. Choosing the stubby4j was a good decision as it was the specialized tool written to create simulators only. But as the stubby4j was not having all the features a simulator need, he customized it's build for our simulators. All the team members were happy.

After few weeks, I picked a story to transform other simulators using stubby4j. The story was previously closed as it was hard to implement in stubby4j. I ingonred the comment and started working on. I spent 2 weeks but couldn't solve the problem. I read the comment in between but It was very late to take the step back. I was not able to give proper status update in the daily standup. Other team members (working from offshore) were thinking that I'm just passing the time. However my manager handled the situation very well and asked if I need some help.

This was friday, I took the leave as it was my wife's birthday. We couldn't go out due to the bad weather. I was thinking about the code all the time. Hence I started to write a new utility to handle all the requirement a webseervice simulator need. I took 2.5 days to complete it. On Tuesday, I demoed it to the whole team. And published it as an opensource application "STUBMATIC". In few weeks I received the good response from other teams as well.

I'm a full time open source developer now.

Questions/best practises for git?

For example:
- use present tense in commit messages. (why though?)

A friend of mine also starts his commit messages with either [Task] or [Cleanup]. Useful for finding Commits in Gitlab etc, because only the first line is shown from the message.

Also, one teacher recommended the usage of branches and the other didn't because of alot of potential merge conflicts when working in a Team or a larger Collaboration. What are your thoughts?

Sorry for the messy post, have a hangover

Fucking fuck !
I work with a senior Dev,
It’s pretty much like am working under him....
He’s like a great Dev no doubt about it

But !!!!

He’s a fucking dumbass when it comes to working in a team. He makes changes in my code without telling me. He says He forgot to tell me , every single time

When I ask him how a piece of code works , he says it’s pretty much obvious and acts like even a 6 year old kid Would know this ,
He doesn’t think 2 steps ahead before solving a problem usually creating another problem !

We were once working on a language which we weren’t very good at , so I suggested him to ask another Dev in our company about inputs on our code structure to which he completely Disagreed saying they really won’t know much and that he knows more than them..
Fucking dumbass thinks he knows more than most ...

I have tried confronting him multiple times but he feels but he just won’t listen...

!Not Rant

I'm so hopeful. It's actually comedic.

Short backstory catch-up. I started working with an *actual* huge firm.
And unlike my other horror experiences with huge monopoly firms, this one is actually chilled out. So different that it seems almost like a startup.

Idk how tf they preserved this dynamic but I literally like everybody in this team of twenty-ish individuals. In fact I somehow even look upto some of them.

Hope this stays up and I might be locked in for a few more years.

Got my first dev job last November and I've been working as a contractor for the government. Supposed to be on a 4 year contract job, just found out that out project is being pulled in September. Is this common for federal contract work? My Human Resources team haven't been very helpful in explaining the process to me. Is private sector development any less volatile? I don't have a mentor or anybody I can bounce questions off so sorry if this is more or less common knowledge :/

So, apparently that another kickstarted IoT chip dev team forgot to bind reset button to anything, so it is just sitting there as a fidget toy and they also messed up with usb-to-serial connection so it is working only in transmission mode. I am just sitting here with bricked chip with no adequate possibilities to unbrick it.

Java 8 to Java 11 all in under a year. Convince me this isn't the Angular team working on Java. There are the ones with a knack for teleporting versions. Honestly I could give less care on what newer changes occur cause....Kotlin baaby!

I was in dependency hell for two days.
Im a junior working in a team creating an ember app. Suddenly a main component refuses to work since an addon threw "EmberObject undefined"... Nobody could reproduce it and we where out of ideas, so I tried fixing it for 2days (7h total). I finally got it working after updating yarn :D
It never felt so good working again :)

My team leader/manager tends to assume that when you call in sick, you'll be sipping soup, wrapped in a blankie, while working from home.

Ahhh... NO! When someone calls in sick, you assume the worst, phone the florist so long and prepare for standing next to a hospital bed!

TL;DR: working too fast is as worse as working too slow

3 months ago the team leader left.
Sincee then, me and another dev are sharing his responsibillities.

Me and him used to do a lot of testing.
(In our team, the devs test and CR each other)

Now that he left, I often find myself sitting without anything to do - because I did all the available tasks and no one tested them or gave feedback.

Sitting with nothing to do feels aweful.
My manager sits behind me, so i cant sit on devRant or Twitter without feeling bad about it.

So i'm working with people from another team to bring about a feature. I was wondering, "how come they're churning out so much shit in so little time!?"

Apparently, they make code, merge request to the release branch, and then do unit tests later.

How do people, in good conscience, think that they can skip unit testing for extremely vital components???

What is the point of working on a team in an open work environment if the only interaction I have with them is during our twice-weekly stand up?

Tried making a game with a team.
The voice actors, landscapers, concept artist, 3d modellers all treated me (the only coder) as the one with the easiest job in the team.

After spending 40+ hours working on the code I got sick of the way they treated me. I deleted all my comments from the code and quit via email.

Some people think they can easily code if they were willing to put the time in. When they actually have to do it they give up, because it gets super complicated and difficult.

Is the office dead in the dev world? Does everyone prefer to work remote from home, coffee shops or Coworking spaces? Or is there still value in working as a team irl, but modern office culture is killing it?

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

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

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.

It has finally happened. I have escaped the land of bloated Objective-C and JabbaScript. This week I have started on another project, a full stack team working in Angular, Java, Hibernate, PostgreSQL. The dream has come true. Java it has been too long my friend.

So you're working on a product that basically the main thing it does is fire off http requests and parse their responses into a nice model. We've made some nice helper class that allows you to do this easily, but a simple piece of functionality is not in there yet.

You agree to add this one simple function and decide to:

- Not conform to coding standards set by the team
- Document its behavior which does NOT match the implementation
- Not write a single fucking unit test to prove it's functionality

ARE
...
YOU
...
FUCKING
...
MAD?!

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.

My company boss wants to reorganise the team structures drastically.

Currently we have different teams for each product. And in that team we have a lead, frontend and backend developers working in sync.

The boss wants to split the teams not based on product.. but based on technology / frontend backend. Then assign the members to products based on demand.

Not sure how that is gonna turn out..

I'm at work but not working, at all!

Planning was done very badly, my team finished in a very effective and efficient way, even before the timeline(including tests and all other things).

It's been a month(or so) since I'm not doing anything, the start was cool, I know most of you are gonna say you envy this, believe me, I'm not, I feel useless and the sense I could be fired at anytime increases everyday (my personal paranoia).

What would Brian Boitano do?

I just discovered that this game I worked my ass off to make for the past month doesn't meet the requirements. I have 2 days until I have to turn it in to rewrite the entire thing in another language.

I quit. I don't need that kind of stress, and heaven knows I ain't gonna finish it either way. I informed the team that I wouldn't be working on it after for a long time either. I just need to not look at it for a while.

Guys ! Need some help !

I am a final year CS undergraduate;will graduate in 2017 . I have been working with a team of freelancers developing websites and apps for the past couple of years. The thing is our client base is very small and the income is unstable because of our poor marketing and lack of good developers. Our team lead only doesn't maintain any version control,no code comments,sub standard code, and spends all the savings(we keep some money aside for expenses like meetings,traveling as a team etc) on movies,hangouts etc . I cannot tell it to his face but I have been looking to move out for sometime.

Should I continue freelancing by myself or apply in jobs ? And if I apply in jobs, do I apply as a fresher or a someone with a couple of years of experience ?

And if I continue as a freelancer,where do I start ? I checked upwork and freelancer.com but they have some cut-throat competition out there .

In recent time my anger comes from a junior dev who keeps saying he's got no time to test and breaks working code leading to others getting the blame and the team leader not addressing the problem.

In the past it was micro managing managers who thought they knew how to make a UI best, and also that one project where they gave a client carte blanche on changes to avoid legal trouble. Nothing more infuriating than multiple people telling you how to change things over and over while you're being passed around in their power struggle.

Anyone else find slack a time waster unless you are actively working on a team? I feel it fails when used for a user group: l have left most slack teams because it is like repeatedly looking in the fridge and not finding anything interesting.

High school robotics team. Total of three programmers and one coach who understands programming concepts, but not syntax or anything. One programmer, putting it bluntly, is incompetent and doesn't even bother to learn anything. The other one that isn't me is apparently fucking lead programmer and team leader (IM A SENIOR. SHES A FUCKING SOPHOMORE. WTF.) and she has done about 5% of the programming this year. I've done the rest with the help of a programmer from Ford whom we bring in. All she does is tell you to do shit for her, and if you don't, she pulls the authority card on you.

And I have maybe three days, after a full day of school mind you, until I need almost every part working on the robot code. Fuck me.

Hi ! This is not a rant but more like a need for help.
Currently i am working in a retail job , but i am planing to open my own business where me and my team can develop apps and webs.
My family and friends are telling me that i will fail.
What should i do , chase my dream and become unemploymed for a short period of time , or continue the way i am living ?

Thank you for your time and patience , and i am sorry for grammatical mistakes !

I've submitted a PR to a large open source project, and I've had no feedback in over two weeks.

I spent a weekend and many late nights working out how to solve this bug - it was my time - and the project team haven't eaten acknowledged the PR.

[Background]
Back in September I joined a startup after my first job in MNC for about 1.8 yrs as a fresher. I always wanted to learn, but the experience in that MNC was not at all fruitful. So ai decided to join a small/mid size company or a startup. To my luck, I got in this small startup in a week after my resignation as a front-end dev (always wanted to be).
It's an automation company, so you can find software, electronics, even mechanical engineer.
The team was almost a year younger than me. It was a team of around 12 people, in which 5 of them were from Business development.

The tech team was too driven and knowledgeable. Always trying new stuffs and motivating to do the same. I was highly motivated by them in my initial days, watching them working on new stuffs.

So I started with revamping their website completely in Angular 4, and did it in around a month or so, being new to Angular. Outcome was pretty satisfactory. I wanted to work on new projects, but just to get the cashflow in they started getting in WordPress projects. It was frustrating, I wanted to work more on new technologies like Angular, React, etc...but just for the survival of the company I had to work on WordPress, so to respect their urge to get going I kept working on 3-4 projects in parallel, and mind you the clients were from hell !!

Fast-forward 4 months, I am still working on few WordPress websites, and one internal GPS based project in React. And I haven't received my salary for past 3.5 months, since the company is still struggling with the issue of funding and getting money from clients. I kinda liked working there because there was lot to learn even though they are so young, but I had bills to pay too.

And I am in dilemma to leave the company or not, because I already stretched 3 months out of good will and guilt of leaving the company in high time. So i finally let the CEO know that I cannot stick for any longer. And i was done with the false promises of getting the salary "next month" everytime. All the money getting inside of company was invested heavily on the product we were building and no one was getting the salaries. Others were fine since they were founding members too.

Long story short : I finally left immediately and now working in a good company as a React dev. I hope they do well and I would love to see them grow, but please *STOP* making false promises and hold on to employees on a lie.

So I had to travel to the city for a team project I was working on. On arrival, I stopped to check-in at a hotel and was given the keys to room 404. I climbed the awfully complicated stairs for about five minutes only to not find the room in the end.