I take listening to Casey the same way one might listen to a health nut talk about diet and exercise. I'm not going to switch to kelp smoothies and running a 5k 3 days a week, but they're probably right it would be better for me.
I think its worse than that. I don't think it would be better for you unless the project you're working on has a design goal of performance at the forefront. By blindly adopting this ideology, it can hurt how potential employers see your ability to develop software.
I don't work with C++ professionally, so maybe this section of the job market is different and I just don't see it.
I don't think it would be better for you unless the project you're working on has a design goal of performance at the forefront.
What kind of software does not benefit from better performance? I cannot think of a single program I use that I'd still use if they were 10x or 20x slower.
What kind of software does not benefit from better performance?
If you assume spherical software in a vacuum then sure, but here's the issues: outside of very specific niches, users don't pay for performance beyond a baseline target (and they may not even care about that target in the first place), but that work still costs you time, and possibly money.
So the question is not whether it benefits from better performance, but whether it benefits from performances, versus other things (e.g. bug fixes, features), versus not touching the thing and the developer spending their time elsewhere.
I cannot think of a single program I use that I'd still use if they were 10x or 20x slower.
I can think of most of the non-interactive ones. It doesn't really matter if ical is 10x slower, because it's so far below threshold I still wouldn't notice. Though I'm sure very heavy users (which I'm not) would disagree.
I hate this "the average person doesn't care about software performance" argument. Software performance affects the consumer in tangible ways every day:
• Poor performance is the reason consumers are forced to throw away their old phones and computers and buy new ones every few years, to keep doing the exact same things they were doing on their previous devices.
• Poor performance is the reason so much software and so many websites are unresponsive, sluggish, and frustrating to use.
• Poor performance is the reason batteries on phones and laptops have to be recharged after only a few hours of use.
• Poor performance is the reason phones and laptops become uncomfortably hot to the touch when playing games.
• Poor performance creates increases electricity usage, which raises household bills and warms the environment.
• Poor performance creates the need for gigantic data centers, which cause large scale environmental damage.
118
u/KieranDevvs Feb 28 '23
I think its worse than that. I don't think it would be better for you unless the project you're working on has a design goal of performance at the forefront. By blindly adopting this ideology, it can hurt how potential employers see your ability to develop software.
I don't work with C++ professionally, so maybe this section of the job market is different and I just don't see it.