497 karma · joined July 24, 2022
Pro baseball players report that they can see 90+ MPH fastballs clearly, down to details like the stitches on the ball. Zen martial artists also have claims of being able to react as if time has slowed down.
Nothing I've done on the job involves deep computer science. There are people who need to know that stuff, but they are specialists. Building CRUD servers or web frontends uses very little of what I studied in college, beyond basic understanding of data structures and algorithmic complexity.
I'm glad I learned CS, and wish I had learned more of it, but it should not be a requirement for getting a code-monkey job.
I could figure it out, but the issue is that it will take time, and it is stressful. A new college grad by contrast still remembers Data Structures 101, and how to manipulate trees. This kind of "bozo filter" favors both new grads, and people who spend a lot of time memorizing trivia in order to solve these problems quickly.
Looking at my career, it tanked at age 44, in 2007 due to the financial crisis, and has never truly recovered. Part of this is the reality of getting old. Age discrimination is real.
I am now 60, and still employed, but mainly with contracts, and even those have been difficult to get, in part because I am not a good interviewer.
My approach has been to focus on senior software engineering roles, even though that could be considered "junior" given my decades of experience.
All I can suggest is that you cram for interviews for whatever roles you are hoping to get. Read Cracking the Coding Interview, practice solving problems on Hacker Rank, cram for design and behavioral interviews, etc.
Yes, I had to practice doing l33t code bullshit. It is part of how we have to play the game.
From my experience meditating, one can go through stages of body paralysis, and then enter lucid dreaming states, while maintaining awareness.
Some advanced meditators claim to be able to be aware at all times, even in deep dreamless sleep.
I've tried doing a good job and asking for raises, they never match market rate.
There is no guarantee that your current stable job will not suddenly come to an end for many reasons. Outside of a few rare companies, there is absolutely no reason to stay, if they are not paying you market rate.
FAANGS are unusual in that they actually do reward productive employees.
I'm the top performer on my current team. After 3 years of no raises, I threw a bitch fit, and after a bunch of bureaucratic bullshit, I ended up with +6%. I have 0 stock or benefits because I am a contractor, which is a whole other load of shit I could complain about.
We subsidized the nuclear power industry for many decades. We also perversely spent $trillions subsidizing the fossil fuel industry.
What the author and others point out is solar lacked those massive subsidies. Had we spent the same amount on subsidies for solar power, as we spent on nuclear or fossil fuels, solar power technology would have advanced much faster.
Yeah, maybe if we dumped even more cash in to nuclear, we might have those cost efficient reactors people keep dreaming about. Or maybe not, because there are compelling arguments that nuclear power will never be able to compete against solar on price. Yes, I am aware that the sun isn't always shining...
Blocked threads are seriously bad for performance. Yes, Java 21 project Loom will help with that (finally), if people get with the program.
There aren't any race conditions, because our classes and data model are fully immutable.
The problem with our legacy servers was that the original devs didn't know what monads were, and decided not to use them. Error handling is now great, by using...
you guessed it, monads.
The snake woman by is shot by Deckards large calibre handgun, gets up and keeps running. Priss, when dying goes into a spasm of inhuman twitching. Deckard never does anything like that.
Deckard by contrast is nearly killed by Roy, who toys with him. Casually dislocates his fingers, causing excruciating pain. Then puts the gun back into Deckard's mangled hand.
In the final battle, Deckard is bloody and beaten, and actually loses against Roy. Roy I think laughs off some serious damage, including smashing his own head through a wall; at the end he only stops fighting because his time is up. This isn't "maybe a bit less strength". This is a kid fighting against Mike Tyson.
I don't look at it as Deckard being strong "enough to come out on top every time", I look at is as a human with a gun, barely surviving against inhuman opponents.
Of the top of my head: Voltron, Tranzor-Z, Starblazers. Speed Racer was being rebroadcast on MTV.
Harmony Gold did nothing to actually promote anime, beyond hyping their own products. Robotech was the English translated anime that happened to be on air in the US when the necessary conditions for the anime explosion were in place.
Those conditions were:
Affordable VCRs (in the 70s, they cost as much as a small car).
The Usenet / internet (for coordinating, sharing information, and creating tape sharing networks).
Low cost computer video platforms for subtitling (e.g. Amiga + Video Toaster).
In terms of popularity, people forget that Speed Racer, Kimba, etc were broadcast on network television, and had far more impact on popular culture than Robotech, which was syndicated.
Captain Harlock ironically what got me interested in anime in the late '70s. It was not widely broadcast in the continental US, until Harmony Gold's despicable hack job which came after Robotech.
One source of subtitled anime in the 70s was from Hawaii, which has a significant Japanese population. But to get that required having contacts with one of those very expensive VCRs.
IMO the monologue at the end was Roy coming to terms with the end of his life. There was nothing to be gained by killing Deckard. He wanted to be remembered.
Anyway, it is IMO incorrect to say that the book did not suggest Deckard might be an android, and likewise, the movie only hints that Deckard is a replicant.
Phillip K Dick's writing was all about mind-fucks and the difficulty of knowing what is true.
Today, Apple Silicon is smoking all but the top end Intel chips, while using a fraction of the power.
Every company I've worked for during the last 12 years gives out MacBook Pros. And I've been developing using Scala / Java for the last 20 years.
Employers manage Macs just fine, this isn't 1999. There have been studies showing that Macs have lower IT maintenance costs compared to Windows.
I admit that I haven't dealt with Windows devices in a long time, maybe there are some good ones available now, but I find your statements to be beyond belief. Apple Silicon Macs have blown the doors off the competition, out performing all but top-end Intel laptops, while using a fraction of the power (and I never even hear the fans come on).
Not all teams run tons of containers on personal computers. All our servers are running on AWS. I rarely ssh into anything.
I like the fact that OS X is based on UNIX, and not some half-assed bullshit bolted onto Windows. I still have bad memories of trying to use Cygwin 15 years ago. Apparently WSL is an improvement, but I don't care.
Mac runs all the software I need, and it has real UNIX shells.
AFAIK there is no rule in K&R requiring no braces for single-line blocks. In that situation, braces are optional.
The K&R style was hugely influential on Java and many other languages, it has nothing to do with green-screen terminals (I used those, as well as white and amber), it is just a style. I also moved on from vi, and use IntelliJ and Sublime most of the time.
The only difference between K&R braces and Java braces is that they combine lines on if-else. The Java guys did it because it enabled them to fit more code on to overhead slides. Overhead slide projectors predate green-screen terminals BTW...
The vampire capitalists did the standard playbook:
leveraged buyout.
transfer debt to the once healthy company.
extract yearly management fees.
fire and/or encourage many employees to leave.
shift maintenance to low cost foreign outsourcing company.
skimp on R&D and customer support.
In the short term, profits go up. Long term, the once healthy company slowly dies, as customers get pissed to the point they are willing to incur the cost of transitioning to a new vendor.Not only was this company once healthy, it had astonishing employee retention. We are talking many programmers and support people with 20+ years of specialized knowledge. People seem to forget how much productivity is lost with high turnover.
Since I am an introvert and on the autistic spectrum, traditional interviews are an uphill battle. Even reasonable ones like you describe.