I'm super excited for all the free money and data our new AI written apps will be giving away.
3,494 karma · joined March 13, 2012
I'm super excited for all the free money and data our new AI written apps will be giving away.
Clean Code pushed things in a better direction, but it over-corrected. In many ways APOSD (published in 2018) is a correction against the excesses of Clean Code (published in 2008).
Will people swing too far back, to giant methods, deeply nested conditionals, etc? I don't know. But probably.
Nobody wants to pay a bunch of desk workers six figures to make their business go brr, but they currently they have no choice. Trust me, every executive resents this to their core and they want all the programmers to go away - including github executives.
20 years ago you would hire a few expensive architects who would try and design the product in so much detail cheap jr programmers could build it. It didn't go well.
4GL languages tried to abstract away all the hard stuff - again it didn't go well.
"Low code" was big just before the AI thing. It didn't go well.
Attempts are outsourcing are constant.
Now we have LLMs. So far this has come the closest to the dream of eliminating expensive programmers. We'll see how it goes.
"AI" driven programming has a long way to go before it is just a better code completion.
A good number of companies out there move to google scale infrastructure and spin up whole devops teams when they would be fine without all that out of fear of having to move later. That later might never come.
Your presentation layer is probably always going to need to do some manipulation of the number anyway (put a dollar sign on it, etc) so using a decimal amount just for presentation needs isn't a huge win. But it will work too.
You get what you measure. Nobody measure software quality.
I'm genuinely curious to hear from people who have had what they consider effective management, what did the manager do to make your work better?
Slack claims it isn't a problem because the user doing the "ai assisted" search has permission to both the private and public data. However that data never existed in the format the AI responds with.
An attacker can make it return the data in such a way that just clicking on the search result makes private data public.
This is basic html injection using AI as the vector. I'm sure slack is aware how serious this is, but they don't have a quick fix so they are pretending it is intended behavior.