I am losing it at how many of my peers have forgotten what software engineering is.
-
I am losing it at how many of my peers have forgotten what software engineering is. It is not typing in lines of code.
@bert_hubert Programmers convert problems into code.
Unfortunately, programmers also convert code into problems. -
I am losing it at how many of my peers have forgotten what software engineering is. It is not typing in lines of code.
@bert_hubert that's right, it is actually mostly typing in Slack and MS Teams messages /joke
-
@bert_hubert it is also indenting lines of code
@rotopenguin with tabs or spaces though?
-
@bert_hubert@eupolicy.social This really makes me wonder whether the decades of constant blog posts about method, such as software craftsmanship, *-driven design, agile, extreme programming, etc etc etc (event sourcing, the hexagonal architecture, etc etc etc etc etc dear lord there are so many), were all, ultimately, not serious. If a single technological advance coupled with hype and corporate pressure is enough to convince people to throw all of that out, how serious could it have been, really?
@abucci @bert_hubert lovely point. And Iβm not saying you are wrong. Only few of the proponents of the things mentioned did not pivot the last two conference seasons.
-
@bert_hubert it is also indenting lines of code
@rotopenguin @bert_hubert Found the Python and Fortran enjoyer
-
@bert_hubert <sarcasm>Are you not happy with progress? Just architect something and the LLM will even review itself. We no longer need those annoying "why this, why that" people anymore. Move fast and .... who knows</sarcasm>
@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.
-
@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"
-
@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
-
@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 and whether your packet drops can be repro'd, what skills you have written up, how good your design docs are
-
I am losing it at how many of my peers have forgotten what software engineering is. It is not typing in lines of code.
@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.
-
I am losing it at how many of my peers have forgotten what software engineering is. It is not typing in lines of code.
@bert_hubert Pfft no. It's Jira. <runs>
-
R ActivityRelay shared this topic
