IS THIS SOFTWARE DEV? | Prime Reacts

Not sure how many folks here work as a software engineer contractor for the gov't. But I'm pretty sure (sigh...) it's literally the worst. lol Literally in meetings all day and only have like 2 hrs (probably the best case scenario) in a day to do meaningful engineering work. And management wants to be on time estimation meetings too

Coding is fun, tie wearing useless middle management suck to deal with.

AGILE SUCKS HARD, NOTHING GETS DONE

sublime - monokai 💘

The only useful part of sprint plannings in one of my recent companies was that it allowed me to point out the tickets that were not ready for development yet, but still were being pushed through by product managers

This was cathartic. My workplace heavily leans on Agile and I've felt like I'm crazy for questioning how useful it is to be in so many meetings.

Shout out to my vi chads....lol

To me, agile is the agile manifesto, and sprint plannings is a management agile cargo cult.

I work about 1 hour a day yes. sometimes I dont work for 4 days and then I make it up by working for a whole morning/afternoon. Sometimes theres slow weeks where I barely work, but there are also crunch weeks where I work most of the time.

"I dont want to hear about your dog in the daily - STFU and go on"
God... how many times i wanted to say that but werent able because i would be dragged immediately to HR, in EVERY Company i was in the last 10 years

and: i paid for Sublime - i even developed plugins for it xD

You know what, working as a programmer and doing coding are two different things.
My opinion: sprint planning need, stand-ups need. Its work, you would know what team does, 30 minutes of your time worth it.

i get value out of sprint planning because I code during the sprint planning

Where is the Retro? Where is the group therapy for manchildren / womanchildren?
Also: what does my scrum master do? She is giving the speaking order in stand ups but when she is not there...we handle fine without her. So what she is really paid for is a complete mistery to me.

Task estimation and sprint planning are a part of SCRUM, not Agile. Agile is just a methodology for constant Git commits, failing fast, and moving forward. A lot of people confuse Agile for "SCRUM" or "Kanban" but the latter two are simply other methods for organizing tasks. Agile only defines the greater philosophy for developing software more swiftly.

Our team of about 10 have standups everyday. But they only last about 15 min. I'm working this and have no roadblocks. When I've had a roadblock sometimes another developer would say he had it too but to just Slack him after the meeting. We don't do sprints we just get our stuff done. I'm the merge guy but also code. Merge changes to Dev, Staging, and Production after QA finishes their tests. Once it's DEV it's pretty easy to move. Click of a button and CI/CD goes to town.

YES, AGILE IS SHIT. Thank you

Clearly, a no-estimate guy having opinions on something they know little about. Unknown unknowns my friend.

1

Prime: I’ve never once’s planned a sprint in my decade at Netflix.

Then the chip crunch.

This is the absolute epitome of a flex.

You think that's bad? My company switched to SAFe. Screw planning the next 2 weeks. Now we have to plan the next 12 weeks. And the meetings last two and a half days.

They literally took the worst parts of Scrum and the worst parts of Waterfall and created this ****ed up baby out of it.

The "standup" ritual is absolutely nothing more than the most lazy method of project management.

I genuinely don't understand the agile hate. It works great at my company and my team is really healthy/productive. We rarely waste time and have really efficient meetings. Any extra talk that we do takes a few minutes and it's because we enjoy a little bit of socialization occasionally.

When SCRUM goes over the top it becomes scrotum!

Great sprint planning meetings is devs engaged on stories and discussing implementation which they would need to anyway to implement those stories. Bad sprint planning meetings is PM / design endless going over what their stories really mean. Those should be replaced with a meeting about that feature / feature set. This arbitary timebox planning / retro meeting style is just a crutch for culture where managers have no memory and constantly start new work before the other finishes. Kanban addresses this.

Meetings are just a way for middle management to look productive to upper management since most of the time the people in upper management aren't very technical. My team has 3, 1 hour meets a week and most of it is just trying to burn time.

I like XXXXXXXL size in my estimations and that was one funny video

8 months later... What was in the box?

Techlead (soy dev) always gave me uncomfortable vibes. Not much value, but lots of handwaving and superiority complex.

man looks like dr dis

I never liked techlead, the first clip I saw was „what makes you a good developer” and the first answer was „type fast”. I laughed, then watched a few clips to understand why his every take is wrong.

My last team was entirely based out of Minnesota, nothing against people of Minnesota, lovely team, lovely people, but meetings were hella long , 5 min meetings extended up to 20+ min, and God help Friday because everyone has to share what's they gonna do on weekends. I had to make shit up because I have no life outside of work.

monokai rips

try having daily meetings where we have no clue what the requirements are, so we have to plan another meeting with someone who does, only to find out in the meeting we need to schedule a second meeting.. and cycle continues.

Tech Lead's marriage wrecked him

My experience as a non-millionaire engineer, 99% of companies who use scrum, implement scrum incorrectly. Thankfully my current team is doing it mostly right and our team culture is healthy enough that if something isn't working, we can improve on whatever the issue is. But I ain't gonna lie, meetings f'ing suck!

What is daily standup meetings became so widely adopted because they actually provided the value of short term consequences for undiagnosed ADHD people (which seems to be a lot of software devs if I go off my own career of knowing how many got diagnosed as an adult).

I worked in R&D and planning 2 week sprints took us 1 whole day. But working in biotech lots of task were unpredictible becouse of biology nature. Even after 20 sprints we have like 50-60% completed tasksL :P

When people ask you to write docs, I think "...unit test much!"

his use of outro misic mid video makes me deeply upset and is also making me cringe. send help

hours, days, weeks, years, and my favorite estimate - ages 🤩

Yeah this is cargo cult development 101 my team does it but I ignore nearly all of it with no problem

A good sprint planning session should take 5 minutes: establish velocity, draw the line, maybe switch 2-ish stories that would block other stuff, done. 5 mins

is

I even bought TechLead's wallet merch :D

1