skysight-inc/HackerNews huggingface dataset:
It _is_ an improvement.

If you just do "Map.get(x)" and you get null because your thinking was wrong, then the NPE will pop up potentially 10 layers later or an hour later, when the null-value was tried to be used in your program.

On the other hand, with "Map.get(x).orElseThrow()" you will have an exception thrown immediately! Even better, you should customize that as "Map.get(x).orElseThrow(NoSuchElementException(x))" so that you know the value that was unexpectedly not in the list.

That will make debugging much easier and will potentially fail a test case while a "Map.get(x)" might not cause the test to fail.
The unsolved mystery of the Earth blobs (2019)
IANAL and all the requisite disclaimers, but GitHub explicitly recommends that you use one free account for both personal and work stuff, and there's fairly granular organization-level access controls built into the platform to keep those things separate. If I have a personal GitHub account and FooBarCo adds me to one of their GitHub organizations, that does not magically make any repos I have access to that are not part of their GitHub organization the legal property of FooBarCo.
That's me.

After five years out of the rat race, you couldn't drag me back with a locomotive. I just turned down a fairly enticing prospective offer this morning. I was flattered, but I'm really having a blast. The money would be nice, but the aggravation would not be nice.

I didn't actually want to be here. No one wants to work with us "olds," so it's not like I had a choice. I could have gotten a job, but the only companies that showed any interest, made it clear that I would be treated like garbage.

I've been amazingly productive over the last five years. It's crazy how good things are, without middle managers (Disclaimer: I wuz one) pissing all over my work.
Except the vast majority of them own property that they originally purchased for under $50k which, if sold, would net them hundreds of thousands or even millions of dollars. Many of them are on pensions (something that doesn't even exist anymore), plus they receive social security payments.
The other side of the coin is that we are getting better tools. Vue 3 with the composition API is a lot easier to work with, reason about and maintain then the legacy API.

However the real counter argument is that vanilla javascript apps are also easier to write these days. If you have only a small interface to something that you have to maintain but only infrequently, perhaps a vanilla app is better suited. Vue apps are better suited if you want/need to a) get things running quickly (e.g. a prototype) and/or b) have a team of developers which need to maintain a large codebase together.
What's the point of striking in the globalization era? The number of hungry would be workers that would gladly take 1/10th the meager salary of a Western worker is in the billions.

What's to keep John Deere from uplifting the whole plant and shipping it to, for example, SouthEast Asia? Note that this is a long term lose-lose proposition for both workers and capital, see ARM China debacle for a textbook example. Alas I see no medium term disincentive on the horizon.
That took me too long :)
Back when I was originally doing web development I wouldn't have touched JS but I actually quite like it now. It might just be a sign of early-onset dementia though.

I doubt that I would have enjoyed developing in JS before JQuery or the new extensions added in ES6
Everyone is saying they could have gone to X, Y or Z instead of going to OnlyFans. IMO this decision to host on OF was very deliberate. Had they gone to any other platform no one would have raised an eyebrow. But because they went to OF everyone is doing a double take because of OF's reputation.

They knew (rightly so) that if they opened an OF account, they would get a bunch of free press and bring more eyeballs to their artwork.
There's a difference between "software developers" and "FAANG software developer" though, which is a source of great cognitive dissonance when people see that industry averages are only slightly above $100k/year but FAANG compensation is like 3-4 times that for basic engineering work.

Both are paid a premium, but FAANG is paid a massive premium, and there isn't much precedent for collecting that massive premium continuously for 30 years.

EDIT: Actually in that spreadsheet I would argue that the $250K compensation is too low, the 10% return on investment is too high, and the 30 year timeframe is not sustainable.
Deer goes through waves of big profits then loss. Looking at the last 4 quarters doesn’t give you the full picture.

https://www.macrotrends.net/stocks/charts/DE/deere/revenue
I've been talking about this for a minute. Boot camps are pushing the "you can make tons of money in just 4 weeks" narrative. CS skills are ironically becoming a huge differentiator. that's why I've been indiehacking on https://qvault.io
Women are not being leaders in math and technology. They are getting PhD in non technical things, but tech is what is leading the world.
> so I tried to provoke some questioning of that assumption, and got blocked for my trouble. Certainly she had the opportunity to clarify at the time if that wasn't what she was talking about.

What would be the point of clarifying to you if you jumped in with those assumptions? She doesn’t owe you anything. Blocking someone like that seems like the right call.
I think combinatorics might be more relevant here.

I'll note that I mentioned basic topology in my reply, because topology does indeed have deep connections with type theory that most formal verification systems are based on, interpreting types / theorems are spaces, terms / programs / proofs are continuous functions within them.[1] But basic undergrad topology typically studies more well-behaved (read: more like the real number line) spaces than this.

[1]: https://www.andrew.cmu.edu/user/avigad/Talks/fields_hott.pdf
One of my elderly grandparents has a pension from doing what would today be considered a "gig economy" 1099 job (was W2 w/health insurance and a retirement account back then), and this has payed enough for him to live off of for the last 25 years of his retirement. He get's $1800/month because he worked as a bag boy 30 years ago. It's nuts.
Another thing that boomers didn't have is access to information. These days everybody can learn anything from the web but in the pre internet era there was no way for people to know how to manage their finances unless they had someone close to them who guided them. Even then, predicting the future was always very hard.
> There are plenty of opportunities for young people to get rich.

Can confirm. I was directionless in life until I read a comment on a message board about working from home on Google with the potential to earn $5,000/week. I made my first million in a year and a half by investing the earnings from that into meme stocks, pink sheets stocks and SPACs I found on Reddit while living at home with my parents.
They probably will be, what will be (truly, materially) different?
Don’t install a UI toolkit dependency because you heard it’s the new hotness on Twitter?
Not saying you're wrong, just playing devil's advocate that you could say $4.3T was worth a lot more in 1989 than $7.5T in 2021 based on the outsized pace of inflation for necessary goods to continue living well and growing your personal wealth (homes, healthcare, education). It all depends how you define inflation, and arguably the method to weigh inflation currently does not reflect the growth of those previously mentioned items accurately when compared to their importance.
I agree strongly and think once you regain your fear of dependencies the JS ecosystem actually isn't that bad. The kinds of packages that save me months or years of work are generally of reasonable to great quality, it's packages that (theoretically) save a couple days or weeks that tend to be the real stinkers.
Hmm, is that just because of the template resolution? (and so wouldn't apply to constexpr in C)

AFAICT, something about the template declarations is making the call of f(x) to be "who could know" (which should just be fail).

The same thing with concrete types says that f isn't constexpr [3]. And you have to make it actually constexpr by removing the static from counter [4].

[1] https://docs.microsoft.com/en-us/cpp/cpp/constexpr-cpp?view=...

[2] https://godbolt.org/z/7rGWbP1xz

[3] https://godbolt.org/z/5WjMr3Kjv

[4] https://godbolt.org/z/v9rc1j9zc
At it's heart, FIRE is a reaction to how tenuous, unsustainable and unstable the job market has become in recent years. I don't particularly want to sit on the couch and binge Netflix, but I have such low faith that I'll be able to maintain decent employment that won't destroy my physical and mental health till the age of 67 that FIRE is a completely reasonable thing to aim for. The only unreasonable thing is the core assumption that past performance is a guarantee of future results. Oh well.
To improve locality it has to be on the same cache line, effectively linear probing
Well, for example here, just how large is the social impact?

And where it is large, and here it just isn't, why?

As for tweaking...

What center? Along how many axis?
It isn't just JS apps that are like this though. I had to redo a site for a client a few years ago that was done in some horrific php CMS that had a whole site management architecture applied overtop of it. It was a nightmare to even change a page.
Absolutely! People really don't understand the scope of the rot.

The LA Unified District has 25K teachers...and 50K administrative staff. Moving onto universities, Penn State has 8000 Academic Staff... and 17,000 administrative staff. The bloat is obscene.
I am sinking in debt thanks to my college, and you think boomers have that problem? No, they don't, and I wonder how old you are considering your views -- I honestly don't think you know any boomers with views like this, considering your only argument is the ones at grocery stores. My grandfather worked at a grocery store for 30 years and has a pension still going to this day. No jobs have pensions anymore. And I bet all those boomers working there have houses, but we Millenials cannot even get a down payment for a home. But sure poor said difficult life of the boomer.
·Saying "there is no such thing" does not make it true. What are you? 10?

·You should be able to look whatever you want, even old.

·I`ve been in lots of situations where the first thing the hiring manager asks is the candidate age and drops the CV as soon it finds out is older than 35.
well you can always write your own framework. I'ver had to do that a few times and the main benefit is that it fits your coding style and you're the only one that can break it.
It depends upon the OS.

I find that it is reliable for Linux and Windows. It is easy to copy an ISO onto a flash drive, it can store multiple ISOs, and those ISOs can be updated without overwriting other data on the drive. This means application installers and data backups can be stored on the same drive, making it a very convenient recovery drive.

As for other operating systems, they seem to boot partially but the boot process ultimately fails when they try to access the drive directly.
You should really talk to someone about this, because you attitude of “I missed out on an internship, so my life is ruined” isn’t healthy.

People at FAANGs don’t “own the company by any means any more.

And the fact that you have a job (and probably a good job in software) shows how privileged US developers can be.

Having an office job, in a growth industry, in an in-demand field, in a country with lots of opportunities is a huge privilege that most don’t have have.

Sure you don’t work at an ad-tech FAANG company earning obscene rates, but it’s not the end of the world.
Shipping large equipment isn't easy, it doesn't fit in a standard shipping container, and there isn't enough demand to make custom ships (cars get custom ships )
d) Ramp up population to 20B people.
I believe the United States slow walked its own Prompt Global Strike [1] program because it was perceived to be needlessly escalatory [2]. That sounds like sensible policy making.

[1] https://en.wikipedia.org/wiki/Prompt_Global_Strike

[2] https://web.archive.org/web/20121220071303/http://defense.ao...
Even ExxonMobil by itself does not contribute more than 0.00001% to the total global emissions, and they keep our infrastructure running.

So I guess nobody has to do anything about climate change since they individually represent a tiny fraction of the problem.

Then why do the peasants pay renewable energy tax?
Beans have to be carefully processed? I soak them in a half-gallon Ball jar for at least a day, but that's pretty much it. I usually swap the water out a few times because I procrastinate pretty badly when it comes to cooking and the water gets murky after half a day or so. If I haven't cooked them by the next morning I toss them in the fridge so that they don't start smelling sour.
What have I been neglecting to do, and when should I expect it to kill me?
Wow. Wagies must HATE you! Where can I click to learn your ONE WEIRD TRICK to early retirement?
Unfortunately, laser printers have chips counting the lifetime too, e.g. https://www.google.com/search?client=firefox-b-e&q=Samsung+M... . Or the HP logic bomb mentioned above: https://news.ycombinator.com/item?id=28889672 (it was actually a logic bomb, as the check was AFAIK activated several months after the FW upgrade was released).
Yeah, while I think the blame lies on both Vue and the author, I feel like the author is shifting too much blame off of himself.

Vue messed up because eslint wasn't pinned I assume (looks to be pinned now at ^6.7.2, so it shouldn't happen anymore) so upgrading gave you an incompatible eslint version.

Author messed up by blindly upgrading all dependencies, jumping major versions, and expecting everything to work fine without putting in work to double check. Yarn even has a kind of `interactive-upgrade` command that shows versions/links to changelogs iirc. There is also documentation for upgrading project dependencies at [this link](https://cli.vuejs.org/guide/installation.html#project-depend...) that I came across while playing around with vue cli.

I took the liberty of generating a Vue 2 project and seeing what dependencies are in the package.json

"dependencies": {
"core-js": "^3.6.5",
"vue": "^2.6.11"
},
"devDependencies": {
"@vue/cli-plugin-babel": "~4.5.0",
"@vue/cli-plugin-eslint": "~4.5.0",
"@vue/cli-service": "~4.5.0",
"babel-eslint": "^10.1.0",
"eslint": "^6.7.2",
"eslint-plugin-vue": "^6.2.2",
"vue-template-compiler": "^2.6.11"
},

I don't think it's too bad if you've ever seen create-react-app unloaded or whatever, although I've never used Vue so I could be missing the equivalent unload step that generates a million more dependencies.
You lived the NEET dream.
> What's to keep John Deere from uplifting the whole plant and shipping it to, for example, SouthEast Asia?

They already would have decades ago if the labor cost arbitrage was worth it.
I'm a huge TypeScript proponent, but it took me a long time to get on board because getting it into an existing project structure is not easy. I don't even mean the translation portion (which you're also probably doing as you first learn the language), but the configuration of the tool. There are a lot of options and none of them are labeled "please just find my missing dependencies. I can see them right there".
>" I literally don't understand how people can even do it."

While I definitely appreciate types and normally work with the languages like C++ sometimes I do some front end JS libs and frankly do not have any mental troubles using plain JS. As for whether it is "safe" - all that matters to me if it works to specs and the customers are happy. Since I am programming since like forever I guess I've got enough discipline, common sense, knowledge and experience to produce decent code.
I see so many job postings for “fresh grad” roles. I interpret them as “we’re not going to pay very much, so take your senior skills elsewhere”. Current company hires a lot of fresh grads and interns, not always a good staffing decision for the projects since they need a lot of mentoring.

Are we about to start swinging back to the “nobody hires really experienced devs because they’re too old/expensive” discussion soon?
I can definitely appreciate rants like this, and I think anyone who has been in JS development for a while has hit some sort of dependency incompatibility headache like this. That said, I'm also always left a bit annoyed when the author isn't really introspective to think about what benefits came with the environment he is bitching about.

As much as everyone loves to complain about "dependency hell" in the JS/Node ecosystem, the fact that there are tons of high quality (or, at least discernible quality) components, largely for free, is something that really didn't exist before say the mid '00s. I'd also highlight that "component reuse" was literally the holy grail of software engineering for decades prior.

The simple fact is that to get the benefit of a very robust dependency ecosystem requires more work managing those dependency versions. Running the equivalent of `npm update` on a regular schedule is pretty much required lest your dependencies get too far behind, and then when you are forced to upgrade due to a security issue you find you have tons of backwards incompatible changes.

I'm not saying things like NPM can't be greatly improved, but I think it's important to acknowledge the benefits that the JS ecosystem provides.
> Deer goes through waves of big profits then loss.

No they don't. There's no magical set cycle of outsized profits and losses waves for Deere. Globalization and the world adding 80 million new people per year has created a potent demand for their product, which is why their sales have done well over the last ~5 years ($26b to $42b) - there's another 400 million mouths to feed in that time and another billion more on the way. And those people have more money to spend on calories than past generations. It adds up to the world needing a lot more farm output and a lot more farm equipment.

> Looking at the last 4 quarters doesn’t give you the full picture.

I wasn't only looking at their last four quarters.

Their last five fiscal years have been stellar in fact and getting better by the year. Covid only barely slowed them down. This past decade has been the best, by a dramatic margin, in the history of Deere.
You mean Hindu religious/fusion music or Indian music?
In terms of raw wages, it seems like overall the millenial generation does have either lower wages or higher debt than the boomer generation. Page 16 (table 2) compares wages from 1979 to 2019: the wages have gone up for college grads but have gone down for non-college grads. [0] Do note, of course, that to get those college wages, most students needed to go deeply in debt.

In terms of the larger economic environment, the boomers were generally born and raised during the Golden Age of Capitalism [1], but they likely entered the workforce around the time of the early '70s recession. However, the '80s and '90s appear to have been good times to have a job, but as each year went by, it became less and less good to have non-college jobs as the stats above show us. For millenials, the non-college jobs have been objectively worse in terms of pay, and the job opportunities that did exist were hampered by the .com bust (more a Gen Xer hindrance), the '08 bust, and of course, the covid shit show.

[0] Wages: https://sgp.fas.org/crs/misc/R45090.pdf
[1] Golden Age: https://en.wikipedia.org/wiki/Post%E2%80%93World_War_II_econ...
Actually, in a closed bucket hash table why would you use a linked list and not some kind of tree structure in the leaves?
Not to be insensitive, but it would have been interesting if they had a member of the family play an Andorian in Star Trek. Think about it.
A dislike button would be handy. There is that feature on some of the generated playlists, but I don't think they do anything. My two biggest issues with Spotify right now are:
1. Release Radar filled with re-releases and remixes, often from artists who have long since passed away. I want new music as in released for the first time.
2. Name collisions. I'm surprised this is an issue, but I will often get songs from different artists with the same name. And then I'm unsure if selecting "I don't like this song" or "I don't like this artist" will affect the actually intended artist.

I've also reached a tipping point where I no longer find new music through algorithmic recommendations. To be fair it's taken about 5 years to reach this point. Now the good music I find comes from searching for curated playlists. It's come full circle as before streaming I got my music recommendations from blogs and friends.
It's interesting you chose "march" because I see it as not that. There is rapid forward progress, as you say, but it's individual parts sprinting at different paces. "March" would imply they were moving together.
Its a result of a lot of trial and error and finding better way of doing things. I dont think anyone likes it, but its byproduct of moving fast and of requirements changing.

Personally I think the web-frontend ecosystem is getting closer to stabilizing. For example React has not been changing much recently in its API and most of its development happens under the hood. A counterexample right now is bundlers. Webpack was the king for a long time, but it has gained more and more features and the code bases it is working on are bigger so its getting slow and complex. Competitors like esbuild and vite that are simpler and faster are popping up. However this is not the fault of webpack but simply that the requirements has changed so much and webpack always had to follow the requirements. Now that the requirements are starting to stabilize new alternatives can be built that can skip all the cruft.

I find it interesting how people in this thread are praising python frameworks for being so stable, I'm in my mid thirties and I clearly remember a time when they weren't.
Offshoring has existed for decades but picking up and moving on a whim is not something companies do overnight. Things like access to raw inputs and availability of skilled labor are major viability factors.

Also, global transportation is a mess right now. Container shipping rates are high and ports are backed up. It doesn't do a company a lot of good if it can't get its goods from the factory to the market they're sold in efficiently and at reasonable cost.
https://mobilemonkey.com/articles/employee-tenure-in-tech-co...

Here’s How Long Employees Are Staying AT The 10 Biggest Companies in Tech:

Facebook – 2.02 Years
Google – 1.90 Years
Oracle – 1.89 Years
Apple – 1.85 Years
Amazon – 1.84 Years
<...>
Great, now theres going to be radioactive exhaust all over the place from everyone doing this.
>Consider that for most top law firms, if you're not coming out of the top 3 law schools they're not interested.

Yes, and this is certainly not a new phenomenon. I used to work with a recruiting department at a large upper-end law firm. They only took new associates from the top 10 universities. This was 35 years ago. So there's nothing new under the sun.
When Did Things Happen? (Surveying Historical Knowledge)
Just click the ad! You won't regret it!
Anything and everything? 50 years people thought we’d have flying cars and unions. Who would have imagined all the automation? It is a world of work that was inconceivable to most people then.
Meccano is better known in the US as Erector Sets.

https://en.m.wikipedia.org/wiki/Erector_Set
plot twist: javascript frameworks are an invention of a cabal of backend engineers attempting to sabotage the client side of things
That’s fair. What environment do you have that installed git at the command line? I’m assuming ‘git’ is a recognized command.