The snes to N64 jump to me is definitely the biggest. It wasn't just graphics, the gameplay completely changed too.
By the end of the snes era I had grown out of games due to endless platforms and 2d fighters (I was 13ish). I was 16 by time I started playing them again. Wave race 64 was just mind blowing. And like nothing else I'd played before.
On the using AI assistants I find that everything is moving so fast that I feel constantly like "I'm doing this wrong". Is the answer simply "dedicate time to experimenting? I keep hearing "spec driven design" or "Ralph" maybe I should learn those? Genuine thoughts and questions btw.
More specifically regarding spec-driven development:
There's a good reason that most successful examples of those tools like openspec are to-do apps etc. As soon as the project grows to 'relevant' size of complexity, maintaining specs is just as hard as whatever other methodology offers. Also from my brief attempts - similar to human based coding, we actually do quite well with incomplete specs. So do agents, but they'll shrug at all the implicit things much more than humans do. So you'll see more flip-flopped things you did not specify, and if you nail everything down hard, the specs get unwieldy - large and overly detailed.
> if you nail everything down hard, the specs get unwieldy - large and overly detailed
That's a rather short-sighted way of putting it. There's no way that the spec is anywhere as unwieldly as the actual code, and the more details, the better. If it gets too large, work on splitting a self-contained subset of it to a separate document.
> There's no way that the spec is anywhere as unwieldly as the actual code, and the more details, the better.
I disagree - the spec is more unwieldy, simply by the fact of using ambiguous language without even the benefit of a type checker or compiler to verify that the language has no ambiguities.
People are keen to forget that programming languages are specs. And a good technique for coding is to build up you own set of symbols (variables, struct, and functions) so that the spec become easier to write and edit. Writing spec with natural language is playing russian roulette with the goals of the system, using AI as the gun.
Everybody feels like this, and I think nobody stays ahead of the curve for a prolonged time. There's just too many wrinkles.
But also, you don't have to upgrade every iteration. I think it's absolutely worthwhile to step off the hamster wheel every now and then, just work with you head down for a while and come back after a few weeks. One notices that even though the world didn't stop spinning, you didn't get the whiplash of every rotation.
I don’t think Ralph is worthwhile, at least the few times I’ve tried to set it up I spent more time fighting to get the configuration right than if I had simply run the prompt. Coworkers had similar experiences, it’s better to set a good allowlist for Claude.
I think find what works for you, and everything else is kind of noise.
At the end of the day, it doesn’t matter if a cat is black or white so long as it catches mice.
——
Ive also found that picking something and learning about it helps me with mental models for picking up other paradigms later, similar to how learning Java doesn’t actually prevent you from say picking up Python or Javascript
I was going to ask the same thing. I'm self taught but I've mainly gone the other way, more interested in learning about lower level things. Bang for buck I think I might have been better reading DDD type books.
I'm sorry that just comes across as unprofessional, weak and passive aggressive. If someone started doing that on my team I'd take it as part of the case against them not a reason to fight to keep them. Also presumably that's in ear shot of other team members, it's disruptive to team morale. If you are serious about looking elsewhere, make it clear you want to stay but xyz is making you consider other options. Do it in private with the right people. Or say nothing at all.
This is an odd coincidence, I went back to Linux recently because win 11 driving me nuts.
Unfortunately I've got two problems that just seem unsolvable.
Unstable wifi network connection and temporary image retention if I use variable refresh rate.
I'm on mint Linux, Nvidia 1660 super, tp link usb WiFi. Other users reporting the same. Back in 2010 on another pc I had the same issues with WiFi on mint.
I don't have the time to mess with this stuff.
I'm considering win 11 lts. I really would prefer not to.
The only thing they've done is observe that the drug dealers outside their house weren't white.
reply