This story is 100% true.

I got hired onto a team of construction workers to build a house. We set up a meeting with Management to find out what kind of house they wanted us to build, where’s the floor plan, what it’s going to be used for, who it’s for, etc. Management said that they didn’t know all that, we should just get started. They told us that we were going to use “Agile” which means that we just work on small deliverables and build the thing incrementally.

The developer team lead argued that we at least need to know how big the thing is going to be so that we can get started pouring the foundation, but Management told him they just don’t know. “What we do know,” Management said, “is that the house is going to have a bathroom. Just start there, and we’ll know more when it’s done. You have two weeks.”

So we just bought a port-a-potty, and screwed around on the internet for two weeks. Management was outraged. “You call this a house? This is the worst house ever! It doesn’t even have a tv!”

So we bought a tv and put it in the port-a-potty, attached to an outdoor generator. We were going to buy a a dvd player and get it hooked up to cable, but Management rejected the expense request, saying that they didn’t know if we needed it, and we’d come back to that later.

Management decided that we definitely need storage space, so we bought a boxcar and duct-taped the port-a-potty to it. Then to our horror they set up some desks and put a few miserable business interns in there. It went on like this…

After a few years the boxcar grew into a huge, ramshackle complex. It floods, leaks, it’s frozen in the winter and an oven in the summer. You have to get around in a strange maze of cardboard tubes, ladders and slides. There are two equally horrible separate buildings. We’re still using just the one outdoor generator for all power, so electricity is tightly rationed.

Communication between the buildings was a problem. For one of them, we use a complex series of flag signals. For the other we write notes on paper, crumple the paper up, and toss it over. Both of these methods were suggested as jokes, but Management really liked them for some reason. The buildings mostly talk to each other but they have to talk through us, so most of what we do is pass messages on.

It was suggested that we use paper airplanes instead of crumpled up balls, but the fat, awkward fingers of the Business Majors who inevitably take those jobs couldn’t be trained to make them. I built an awesome automatic paper airplane folder, but once again they couldn’t be trained to use it, so they just went back to crumpling the notes up in balls.

The worst part of all this is that it’s working. Everyone is miserable, but the business is making money. The bright side is that this nightmare complex is done so now we know what kind of building they actually needed in the first place, so we can start work on it. Obviously we can’t tell Management anything about what we’re doing until it’s finished. They noticed the gigantic hole in the ground where the foundation is coming in, but we told them that it’s a cache reset, and they mostly ignore it except when the occasional customer falls in.

I’ll probably be out of here before the new building gets finished. I could get a 50% raise by switching jobs, but Management still doesn’t think I should get a raise because I missed a couple sprints.

I hate ZenHub. For those who haven't heard of it, it's an agile project management solution that is hacked (and by hacked I mean really hacked) on top of Github.

It's touted as being convenient because you can have all your issues in Github and then look at them in epics and board format. Sounds awesome. Except it's not. For everything "convenient" it does, it severely lacks the most basic ticket management features that make any ticket management solution usable. Ex., you can't copy tickets. That's right - if you're creating 20 similar tickets, which I've needed to do in the past, you must create each one individually. New ticket -> add labels -> add assignee -> add title -> add description and then submit. 20 times.

ZenHub is so bad and so poorly conceived that many of those who use it have lost sight of project management reality and are blind to the 300 other PM products out there that are better.

True story: a couple of weeks ago people were celebrating because ZenHub added functionality to allow you to define what epic an issue belonged in while you were creating it. For those who aren't familiar with what that means, let me explain: before two weeks ago, when creating an issue in ZenHub, to fill out this "epic" field, you needed to first create the issue and then edit it to fill in the epic.

Let me break that down in devRant terms: it's the equivalent of not being able to add tags to a rant until you create it and then go back and edit it. Complete lunacy is the only way to describe it. And when they added the functionality two weeks ago allowing you to do it all in one step, people praised them!!!

Yeah, ZenHub sucks.

i hate everything about programming except programming.

i hate version control, i hate agile, i hate package managements, i hte deploying, i hate clients. I hate that i cant get shit done.

Feeling like I've gone back in time about 15 years!

Just told my CTO about various improvements we could make to the development process. Things like git, continuous delivery, agile project management apps such as Jira, task management such as Gulp, etc.

His response - "never heard of them. I bet they'll pass in a few months. Just another round of fads".

I hate all of the people that think "agile" means "do everything at the same time, with no cost". Or, other fuckwits, think that "agile" means "fuck plans, dev team will figure something out".

Both of these types apparently did not read any publication about the subject.

Aaaaaaaaaaaaaaaaaaaaa!

For the first time I am feeling like.... I hate my job.

Agile and Scrum can be fucked, but at least there is a work methodology. I was hired by a company being run the old school way.

These guys never heard of git??
- Fuck you. We never used git and neither should you.

Client company does not want to give me push/pull access to their gitlab instance??
- Fuck you, you can use our RDP server for that.

Project planning features be damned, they've got email, Teams and videocalls!

Can I develop in peace? Fuck no, I have to give IT support to the guy who hired me.

Our timeline is defined IN A FUCKING WORD DOCUMENT FOR FUCKS SAKE. I can't connect Issues to milestones in a Word doc

Oh, and the customer is running everything on prem. If there is a need to scale up, FUCK ME. I should have specified 20 machines from the get go or gtfo. We're using 2 machines to run 8 different services that are going to be ingesting and computing data.

They want state of the art on a cheapskate.

And I have nothing else lined up at the moment. Although I am soon to renew the contract... This contract binds me with professional responsibility for a project being ran by people who do not give a single fuck about optimizing the work process.

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?

I fucking hate estimating time.

I appreciate that agile is better than any planning type before it, but HOLY SHIT is estimating time a fool's game.

I've been at this over a decade now and I'm still like.. 50% accurate at best. The complicated shit is seldom obvious, and usually if I think something will be complicated it ends up being very simple once I dig in.

Why fix tomorrow, what you can write properly today!

Seriously, why does everything have to be [M]otherfucking [V]omit [P]rojectiles and dealt with later when it falls apart, rather then spending that extra few hours / days making it fucking stable now, instead of months some where in the future.

Excuse me, I have yet another foreseeable fire to put out.

When there’s a glaring user-facing issue in your company’s app that can cause the user to spend mobile data after specifically choosing a setting that’s supposed to prevent that.

And your boss says your fix is “out of scope for the current sprint.” And the product team agrees with him.

I ALREADY DID THE WORK AND HAD IT VERIFIED BY QA.

Sometimes I Hate agile. Then again, I don’t think we’re doing it quite right anyway.

I hate it when “We’ll, we’re agile” becomes more of an excuse than a plan.

Q: What does a very fat software engineer hate?

A: Agile development.

This is my first time experiencing agile development with its daily scrum meets, and I hate it already.

I have so many questions in my head…

Should I focus doing front-end or back-end?

For mobile dev, flutter or react native?

Kanban or Agile?

Google cloud or AWS?

Switch to Linux or stick to WSL2?

Solidity or Rust for blockchain apps?

Best low-code that my dev peers won’t hate me for using?

If starting a project,
Bootstrapping or chase after VCs?

Do you guys use conditioner when you run out of shaving cream?

Keto or vegan?

Is milk really that bad for our body??

TL;DR: I hate how management doesn't listen to devs (even Dev managers).

We need to sort out our release process where I'm at. It takes a Dev about 2 solid days to complete and it's hideously involved and ripe for human error. They're completely out of action until it's done and it happens once a week!

It's stopping us releasing business critical bug fixes and features that need to go out. Instead the work just sits in develop for days doing fuck all.
Can't be agile if it takes so long to deliver value 🙃

Plus makes any fuck ups by our department look worse as it takes an age until it's fixed which reduces their collective trust in us and our opinions.
Making any improvements we want to make harder todo as they're harder to convince 🙃

Has anyone had any success getting automated releases?
How did you convince management to prioritise it?

I need to convince someone who has some influence in my company and ask how they got that influence

what kind of dumb fuck you have to be to get the react js dev job in company that has agile processes if you hate the JS all the way along with refusing to invest your time to learn about shit you are supposed to do and let's add total lack of understanding how things work, specifically giving zero fucks about agile and mocking it on every occasion and asking stupid questions that are answered in first 5 minutes of reading any blog post about intro to agile processes? Is it to annoy the shit out of others?

On top of that trying to reinvent the wheels for every friggin task with some totally unrelated tech or stack that is not used in the company you work for?

and solution is always half-assed and I always find flaw in it by just looking at it as there are tons of battle-tested solutions or patterns that are better by 100 miles regarding ease of use, security and optimization.

classic php/mysql backend issues - "ooh, the java has garbage collector" - i don't give a fuck about java at this company, give me friggin php solution - 'ooh, that issue in python/haskel/C#/LUA/basically any other prog language is resolved totally different and it looks better!' - well it seems that he knows everything besides php!

Yeah we will change all the fucking tech we use in this huge ass app because your inability to learn to focus on the friggin problem in the friggin language you got the job for.

Guy works with react, asked about thoughts on react - 'i hope it cease to exists along with whole JS ecosystem as soon as possible, because JS is weird'. Great, why did you fucking applied for the job in the first place if it pushes all of your wrong buttons!

Fucking rockstar/ninja developers! (and I don't mean on actual 'rockstar' language devs).

Also constantly talks about game development and we are developing web-related suite of apps, so why the fuck did you even applied? why?

I just hate that attitude of mocking everything and everyone along with the 'god complex' without really contributing with any constructive feedback combined with half-assed doing something that someone before him already mastered and on top of that pretending that is on the same level, but mainly acting as at least 2 levels above, alas in reality just produces bolognese that everybody has to clean up later.

When someone gives constructive feedback with lenghty argument why and how that solution is wrong on so many levels, pulls the 'well, i'm still learning that' card.

If I as code monkey can learn something in 2 friggin days including good practices and most of crazy intricacies about that new thing, you as a programmer god should be able to learn it in 2 fucking hours!

Fucking arrogant pricks!

Before 2012, I always worked in cubicles and had weekly status meetings. In 2012 I moved to a big city and learnt there was something worse than cubes: the open work plan. Marketed as a way to increase coloration, the open work space is really just the result of real estate prices being expensive in cities and how desks are cheaper than 3-cube walls.

Up until 2013, we'd usually just have the weekly status meeting. Here are your tasks for the week. I'd do them at my own pace. Some days fast, some days slow, but they'd all get done by the end of the week and I'd proudly go down my list of stuff I had done.

Since then, it's all been "agile" and "stand-ups" every. fucking. day. The work is endless. A Product Owner once told me that stand ups weren't suppose to be status meetings; that you were only suppose to say if you're blocked or need help. But in every place I've worked at, they're daily status reports. You have to preform every day.

I really hate IT today more than ever. I miss the cube. I miss the weekly status reports. Today things are so high stress and higher paced and the work is endless. You can't even really pace yourself anymore.

Fuck agile,fuck scrum masters now I really hate the word story and epic.

Luckily I don't work at a place like this anymore, but I sure hate it when a company touts that they are an effective company who has implemented agile "the right way", then when they describe their process in detail, it is almost exactly the opposite of what agile is supposed to be.

I've worked for a couple places that just couldn't get their head around the fact that one of the reasons agile exists is because estimating software is hard, and only after doing agile the real right way for an extended period of time can a company expect to have realistic estimates. The business can't go a week without hard deadlines.

I work for an investment wank. Worked for a few. The classic setup - it's like something out of a museum, and they HATE engineers. You are only of value if work on the trade floor close to the money.

They treat software engineering like it's data entry. For the local roles they demand x number of years experience, but almost all roles are outsourced, and they take literally ANYONE the agency offers. Most of them can't even write a for loop. They don't know what recursion is.

If you put in a tech test, the agency cries to a PMO, who calls you a bully, and hires the clueless intern. An intern or two is great, if they have passion, but you don't want a whole department staffed by interns, especially ones who make clear they only took this job for the money. Literally takes 100 people to change a lightbulb. More meetings and bullshit than development.

The Head of Engineering worked with Cobol, can't write code, has no idea what anyone does, hates Agile, hates JIRA. Clueless, bitter, insecure dinosaur. In no position to know who to hire or what developers should be doing. Randomly deletes tickets and epics from JIRA in spite, then screams about deadlines.

Testing is the same in all 3 environments - Dev, SIT, and UAT. They have literally deployment instructions they run in all 3 - that is their "testing". The Head of Engineering doesn't believe test automation is possible.

They literally don't have architects. Literally no form of technical leadership whatsoever. Just screaming PMOs and lots of intern devs.

PMO full of lots of BAs refuses to use JIRA. Doesn't think it is its job to talk to the clients. Does nothing really except demands 2 hour phone calls every day which ALL developers and testers must attend to get shouted at. No screenshare. Just pure chaos. No system. Not Agile. Not Waterfall. Just spam the shit out of you, literally 2,000 emails a day, then scream if one task was missed.

Developers, PMO, everyone spends ALL day in Zoom. Zoom call after call. Almost no code is ever written. Whatever code is written is so bad. No design patterns. Hardcoded to death. Then when a new feature comes in that should take the day, it takes these unskilled devs 6 months, with PMO screaming like a banshee, demanding literally 12 hours days and weekends.

Everything on spreadsheets. Every JIRA ticket is copy pasted to Excel and emailed around, though Excel can do this.

The DevOps team doesn't know how to use Jenkins or GitHub.

You are not allowed to use NoSQL database because it is high risk.

What a week... I feel like I am on here ranting more than usual.

The Marketing Director and Project Manager keep telling me to let them know when I am stuck on tasks so they can unblock for me, but I FUCKING DO. I don't understand why they keep telling me to speak up, because I use multiple channels to tell those who are the blockers that I need an update.

I add comments on my Monday.com tickets and @ the relevant people, I send MS Teams chats to them, we even have a daily standup where I mention that I am stuck, as well as a OneNote daily update that gets sent to management where I mention that I am stuck and tag the people who need to help me out.

I have been stuck on a task for two sprints, which should have taken me a couple of days to do.

I really feel like I'm talking to brick walls, am I that unimportant? This is supposed to be "agile scrum kanban blah blah blah sprints story points people over process bullshit". I hate it. Y'all are doing it wrong... Fuckin robots.

I need a fuckin drink, thank God it's Friday.

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 you and your agile and scrum
nothing will fix your laziness and stupidity
I hate wasting time for this bullshit

When companies don't understand what DevOps is and don't know how to implement it.

I hate when the term DevOps gets slapped onto a traditional Ops or sys admin team and they call it a day.

It's become the new agile.

Some of you know I'm an amateur programmer (ok, you all do). But recently I decided I'm gonna go for a career in it.

I thought projects to demo what I know were important, but everything I've seen so far says otherwise. Seems like the most important thing to hiring managers is knowing how to solve small, arbitrary problems. Specifics can be learned and a lot of 'requirements' are actually optional to scare off wannabes and tryhards looking for a sweet paycheck.

So I've gone back, dusted off all the areas where I'm rusty (curse you regex!), and am relearning, properly. Flash cards and all. Getting the essentials committed to memory, instead of fumbling through, and having to look at docs every five minutes to remember how to do something because I switch languages, frameworks, and tooling so often. Really committing toward one set of technologies and drilling the fundamentals.

Would you say this is the correct approach to gaining a position in 2020, for a junior dev?
I know for a long time, 'entry level' positions didn't really exist, but from what I'm hearing around the net, thats changing.

Heres what I'm learning (or relearning since I've used em only occasionally):

* Git (small personal projects, only used it a few times)
* SQL
* Backend (Flask, Django)
* Frontend (React)
* Testing with Cypress or Jest

Any of you have further recommendations?

Gulp? Grunt? Are these considered 'matter of course' (simply expected), or learn-as-you for a beginner like myself?

Is knowing the agile 'manifesto' (whatever that means) by heart really considered a big deal?

What about the basics of BDD and XP?

Is knowing how to properly write user-stories worth a damn or considered a waste of time to managers?

Am I going to be tested on obscure minutiae like little-used yarn/npm commands?

Would it be considered a bonus to have all the various HTTP codes memorized? I mean thats probably a great idea, but is that an absolute requirement for newbies, or something you learn as you practice?

During interviews, is there an emphasis on speed or correctness? I'm nitpicky, like to write cleanly commented code, and prefer to have documentation open at all times.
Am I going to, eh, 'lose points' for relying on documentation during an interview?

I'm an average programmer on my good days, and the only thing I really have going for me is a *weird* combination of ADD and autism-like focus that basically neutralize each other. The only other skill I have is talking at people's own level to gauge what they need and understand. Unfortunately, and contrary to the grifter persona I present for lulz, I hate selling, let alone grifting.
Otherwise I would have enjoyed telemarketing way more and wouldn't even be asking this question. But thankfully I escaped that hell and am now here, asking for your timeless nuggets of bitter wisdom.

What are truly *entry level* web developers *expected* to know, *right out the gate*, obviously besides the language they're using?

Also, what is the language they use to program websites? It's like java right? I need to know. I'm in an interview RIGHT now and they left me alone with a PC for 30 minutes. I've been surfing pornhub for the last 25 minutes. I figure the answer should take about 5 minutes, could you help me out and copypasta it?

Okay, okay, I'm kidding, I couldn't help myself. The rest of the questions are serious and I'd love to know what your opinions are on what is important for web developers in 2020, especially entry level developers.

I hate unnecessary meetings. It is a waste of my productive time. Also I hate daily stand ups that becomes a regular meeting with question and answer portion lol

It is like they are lazy creating a separate meeting for specific concerns and just brings it up in the daily stand ups lol nice way of doing agile things lol

I really hate all kinds of tattle that sweeps the hallways of corporations, the gossip behind one's back, BUT this colleague of mine starts pissing me off. Recently joined that team where he should support us getting the Agile thing going. And he can go on for hours of how it should go and how flawlessly it worked in his previous company - all that needless meta talk - so much that a team member jokingly even said: yeah, shut up asshole. But he is all talk. When the name of a library was dropped his experience in using it went to upstream patches. His Linux experience lets us speechless. He is so convincing, I'm even doubting my accusations. Yet his only contribution in code wouldn't show and other team member wasted hours upon hours to recompile plugins to show that shit. Man, just leave us alone watching your youtube live-streams so we can get the shit done.

At my school we have 2 projects a year, mock projects to learn how that works.

For this project we have to use php, agile and we have an actual customer. Since several groups work for the same customer , the customer can choose the best result. (if your product gets chosen then there may or may not be a reward)

In every sprint meeting the customer confirms my thoughts on how much I hate customers without any knowledge.

I'm good at dumbing things down for less knowledge people. But no matter how I try to dumb down demo, she doesn't get it.

I'm so super frustrated!!!!

And she's asking for a feature that she'll probably use once, and I'm not convinced she knows what she is asking for. But will take me several hours to implement. It feels so useless.

I hate project managers trying to stay relevant to a agile development methodology. Our PM doesn't care if we are working and providing value to the customer, only about checking off his Project check boxes.

tech lead CANCELS Monday stand-up becuase they cannot attend. and I work and status and update my tasks in or virtual task board. I forget to send a message mentioning I'll be kissing Tuesday standup. Then he sends me emails like the following sent to me, my manager, and my tech lead: "please remember to notify your team if you cannot attend the standup, and to send an agile status to the team. This is something that is required and not optional. We are trying to firm up all stories and tasks and need to hear a status. We are in week 1 of iteration 4.3. Thanks."

I'm coding and delivering value to the customer. Wtf are you doing dude?

I'm absolutely fuming why on earth would someone try to apply exactly all rules of a theoretical concept. I hate those so called "scrum masters". We can't apply all rules of agile we're not machines. There's real life and theory.

In a sprint planning meeting. Getting frustrated. I guess it's my fault. I guess I assumed that attending the same schedule meeting each week meant that we all knew when everything was due. My bad.

Seriously, I fucking hate systems people sometimes. We have 4 major tasks coming down the pipe, but they are scheduled in such a way in which they are staggered. But they want to punt the 1 of the 4 that is fucking done because it is going to cause a lot of testing, but the other three aren't coming til end of next month AT LEAST. So they want to stick their thumbs up their ass holes and wait to test the other three before testing the one that, again, IS FUCKING DONE!!! Are they worried that a super massive black hole will spontaneously form in earth's orbit and cause time to run backwards and somehow cause December to happen in October!?!?

No wonder systems is so fucking far behind. They can't see the forest for the trees. They're so big picture that months and years are at the same level of granularity. Fucking hell how is scrum better than our current agile process again? Besides the fact that it makes me attend more useless meetings and get more angry.

They are punishing the left hand for the actions of the right. Systems wasn't doing their job so now software has to slow down and miss schedule.

The customer wants to drop Agile in favor of their in-house development methodology. They just sent an e-mail describing it...
I think my team needs a room decorated with cotton flowers and small huts to get into the right mindset.

I can't deal with this stress anymore

I really like working at this company but the stress is getting worse and worse, too many projects going on, deadlines creeping up, micro management through "agile" and many others.

Not sure what to do, I like the people, the projects themselves but I fucking hate the management!

I think I'm gonna have to leave, I might even need a couple months break just to regain my mental power before I get back to work.

I hate surprises.
I join office after a short leave and the other guy is out with a completely new product I have no clue of. (surprise 1)
Next, he's on leave and now I'm asked to fix bugs.(surprise 2)

Just for the curious, I ended up successfully fixing them and adding 2 features.

Dafuck is that swiftUI, already hate reactjs to the bones, and now here we go again, i must code those nested views hell and predict the data channels.
This is killing agile programming bigtime