halis

Nice site though!

In these types of applications, there's already a lot of low hanging fruit to be had from working with an LLM.

If you're on a greenfield app where you get to make those decisions at the start, then I think I would still use the LLMs but I would be mindful of what you check into the code base. You would be better off setting up the project structure yourself and coding some things as examples of how you want the app to work. Once you have some examples in place, then you can use the LLMs to repeat the process for new screens/features.

  Very good article. I feel that corporate executives as a class are causing this huge mess from a simple lack of understanding of software engineering. Throw more bodies at the problem has never worked in software engineering, in fact that's a surefire way to make things worse and slower.
  Throwing more bodies + AI at the problem is even worse because the speed at which things get worse is much faster. If you have people that don't understand the implications of what they are doing, you're on the path of heading over a cliff some day.
  AI is a useful tool, when put into the hands of someone that is competent. They can fire junior devs and refuse to hire them as much as they want, this strategy will come home to roost sooner rather than later.
  If a C-level executive thinks that AI can replace their engineers, then I say do it now. Go all in and replace them all right now. Use only AI and a few VP-level AI whisperers and let the catastrophic failure that this will result in happen faster so we can get back to reality quicker.

In my opinion, they aren’t actually coding anything and have no amount of understanding. They are simply advanced at searching things and pasting back an answer that they scraped online. They can also run simple transformations on those snippets like rename variables. But if you tell it there’s a problem, it doesn’t try to actually solve the problem. It just traverses to the same branch in the tree and tries to give you another similar solution in the tree or if there’s nothing better it will give you the same solution but maybe run a transformation on it.

So, in short, learn how to code or teach your kids how to code. Because going forward, I think it’s going to be more valuable than ever.

They could fire you or your whole team and that won't fix the bug either, in fact, that will make it take much longer as they'd have to hire replacements that won't be up to speed.

I would work hard to solve the issue, keep my mouth shut and if it wasn't finished by the next day and someone asked me about it I would tell them about my progress but that I needed more time.

I would turn in my 2 weeks. If asked why I was leaving I would just give the standard fluff about new opportunities etc etc.

Talking about the manager is a gambit. If it succeeds, maybe they make your life there even worse by confronting your manager.

If it fails, then you look petty and disagreeable and maybe even get walked out the door.

Never burn a bridge, just in case. Leave on good terms, but leave ASAP.

¯\_(ツ)_/¯

But they can Google. They can study for interviews that quiz you on computer science trivia.

The interview process on the coasts is broken. In the midwest I don't have to deal with that shit.