My take away is that we may have a mild recession, but the likelihood of a massive recession is a lot higher than it has been in decades.
17,869 karma · joined October 21, 2008
https://twitter.com/zachaysan
www.zachaysan.com
My take away is that we may have a mild recession, but the likelihood of a massive recession is a lot higher than it has been in decades.
1. Hype around new technologies is sometimes warranted. Electrification, for example. It wasn't clear how long it would take for these weird new internet companies to really start turning a buck, but after a few years spreadsheet parameters were updated and the whole financial industry saw the writing on the wall for most web companies.
2. Many profitable and completely unfunded web companies primarily received their funding from other web companies that were. This set off a cascading reaction of bankruptcies and massive layoffs. Advertisers, publishers, tool makers, and many others were in this second category of legit business that lost the vast majority of their customers.
One of the downsides of an inflating currency is that there is a general feeling of "well I have to invest my money somewhere!" that is hard to overcome and leads to bubbles until the sky starts falling, so I agree with you that psychology is a factor; but the fundamentals still dominate in the medium to long term.
Look, I don't really care about money after a certain point. So I'm not trying to encourage people to do stuff for money. What I'm trying to say is that there is a world of software development renumeration that is achievable if you keep developing skill and it is far less challenging than dealing with a C++ codebase.
Even caller id is a major win on its own.
It's very doable and far easier than understanding C++ in my opinion.
My first win was baking a potato more than a month into it. Under normal circumstances I'm a good cook.
You sound depressed. Do the right thing with the employer and quit. Say you thought you could push through it, but you can't with the depression. It's not fair to make them fire you, even if you don't like it there. If you need financial support file for disability.
As soon as you possibly can, start working on something you 100% agree with. If you've always wanted to serve coffee at a cute cafe, do that. It doesn't matter how much it pays you can figure the money stuff out later. You are in full blown avoid-this-getting-any-worse mode right now.
I truly wish you the best and hope you make it through this. The day can be better again. I know how hard it is to believe this when it happens, but it is true. Do not give up.
Why not be an proficient Python developer and make the same compensation[0] with better docs, better libraries, better codebases, no compilation annoyances[1], easier to read code, and fewer not-defined-by-the-spec weirdness?
C++ would have to pay 4x what Python pays for me to even consider doing it again. It literally makes me sad when I write software in it. Especially the libraries.
[0] Mid-six digits as an IC is very doable in North America.
[1] If you want to count the occasional Cython thing, fine. Almost no compilation annoyances.
But for long distance, no thank you. I will not go back to the 90s just for that one reason alone. It was hellish calling across the Atlantic. Like 15 cents a minute with a 1.5 (sometimes 2) second delay between speaking. And having to remember the dialling sequences and complexity around looking up foreign phone numbers, both of which are now just built into the cell phone.
Or having to trudge around in the rain for a phone booth and having to page through a worn out phone book just to make some dinner reservations. Yuck. I'll take the bluetooth shenanigans, thank you.
If you're doing:
SELECT * FROM serious_money_table WHERE user_id = :user_id;
How is it all that different with Redis? Someone can mistakenly send in a :customer_id when writing records, but I don't really know anyone out there that also stores user_id into every table they query user_id from.Something like: user_profile_bio.[user_id]
If that returns the wrong bio from Redis, then something is broken in Redis, no? Or are you suggesting that I create some sort of format that duplicates the user id in the data itself?
If you want to argue the Drake equation on its own, that is cool, but it wasn't what I thought OP was talking about. My central argument is that if we are first that is pretty unlikely because we have 1000s of intelligent species and for us to be first of many on our own homeworld in addition to being first in the galaxy or beyond is much less likely.
That said, I could see an argument being made for combative intelligences coevolving increased intelligence and this being the counterpoint to my counterpoint. Though I don't buy it.
> our existence now is so unlikely that it's possible that we actually are the first. Something has to be first.
When the OP said that ^ I took we to mean humans with technology, presuming the OP meant that we were somehow special. Basically I took it as him saying that we're first because we're lucky so my argument was:
> How are we lucky? Look at all the other intelligent lifeforms on Earth! Surely the lucky winners would have had some sort of fluke that made them one of the few with intelligent brains on their planet! This could have easily happened sooner on Earth!
If the OP meant that life itself was extraordinarily rare on any given celestial object then that is something I don't consider especially groundbreaking since its part of the Fermi Paradox formula in its basic form the precise value of which has been debated for years and I do not find convincing.
The military has to plan for the full range of the scale, from small brush fire near a minor ammo depo to full blown WWIII. But the part that is 75% towards full blown WWIII is so often overlooked by commentators it's like it doesn't exist. I could come up with 100s of scenarios where most of the internet works but there is a recently-started nuclear war. (India vs Pakistan, for example.)
As for number two, it's hard to comprehend a response that is reasonable because our cognition may be part of the "disturbing reasons" right?
The theory I more and more think is probably right is that there is some major aspect of the universe that we get wrong. What is more likely, humans thinking they understand something when they don't or that no life form was able to spread amongst the stars in billions of years? I have plenty of lived examples of humans with false knowledge.
It's a sort of meta Drake equation. [Likelihood humans are not as wise as they think they are]*[rest of drake equation] and I think the drake equation, as stated, correctly leads to the term "Paradox" given the conventional understanding of science as communicated by scientists.
As for reference checks: If a reference is on a resume that I've been handed by a candidate or that candidate's agent I check it. Glowing references really highly correlate with job enthusiasm and honestly most developers don't list them anyway, so even having one that's positive without being glowing is a good signal.
I don't know what is going on with Italian olive oil these days, and maybe I've just had a bad couple batches in a row, but it will take a long time for me to trust it again. It almost always tastes diluted with other oils to my pallet.
It's a giant forest of tiny little details that scientists talk about. There is nothing close to the "we're all on the same(ish) page" that software developers have. The example I went with was one I had some partial familiarity with as a former structural engineer, but ever that I found boring, let alone what type of enzyme a specific frog in the amazon uses to evade the poisons of a given snake.
The graph is too large for science to have any sort of meaningful discussion these days.
Do you want to hear about a 1mm thick polymer when overlaid on a w-section of a certain size and brought up to a certain temperature has certain properties that make it better for loading patterns of structural members of a floating ship?
Me neither.
HN works partially because almost all of us code and almost all of that code, code at least some of the time with concern for the network. This unites the focus to certain types of companies and subjects.
Scientists go down their own, squirrely rabbit holes.
Data science.
In the past (around 2010 to about 2018) I did the web stuff in Rails and communicated through the database for the ML stuff I needed from Python, but even though Rails is better than Django, these days Django is good enough and it isn't worth the tooling and the employee dual lingual requirements to justify both.
It sucks and I wish I could use Ruby more. I agree Ruby and Rails are both better than Python and Django on their own, but the scientific computing part of Python is just so phenomenal that there isn't really anything to do about it anymore other than to accept it.
Ruby is like Elivish. It's poetic and beautiful and consistent where it counts, full of symbolism and grandeur, but in a world of dwarves, humans, and orcs it just isn't useful enough to justify making an entire team learn it.
Since you're quoting Lewis and mentioning prayer, it's at least debatable whether we're all going to die, depending on your understanding of 1 Thessalonians 4 and how it relates to John 12 and other parts. :)
But I agree with you. Arms control is useful and people should work on it, but for those that don't feel called to worrying about nuclear war isn't productive.
Still cool though.
This isn't my invention. This has been used before in a limited form at Dribble and it worked to keep the riff raff out.
2. While there, consider if burnout is partially your subconscious telling you something. A lot of people, myself included, have gone through phases where we later realized that the joy in learning how technology is made has faded and the mission that we're attached to doesn't actually align with what we actually want to do. Sometimes it's ok to quit a six digit position and take a five digit one if it means it fulfils some longing in our life, like help a friend, help the poor, or safeguard the world in some way.
3. See if there are aspects of your life that you may, deep down, want to change but that you're avoiding changing. For me, it was excitement. Note that these are different than mission in that they're self or at least family directed. Be clear eyed about the risks, because ultimately you are responsible for the choices you make, but don't be so cautious as to be cowardly. If you want to fire a gun at bad guys, first understand that they may fire back, but ultimately if you still think it is the best call, to not do so is cowardice.
4. If nothing above works, just start helping the least fortunate. It has a double effect of reminding yourself, viscerally, just how bad it can get[0] while also providing your mind with a sense of community and purpose.
[0] I met a former programmer at a soup kitchen who just had a run of bad health and life issues.
I do not think every weakness is a vulnerability. Were it so, then all things are vulnerabilities to some agent or entity in some sense, since weakness is often defined in relative terms.
If another system is easier to use for say, signup. Then of course the system I propose will have to leverage its strengths to make up for the fact that it is harder to join. But there are plenty of nightclubs and restaurants that one can just simply not get into unless they know someone. They're often the most acclaimed.
If the system I propose leads to a celebrity's ouster then the mechanisms and business orientation of the system would need to leverage that ouster to its benefit after, of course, making sure that the system as designed only ousts truly irritable people.
One may say, "but if a given celebrity attracts many people and their ouster would lead many of them off of the platform how can this be used to our benefit?"
But it is precisely this dynamic that the system that I advocate for has as its chief strength! Those that would leave merely at the call of a scorned leader despite having a more fruitful and productive conversation on the platform are those that are most probably least likely to positively engage with the platform in the first place.
Not more so. Vulnerability is a function of defensive capacity. There is no reduced defensive capacity. If anything, knowing who invited whom can allow one to allow web-of-trust based checks on suspicious login, allowing for more stringent guards.
> For a first approximation, even if one user can only invite 2 users, exponential growth will mean that bots may still pose a problem.
In these types of systems users earn invites over time and as a function of positive engagement with other trusted members. Exponential growth is neutered in such systems because the lag for bad actors and the natural pruning of the tree for bots and other abusive accounts, leads to a large majority of high quality trusted accounts. This means that content flagging is much more reliable.
So, yes, bots are still a (minor) problem, but the system as a whole is much more robust and unless there is severe economic incentive to do so, most bot operators understand that the lower hanging fruit is elsewhere.
It works just fine if you're willing to move to an invite only system and ban not just the bot, but the person that invited them. Possibly even another level up.
The problem with this system is that it leads to much less inflated numbers about active users, etc. So very few companies do it.