My project manager sent this to me today.

A group of ten top software engineers is sent to a class for aspiring managers. The teacher walks in and asks this question:

"You work for a software company which develops avionics (software that controls the instruments of an airplane). One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"

Nine developers raised their hands. The teacher looked at the tenth and asked, "Why would you stay on?"

The tenth said, "if my team wrote the software, the plane would not get off the ground, much less crash.

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

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

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

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

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

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

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

Then Gordon leaves and everything is shit again

"I am not happy with the quality of the product"

*Ignores

"I dislike how I am forced to work here"

*Ignores

"The team does not understand software design and is writing 2000 line single functions"

*Ignores

"I am starting to think the product cannot be saved unless we start focusing on quality"

*Ignores

"I am not happy in my job anymore because I want to work as a professional..."

*Ignores

"All I ever do now is put out fires"

*Ignores

"I quit"

PM: 2 months? no thats way too long, do it in 1.

Director: I had a chat with someone else who doesn't work on this team, he says that developer you complained about is a good guy and we should keep him on the team.

Business: No, we don't have time for tech debt, lets build these new features as quick as possible and lets see where we are.

everyone: WHAT DO YOU MEAN IT CRASHED AGAIN??? THIS IS UNACCEPTABLE

Participated in an IEEE Hackathon where we built a line following robot. We were the slowest, but we had the most accuracy.

The image is our first attempt at getting it to work, consequently, we were the first team to actually get a prototype finished and working. Other people were trying to cram as many sensors as possible. We stuck with one, and 47 lines of code to make it work. Everyone else had more than 2 sensors and I can only imagine how much code they had.

Latest from my team,
One of the Dev copied code from a stackoverflow question.

Got same exception as highlighted in the question and started complaining that his code does not work.

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

So yesterday I became an actual human rubber duck!

So I have a colleague in my team that for weird reasons is not allowed to work with the same thing as the other colleagues in the team is allowed to work with. So she´s kind of alone, working on another project, and that seems to suck really hard.

And this is how I became a human rubber duck. She asked me a couple of questions about a technology/language I´ve never touched before and I told her I never worked with that technology or language and know nothing. But she was eager to get me over to take a look at what she meant.

So I came over to her screen and she started to tell me everything about the project, the technology and the language. I soon realized she wasn´t only looking for help, she was probably feeling alone in the work she was doing and just needed someone to talk to. So I took my role as the human rubber duck and sat down to listen to everything even though I almost didn´t understand anything.

I think it actually helped her even though I did nothing.

Being a human rubber duck felt good!

The following meeting occurred at a client between a recently added client PM and our team, we'll call her Shrilldesi, previously from one of the main consulting vendors.

*Meeting begins after 15 minutes of bullshitting, waiting for people to file in*
Shrilldesi: "Ok everyone, let's get started
TeamMember: "We're still waiting for Z and W, not sure why they're late."
SD: "We can start there. It was decided had to lay off Z and W, because we didn't have enough work."
Moi: "Wait, what. Who made that decision? Why weren't we consulted on this? We have another project starting next week that they were needed for. They just delivered the entire public facing rewrite, why would we let them go?!"
SD: "It was decided by myself, pajeet, and venkata looking at the backlog. Not enough work, week gap."
Moi: "This is going to hurt our ability to deliver the next phase. When are we going to start interviewing new people, the project begins next week?"
SD: "We will interview new resources as needed."
Moi: "Who is we? And 'as needed' is yesterday, or realistically several weeks ago as the. project. starts. next. week. Also, we're obligated by federal law to bring back anyone we lay off before we hire anyone else for the same position."
SD: "Interviews will be done by myself, Mohd, and Pajeet."
Moi: "...can I point out that there's only one modestly technical person in that group, they're an admin, and none of them are from this team? How do you conduct an engineering interview without any engineers?"
SD: "That does not matter, I have watched enough to be able to ask your questions."
Moi: *anger intensifies* "I have to respectfully disagree. I don't feel it's appropriate to cut us out of the process of interviewing our own team members."
SD: "It is decided, we will take care of it, let us move on. Next, we need to find work for the Manasa, she doesn't have anything to do."
Moi: *sharpens baseball bat* "...shouldn't we just fire her then?"
SD: "Oh that is so mean, why would we fire her? We were thinking she might be able to do some of my project management work."
Moi: *sharpening intensifies* "You do realize it's a violation of H1-B statutes for someone to be employed in work other than what is stated on their contract, and Project Managers are specifically listed as not specialized skillsets per federal law."
SD: *ignores question* "We also need to find work for the offshore team, they don't have enough to do. Please find them work for the next period."
Moi: *checks how long the wait period is for ar-15s*
SD: "We also have a new person rolling onto our team, he comes from the xyz team, Dikshit *gestures to person we all figured was lost*. He will be handling our front end development."
Moi: *seething hatred* "WE JUST LET TWO EXCELLENT FRONT END DEVELOPERS GO. WE DO NOT NEED DIKSHIT."
SD: "Please calm down. We will be replacing the other two shortly, there is no problem."
Moi: "Have you heard nothing I've said? Did you even run this by legal and HR? Why did we let them go in the first place? Why do we even need Dikshit?!"
SD: "I said it before, please listen. There is not enough work for them. Dikshit will do front end. What is unclear?"

Note: There's not really any dramatization here. It's almost verbatim what happened. Eventually, the next project was cancelled, they incrementally rolled the rest of the local team off. They then had the cojones to express aghast anger when I notified them I would not be renewing my contract, and open hatred when I explained to them I was not a slave, and I refused to be a bag holder for the inevitable failure of a project without any chance of success. I don't really care what happened after that, they can all burn in their own little nepotistic shitshow of perpetual failure.

A group of ten top software engineers is sent to a class for aspiring managers. The teacher walks in and asks this question:"You work for a software company which develops avionics (software that controls the instruments of an airplane). One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"Nine developers raised their hands. The teacher looked at the tenth and asked, "Why would you stay on?"The tenth said, "if my team wrote the software, the plane would not get off the ground, much less crash."

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.

Ahhhhh devrant... long time no see.

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

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

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

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

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

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

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

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

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

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

I dont know what to do...

Edit: I missed you, devrant

Yesterday, the whole dev team went out to lunch and we ate a lot and we drank a lot until we all got drunk! Since we are paid for the number of hours we work, we all decided to go back to the office and work.

WE WERE DRUNK WORKING! Drunk coding ftw

Result: The server is down right now because someone fucked it up and I think i ruined my code yesterday because I wasn't really myself. The whole team was crazy as fuck. One of us just came back from Poland so we were drunk and high from all the polish chocolate we ate.

I hope they fix the server so I can check what kind of bullshit the drunken me did yesterday o.O

Company: we care about work/life balance (as long as shit gets done)

Company: we care about mental well-being (except when shit has to be done "now!")

Company: we help each other (we push work around until someone finally do it)

Company: management is here to help you do your work (as long as you don't ask them to help you to solve a real problem)

Company: we are agile (except we have more sub-processes than ever)

Company: we only hire best (and then put them in the team of morons)

Company: we are customer centric (that's why we are delivering bugged features)

Company: we constantly rise the bar (deliver more shit in shorter time)

... did I forget about something?

managers: We're all aligned! Let's work as a team and get this started!

devs: ok...

managers and devs meeting to discuss next features: * canceled by managers *

managers: (word for word, can't make this shit up) we cancelled the meeting, we will define the roadmap for everyone

> WE will define the roadmap for EVERYONE

devs: uh wtf???

one hour later, managers: guys we are defining the roadmap can we have a call to discuss?

fucking asshat, insolent, disrespectful pieces of shit

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

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

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

No overtime pay because we had salaries.

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

I used to work as an all-in-one IT guy in a company. One day I got a call from our HR team and the HR said "my Internet banking account has been hacked! It's logging in automatically!!" So I went to see the issue, and the so called "hack" was because she allowed Mozilla Firefox to save her login credentials, and because of that the login form was automatically filled. Such a stupid ass

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

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

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

One team was delivering for 12 months.

... but definition of done not met. Code crap everywhere. Tests barely there and are total mess.

I inherited mess after previous lead engineer.

I exposed all the issues to the management in a straight way, no sugar coating.

... and now guess who's the bad guy for "complaining" instead of shut up and "making it work"?

P.s.
"Giving accurate report about situation" is seen as "complaining".

These fuckface wantrapeneurs, posting jobs (paying to do so) and then offering bullshit like:
- We have no funding, so you'll work for free for some time.
- Paying in fucking crypto.
- Wanting a full stack rainbow puking and shitting unicorn for peanuts
- Fucking scammers, posing as legit companies and asking you to install Anydesk.
- Asking absurd interview tasks and times (a couple of days worth of work for a task).
- Whiteboard and live coding interviews with bullshit questions thinking they're Google, while having 20 devs.
- Negotiating salaries and when presented with contract get the salary reduced by double the amount.
- Having idiotic shit on their company websites like a fucking dog as a team member associated as happiness asshole. (One idiot even had a labrador during the video interview while cuddling him)
- Companies asking you to install tracking software with cam recording to keep you in check. (Yeah, you can go fuck yourselves)
- Having absurd compensation schemes, like pay calculation based on the "impact" your work has

Either I'm unlucky or job hunting has become something else since I last started searching.

Boss's son (who, despite being 19 and having no formal education or experience, was head of the technical team, consisting of one ops guys, one part-time web developer, and one part-time data entry/programmer) brought a cross bow to work. Just strolled in with it one day and took it back to his office, walking past all the visibly uncomfortable employees. One of the marketing ladies said to him "wow that's a bit scary" but it had no effect. He also wore a trench coat and kept a flying squirrel in a sock in his pocket.

At another place (not doing dev work) I had my manger tell me to type more slowly to get all my hours in, as I was promised 20/wk but they had about 3 hours of work for me to do. I quit after a month.

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

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

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

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

Ohhhhhh YEAH!

Wish me luck. 😎

Job interview.

Head of development: "I'm looking for the perfect php developer with perfect MySQL knowledge."

Me: "We'll ok. Good look with finding that unicorn. I think we are done here."

The problem with some people is that they are the gatekeepers for other people's careers and that they are begging to be bullshitted: "Yes of course I am the best of all php developers! And I don't only know MySQL but am pretty awesome in YourSQL as well!" As if I want to work in a team posers.

One of our internal customers to my team: "We need this new feature to be implemented as soon as possible! It's super urgent!! Work on it asap!! PEOPLE ARE DYING!!"

Us: "Ok, we'll prioritize this feature and deliver it as soon as we can"

Them: "Is it ready yet?"

Them: "Is it ready yet?"

Them: "Is it ready yet?"

Them: "Is it ready yet?"

... One month later ...

Them: "Is it ready yet?"

Us: "We're done! We implemented everything as promised! Please give us your credentials so that we can whitelist you and you can start using the new service"

Them: "Okay, we will get back to you"

... Two months have passed since then and still not a single word from them. I'm starting to wonder: are they still alive? 🤔

Hi Dev Ranter,

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

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

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

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

Looking forward to talk to you.

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

#TheCoronaEffect

Before Corona: (Work From Office)

Boss: Let's have a call.
Me: Sure, allow me some time I am assisting the team on a new feature in the app.
Boss: Ok, ping me as you get free.

----------------------------------------------------------

Now: (Work From Home)

Boss: ***Calls for the 15th time in a day...***
Me: (With Bleeding Ears) Yes sir, am here...!
(Having to pick up every single time as he knows you've got nowhere to go 'coz the whole city is in LockDown)
Boss: ***Talks for another 1 hour with screen share***

My Boss is a bigger threat to my health than Corona now!!!

#GoCoronaGo

Satoru Iwata.

You might remember it as the former president of Nintendo, but he was also a very impressive programmer. As he was president of HAL Laboratories, he helped with the development of Pokémon Stadium for the Nintendo 64 by porting the Pokémon Red/Blue battle system not by having any sort of documentation, but by reading the assembly source code.

He did so to allow Game Freak's developers (who were only a team of 4 at the time) to focus on their work on Pokémon Gold/Silver. But he did more: when they had to localize Red/Blue for America, they couldn't fit everything in a cartridge. They had the same problem while developing Gold/Silver, since cartridges had at most 8 Mb of storage capacity back then, and they had to fit not only the Johto region but the Kanto one as well! So Iwata stepped in, and created a graphics compression tool which managed to make everything fit in the cartridges.

He did this while not even being part of Nintendo, and the work was so impressive that the Pokémon devs thought it was "a waste to just have [him] as president!" (ie. why not make use of such programming skills).

Truly someone I look up to.

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

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

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

Some time ago I quit my job at a big corporation. Getting treated like a resource, a production line robot, just isn't for me.

My current job is way better. Small company, lots of freedom, getting to work on multiple projects, the result counts. But, as a small company, we also collaborate with big corporations. So I joined a team at one.

Watching my coworkers there, I'm reminded of robots again. Lunch break? 15 minutes tops. Just shovel some edibles into your face hole and back to work. Five minutes break between meetings? Open laptop, work work work. The concept of "needing rest" seems entirely foreign to them.

Yesterday our product owner "relayed some criticism" from other team members to me. Apparently, me going to the toilet in breaks is "suddenly disappearing". Or me not replying within 15 minutes in the chat is outrageous. And then he tried to berate me how I'm "his developer" and his team's tasks have top priority. So, according to the PO the problem is me and I should "get used to their mode of operation".

How about "no". I quit a fucking job because that "mode" is simply inhuman. After that feedback, you bet I'm taking my legally protected 30 minutes lunch break and any other break I can. Because fuck yourself, you're not going to burn me out. The best part, that team has smokers who "suddenly disappear" twice as much as I do, but apparently that's somehow a-ok.

I had to remind him that his project is just one of several I'm working on, so no, not "his dev". While that wasn't exactly a powerful comeback, it did shut him up. Still going to talk to my boss on Monday, at least to ensure that the PO can't talk shit about me behind my back.

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.

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

- Senior python engineer with multiple years machine learning experience.

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

- Architect for a .NET team.

- Senior UX Researcher.

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

... not much hope in this process

Once a CEO is 24*7 a CEO. For me it's Chief Experiment Officer

And only dreamers can have that title. One who dreams at night and work it out the following day.
Having a startup is much more than just having an idea
It's about revenue,
It's about value,
It's about team,
It's about impact,
It's about growth,
It's about compliance,
It's about being finance, marketing, HR and tech expert at the same time.
It's about respect the supporters,
At the end it's about the money you earn as an individual.
For playing all the above roles, you need to dream real big.

To me startup is about falling in love with your work first.

-
By an Indian CEO

Best co-worker? One of my team who was cut from the same cloth. I could ask him to do anything without giving a how-to. I could then carry on with my work knowing he would deliver on time and at least as good as I would have done. We've been mates ever since.

I'm a lead Dev on an agile team. We were just handed a fixed scope, fixed date project. On Monday, instead of helping push this out, I get to have a meeting to explain how throwing more bodies at it will slow us down.

"No! We are not code monkeys! Knowing JS and Java isn't the same as knowing our application. Stop fantasizing that it's a simple manpower issue and leave us alone so we can work these fucking nightmare timelines in peace!!"

I'm looking for a better way than that to explain it to the Sr management for the business so I don't get fired.

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.

Thanks to Devrant I've learned about rubber duck debugging. Never heard of it before! It reminds me of a story many moons ago when I worked for a certain multinational company as a business analyst. The company brought in some consultants who basically stole the work my team was already doing on a big project (a horrendous series of spreadsheets linked to data coming from the core systems) and sold it back to the company for an insane amount of money as their idea.

When they launched the new product, the team I was in was asked to test and review it. It took my colleague ten seconds to bring the whole thing to its knees and trigger a corrupt data export back into the core systems. Bearing in mind this external company somehow managed to charge tens of thousands of pounds. So what did my colleague do? Hack the system? Some kind of complicated sabotage? Nope. He typed "FISH" into one of the spreadsheet cells! Thus the FISH test was born.

That day I learned several things: it's easy to break things with a fish; the importance of validating your input; and the satisfaction of showing up the smug bastards who stole your ideas and work.

Recruiter:

... the bank purchased a 3rd party tool and hired a 3rd party development team to add some features to the tool. That external team hired their own 3rd party team, and now there are 400+ bugs in the system. Would you like to work as a test-automation lead on this project?

Me: Fuuuucck no.

Fuuuccckkkk! I just realised I made 120 commits over the past 100 hours.
It's a big thing for me as a developer and open source enthusiast because I finally understood how to work on open source projects with a team and also I've been able to give equal time to all my current projects.
Also, GitHub going green is a beautiful feeling xD

So proud of myself lol

In the last project i worked in, the product owner wouldn't treat people as people but as resources.

The problem with that is you just look at people and their work in terms of a checklist and remain blind about real humans face.

She wouldn't understand the challenges of building something with an absolutely new stack which people needed to learn from scratch and put pieces together. She wouldn't be supportive of people trying out things and fail.

One fine day I told her that I was spending too much time on meetings and i should be excluding that time from available sprint timings.. she made me open my calendar in a screenshare session with all team members. Made me go through go through every meeting invite i had on calender and ordered which ones should i be attending from then and which ones i wont. That was insulting. It broke the trust.

I decided to not work with the project. Stopped putting my heart and soul into it and eventually got out of it in a month time.

Don't put your team into a position like this ever. You have to trust them with the problems they face and try to find a solution. Scrutinizing and micro management will always kill the team.

Literally what I do 80% of the time at work.

I am the only one that:

Knows CSS properly
Knows SCSS
Understands how to set up a proper front end workflow
Etc
Etc
Fucking etc

I AM the css dude at work and I FUCKING HATE working with CSS, at the same time I take it upon myself to push through the projects because my team is shit at it and I would rather work with it than to have someone else do it and then fix their shitcode.

As a whole....i dislike design. Badly.

Today’s achievement: my phone didn’t autocorrect ‘fucking’ to ‘ducking’.

Clearly it’s as pissed off as I am about receiving shitty emails from the other team manager in my dept giving me and my team work to do and throwing us under the bus when he does jack shit all day except read BBC news and go on Facebook. On the odd occasion he does actually do work, it’s not good work, it’s riddled with bugs because he’s ‘too senior to need a code peer review’. Such a fucktard...

Oh, and the work he’s asked us to do technically sits in his team so I’ll be firing that straight back at him 😁

I’m all for being a team player and helping each other but I’m going to protect my team over helping someone. The gloves are about to come off....

We are rebuilding an internal web app our company uses and this is how the meeting went down

Me: since this is a big undertaking so we should all work on this as a team and divide the work load

Boss: I can't afford the internal costs to have you all on this * assigns the part timer to the task*

Three months later after launch

Boss: this is not at all what I expected! I want the entire team on this now! It's a top priority!

Told by Gerald Weinberg in various incarnations:

A group of ten top software engineers is sent to a class for aspiring managers. The teacher walks in and asks this question:

"You work for a software company which develops avionics (software that controls the instruments of an airplane). One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"

Nine developers raised their hands. The teacher looked at the tenth and asked, "Why would you stay on?"

The tenth said, "if my team wrote the software, the plane would not get off the ground, much less crash."

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.

Fuck my manager. >_<

I'm a fresher at a medium-sized company. Our team is relatively new and we don't have a dedicated support team for the product the team developed (before I joined the company).

So when I was allocated to the team, I was put into support, citing it as a good learning experience (and it was). But it's been a few months. And the support work got boring and uninteresting, looking at logs which don't say anything, dumps which are completely normal and most of all, dealing with unresponsive OSEs, when they claim the issue is super critical and really tricky.

Anyway, there was this tool (among other things) that had to be developed as a support tool for our product and I ended up being paired with a guy who ended up being in charge of it. We started working on it slowly, designing and implementing a framework for the tool.

This goes without saying, I love development.

4 days later, my manager says "why are you developing it? Who's gonna look at support issues?"

Fucking hell. I was hired to be a developer and you got me just decide to up and shove me into support for the next 3-6 months while others are at least enhancing our shitty ass product? And I can't even quit for another year and a half because I signed a bond!

Oh, the depression.

!rant
I recently moved all our tasks from grunt to gulp and integrated bower as the front end package manager. Also I wrote a lot of guides to set up standards and how-to for the team.
It's my 3rd month in my job and first major work. It took me more than a month to completely set it up and train everyone to use those new integrations.
Today all my seniors applauded my efforts. So much happiness 😀

I just realized something in my work place, I'm the only one beside the intern (lol) on my team who is proficient in english.

I was helping a coworker debug some issues and she couldn't understand the OBVIOUS error message telling her precisely wtf was wrong and the exact line...

I know something for sure... In our area English is basic, learn it or gtfo. I might as well conduct half the interviews in English from now on.

back to devrant, yay!

closed my account when i entered a really nice company, but after a year it was taken over by another one that was not-so-good at all, started working for another startup and, BOY, i really didn't miss ranting about work, but now i NEED a place to let this all up, little by little, somewhere, before my brain melts

current startup is one of those founded by rich dudes who had an "amazing" idea that, as time passed, turned into a monster that not only eroded the team from inside, but also made us see how spoiled the bosses are

Today I got fired (I work for a outsourcing company and was the client that "fired me") and the reason was that the work load was low.... funny thing is that they contested a new dev for my team and she is staying only because she is in the same office as the main team and I'm on a different office.

How fucked up is this?

First rant goes here...
Had an interview for post of android dev at a start-up(please note: they specified they need a full-time android dev for their team, junior role, even freshers would do). Not a single question asked from android- architecture, apps, libraries, not even anything from my resume. They thought that any person who can 'reverse a linked list on paper' can work with them, but not a dev who has a year's experience in android development.
At the end, after asking me about a dozen (quite simple) DS questions, they said they can't provide the opportunity to a fresher, and I can join as an intern for 3-6 months and 'work my way up'.
WHY THE FUCK YOU SAID YOU NEED A FULL-TIME ANDROID DEV WITHOUT MUCH EXPERIENCE? AND WHY DIDN'T YOU ASK ME RELEVANT QUESTIONS?

I recently joined a new company where work is quite different than my previous company.
Every day at work is challenging for me. There is good exposure to learn technology in depth. But time constraint to deliver module like under 3 days does not let me learn my work, also I am not satisfy with the quality of my code that I provide, it more looks like a patch. In my previous company I was favorite developer of my team but here I feel like a fresher who doesn't know from where to start.

Even I feel like my presence does not make any impact in office as I am just like an extra player of the team. I am slow at my work because I learn then I code due to which my manager does not consider me for any new work. I feel like left out in my team.

Once I overheard one of my colleague he called me helpless and were making fun of me. With every passing day I am losing my confidence.

I have no github reputation. It's like I am jack of all trades but master of none.

Every day is like big fight day in office.
I know our only way to survive in this industry is to keep on learning but in smart way. I am not sure what's that smart way?

Any advice would be helpful.

A manager who felt that it was okay to come and speak to me about something that they were unhappy with in my conduct towards a member of our team, in a public place, loud enough for others to hear.

The conduct that made the manager feel the need to do this was my response to something another team member asking me to do. I had a lot on my plate with work, and had been given at least 3 additional tasks already in that meeting and my response to having to do yet another thing for this other team member because they "hadn't any idea what to do" was simply that I was quite busy and if it wasn't high priority it could wait one week as I have 3 other higher priority tasks that week to do. This resulted in me getting a warning and in a very public place.

Shouldn't have let it get to me the way it did, but the stress I was under and the way in which it was conducted just broke me and I cried. That nearly pushed me to leave my job and industry entirely.

CTO: Research, problem analysis, customer need validations, and data based prioritisation is stupid.

Me: So, then why should we solve this problem?

CTO: Because my team invests a lot of time in here (read "because we build a shitty system in past without thinking and we are doing it again").

Me: I don't see this as a good idea.

CTO: I become emotional when I request product to align and they don't. We must solve this problem and not what customers want.

Me: I am not participating here.

CTO: And I want you to work on weekends to support my team.

Me: *disconnects*

There was this uni project where the teacher gave us a project to work as a team (the entire class, 17 people). We were meant to use Scrum, and deliver the first release in 1 week.

Turns out no one except me did the work, and this went on in the upcoming sprints, even with me telling the teacher what was going on.

Then, one day, a girl (let's call her Rose) did a commit to git, and I thought that something as going to change...She committed and push a new line at the end of a file.

After 2 months, the project was done. I had done 4k+ lines of Java EE + Hibernate + JSP code (which was very difficult to me) and the grading came out. I got a 7... most of the rest of the class got an 8 or 9. They did nothing.

When questioned by me, teacher said (it was a group project...)

TL;DR: I did the work of 17 people in a university project, got the worst grade of them all.

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 got the task to set up an NAS, because "server has too high maintenance costs".
I built two databases for this company and the big boss loved my work. (spoiler:not because my work was outstanding but because I, as a student, am cheap and willing to learn).
And now? Reality hit me for good. I looked for a enterprise worthy NAS solution, sent them the details, they bought it and now it's 00:00 in Germany and I'm sitting in the empty hall, trying to configure the storage to work like they want it. On a friday. Alone. As the only member of the IT-team. With way to much responsibility.

So... Yea, fuck you for good. I hope your backup gets an disk error at the same moment i quit. (but first gimme mah monney)

I work at a 6day work week company and this week it was 7. We work more than 10hours a day in a 7×27 foot co-working office space. My manager sits just 2foot away from me to my back. He is toxic as hell and nano(micro) manages the team. I stay very near to office and I feel like I am a dead person just living to work.

Is this a good reason to change the job after an year ? I feel lonely and negative. My manager sitting just few inches away from me makes me feel like a fish trying to behave outside water.

But the best part is I got to work on many things that helped me gain lot of tech expertise still he wanted control every piece of code.

A group of ten top software engineers is sent to a class for aspiring managers. The teacher walks in and asks this question:

"You work for a software company which develops avionics (software that controls the instruments of an airplane). One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"

Nine developers raised their hands. The teacher looked at the tenth and asked, "Why would you stay on?"

The tenth said, "if my team wrote the software, the plane would not get off the ground, much less crash."

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

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

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

Took me looooong looooong time to understand that the primary work in a managerial role involves meetings and calls as the *main* thing, not something you do sparsely to stay aligned with the team, so them calling 3 hour long meetings might feel like a waste to me but for the manager it is what they would consider proper work.

At least that's my current hypothesis in trying to justify the time that's 90% wasted.

Lots of talk about sexual equality in the dev community. Personally I work in a small team, equal mix of male and female. I can honestly say there was no bias towards hiring as I was the one who hired them all, I employed the people I work with because they were the best candidates.
Questions to you all - have you experienced bias in hiring? Have you seen 'positive discrimination' (hired because someone was female - not because they were the best person).
In the U.K. the media is saying there's a huge shortage of females in the sciences, I like to think there's a positive push to get more women into science, but what's the reality? What's you're experiences?

Just got accepted for a game developer. Ive been making games since I was 12 as hobby. Did a few months of university level of Game Development. Then started as web devloper professionally. The company I work for found a project as game dev for me.

I love my work and the sales team for finding me that job, even though its out of scope of their regular projects.

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

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

Great bosses so far...

So, we’ve a small UK based dev team, we follow good practices and get good results. But ‘they’ want to deploy quicker (it was suggested we skip the test phases...) but don’t want to invest in more staff.
So their suggestion is to outsource development to Bangladesh and have us in-house devs work on discovery and innovation.
I’m uncomfortable with this as it feels they are thinking they can get quicker and cheaper dev done abroad (which I hate as it feels disrespectful to my fellow dev brothers n’ sisters).
Also disjointed as in my experience planning and dev’ing work best when you can talk face-to-face.
Thoughts?

Serious Question/Poll

Imagine a job where instead of a worker, you're a partner. Hold on, I know that sounds markety...

Let's say instead of an employee, you're basically like a free agent. The company has a pool of projects that are approved to develop, and you can pick what project and what team to work on. More than that, you can even choose how much you want to work on it, and get paid accordingly in ownership stake of said project (on top of your base salary)

What if you were encouraged to submit your own ideas about everything, and that feedback is instantly public, before anyone (management) can water it down, take credit, or worse, suppress it entirely.

What if you could work from anywhere, home, not home, middle of the ocean, whatever.

Plus, we give you a budget to buy your own pc/mac whatever. As long as you can code on it, we don't give a shit.

Also, foosball and ping pong, beer, coffee, cool work environment and all that kind of shit too.

Paid training, for even whimsical new technology, in fact, especially so.

Want to do agile, fine, hate it? fine, just find the team and project that does what you want.

What else am I missing?

That horrible feeling that you're holding the team back as a junior dev.

What took me two days of struggle, it took the senior dev a glance to solve the issue.

Literately took them less than 10seconds to complete the task which I spent two days both at work and after work of debugging and research to try and solve.

Why are they paying me to work here.

Not an actual teacher but definitely the guy who thought me the most: @java9

@java9 is a friend of mine who started the apprenticeship with me, but had serval years more of experience than I did.

At first he helped me get through the first complex tasks.

Luckily we are in the same class at professional school, and he helped me studying a lot.

Because of him I was able to develop my skills rather quickly.

Over the years our relationship developed into a close friendship.

Now we are working together as a team on more than side project and I've learned to love his perfectionism when it comes to code.

It's a pleasure to work with you @java9

Thanks for reading fellow ranter, here is a picture of us sharing a beer as a bonus

Two of my team members were trying to make a website responsive for over an hour. They tested everything. They checked the JavaScript, checked their CSS media queries, tried everything but it just wouldn't work on mobile browsers.

So as usual they decided it was "impossible" due to "WordPress constraints" and told me that it would work on the browser but not desktop.

I just added the meta viewport tag. It literally took 10 seconds. It worked.

I hate people who give up easily. Just hate it.

IF YOU UPDATE AN ADM PLATTFORM FOR FUCKS SAKE DON'T DO THE FOLLOWING THINGS:

1. ONLY DOCUMENTATE IT IN A POWERPOINT

2. WRITE DOWN IPs AND PORTS ONLY ON A WHITE-BORD

3. MOVE TOOLS TO OTHER SUBNETS OR DOMAINS WITHOUT PROPERLY KNOWING THE WAYS OF COMMUNICATION BETWEEN THEM

4. USE YOUR PERSONAL EMAIL ADDRESS AS RESET OPTION FOR LICENCE-MANAGEMENT ACCESS IF NO ONE KNOWS THE PW

5. LEAVE THE COMPANY THE DAY AFTER THE UPGRADE IS DONE

Because the guy who has to take care of the upcoming problems is not going to like you!

BUT having to deal with all of this at once would not be a problem if your, so called team (30 People who work with those applications e.g. as test-engineers) would actually work together instead of having that "not my daily business, I am going to drink coffee" attitude.

Apparently I am the only one who has enough balls to see, admit, and report a problem to our leadership.
This always leads to Me fixing the issue...
....that's alright I am learning a lot...
...BUT IF A TEAM-MATE, WHO HAS THE SAME DEGREE AS I AM GOING TO GET, LEAVES EARY BECAUSE: "HE DOES NOT KNOW WHATS WRONG", IT TRIGGERS ME!!!

- The apprenticeship guy

PS Needless to say hundreds of clients have access to those systems and I worked through a shittload of official tool docs just to get to know the tools first...

Was invited to work on a new startup which had 2 founders and 3 devs including me.
Within 2 years, founders started fighting related to equity and stuff. Those mfs Finally dissolved the company.

We 3 became jobless but continued as a team and with the contacts we got from previous startup we started working on projects outsourced by other companies.

I was the designer, and the other one a passionate android and ios dev, last one was a pro php, node.js dev. We were super productive and fast. Worked together alot until one of us got a really good job in a company.
We still work on some crazy projects, discuss random shit, help each other with their projects whenever we meet on weekends.

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.

As a software house, we have many teams on different projects. One project was due to a Thursday, and the PM asked the team 1 week before if they could work over the weekend since there's a lot of things to do.

On the Friday before, one of the devs showed up a bit later than usual (around 10am), but ok...

After lunch he asked to talk to HR and also the boss. They talked for around 2h, then he started to say "goodbye and good luck" for everyone.

The project was on fire and he just... leave.

On the next 2 months another 4 people leave the company. All from the same team/project (but not with a big surprise like him).

Apparently, the team was constantly complaining to PM and boss about unrealistic deadlines and constant requirements changes, but they didn't did anything about it. Just when more than half this team had left the company they started to rethink this actions to this project and the others on the company.

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

How do you tolerate a colleague who

- Fails to work as a team member, is inherently lazy and writes software that is simply horrendous
- Blatantly takes the easy road and even admits to it
- Has no sense of pride in the work they do
- Is your supervisor

I see a lot of people with shitty interactions with recruiters, but I have the chance to work with one to get into what I want to do (net ops incident response) if I call this recruiter.

Backstory: friend applied for a position, got offered this morning (not going through a recruiter) AS recruiter called him for another position within same company. Friend explained situation, but said someone (me) might call recruiter to talk.

Job would increase salary by minimum of 25% and is much closer to what I want to do. Even if I'm still on call, it's a larger team and I'm interested in the stuff.

How do I not get screwed by recruiter? And am I am ass for applying when I know it's < 1 year and I'd be leaving my team down 2 people (so at half capacity)? And do I care?

I spent two days in a row fixing chairs at work because our whole dev team was waiting for issues (which means helping QA team and playtesters testing the whole game).

Just when everyone left and Im standing up to go as well a playtester comes up with a release breaking bug in the handwriting recognition code...
Since this game is build for a charity which will release it in a country at war we cant push the release date.

Guess who is making overtime trying to fix this bug?

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

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

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

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

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

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

I am not on the list.

My ENTIRE TEAM is not on the list.

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

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

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

Passionate programmer attends one of the toughest interviews ever and solves lot of algorithmic problems coding in different programming languages. Impresses the interview panel providing solutions with as much as efficiency as possible. Gets selected, completes induction and gets a nice Dev machine allocated.

Manager walks in and says we got to work with the production support team on fixing a UI bug.

First company I worked for, overall it was a good experience, but at one point they promoted a consultant to project manager, and their planning skills were about as good as their people skills, which is to say, appalling.

We had a project update for a huge client, that required, for political BS reasons, that most of the team spend several weeks on-site, 300km away from home.
Go-live was approaching, and the plan was: migration starts Friday night, shortly after midnight (so actually, Saturday) once the client’s IT confirms DB is backed up. Expected duration: 5 hours.

- So, you expect me to work from midnight to 5am on Saturday? And when do we start working on Friday?

- 9am, of course.

- 9am!? So you actually planned a 20 hour work day? (Note: legal maximum here is 10 hours in a day, 40 a week)

- And we have to be there on Saturday 1pm to recheck everything is running smooth.

wtaf were they thinking?

Working in a non-IT department makes working as a developer really painful if the whole organisation is set up to be restricted with software installs or using specific hardware etc.

For context, I work in a marketing team with literally myself and one other developer, and some other people in a completely separate organisation, physically separated. We're responsible for overhauling the website and associated sites as part of a transformation project.

Had to use my own, shitty 2013 macbook to run XAMPP because I'd have to file a software request to IT for anything remotely developer related (even trying to run Git, Node, or Python or anything is a pain because I can't actually install anything permanently or to an actual drive as it's all network accounts).

I'm not asking for equipment/access because I'm an elitist bastard, I'm doing it so I can actually do my job.

God forbid I want to use a text editor, or some kind of build tool to manage our codebase better than just cowboy coding it without using my own device for work matters.

As a junior dev I'm really frustrated at work today. My boss wanted us to complete a project within 3 weeks. The project includes a multi-tenant hotel system that includes reservation, invoicing, advanced reports, housekeeping system and an API. I'm starting to feel something about myself, I have no progress. I'm so slow. I love what I'm doing but maybe this is too much.

ps. we're a team of 2

This morning, I felt pretty good. I had a healthy breakfast and I took the longer U-bahn journey into work so as to enjoy the Autumn scenery. I get to my desk after greeting my colleagues with the customary "Guten Morgen" and I began to plan my work for the day. I see there is a new ticket assigned to me which relates to a HTML issue. The customer support team are able to use a HTML editor to made changes to a section of a user's dashboard and from time to time, I get asked to fix their mistakes. Usually, it is something small, but it makes me cringe every time I see the markup. "Tables...tables everywhere!!!", sighed the once happy dev.

Time for a coffee break and a sit-down with the support team

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

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

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

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

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

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

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

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.

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.

Fuck my company. Let the technology people work with technology.

I work at a small company who constantly brings in people who are absolutely useless. The project manager requires me to take items out of azure Dev-ops into an excel because he will not take the time to understand how a board works. The business analyst hands bullshit requirements in formats which no one but him can understand under the pretense that the Devs and architect can ask him when they feel like it. The CEO wants a power-point which again the technical teams have to prepare for him because the project manager or BA will not have time for it. However they make sure to gut the estimates handed over by the Dev team and introduce unfeasible deadlines.

Meanwhile the client has zero problems as the work still somehow gets done due to people in the Dev team overextending. Goddam leeches wasting mine and my teams time doing bullshit.

TL;DR:
JuniorDev ignores every advice, writes bad code and complains about other people not working because he does not see their result because he looks at the wrong places.

Okay, so I am really fed up right now.
We have this Junior Dev, who is now with us for circa 8 months, so ca. a year less than me. Our first job for both of us.
He is mostly doing stuff nobody in the team cares about because he is doing his own projects.

But now there's a project where we need to work with him. He got a small part and did implement that. Then parts of the main project got changed and he included stuff which was not there anymore. It was like this for weeks until someone needed to tell him to fix it.
His code is a huge mess (confirmed by senior dev and all the other people working at the project).

Another colleague and me mostly did (mostly) pair programming the past 1-2 weeks because we were fixing and improving (adding functionality) libraries which we are going to use in the project. Furthermore we discussed the overall structure and each of us built some proof-of-concept applications to check if some techniques would work like we planned it.
So in short: We did a lot of preparation to have the project cleaner and faster done in the next few weeks/months and to have our code base updated for the future. Plus there were a few things about technical problems which we need to solve which was already done in that time.
Side note: All of this was done not in the repository of the main project but of side projects, test projects and libraries.

Now it seems that this idiot complained at another coworker (in our team but another project) that we were sitting there for 2 weeks, just talking and that we made no progress in the project as we did not really commit much to the repository.
Side note: My colleague and me are talking in another language when working together and nobody else joins, as we have the same mother tongue, but we switch to the team language as soon as somebody joins, so that other colleague did not even know what we were talking about the whole day.

So, we are nearly the same level experience wise (the other colleague I work with has just one year more professional experience than me) and his work is confirmed to be a mess, ugly and totally bad structured, also not documented. Whereas our code is, at least most of it, there is always space for improvement, clean, readable and re-useable (confirmed by senior and other team members as well).
And this idiot who could implement his (far smaller part) so fast because he does not care about structure or any style convention, pattern or anything complains about us not doing our work.

I just hope, that after this project, I don't have to work with him again soon.
He is also one of those people who think that they know everything because he studied computer science (as everybody in the team, by the way). So he listens to nothing anybody explains to him, not even the senior. You have to explain everything multiple times (which is fine in general) and at some points he just says that he understood, although you can clearly see that he didn't really understand but just wants to go on coding his stuff.
So you explain him stuff and also explain why something does not work or is not a good thing, he just says "yes, okay", changes something completely different and moves on like he used to.

How do you cope with something like this?

My PM frequently asked me what I'm doing as a Programmer in my Team because he wants to understand us better - I first started out explaining him every Detail of our work - he didn't get it - I then simplified it and told him We are creating the functionality and Gameplay features - he didn't get it. I then finished our conversations with telling him what I do like that "I drink coffee and I know things" - he was satisfied and I could work on

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

I am a senior Android dev, and I have an old colleague (iOS senior dev). We work on the same project, but in every estimation session he pushes a lot on the lower side: he estimates 4h a task that normally takes 6h or 8h, and the reason is that he has no social life. Right after work he starts working again from home (I can see all his commits), he also works almost entire weekends. I would say he works as average 12/13 h per day.
I don t want to work extra time (unpayed).
About him, it is his life, so I don t care...but at the same time this makes me pressure. I care a lot about quality of code, and I don t want to sacrifice it just for catching up. Most of the people in the team know that he works a lot extra time.

How would you handle this?

I have been burnt out for over a year and a half now combined with mental health issues.

I was working an underpaying job, doing senior-dev work for a less than junior-dev pay, with an incompetent understaffed team. The work was so mundane and most of the clients were stupid. I hated work, my colleagues, and most of all I hated programming.

I finally quit the job and quit programming as well. I couldn't touch or see a terminal window without panicking. I've been spending my time binge watching series and movies.

Recently though, I've started picking up coding again. I've been blogging and doing some changes to my blog beside other light stuff.

This is the story of my first burnout and it's taken its toll on me. I hope it's the last one but who knows.

I work for a big financial company and they're saying i'm going to get a promotion but have to go through an interview process and be compared with external candidates. Basically that a new position will be created and I need to apply for it.

To me it feels like an insult as promotions should be a reward for good work done on the job?

And technically I'm like the most experienced, expert on the team...

Everyone comes to me asking for help or to explain things...

"let's use git for this game jam"

Wait! Don't go! I love git and use it on every project I work on! You'll have to hear me out here.

This was 4 years ago, at my first Global Game Jam. Every jam and game I'd worked on up to that point, I was the only Dev; no need for git, as backups were more than enough. I joined a group with high hopes for the game jam, with three coders and a proper art team.

The entire jam was "1 step forward 2 steps back", as git somehow constantly overwrote code as fast as we could write it.

By the end of the jam we barely had anything to show for our hard work. The takeaway isn't even about git. It's simply to never work with other people. Git is a great protocol but it can't stop people from accidentally fucking other people over. Every jam since, I've worked on my own and had a far better time of it.

I got recognized!

I'm new here and was mostly learning, but my team pushed through some bad issues and I got recognized as well. Even for helping whatever little I could.

For all the rants of bad bosses and clients and work. Here's a happy one. :)

I'm in good company in this company.

I fucking hate people who report somebody else's work as their own successes so much.

I've written a fair amount of perf tests for our project so far (actually I'm like the only person doing that). Some fucker from another team asks me if I could write one more. I agree, because why not. I spend a few hours, making sure to cover all cases and commit the test. Then the same fucker runs it and reports it as HIS PERFORMANCE MEASUREMENTS.

0 credit given to me. Fuck you, I just wanted to be helpful and you used this.

I'm still quite young and tend to fall for shit like this, but getting more and more grumpy because of those people.

I used to work at a printing company as their only developer. I was often pulled from doing any development work, and instead would be printing documents, posters and postcards. One time I was printing and developing at the same time for a 12 hr shift. I fucked up over 30 thousand printed pieces of double sided postcards, where the front and back didn't align properly. So it was impossible for the guys to cut them. I left the job about 2 weeks later, and found myself a job that's doing only development, and was working as part of a team of very talented developers. I still have a good relationship going with my past employer though, despite that incident. My supervisors were very nice people.

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

A group of ten top software engineers is sent to a class for aspiring managers.

The teacher walks in and asks this question:"You work for a software company which develops avionics (software that controls the instruments of an airplane).

One day you are taking a business trip. As you get on the plane you see a plaque that says this plane is using a beta of the software your team developed. Who would get off?"Nine developers raised their hands.

The teacher looked at the tenth and asked, "Why would you stay on?

"The tenth said, "if my team wrote the software, the plane would not get off the ground

Back where I used to work, we had this a-hole call center guy who isn't a programmer but got promoted as our team leader. He said he used to program on his early days at the company (?) . He claims that made back-ups of his source code in MS Word and even tries to gives us a lecture about backing up programs.
I really hate those a-wipes who often get promoted and suddenly goes up to their heads

Was on my first internship, told to analyse and prepare stuff for the Android dev to build an application for a big client. Did it before the end of the internship and team was satisfied with my job.

Because the Android dev had already lot of works on other stuff they let me start the development of the app.

The end of my internship is coming, the app is not finished but the team agreed that my work is not bad and that I should continue to work on it.

I finally get hired to finish the app, when we first publish it 95% of the code was mine and the boss started to stress because he let an intern (that became an employee) build the application from the ground. But the application got quickly its 4.5 stars on the playstore and more than 10.000 downloads.

I quit the job a few time after the publication of the app but I feel proud and happy that this team let me work on one of the biggest project they had as I was only an intern without any professional experience.

This is not "badass" but this is my first and best experience in the professional world !

What is it with inabhorrent arrogance plastered all over IT as a whole?

I get younger, inexperienced people telling me I'm wrong constantly, criticising my work despite them having no clue (visible from their own work standard and TTL of their projects) .
Similar from older generation, who are resistant to change and aren't even part of my team telling me I'm doing my job badly.

Real story :

There's this one colleague, who was a very good friend of mine. Always helped me in everything. That one friend in the team, who shares a lot of stuff with you.

And she suddenly, turns offensive when it comes to professional things and mainly competitive stuff in the team.
She becomes a completely different person when I get recognition for something in the team or when I become popular in the team.

She has that feeling that she should always stay in the lime light.
When I steal the show by doing something good, she starts to show faces.
Decided that it is a unhealthy friendship, as the friend i knew is no longer a friend when it comes into professional behavior at work,
And it started reflecting a lot in our personal friendship, outside work too.

Decided to cut the friendship and only be colleagues.

Did the same happen to someone else? Did you lose a friend because of things like this?

Haven't ranted in a while so here it goes.

Head of product took me (senior dev) to a high value client workshop/demo session and over the course of two days found the reason behind why the dev team has been pushed to the limit as of late and sales/product team has been making promises to clients without checking with dev leaders on reasonable delivery dates on massive new features.

I tried my best to manage expectations by differing talking about delivery dates by saying "lets discuss that with the team" rather than giving out dates right now. But as soon as the meeting ends he sends an email to the client confirming delivery dates on features that we have done no research on or even specialize in!

Please tell me this is not how well established businesses work or is that the new reality of things. In either case I wanna find a new job :/

Several years ago I joined the company I currently work for, as a software support person, with the intention of eventually moving toward the development team.

After a few years doing that, I gradually realised that working in the development team for our products didn't seem that appealing after all, so I went for a more technical support role (essentially debugging all the really complicated problems and reporting the bugs to the devs) which I find fascinating - trying to solve these puzzles is an interesting challenge. It can take days, sometimes weeks to get to the bottom of something really inexplicably weird.

As part of this I get to do some internal dev work on the teams projects (nothing that gets used directly by external users though) and have learned loads of things from my boss over the years (even before I joined this team).

It has its frustrating moments of course but I am definitely glad I didn't follow my original intentions of just being a developer on our main products.

Sometimes what you think you want isn't actually what's ideal for you :)

I was employed as a Researcher so for three months i basically did nothing but read, document, read, document, read, document. Then one day in a review i was doing a demo that required sql. Three months no coding. Of course I've forgotten. And now, this ass back boss of mine gets surprised because i asked for help on update syntax for sql?!?! Like, come on. I COULD GOOGLE THAT. No big deal. But it was to him. He thought i was incompetent as a software engineer. So hE DECIDED TO JUST RANDOMLY PUT ME IN A DEV TEAM and i was expected to perform as fAst AS THEM while still doing mountains of task on research. Worst part is THEY EVALUATED ME BASED ON THAT PERFORMANCE. AFTER I WORK MY ASS OFF FOR THREE MONTHS AS A RESEARCHER, I GET EVALUATED BADLY BECAUSE I DIDNT MEMORIZE THE UPDATE SYNTAX NGNGNNGGNGNNGNGGNF

Figured I'd post for some advice here and see if anybody has had previous experience or success with a situation like this.

My team is generally comprised of full-stack developers completing front-end custom work on sites, writing back-end tools, and fixing broken sites. We are a rapid-response DEV team, and we typically turn around any custom requests in less than 5 days and fix any broken sites on the same day as they were reported. We manage almost 15,000 sites across multiple countries, and deal with very large corporations that many of you interact with every day (I'm trying to be cryptic here hahaha.) There are 16 of us on our team, and we are the only DEV team within our department of 500+ people. We are also the only DEV team taking requests from these 500+ people. The way the department works, we are the final say on whether a specific piece of custom work will get completed or not, and we are the go-to people when anybody has a question about our system infrastructure or if our system can accommodate a request, along with how to fix any broken pieces of our platform. We typically get about 150 requests per day. Lately, the entire team has become unhappy with our compensation for the work we do. We're quite underpaid, and they keep giving us more responsibilities without any sort of extra compensation. We've discovered that there are a large amount of non-developers below us that are getting paid more than we are. We've found that we get paid about $15,000 less than a comparable DEV team in a different department (let's call that team DEV_2,) just because of which department our team exists within, and how our department defined our job back when this position was created a few years ago. Ever since the position was created, our team's responsibilities have exponentially increased. We believe that there is absolutely no reason that an entry-level position below us should get paid just as much, or even more in some cases, than a developer. Of course, we're not asking to pay them less. Instead, we've decided that we're going to bring this up with our manager and schedule a meeting with him, our Department Director, and Human Resources, and voice that we believe that we should be on the same payscale as the comparable DEV_2 in the other department.

To be a good developer on our team, you need to not only have coding expertise, but also an encyclopedic knowledge of what you can do within our platform without any coding. You need this knowledge so you can pass it along to any people in positions below you, in case they didn't know that something could be done without custom code.

We're going to argue that if it weren't for our team, the company would be losing millions of dollars in clients, because people wouldn't have anybody to go to for platform infrastructure questions, broken websites, or custom work. Instead, they would need to send these requests to the DEV_2 team, which currently take about 6 months to turnaround requests. Like I said, we are a rapid-response DEV team, and these particular clients think that a 5 day turnaround time is ridiculous. If they had to wait 6 months for their request to be completed, they would cancel their contracts.

Not to mention the general loss of knowledge if the members of our team went to a different department, which would be catastrophic for our current department. Believe me, this department could not function without this DEV team. If we all went on vacation for a week, the place would be on fire by the time we got back, and many clients would be lost.

Do any of you have any experience with a situation like this, and if so, how did it turn out? Thank you!

So I handed in my official resignation last week as I will be changing to a new job next month. So one of the last big things that I have been working on is a Jenkins server for the rest of the team to use and currently writing up the documentation for it.

However I haven't been told who I will be handing over my work to, but the bigger thing I feel is that even if I write all the documentation, no one will actually read it. Reason I think this is because I doubt anyone else in the team will even use the Jenkins server. The major issues are that no one writes unit tests and don't even understand what CI is!

So right now it feels like my final month of work will all be for nothing and makes me wonder if I should even bother writing documentation, especially if it isn't going to be handed over to anyone.

The company that I work for has recently recruited a team for Web Development, so they don't have to pay a monthly fee to the previous team who designed their website.

They have over 3000+ products in the old website, and no logical way to import them to the new website. The old team was asking for 300$ to give them an API which would return the product details in an XML format.

Obviously, paying that amount of money wasn't logical for a dying website, so the manager decided to hire someone to manually copy the content from the old admin panel to the new one, that is until I stopped him.

My solution? Write a simple web scraper to login to the old panel and collect data. Boom! 300$ saved from going to waste.

Now, the old team found about this and as much as my manager was happy, they were quite angry. So they implanted a Google reCaptcha to prevent my bot from scraping the old panel.

I spent about 20 minutes, and found out once you're logged in to the old panel, the session is saved in a cookie and you are no longer greeted by a Captcha.

So I re-written a small portion of my bot, and Boom! Instant karma from manager. We finished publishing the new site, and notified the old team, only to see the precious look on their face. Poor guy, he thought I was a wizard or something 😂😂

That's what you get for overcharging people!

TL;DR: Company's old website team wanted to overcharge us writing an API to fetch 3000+ records.
Written a basic web scraper to do the same job in less than an hour.

I'm quitting my current job. I don't like my lead, and he doesn't like me either. Our team consists of two people. Me as a Junior Developer, and a dude as my senior.

Our company used 3 different organization chat in Lark.
1 for global developer team, 1 for local developer team, and the other for the operational team.

Countdown 3 weeks before my resignation, I got removed from the global chat room. 1 week later suspended from the operational chat room. The interesting thing is that, my senior teammate who resigned the same date as me does not receive the same treatment.

I still have tasks to do and it is hard to work with teammates who are not in the same organization chat. I also need to work on my benefits which require chats with the operational team.

I already asked HR and they took their sweet time to respond. Approximately 2 weeks after I privately messaged them. How responsive 😧 Even then their answer was vague and I didn't get the what I questioned for.

I'm kinda annoyed by this. No communication, no announcement. This company is just straight up shitty.

Have you ever argue with a developer who:
+ have the same level as you
+ on the same position in the company
+ in the same team
+ OLDER than you
+ thinks their code is the best

A few years back, a coworker and I argue about how to implement a feature. I proposed an approach. He proposed a different one. I immediately saw some problems and told him. But hell no, he defended his idea so strongly that I just gave up since I will leave the company soon.

2 weeks later, when the sprint was about to end, the whole team had to work overtime to fix the mess because of his terrible approach.

If I ever get the chance to start my own company or pick out the dev team I work with... I will never, ever, ever work with anyone who doesn't understand how to abstract out a problem. Our prod DB is a mess and our API is a mess because we left it to some dudes who are dumb as shit and doing everything ad-hoc. Now their ad-hoc shit doesn't work anymore and I get to clean it up. 😫😞FML

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

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

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

In "Sprint Planning", the team is supposed to come up with stories, break those down into tasks, estimate those tasks as a team, then let devs choose what tasks they want to work on based on the stories pulled into that particular sprint.

Instead, our manager creates the stories. He assigns the stories to each developer and then has that developer announce his theoretical tasks (without any research on feature's or project's requirements!) in front of the entire team. So, when I say, "I think it will take me 6 hours to implement this feature", he says, "6 hours? I think it will take 3." and then types the estimate as 3. I have so much rage when that happens. Then we continue to sit in the room for 2.5 hours where we go through this long data entry mess of him typing out tasks and second guessing estimates. There is no team deliberation or collaboration, its whatever the manager says.

While there are many issues I take with this approach, my pet peeve would be the second guessing of the estimates. It would make sense for teams members to second guess estimates as long as they are the same teammates who have the ability and possibility to take on the tasks themselves.

But I disagree with a manager seconding guessing an implementation feature that "I" definitely have to do alone, and they do not possess the immediate knowledge to implement it themselves.

Weeeell…

I have been in a team where every week they had this long and complex task of refactoring everything and changing lots of assets (~2 days of work every 2 weeks) cause the senior tards refused to use a script for it. Told them to use the goddamn backend or a script… the answer? “But that would take at least two days of work! Maybe even three! (As a one time job)” Math you ducking ducks! The second time you use it you are in a time profit!

Last week I got told by an incoming CTO, a week old to the organisation, that I'm good for nothing and unable to produce any work. He told me that he'll replace me and put me in a team where I'm more resourceful as I have been consistently underperforming. (He doesn't understand data science yet fyi) Then, he informed he's hiring 5 new teams members.

Me (junior data scientist) being really passionate about work was shook to hear this. So much so that it took me a week to even recover from it. I have considered counselling sessions too.

Week later, 5 new team members decide to flip his offer and not join. Another existing senior member decides to leave as well. Meanwhile, major issues in existing systems emerge and only I could solve the same. Still haven't heard back any from him though.

Is this the industry standard though ? Is this how CTOs normally function ? Throwing shit at people without knowing their value or valuing their efforts ? Especially with junior developers. It's only been 2 years in this profession and I've not met more than 3 genuine and helpful people. Maybe it's just my organization.

Best:

Leaving my work in the soul crushing dog eat dog world of transportation and logistics for higher education software for colleges and universities .
I work at a college and I fucking love it and love my team.

Worst:

The soulc crushing dog eat dog world of transportation and logistics where I worked as a backend developer and lead mobile developer. Not only did it made me hate and despise native android development, but it also made me despise the human race as a whole. Watching a motherfucker letting go of employees that he knew personally (as in bbq with their families and shit) because my software automated a large portion of their work(it was meant to make it easier for them for that i was originally told) was absolute and total bullshit and i still carry that fucking remorse with me. After that I vowed never to do that sort of bullshit work again....sort off. No one gets fired at this institition for it. Logistics sucks big monkey dick and the people there are the absolute fucking worst. Every single motherfucker i met was a fucking shark, all of them and they would not think about fucking people over if it saved them some money.

Yeah, that even tops the military and that was fuuuull of fuck fuck games and other similar fuckery.

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?

Client : you are hired as a developer.

Me : we need more developers as there's more work and less time.

Client : Ok, here's another dev

(Meanwhile me doing my work...)

ON THE DAY OF DEMO :

Me : Here's the demo.

Client: it's incomplete, where's more work?

Me: that's the part of 2nd dev you hired before

Client : I don't care, I fucking need a work!

Me inside: (Why the fuck would the first dev becomes a task/team manager just because is the first one to join the project! Arrrgh!!! Hire a fucking scrum master to manage your fucking tasks/team, am just a fucking dev! )

Currently developing an app with React Native for work. It started as a "would be nice to have" feature but now people wanna join my dev team and company wants to see results too. And I am just a student trainee. FeelsGoodMan

As a person from low-paying country, how do I reconcile with the fact that for the same work, and the same 8 hours, I get 1/3 of what a person in Germany does? In my previous team (same company), one of my teammates was from Germany. The same team, the same work, but he happened to earn a lot more.

This bothers me a lot sometimes. I have seen people requesting to be transferred to another country, and being denied, presumably because of the salary difference. Then, the person leaves, and someone in Australia gets hired. So, rather than moving a veteran person of whom you know fits your company culture to a higher-paying country, you let him go and hire a newbie in an equally-expensive country? What the fuckity fuck?

And to my friends from high-paying countries, especially managers: you don't have to feel bad, but have some common decency. If you come to my country, do not say "oh gosh, everything here is so cheap," or "the dinner for the whole team costs less than buying my family of four a dinner back home." That's offensive as fuck. If that's the case, fucking give me a raise you cheap fuck!

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

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

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

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

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

Ok so we have 2 useless remote contractors in our team who got hired as seniors but actually are juniors. They take weeks to deliver most basic things and never ask for help or offer help for others. They take days to fix most basic comments after review.

Today our teamlead in a call said that it's a cultural difference, these guys dont ask for help because they are very independent.

MOTHERFUCKER, I WOULD BET MY SALARY THAT THESE IDIOTS DONT WORK EVEN 10 HOURS A WEEK.

I was doing more than them when I was a mere junior.

!Rant But this is hilarious 😂

Appraisal interview of Gayle:

Gayle:- Sir, I scored 211 Runs in 118 Balls. I made the team win the crucial match. I should get “A” rating.

Management:- You hit 17 Sixes and 23 Fours. Though, that is good but that is not something new you have done. That is why we hired you. As this is not something new, I will mark it as “Innovation Lacking”.

Gayle:- But sir, I played according to the situation. I took 21 singles as well.

Management:- Exactly, your performance is not consistent. You played 15 Dot Balls as well. This means, you failed to optimize the resources.

Gayle:- But…

Management:- Also, I would like to mention that you are not a team player. The whole team scored 112 and you all alone made 211.

Gayle:- What??

Management:- Yes. So, overall, you are getting a “C” rating for the year. Improve Consistency, Innovation, Utilization and Team Work...

I have to make a big decision about my future as a developer...
(Long rant)

I am currently in an apprenticeship as a dev.
The thing is i was forced to do testautomatization.

I was there for half a year and had a good time.
But now my trainer (the guy who assigned me all the work and showed me all the stuff I learned) has been fired.

And now it sucks... they don't teach me new things anymore and don't give me time to catch up with the new technologies.
(This was different in the past!)

I was forced to do manual testing for the past few week.
Therefor i am working with a friend and his trainer.

One day i was talking to my friend about how things have changed in the testing-team.

His trainer was listening (we did not know) and sayed: If you want i can ask my boss if it is possible that i can teach you as well.

Now the point is i woud love to work with him. I love the work they do!! (Java; don't hate me)

But it will make the testing guys mad and I dont know how HR will react.

I am pretty sure it will reduce my chances of getting a job (at this company) if I change the team...

Should I talk to HR or not? What do you think?

Thanks for reading and sorry for my english bugs.

This is long rant/story:

My manager conducts sync-up meetings regularly. The idea is to sync up all developers on current state of work. He does’t conduct stand-ups. He doesn't have time for it. He rather discusses on individual basis if we are blocked. The rule of the sync-up meeting is NOT to discuss any blockers or problems but simply explain each other what we are doing and how we plan next.

Sometime ago, the manager brought up and explained a new way of working in the sync-up meeting. At this point, a new developer in the team was absent due to sickness.

Today, there was a sync-up meeting and the manager started to question the new member about the newly introduced way of working. He was unaware of it and the manager never communicated this important information via email or any mode of communication available.

So, the conversation goes on as follows:

"Manager": — "Why didn’t you complete your task as per the new way of working?"
"Employee": — "Well, I've no idea. Am I supposed to do? I’ve been working as usual like any other"

"Manager": — "We have a new process and you have failed to follow it, so we’re late in delivering your work"
"Employee": — "I’ve already finished my work on time. I've raised a pull-request this morning"

"Manager": — "It doesn’t matter, it is not merged to main branch and so we can’t include your work in the release"
"Employee": — "I’ve no idea about the new process"

"Manager": — "Haven’t you asked around about what happened from previous meeting"
"Employee": — "Yes, I have. I was told which tasks were handled, but nothing about a new process"

"Manager": — "Aren’t you interested to learn it?"
"Employee": — "Why won’t I be interested? I was on a sick leave and I have no clue what happened here"

"Manager": — "What’s happened is past now, let’s not focus on it"
"Employee": — <Dumbfounded>
The Employee felt ashamed in front of everyone. He did his job but it didn’t pay off.

…. After an hour … the Employee had a talk with the Manager

"Employee": — "You shouldn’t have pointed me out in front of everyone. It made me feel real bad. You should have emailed this information if its important for the team."
"Manager": — "I have no idea what you’re talking about. When did I say so? I think you’ve a bright future in the team. You should be focusing on doing better things."

Employee goes back to work. A minute later, the Manager sends a PowerPoint screenshot of the process in the group chat.

**The Process**
It's about delivering release packages based on priorities defined by client. Each release package is a set of work items or requirements. Individual developers are assigned to work items. They are expected to deliver on planned delivery timelines in order to consider a work item into a release package.

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

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

Question about burnout here!

I've been a developer for a year and a half now and I've reached a point of burnout. Experiencing a lot of external stress as well as internal (handled well with a fantastic and supportive team)

I'm taking some time away from work and having a much needed break but I'm worried that for now, I can't code! I've got no drive at all to learn anything new, I'm just sat here waiting for a production push.

I'm by no means thinking of changing careers or leaving my current role and the lack of concentration is likely as a result of stress, I just wanted to hear some of your stories so I feel a little less alienated!

Being new to this is pretty overwhelming at times!

I recently have been delegated the responsibility of managing a 4 people team by planning the sprints, scheduling tasks, and in general "take charge" (as said by the boss).

What bothers me is there is this "developer" with a heavily toxic attitude, who feels he is above all laws and knows everything just because he joined some months ago all of us.

He is basically a human linter. When he code reviews, you can get away with any major mistake if your linting and indentation (and all that shit) is according to "his standards".

A new guy recently joined the team and was given an overwhelming task by the boss just to test whether he belongs here. (Again, wrong, in my opinion). He didn't know any of the technologies he needs to work on to complete that task but he still learnt them and got a working product. Albeit not according to our God's "standards".

Cut to the chase, the asshole dev is now mocking him in PR comments and demeaning him in every discussion. As a "team lead", what should I do? If I let it go, it'll make the environment toxic and I don't want him to get away with it. If I do take any action, I don't want to be seen as as pussy who can't take such minor insults. Please advise.

PS. The asshole developer once wrote a "friend request accept" API endpoint in such a way that when any single person accepts a request, that'll cause all pending requests (from any person to any person) get accepted. Fucked up the DB queries basically. This is just to give a perspective on what I'm dealing with here.

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

So, I departed for a month long Erasmus in Portugal and got to work for an education related business. From day 1, all my tasks consisted in transcribing data from paper to excel sheets, and then using that data for various different tasks. It became obvious that I wouldn't have had much programming to do by default, so I started creating a series of Python scripts to automate part of my work or aid me in some bothersome areas of it, and what at first seemed a grueling series of boring and repetitive work soon actually became fun. From this point on I challenged myself to make the scripts better and better under as many aspects as possible. I eventually ended up concluding all my daily tasks in a matter of 15 to 30 minutes everyday, as that's the time it took to adapt the scripts to the new document formats of the day :P Jokes aside, this truly proves a point though: small businesses like this one, that very much depend on manual labor for tasks that can easily be automated by 50 lines of code, truly would benefit from a prepared IT and development team, and it shocked me to see how little these guys know, and are even afraid at times, about innovative techniques to speed up work substantially. Truly a great and humbling experience for very young devs like me :)

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

Not a rant but as an intern that is older than several of the members of the team I'm assigned to, including my mentor, it was still nice to be complemented on my ability to find workable solutions on my own rather than running for help whenever there is a problem.

I thought it was rather weird to be complemented on this but apparently how I work isn't always the norm.

!(isRant(thisPost));

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

God I hate when dev work gets all political.
Our team had a technical meeting with a difficult partner/customer, that wants to connect to our internal service, so we are writing an Integration Service for this.
Apparently the project is very important on both sides and highly political so in the meeting there was a member of the Board of directors of them. We just wanted to check one feature to verify they can connect, etc.
After some minor bugs showed up, that guy goes on ranting about how this is all a joke ("Verarschung" literally) and how we did not deliver all features yet as promised (Note : that was not promised) and basically indirectly personally attacked us, our company and our team.

It's incredible how such assholes can stay in such positions.

Guys, serious question.

I work in a startup as a cto. We have a very low budget and considering hiring people offshore.

Does anyone have some experience in hiring and piloting a remote team? Would you recommend it?

I work on a team project for a test and maintenance course in University. We agreed as a team to adopt a git infrastructure that would prioritize the stability of the master branch at all cost by only updating commits up to the next stable point and tagging every single release. We have a long polling development branch to prepare our releases and we create feature branches for the tickets we need to resolve. I even wrote documentation to make sure that we don't forget and protected the master branch on gitlab from direct modifications.

Can someone fucking tell me how one of my teammates managed to fuck over all of this and work on an unfinished feature straight on master?

N.b. I know that he probably edited straight from gitlab's online text editor because they have a big where they don't restrict modifications on protected branches.

The longer I work on front-end the more controversial my opinions become:

- Styling a button with display:flex is dumb.
- The DOM is not hard, unlike what the React team wants to have you believe.
- Specifying a <form> action matters, even if it's empty
- ES5 was the real JS revolution, ES6 mostly sugar-coated marketing
- Disciplined BEM (S)CSS is simple and flexible enough for most needs (vs CSS-in-JS, CSS modules)
- If editor support for Jsdoc were as advanced as Typescript, you wouldn't need the latter.
- There are cases where using floats and inline-block displays is better than the flex CSS box model

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

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

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

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.

Soo highlight. I’m a Tech Lead dev, and I happened to have had a gunshot injury in 2021 Dec, and kinda suffered some hectic stuff but long story short, I went through a full year from recovery and blah blah, but anyways after that year when I went back to work my boss(former), asked I go for psychological tests etc, then after that I passed everything as normal but then soon as I went back to work my boss took me to HR for some special performance review process that could mean I get fired or put back in the team again. My question is it this a fair trial when I never got another chance to work again as I was hired??? I need help pls :(

I really hate slow developers

No scrap that I hate developers who claim they have experience and knowledge but are so slow and can’t grip the basics.

Surely if you’re are experienced you should be able to work independently and not have someone hold your hand the entire time.

We will never get things done we are a small team as it is you gotta pull your weight man

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 work at a company that sees front end developers as, basically, lab rats. I make less than my coworkers, who are all underpaid, and also turn out more clean code (based on mutual agreement, plus the only person who documents anything) than the rest of the team, and at much higher quantities.

Why? Because I get my ass handed to me by depression and anxiety every morning, and end up coming in ~1 hour late everyday. (For nearly a year now, even with medical intervention)

I'm probably going to be fired for it fairly soon, as well as get swallowed in medical bills.

On the bright side, I finally fixed a bug with my portfolio website that I've been working on, so I've got that going for me which is nice.

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?

"In a sentence: Technically brilliant, delightful to work with, combined with a self-awareness and strong desire to improve. We also want to make sure everyone is highly supportive of each other; we win as a team."

In short: you're looking for a unicorn, which your company won't be.

Guy really said he wants the charisma of Steve Jobs and the technical genius of Wozniak...

are people really this stupid?

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.

Best:
Got a role change to automation engineer, which is sort of a 'just fix problems' position, like with tooling, get rid of manual work, remove as many spreadsheet as we can.
I started looking into rust.

Worst:
People think we depend heavily in javascript because our products are extensions, our golden product is an extension, so a few members of my team insist in depending in our core team and use their javascript stuff, even for string parsing, even if we do have a python package that does rhe same thing that is officially maintained too.
I refuse.

The good again:
My boss let's me refuse, I am not forced into javascript, they let me use whatever I want as long as it is reasonable.

As a developer, I WAS love with the concept of WFH. Thankfully, my office has no fixed hours (except for meetings!) and I can work at my pace peacefully. But lately, with WFH becoming mandatory, I can't seem to find time for myself!

Here's what my schedule looks like:
a. Start working at 10am
b. Standup at 11:30am
c. Lunch break at 2am
d. End work at 7pm.

A fairly simple routine but not sure why my team finds it completely normal to call me in off hours and moreover expect me to jump in a call too! I wish it was a 1-day affair. But no. It's a 24x7 day affair. Yes, let that sink in. 24x7.

How I wish there was no COVID and thus no lockdown. At least, people respected the work timings then !

At work, how often do you create your own apps? As opposed to adding a new feature to an existing one?

I am thinking maybe the biggest difference between me and everyone else on my team is because I have a lot more experience creating my own apps.

So when I get a problem I tend to start by thinking how to create a new app for it, what would be the ideal way to solve the problem. And then if needed, figure out how to integrate it into an existing project.

Whereas everyone else thinks about how to solve a problem within the context (and constraints) of an existing app.

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.

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!

I did a communication and multimedia design study because I was convinced I already knew almost anything.

Ooh the beauty of youth.

But it did help me in the long run, communication with clients and being able to present work with some decent looking presentation and mockups gets the managers all horney as teenagers on springbreak.

Pretty sure thats why I beat some competitors on big projects while their technical skill and team where much better.

One of my bad dev habits is that I tend to take up too much work because a lot of devs I had to work with seemed not competent enough. It's a bad habit because I get way overworked which influences code quality and deadlines.

I have to learn to trust more in others and give up some responsibility... it's hard though.
I think a big influence on my mindset has been that I never worked in a team bigger than 4 developers and I had way more experience in web dev than the others.
I sometimes may appear as an arrogant prick, but it's not intentional.

Due to resource scarcity, my manager Bob had lent me to other manager John. I started working on John's project and now there is a hardcore dependency on me, as I have done good enough work on it. I was also taking some small work items from Bob parallely so I can be up-to-date with my own team, Later Bob calls me and says he wants me back, since my own team has lot of pending tasks. John's project is still unfinished and will take longer then ever. So far, I am dividing my time between the two teams.

My concern is if I pass on John's project, will I even get recognized for it and since John will have no one concrete to work on his project, he will later keep bugging me for help.

And I feel like I don't belong to either of the teams (I am like a step son to both my parents) 😔

First year of college. We had to write a program in assembly to let lights go on and off slowly but I couldn't get it to work and googled the shit out of it trying to get it to work to no avail. So I go to the teacher as I expected him to have a bit more documentation/knowledge on how the shit worked. He literally said oh let me google that for you. Which made me go 🤦‍♂️. In the end I never figured out how to get the lights on or off but luckily my team mates did a good enough job to get us passed in the class.

My manager has sucked the soul out of me. I feel drained, anxious , highly demotivated and I have lost hope in life. He has a toxic way of managing people. The team is always micromanaged and even in that he keeps scolding people for not completing tasks in the timeline which he thinks is right. I am always filled with multiple tasks on my board and he wants me to complete all of it in one day irrespective of complexity. We have a standup that is scheduled for 30 minutes but goes on for 1 hour 30 minutes and all he does in that meeting is tell people they have not done enough even while we have done far above our levels. And there is a meeting again in the evening to update on the tasks where he again starts scolding everybody. Few of my teammates say that whatever we do we will get scolded. We have never really celebrated any success as a team. He expects the team to be always available like 24*7 and work for atleast 14 hours a day and sometimes overnight for like more than 20 hours a day. And we have alternating 6 days work week even when ceo has approved 5day work week for tech. My manager doesn't treat anybody as humans , we are all just machines to drive his deliverables. He values only deliverables. It's very difficult to get holidays. But the problem is he has inflated my salary a lot and I have un-vested esops which is holding me back at the company.

I hate it when managers and team members don't utilise JIRA as the one source of truth.

When you move your card into the Review column, set the assignee to `unassigned` so that people know to pick it up. It's so much easier to understand the state of it !

"But then we don't know who's worked on it" - is NOT a valid reason to leave the original author as the assignee. It just leads to work not being reviewed.

This started as an update to my cover story for my Linked In profile, but as I got into a groove writing it, it turned into something more, but I’m not really sure what exactly. It maybe gets a little preachy towards the end so I’m not sure if I want to use it on LI but I figure it might be appreciated here:

In my IT career of nearly 20 years, I have worked on a very wide range of projects. I have worked on everything from mobile apps (both Adroid and iOS) to eCommerce to document management to CMS. I have such a broad technical background that if I am unfamiliar with any technology, there is a very good chance I can pick it up and run with it in a very short timespan.

If you think of the value that team members add to the team as a whole in mathematical terms, you have adders and you have subtractors. I am neither. I am a multiplier. I enjoy coaching, leading and architecture, but I don’t ever want to get out of the code entirely.

For the last 9 years, I have functioned as a technical team lead on a variety of highly successful and highly productive teams. As far as team leads go, I tend to be a bit more hands on. Generally, I manage to actively develop code about 25% of the time to keep my skills sharp and have a clear understanding of my team’s codebase.

Beyond that I also like to review as much of the code coming into the codebase as practical. I do this for 3 reasons. I do this because as a team lead, I am ultimately the one responsible for the quality and stability of the codebase. This also allows me to keep a finger on the pulse of the team, so that I have a better idea of who is struggling and who is outperforming. Finally, I recognize that my way may not necessarily be the best way to do something and I am perfectly willing to admit the same. I have learned just as much if not more by reviewing the work of others than having someone else review my own.

It has been said that if you find a job you love, you’ll never work a day in your life. This describes my relationship with software development perfectly. I have known that I would be writing software in some capacity for a living since I wrote my first “hello world” program in BASIC in the third grade.

I don’t like the term programmer because it has a sense of impersonality to it. I tolerate the title Software Developer, because it’s the industry standard. Personally, I prefer Software Craftsman to any other current vernacular for those that sling code for a living.

All too often is our work compiled into binary form, both literally and figuratively. Our users take for granted the fact that an app “just works”, without thinking about the proper use of layers of abstraction and separation of concerns, Gang of Four design patterns or why an abstract class was used instead of an interface. Take a look at any mediocre app’s review distribution in the App Store. You will inevitably see an inverse bell curve. Lot’s of 4’s and 5’s and lots of (but hopefully not as many) 1’s and not much in the middle. This leads one to believe that even given the subjective nature of a 5 star scale, users still look at things in terms of either “this app works for me” or “this one doesn’t”. It’s all still 1’s and 0’s.

Even as a contributor to many open source projects myself, I’ll be the first to admit that have never sat down and cracked open the Spring Framework to truly appreciate the work that has been poured into it. Yet, when I’m in backend mode, I’m working with Spring nearly every single day.

The moniker Software Craftsman helps to convey the fact that I put my heart and soul into every line of code that I or a member of my team write. An API contract isn’t just well designed or not. Some are better designed than others. Some are better documented than others. Despite the fact that the end result of our work is literally just a bunch of 1’s and 0’s, computer science is not an exact science at all. Anyone who has ever taken 200 lines of Java code and reduced it to less than 50 lines of reactive Kotlin, anyone who has ever hit that Utopia of 100% unit test coverage in a class, or anyone who can actually read that 2-line Perl implementation of the RSA algorithm understands this simple truth. Software development is an art form. I am a Software Craftsman.

#wk171

The moment when client test team rejects a fix as it "doesn't work" when it's clear they haven't read the documentation 😂

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

Does any developer here does design work as well as code. I got pulled into it. was expecting a only dev job, according to the job description" but the creative team start handing me InDesign task and Photoshop task with no experience in design. is that crazy or normal for front end developers?

First rant that I really want to get out of my chest!

Never hated a job as much as this one. Haven’t done any development/programming related work since I joined. I have been mostly configuring Linux systems for IoT devices. When I get stuck at an issue, it takes me many frustrating nights to figure it out because no one on the team wants to deal with Linux shit… they’d rather be doing real development work (someone actually stated this!). There’s no one else on the team that knows Linux. Even the manager that was supposedly a Linux fanatic can’t even answer some of my questions and if they do, it’s the wrong fucking answer. Joined the company because they sold it as startup team with big money backing. Was excited to learn new technologies, new best software engineering practices, add new programming languages to my resume. But nope, been stuck at configuring Linux systems. At one point I was just pumping out updated Linux images with our updated application for a month straight. I was so excited when a development task was assigned to me a couple weeks back, but guess what?! There were Linux configuration tasks that no one knows how to do or don’t want to look at it, so my one and only fucking development work was swapped out!

And the funny thing is, I barely had any Linux experience when I joined. Why the fuck was I hired?

Man, I even bought books related to Linux programming (application and kernel) before I joined. Those books barely have a crease in them. What a waste.

Now in my free time, I’ve been learning new technologies on my own. Doing my own projects. But damn, I lose a lot of family time. Sorry wifey, I haven’t been paying a lot of attention to you!

But who knows, maybe this experience will have a silver lining in the end.

Thanks for reading :)

I really hate it when I work on a user story consisting only of a cryptic title: "Implement feature X".

Esp. when I missed planning during a holiday and can only wonder who in their right mind would have given it 3 points.

Why thank you.

Sometimes, just pulling the acceptance criteria out of somebody's nose takes days. It doesn't get better once I realize that not all external dependencies have been properly resolved. It's worse if there are other departments involved, as then you get into politics.

Me: "We are dependent on team X to deliver Y before we should have even planned this ticket. I'm amazed that our team was even able to estimate this ticket as I would have only raised a question mark during estimation meeting. We could have thrown dices during estimation as the number would have been as meaningful and I'd have more time to actually figure out what we should be doing."
Dev lead / PO: "I understand. But let's just do <crazy workaround that will be live until hell freezes over> temporarily."

It's borderline insane how much a chaotic work flow is branded as agile. Let's call it scrum but let's get rid of all the meaningful artefacts that make it scrum.

Fuck, I just found out that I have to replace the (pooled) company laptop, which I sometimes take home with me to continue some (work related) side projects, by myself if something happens to it.

Team lead asks me why I do that .... Because I am stupid enough to invest some spare time to get more valuable for the company, asshole.

And this is also the reason why I asked for a personal laptop as workstation several weeks ago... You dumbfuck

Context: This team has been constantly behind on deliveries, ignoring advice from other teams or more experienced colleague, making mistake after mistake and now, just revealed they have major performance issues, as warned...

So, in the most recent Sprint review they were, once again, criticized for their bad approach and inability as a team to receive feedback and work on that feedback, resulting in mediocre development...

As I left the room I heard one of them say:
"We make this huge rocket that most wouldn't be capable of doing and they cry that it's blue and not green... Others make a ls on a command line and everybody applauds"

Now, this is for everyone to whom the shoe fits...

Listen here you little entitled snotty prick, where do you think you are!? Yes most should not make a rocket when the requirement was a bike! That's overengineering and besides that most of your decisions were arguably wrong!

I will never applaud you or anyone else for doing your fucking job and being mediocre about it... What we applaud is value added! Value to the project, to the process or to the team... Bring value and I will applaud, do your job and you get a salary. Be a snotty childish dipshit and you might find yourself forcefully searching for new professional challenge!

10K bump but salary is probably still below market for the skills I have... Most likely reason? Trump tax cuts...

I can't showcase my skills in interviews assuming I get any... Not motivated in cramming or studying those useless algorithm questions that have little correlation to actual work.

Whatever.... job pays the bills pretty well... Sorta boring as I'm like the biggest fish on the whole team but that's also the upside I guess... May not be true but I think I'm pretty hard to fire...

So now it's sorta 20% work 80% life... So guess I'm done exploring and just gonna exploit...

P.S I wore this while taking a break from solo karaoking.... (Thursday night)

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?