Usually organizational changes are massive efforts. But I guess hype is a hell of an inertia buster.

I don't think they're being snarky.

Also if you're organizationally changing the culture to force people to put more effort in writing the code, why are you even organizationally using LLMs...?

It doesn't say anything about what it's backed by.

If unity gets you making the thing or making the engine gets you making the thing, most important thing is motion.

You gotta avoid the paralysis and just pick the thing that seems feasible and start typing ;).

> Do your job

Which is a volunteer based job lol. Even if it was said in a heated argument, the bug reporter never really apologizes from what I read.

Maybe that's a "strawman" though

It basically helps a ton of engineers work together efficiently which honestly is bigger than the compute cuz you can always throw more compute at all problem these days anyway.

I don't think typing is necessarily to prevent bugs either. It's to reduce the cognitive load of writing code. Others mention that intellisense and LLMs work better with types. Types do a lot more than catching a runtime error of a method not existing.

I am curious about Odin, I'm mostly a go dev so getting something without the GC and go schedule that writes similarly is really interesting to me.

> Does your personal project make money and/or need to be launched quickly?

This makes it clear that you understand why the language would be chosen in the first place, so not sure why it's not clear that eventually requirements change and you need a way to iteratively improve things while still shipping things.

I tried using an LLM to help with a small hardware project and ended up throwing out all the code halfway down the line and doing it myself. I don't have a good time with LLMs and mostly only use it for work.

You're right that a lot less people will be writing code like a lot less people are sewing these days but people still do it for fun.

P.S.: I really enjoyed reading moonbound :)

You both are agreeing with each other.

I was really curious about how it helped you iron out the problems but couldn't figure it out from your description

You're arguing that the standards for medical device firmware should be the same for Pinterest which is honestly just a waste of and effort.

I can see both sides of this specific discussion but treating SW engineering generally as rocket science is lying to yourself ;)