High priority Bugs from the legacy system were pushing productive work out of the sprint enough that a 1 year project due in 2 months was sitting on 6 months of backlog of just my work. There are days where having 20+ years at the company is not a bonus. Fortunately I finally got through to the boss that he wouldn't make any ground on the project at this pace and he had the PM step in. Last sprint I worked on the project nearly full time.

Uncle Bob paraphrase: You're a professional craftsman, act like it.

We work with multiple platforms, a legacy language and c#. This dev uses underscore between variables in c# and camel case in the legacy platform. The thing is the legacy system has used underscores since 1981 and I've never seen a readable example of c# using them between words.

I also told him I was working on learning to use patterns and how the process of software development should work by training. His response... Why would you want to do that?

He also copies and pastes code everywhere and pays no attention to scope.

And worst of all I'm his coverage when he is gone. If I have to debug one more sloppy bug I am going to face desk.

Not to dislike 9 to 5 developers who have no passion for their craft and leech my hard work and knowledge while getting mad at me for not taking my time to sit with them and explain every small aspect of their tools to them that they should already know after having used them for 15+ years.

On a project that will crash and burn due to a badly projected date given to the business. I'm team lead and the Developement manager. I'm not sure how to save my career from this one. 22 years at this company and this may end my employment.

Can't change the date because the business has had it with deployment failures. Not enough time to do any of the technical debt and I'm not sure one if the issues has a solution.

Time to create a resume I guess. Been a really long time.

Let me know if you want a developer in Des Moines!

Feels good when you realize you type like you speak, without thinking about the letters. Only took me a long career to get here.

This was in 2001 on a legacy AIX core ops server. I got tired of waiting hours for the last page of a print job to debug totals. So, I added a print menu option to print it to an HTML file on a share served up by a wab server and send me the email link. Took two years to catch on but when it did, we eliminated all nightly print jobs and took the paper budget down by 90%. All because I was too lazy to keep reloading my desk jet with paper to debug reports and I forgot to take it off the menu.

Is it just me? I skip any rant in all uppercase or with f bombs.

Upgraded the company operations system system from AIX to Red Hat EL with near zero issues and no business interruptions. Platform and OS all in one. Been trying to repeat that with. NET 4 years into it and only 30% done with nothing but problems until we implemented CI & CD.

Met in c++. I read the course book the summer before and decided to ditch the final review class. He followed me as the instructor said "There are two guys that don't need to study!" I waived and said, "NOPE" and kept on walking with a wave. Proved it with an A. no clue what my friend got but 20 years later we are still working at the same company.