The video is 13:37 long. N1C3

For me the problem was that when I became a tech lead, my manager expected me to now know everything that is going on on the project (we have 15 devs contributing at once), do knowledge shares to teach everything I know, be a mentor to everyone, answer all client emails, AND ALSO do the same amount of dev tasks as I was doing before, be responsible for coding the hardest parts of the project, review ALL pull requests from the 15 devs, and also somehow keep up with trainings. ... Excuse me, but how is that humanly possible? I had to drop out due to burnout and they were disappointed in me despite the fact that they now need 5 people to do what I was doing before.

Developers love reinventing the wheel. For some reason, they think they can do it better than their predecessor. Right - their predecessor thought that too, and he's gone now.

Managers are addicted too. Our CTO made everyone prove that we know new technologies, even though our clients haven't changed in 20 years.

Easy to say when you're in USA where pay for work, especially in Programming is soooo high. You can be a picky.

Alastair Cockburn is wondering whether to call it 'packaged Agile' vs 'true agile'; I call it 'commodity agile' vs 'agility'.

Pardon the ignorance. Businesses need to estimate how long things will take and how much labor will be used to complete outcomes, I'm confused how you could report this to management using scrum if story points arent hours etc. When do you use scrum over waterfall? if your requirements are clear and well defined does that mean there is still a place for waterfall in software development? For example no-one builds a bridge or dam using agile.

If I decided to move to management, I'd be the kind that fight the upper level as hard as I can for my team and get fired in no time 😄.

It feels like you repeat yourself at some point in the video. Are you using a clip form mid video in the beginning without a noticeable segway/transition?

I've been doing software development as a professional for 25 years. Before that, I worked in factories. I found working in factories to be way more draining, demoralising, and depressing than coding. And not just psychologically... standing all day in overheated buildings takes a physical toll. I'm talking heat stress on a daily basis for 6 months out of 12. I now have the luxury of working from home.

My attempts at playing any kind of musical instrument were an epic fail, but I'm impressed by those who can.

The company I work for was agile before they introduced agile, then it wasn't.

Have been looking for that kind of path just to being able to grow up as a senior engineer, have been performing as a senior software engineer during the last 2 year, although I still do not perform with the fluency and confidence that I consider necessary.

nice guitar!

At 3:30 the 4th option is giving them the support they need to get the job done (helping them overcome obstacles).

Sadly too often I've experienced that some devs within a team break the united front that should be presented by the dev team. Once a manager/PO/lead wants some new feature for an unchanged deadline, some devs just don't see that as problematic. This leaves the other developers in the worst spot possible: either say no and be the bad guy or go along and have lots of stress.

No, the first thing you have to realize is, not everyone is built to be a programmer. I started programming at 13 years old and it hit me like a religion. I am now 55 and I can honestly say in my 35 year career/40 years of programming, I have never hated it or experienced burn out... until recently. Now it is not because I hate it, it is because I feel my career winding down because of my age/employability due to my age. I have always said, I was born a programmer and I will die a programmer. Back in 1990 when my career started, everyone and their dog wanted to get into programming due to the money, but not everyone was built for it. So many people dropped out of my course it wasn't funny. Throughout my career I encountered so many people who quit their programming careers right around 5 years in because of burnout. Because for me is started as a hobby, I felt like I went to work to play and they threw lotsa money at me. I'd go home after an 8 hour day and code more... just for fun.

Yes agile is driving me crackers - I loath it with a vengeance

I couldn’t agree more. I worked as a software system engineer and lead system engineer in the automotive industry for a decade and left it because it’s just frustrating to do these nonsense stuff/work/burn-down-what-so-ever. But, Instead of sticking my head into the sand I decided to actively work on this problem, which is the reason why I started my own company

At 16:30 you described me perfectly. My current employer will be the last one, and then I'll retire. I've already faced that reality. In terms of learning new skills that another employee would hire me for... that isn't going to happen. I'm too tired for that. My strength and my passion were always in Windows application development in C++. These skills seem to be falling out of favour. Investing huge chunks of energy and time learning skills that will endure makes sense. But at some point down the line, it no longer adds up. This I think is a point we'll all reach sooner or later.

I'm still in the learning stages of becoming a developer, so I've never held a job in the field or anything, but your videos started popping up due to the good ole algorithm and man... this one really resonated with me. I appreciate so much you being so open about your past and I absolutely love/agree with your main objective being helping people be a healthy programmer. It pretty much made my day to hear of your faith in Jesus as well. God bless you man, and thank you so much for these videos

I 100% agree with this and am curious - does anyone in software development not know this already? It only takes one time getting burned before you learn this lesson.

This is absolutely true, In my career I had numerous occasions where my manager would ask me to do a certain thing and after finishing the task, he would say this is not what we asked you to do. From that point on I started writing the requirements in confluence creating mockups and sending the link to the managers and asking them to review and verify the requirements. This happened again and I happily pointed them to the link and the date two which I emailed them the document to be reviewed. That exposed their deficiency in taking the time to review documents and also exposed the issue that upper level was was piling up so much work on their plate that they didn't have time to do these critical tasks. Eventually I left the company, like it or not, management is the key to a companies success.

Goodness I love this channel.

Currently on a project where every standup starts with a slide pointing to where on the literal blue gantt chart waterfall timeline we are. This is not parody. They pay well but it's excruciating.

What is tech.. what is a tech job? When did this label start getting used? Sounds like an ambiguous buzzword. God knows we need more of them.

Agile/scrum = scam

Why are you talking so slooooow?

Important to reiterate your point early on that the few companies actually doing Agile are doing better software delivery and performing better as a business. We just need more of that in the competitive mix in more markets so that real Agile can put non-Agile companies out of business. The proof is in the pudding. But why hasn’t it happened yet is the real question?

5. Do the Good Work on the downlow because management will never give you approval to "waste time" on it

This is exactly what's happening to me right now and I'm going to be blamed. Maybe I will finally learn the lesson.

Our agile and sprint planning just means why is it done yet. Do the needful!

Some clueless management introduced Agile in utility space and it took less than 2 years to decimate their core engineering arm. The result was almost a disaster as no one knows how to keep the lights on! Emphasis on Agile than doing the work!! Agile is new thing for clueless managers.

“Agile” is a cult

The business things software development is manufacturing. Devs think it’s invention. That is the heart of the problem.

"Im really anal about my documentation" I wish this was the case for all seniors, as a junior, I've never seen decent documentation once

On your first point about raising problems, I found it also helps to always come up with a few ideas of your own k how to mitigate the problem. Even if they aren't great answers, at least you are proposing solutions.

You might have 27 years of experience, but I have 53 years of experience. Using the number of years of experience as a measure of quality is fundamentally a philosophical fallacy.

I am an agile coach that is fighting to stop agile in the ways you are talking about! Lets see how long I keep my job :D thanks for the video! (also I never hire anyone who has their certifications at the top of their resume or if they even talk about them)

In my experience, agile promotes good behaviors. Oftentimes, imho, when developers are frustrated with scrum meetings it is because the information conveyed is not currently useful to them and they pan out. The long term effect is that they never really get up to speed on the business and are unable to make the best choices for the software design since they did not care for the full picture. They expect somebody else to write the stories, or rather tasks, so they can focus only on sw development without caring for the reason it is being prioritized. Every developer should always focus on developing the right thing, rather than only doing the thing right..

That last point hit hard. I'm a 12 year programmer who's strength is IC. It's where I'm comfortable, being a bit on the spectrum. I hope I can continue to have success for long enough to save for the day when I don't.

This field is very difficult.

I’ve been a software developer for a long time, and the only thing I’ve ever seen Agile do is cause enormous amounts of technical debt because the project was rushed by project management and we had to go back to fix the things we told them we didn’t have time to do.

Thanks for the little guitar interludes. They kept me from losing my temper every time you brought up one of these pain points, lol. We never did real Agile. Management here just used “agile” as a magic word to mean that they could continuously move the goal line and magically expect a 2 week project to be done in one week, because we’re “agile” now.

What song are you playing at the end?

Rational unified process v waterfall methodology!