@rotopenguin @bert_hubert Found the Python and Fortran enjoyer

@BlackIkeEagle @bert_hubert all joking aside, most large software companies now have automation pipelines that do exactly that: take a Bug off the queue, propose a fix, compile, run unit tests, run regression suites, review and comment the implementation, write up the fix make the patch ready for review.

Sure they only cleanly fix a fraction of the bugs. But that fraction is increasing.

@Nymnympseudonymm @BlackIkeEagle @bert_hubert Are the bugs that trivial? The kind I run into are "router drops packets every 55 seconds when packets per second exceeds 900"

@StumpyTheMutt @BlackIkeEagle @bert_hubert typical example: program dumps core under crazy ass stress coverage test

@StumpyTheMutt @BlackIkeEagle @bert_hubert and whether your packet drops can be repro'd, what skills you have written up, how good your design docs are

@bert_hubert Software engineering maybe isn't LOC, but it does require knowing vaguely what's happening in a program you claim you wrote.

I'll stick to writing lines of code.

@bert_hubert not directly related but this reminds me of the time a client got mad that i deleted some code in the process of refactoring because "they paid for that code"

@andrybak @bert_hubert Lets not forget digging through jira for hours going "oh wait, heres a related... oh fuck this even worse than I thought" over and over again

@bert_hubert Pfft no. It's Jira. <runs>

@Nymnympseudonymm @StumpyTheMutt @BlackIkeEagle @bert_hubert I dare say that a lot of the investigation has been done to identify the behavioral problem by the time you get to this point. I think this work effort is where much over hyped automation fails.

@abucci @bert_hubert the people that researched and authored said blogs were very serious. Sadly many of those paying said authors to do the work that prompted the articles weren’t equally serious.