Deleted Comment
@AGENTS.mdThe reality is that LLMs/agents are just a new way to write code. You still need to understand, more-or-less, how this feature is going to actually work, and how it needs to be implemented, from start to finish.
The difference is that you don't write the code, you tell the LLM to write the code. Once you've figured out the right "chunk size" an LLM can handle it's faster than doing it yourself.
I've found it's actually a little _harder_ in green field projects because the LLM doesn't have guard rails and examples and existing patterns to follow.
Deleted Comment
You’ll lose 90,000 of your 100,000 with one or more little nitpicks.
Probably 50% right off the bat because you chose a keyboard with or without a numpad.
Another huge chunk because you chose the wrong screen (Retina resolution? Low resolution? Refresh rate?)
Too bad, because I want this. Or at least the version of it I have in my head :)
The 3s have been an improvement on the 2s for me, especially in fit and feel in ear.
Personally, I quite like Kotlin, but I haven't been able to convince most of my greybeard colleagues to make the leap.
I like to avoid mixing Java/Kotlin within the same module when I can, but it still works, and parts of our codebase are mixed this way. (by module I mean e.g. the same Maven or Gradle module, i.e. try to avoid a situation where you have a `src/main/java` and `src/main/kotlin` next to each other)
Most commonly our software runs on premises on server-class hardware (or what passes for server-class depending on the industry...), sometimes hosted in the cloud, sometimes on "edge" hardware (think Raspberry Pi class power/spec wise).
One component of the software actually is a web frontend (and a Jetty backend) to go with it, but it's not your typical "web-app" and it's not SaaS. But there's much more to it than that.