To the contrary, the tools already make a material difference. I wrote 10k lines of code in the last 3 weeks--maybe 60% of that was generated by ChatGPT. Sure, I could have done it myself, but if it wasn't for AI my hands would have literally fallen off.
Instead of painstakingly reviewing the output of AI, just write a bunch of tests. It's something you would do regardless.
Reminds me of Resources from Scala. I keep seeing features being carried over from language to language--I wonder if we'll eventually reach convergence where all languages, perhaps within several broad groups like OOP vs FP, look the same with minor syntactical differences.
You're describing entropy. Properties and values distribute in the space until we reach equilibrium. Making all languages mostly the same. Unfortunately this doesn't mean we've found the ultimate programming language. We simply stopped innovating, believing there's nothing to innovate about (while actually we're in a local maximum).
In the 2000s, all the popular languages had C-like syntax and many had similar semantics. But now we're in a world with more diversity (Rust, Swift), so I think things are less convergent than they used to be.
And the thing that links those two groups of people is their desire for things. Never was religious, but this core point of Buddhism (from an ELI5, admittedly) really resonated with me. Wanting fewer things indeed seems to makes you happier.
Expectations are important and are missing from the equation here. Not everyone needs children, a fat pension or a large house to be fulfilled. It is also perfectly fine to be with the same group of people, have the same routines and the same hobbies for your entire life.
The less you want, the fewer milestones you need to hit.
I used to think my dad was boring because he never really wanted to do anything. Worked the same mid-level job for 30+ years, had no friends--just took care of us. A couple years back he passed away, smile on his face. Told me he did everything he ever wanted. Told me not to work so hard.
I think about this all the time whenever I'm stressed about claiming my "ownership in society."
That's a good point. Trying to attain milestones because of some absorbed societal pressure is a recipe for unhappiness.
But that's not really what this article says. If they had someone who said "I thought I needed kids, then I didn't and I'm totally happy with it" that would be aligned with that message. But to have someone who says "I didn't have kids until I was 50" is a bit dishonest, because biological realities make that almost impossible (for women, anyway).
It's really uplifting to show lots of examples of people who took a different path and found happiness in a less conventional way. It's less uplifting to show lots of examples of people who did the conventional stuff, but later in life, because statistically that is unlikely to be possible for most people who leave those things until later. It feels more like building false hope.
The article presents kids as an option after 50 for men, not women, and that’s reasonable. It’s a popular thing to do to draw similarities between decreases in fertility between men and women, but it’s not helpful. There’s a plethora of risks that increase for men, but they all go from “negligable” to “slightly less negligable”.
> The less you want, the fewer milestones you need to hit.
Doesn't feel like a good answer to the complaint that young people today can't possibly hit all the milestones their parents did, and their grandparents took for granted.
The same amount of life, the same amount of effort and dedication, in a seemingly improving and more advanced world, still buys you less life milestones than it did for your elders. If anything, this sounds like a social analogue of a textbook case of inflation.
In 1970, a US couple might have an “imaginarily fair” claim on 1/100Mth of America.
Now, that same age couple might only have a claim on about 1/167Mth of America. That’s about 40% less land or share of other inherently-constrained resources per American. Other countries have had more pressure on their populations.
It’s no surprise that “buying a big lot with a freestanding house” was a lot more attainable when there were 40% fewer people chasing that dream. Part of it is inescapable math.
Inflation adjusted housing prices were basically steady from 1950 to 2000. Yet the US population went from 150 million to 300 million.
It is surprising that for most of the 20th century housing was very affordable and then something changed in the late 20th century that culminated in two housing disasters in the 21st (the first is the housing crash and now a housing market that basically excludes all but the rich).
With interest rates consistently over 7% and sometimes over 16%, a simple price chart doesn’t tell the full affordability story.
When rates fall under 4%, house prices will naturally be higher in desirable areas because a lot of buyers are buying on monthly payment, not headline purchase price. Cheaper mortgages make for more expensive houses.
You said that the size of the population determines housing cost.
Now, when I showed you this is totally wrong, beyond any doubt, you changed the story. Now it's the interest rates that determine housing cost.
This is like trying to have a discussion with an antivaxer. No matter what they say, you prove them wrong, and then they change their story, pretending like the nonsense they said before never existed.
Look up a chart of mortgage rates. You're still wrong. Bye!
Huh, I never thought about it this way. I'm not 100% convinced this is valid math, but I can't find any obvious fault with it. Thanks, I have something to think through.
EDIT: in the 50 years since 1970s the US economy wasn't still - technology made huge leaps across all industries, and lots of wealth has been created. One would think this would offset the population growth, but it seems that it didn't.
Yeah, but people aren't satisfied with just any land. They want the same land everybody else wants in the big cities. They want to be near the population center, but the land there was already relatively filled back then. The computation naturally pushes the prices up to levels that most cannot afford it.
This makes housing into a lucrative investment, which probably drives prices up even further. Nobody wants to see the value of their investment fall, so they fight against anything nearby that would decrease it (NIMBY).
This is a good perspective, but I'm not sure I fully agree. I wonder if it's just that the nature of work, the nature of "what pays well," has changed.
Sure, my grandparents had a nice house, but they also worked the mines (literally). Would I say that the work they do is less effort than making $200k+ sitting in bed writing some code, while drinking Starbucks?
If you don't adapt to the times, you're going to have a bad time no matter what era you are in.
The mythical "middle class on easy mode" of boomers isn't coming back, it should be considered a historical anomaly. A vacuum in time where post-WW2 all but the US was in ruins, giving it economic free reign for a few decades.
That being said, I admit it's not as simple as international competition only. Quite a few life supporting institutes (healthcare, education, housing) are downright dysfunctional for various other reasons.
I'm not sure the "various other reasons" are unrelated. Give people a comfortable, secure life and they will be happy and productive. Chip away at that and you start to unravel every other part of society.
It's bad enough that we have to work for most of our waking hours for ~45 years, but this used to achieve a middle class existence and relative security, an essential basis to form a family.
Now you can be a working couple (twice as much labor as before) and struggle to achieve middle class basics. And even if you do, the world is so volatile that it can be taken away from you on any given day.
Expectations go both ways too. Literally like an itch, the more you scratch the more it will itch after the most transient moment of relief.
People tend to foolishly believe that their wants and desires are in some static container that once filled will lead to satiation as opposed to the reality that the more the container is filled, the bigger the container gets and at the same time it gets harder and harder to add to the container.
Hmm...is this really surprising to anyone? Yes, I'd like the purpose of a tech company to be to "make developers heroes," but in a capitalist society, companies exist to make money. I'm not saying I like it, but that's just the way it is.
I think developers have been treated extremely well--justifiably, I might add, given the profit some of these tech companies are making--but at the same time developers expect things from their companies that no one else would. Could you imagine your local barista complaining that Starbucks isn't giving them a free gym, free meals, transportation expense reimbursements, and making them heroes?
New is not always better, but many times it is. We see this for example in programming languages, where newer ones incorporate the best features of their predecessors.
I think there are two things to be wary of: 1) Selecting a new technology just because it's hot, and 2) Refusing to consider new technology because the old stuff "just works." A good engineer looks at the requirements and selects the best tool to solve the problem while weighing the costs and benefits. Sometimes that's microservices. Sometimes it's monoliths. Granted, I don't know anything about the developers or business problems at that company, but to say that Scala microservices are just bad without justification doesn't sit right with me. It's all situational.
If an engineer comes to me and asks to use something like Scala, he'd better know all the upsides AND downsides (e.g. effect and streaming abstractions, ease of long-term maintenance, referential transparency, vs learning curve, hire-ability, 100 different ways of doing things, etc).
If new is not always better, then you’re stuck with the really hard job of knowing when it’s worth moving to the new thing.
Worse, you’ll be blinded by survivability bias. One easily notices the good rewrites and can easily ignore the bad ones.
Even worse, bad rewrites may be noticed in a place that a year or two ago was deemed a success story. I’ve seen many such cases due to misunderstandings or just political dynamics.
And lastly, don’t let that Engineer do Scala, they’ll brush off the compilation time regression and make all developers lives slightly worse (assuming the project is big enough)
Yeah, good point--when I said new wasn't always better, I was just talking about the case where the new tech solves a problem, but it's not the one you have.
Like choosing GraphQL just because it's new, even if your data doesn't have the structure for it.
Will have to disagree with you on Scala for several reasons I won't go into here--but the point was just that, in order to make these arguments in the first place, you need to do your research. Seems commonsense, but surprisingly many people don't do it (including younger me).
