Here's a nice side effect of a bunch of developers falling irrationally in love with the MacBook Neo: performance optimization might be more front of mind.

I'm working on a little personal app that works great on my M4 Pro, MBP. Yesterday, I built the project on the Neo and suddenly realized that the performance is not nearly good enough on that device. This has led me to dive deeper into what the bottlenecks are and how I can improve them, and now the app is just faster everywhere.

Obviously, performance should always be on our minds as devs, but the incredibly performant hardware we tend to be working from can mask issues. Getting developers working on slower systems acts as a bit of a forcing function to get them to pay more attention to this, so that's nice.
@matt_birchler That's also a potential benefit of the rise of portable handheld PCs and RAMageddon...suddenly developers have a new motivation to actually optimize their games!

@matt_birchler Personally development has a few distinct stages that I have refined and followed for a number of years now.

The first is the most important - producing the correct answer/result. Later, much later, I work on optimisation. But that is much later in the dev cycle.

I write code for data analysis. Getting the right answer is also the single most important step.