kalcode
Joined 9 years ago
Joined 9 years ago
Sigh... HN littered with it these days.
I think others need to embrace that too. Your work can be fun, and can be a joy. But that shouldn't be folks only outlet for themselves to measure.
At one point in my career I was ONLY reviewing and guiding off-shore contractors. It felt even worse than LLMs. But I did enjoy it though, but going to LLMs didn't drastically change my workflow. LLMs feel like leading a bunch of juniors with no real stake or business context.
So for me it didn't fundamentally change things, it just meant I could steer the progress before a PR is created later in the week that misses the mark completely.
There were plenty of other issues in the software development business that sucks the soul of creating out.
So I think you asking the right questions. Cause I felt like I've asked myself those questions even before LLMs.
This video helped me recently too [1]
Also I take pictures and have Gemini critique, give feedback. It helped me learn about the tips more I didn't realize, after switching my tip from a broader knife one to a chisel one, results way better (for that use cases)
Then I did know I just had to practice and get frustrated and come back, felt like two steps back and one forward, one time I was just suddenly making cold joints left and right. But hours practicing can't be replaced by just reading.
This is more answering the title.
But now game development has much better tooling and SDK kits for a while in consoles. So I suspect there wasn't a need to spend extra development cycle implementing custom debug menus and stuff.
We are making the kids endure that out of fear of their college, but stats don't back up the grind they make the kids do.
Software is fast to iterate and test that a lot assumptions can be proven by actually writing the code.
Software is closer to gardening or painting. We discover a lot through practice and writing code. Then we can often write more formal specifications.
But formal method is impractical for most software upfront, and instead is likely used for more serious runtime failures or cost of life.
That's just my two cents.
So their are apps that do use similar or ECSs architecture under the hood, it is just more problem related not a solve everything solution.
You get the best of both worlds, better language than XML/HTML and yah, you can deliver only HTML since the consumer typically doesn't need all that JavaScript, spa stuff. The Island Architecture.
Feels like a good in-between. Good DX for me, great UX and mostly HTML with some JavaScript sprinkled and fallback for users.