I am losing it at how many of my peers have forgotten what software engineering is.

[blackikeeagle@mastodon.pirateparty.be]

@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>

[abucci@buc.ci]

@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?

[notbobbytables@infosec.exchange]

@bert_hubert Programmers convert problems into code.
Unfortunately, programmers also convert code into problems.

[andrybak@mastodon.social]

@bert_hubert that's right, it is actually mostly typing in Slack and MS Teams messages /joke

[freelon@mas.to]

@rotopenguin with tabs or spaces though? 😜

[rotnroll666@mastodon.social]

@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.

[stumpythemutt@social.linux.pizza]

@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@mstdn.science]

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

[mdhughes@appdot.net]

@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.

[hobbs@dobbs.town]

@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"

[unlofl@mstdn.social]

@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

[woody@pleroma.pch.net]

@bert_hubert

Of course not, that's for the olds. It has something to do with vibing.

[josh@hactivedirectory.com]

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

[drscriptt@oldbytes.space]

@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.

[drscriptt@oldbytes.space]

@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.

[troed@masto.sangberg.se]

@bert_hubert In the 90s we had the "Programmer productivity can be measured as LoC".

AI productivity measures seem to be the same ...

[abucci@buc.ci]

@drscriptt@oldbytes.space @bert_hubert@eupolicy.social I personally know more than one person who's spent years writing about some method, let's say TDD, going to conferences presenting their ideas etc, fully independently of their employer. Said folks are now slinging AI slop and writing about how great LLMs are. Blaming the employer doesn't pass a smell test.

[root42@chaos.social]

@bert_hubert just let the AI spew out code. Who needs software architects anyway?

[n_dimension@infosec.exchange]

@bert_hubert

Why waste weeks on design
When you could waste six months on coding?

[mark@mdft.social]

@bert_hubert we're going to have to express technical debt in kiloyears now