Love me some nonsensical medieval illustrations. Compare and contrast to 2023 illustration of Blemmyes (from a game I was working on a couple years ago):
One only needs to look at Horizon: Zero Dawn to note that the truth of this is deeply uneven across the games industry. World streaming architectures are incredible technical achievements. So are moddable engines. There are plenty of technical limits being pushed by devs, it's just not done at all levels.
It's been very easy to observe acceleration in progress over time, and there's a natural question that emerges: Will we reach a point where people can't keep up?
Nothing hand-wavy or silly there. And the discussion of the topic as it was formed in the second half of the 20th century was pretty carefully couched in terms of what-ifs and conservative projection.
There's a lot of speculation in there, but it's pretty carefully couched in scientific terms, and particularly in what-ifs that satisfy even the most stringent demands for conservative thinking.
The singularity in this context refers to the point beyond which predictions will fail because we cannot possibly foresee the consequences of certain technological changes.
There's nothing historical about it; it came about as a result of a few different science writers looking into the future and wondering how we keep up in an accelerating technological context.
I actually agree that it's become something else, but the origin of the term was what I was correcting, and its origin isn't something woo-woo, it's firmly based in scientific speculation.
Um. The Singularity isn't religious in its origin. It's literally a reference to a mathematical singularity.
I'm not entirely opposed to the article's characterization, but this is a big one to get wrong. What the term has become in its pseudo-cult modern context is entirely divorced from what it came out of.
I was making short games. Specifically I was trying to make games that packed the same density of concentrated entertainment as other media.
The abridgement thing sounds like a smart approach, but ultimately I've gotten more enjoyment from shorter games that don't pack the fat in to begin with.
There are visualization techniques that help with the washing over, but there's also the advice, which CBT therapists do give but randos on the internet always forget, that sometimes you're having anxiety (or another "negative emotion") for a reason, and it's a bad idea to ignore it in those cases.
If you want to get better at the "washing over" thing, maybe try visualizations like:
- As you breathe, imagine you're pulling over to the side of the road and watching your anxious thoughts drive past.
- As you breathe, imagine taking each anxious thought and placing it on a leaf on a stream and watching it float away
But in general, security theatre is kind of a legit reason to feel anxious - these folks have real power over you and can screw up your life - so it's ok to just feel it in those situations.
You sound like you've never had an issue, and hey, congrats, but let's not pretend that there aren't plenty of horror stories and legitimate reasons to worry. And suppressing legitimate worry is a bad habit, particularly for folks who don't have white, male, and several other "default" identity markers in their profile.
A buddy of mine introduced me to the concept pair of Fluid and Crystallized Intelligence. That's the short answer to your question. An older dev will have more accumulated experience and will be able to make decisions based on experience much better, but a younger dev will adopt new tools and learn new frameworks faster, and the latter tends to be the heavier load for the average job-lifetime (say 2-5 years) in the modern tech industry.
Nothing about the world's rich folks suggests that they, as a class, are in any way genetically superior to anyone else. Nature vs nurture leans 90 degrees towards nurture.
It's pretty annoying that this person would have the gall to hitch dead artists to his dead horse when many artists are trying very hard to explain that, in fact, mental illness for the vast majority of them is just a plain old problem and not some mystical insight engine.
One tip I have from years in a company that was undergoing major changes in its business model is to pay attention to other workers. In my case, the shop floor guys at an automation company smelled the shift in the wind long before anyone else, and weren't afraid to call it out. When the vast majority (maybe 500-1k machinists) were let go in rapid succession, it was shocking...except if you'd paid attention.
But it's a comparatively huge pain in the ass to use a lot of government services where I live without a smartphone.