frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Anthropic acquires Bun

https://bun.com/blog/bun-joins-anthropic
438•ryanvogel•1h ago•179 comments

100k TPS over a billion rows: the unreasonable effectiveness of SQLite

https://andersmurphy.com/2025/12/02/100000-tps-over-a-billion-rows-the-unreasonable-effectiveness...
91•speckx•1h ago•16 comments

I designed and printed a custom nose guard to help my dog with DLE

https://snoutcover.com/billie-story
178•ragswag•2d ago•24 comments

Learning music with Strudel

https://terryds.notion.site/Learning-Music-with-Strudel-2ac98431b24180deb890cc7de667ea92
268•terryds•6d ago•64 comments

Claude 4.5 Opus' Soul Document

https://simonwillison.net/2025/Dec/2/claude-soul-document/
6•the-needful•3m ago•1 comments

Mistral 3 family of models released

https://mistral.ai/news/mistral-3
472•pember•4h ago•149 comments

Amazon launches Trainium3

https://techcrunch.com/2025/12/02/amazon-releases-an-impressive-new-ai-chip-and-teases-a-nvidia-f...
4•thnaks•4m ago•0 comments

4.3M Browsers Infected: Inside ShadyPanda's 7-Year Malware Campaign

https://www.koi.ai/blog/4-million-browsers-infected-inside-shadypanda-7-year-malware-campaign
40•janpio•2h ago•7 comments

Zig's new plan for asynchronous programs

https://lwn.net/SubscriberLink/1046084/4c048ee008e1c70e/
99•messe•4h ago•83 comments

Poka Labs (YC S24) Is Hiring a Founding Engineer

https://www.ycombinator.com/companies/poka-labs/jobs/RCQgmqB-founding-engineer
1•arbass•2h ago

Nixtml: Static website and blog generator written in Nix

https://github.com/arnarg/nixtml
66•todsacerdoti•4h ago•20 comments

YesNotice

https://infinitedigits.co/docs/software/yesnotice/
98•surprisetalk•1w ago•43 comments

Addressing the adding situation

https://xania.org/202512/02-adding-integers
227•messe•7h ago•70 comments

Advent of Compiler Optimisations 2025

https://xania.org/202511/advent-of-compiler-optimisation
287•vismit2000•9h ago•47 comments

Python Data Science Handbook

https://jakevdp.github.io/PythonDataScienceHandbook/
144•cl3misch•6h ago•29 comments

IBM CEO says there is 'no way' spending on AI data centers will pay off

https://www.businessinsider.com/ibm-ceo-big-tech-ai-capex-data-center-spending-2025-12
57•nabla9•59m ago•45 comments

OpenAI declares 'code red' as Google catches up in AI race

https://www.theverge.com/news/836212/openai-code-red-chatgpt
74•goplayoutside•4h ago•90 comments

Lowtype: Elegant Types in Ruby

https://codeberg.org/Iow/type
32•birdculture•4d ago•9 comments

Show HN: Marmot – Single-binary data catalog (no Kafka, no Elasticsearch)

https://github.com/marmotdata/marmot
70•charlie-haley•4h ago•16 comments

Apple Releases Open Weights Video Model

https://starflow-v.github.io
389•vessenes•13h ago•129 comments

School Cell Phone Bans and Student Achievement (NBER Digest)

https://www.nber.org/digest/202512/school-cell-phone-bans-and-student-achievement
11•harias•1h ago•7 comments

A series of vignettes from my childhood and early career

https://www.jasonscheirer.com/weblog/vignettes/
115•absqueued•6h ago•79 comments

What will enter the public domain in 2026?

https://publicdomainreview.org/features/entering-the-public-domain/2026/
439•herbertl•15h ago•296 comments

Anthropic Acquires Bun

https://www.anthropic.com/news/anthropic-acquires-bun-as-claude-code-reaches-usd1b-milestone
41•httpteapot•1h ago•10 comments

YouTube increases FreeBASIC performance (2019)

https://freebasic.net/forum/viewtopic.php?t=27927
139•giancarlostoro•2d ago•34 comments

Proximity to coworkers increases long-run development, lowers short-term output (2023)

https://pallais.scholars.harvard.edu/publications/power-proximity-coworkers-training-tomorrow-or-...
144•delichon•5h ago•104 comments

Apple to beat Samsung in smartphone shipments for first time in 14 years

https://sherwood.news/tech/apple-to-beat-samsung-in-smartphone-shipments-for-first-time-in-14-years/
39•avonmach•1h ago•35 comments

Comparing AWS Lambda ARM64 vs. x86_64 Performance Across Runtimes in Late 2025

https://chrisebert.net/comparing-aws-lambda-arm64-vs-x86_64-performance-across-multiple-runtimes-...
110•hasanhaja•9h ago•48 comments

Progress on TypeScript 7 – December 2025

https://devblogs.microsoft.com/typescript/progress-on-typescript-7-december-2025/
40•DanRosenwasser•1h ago•12 comments

Beej's Guide to Learning Computer Science

https://beej.us/guide/bglcs/
310•amruthreddi•2d ago•119 comments
Open in hackernews

The Junior Hiring Crisis

https://people-work.io/blog/junior-hiring-crisis/
63•mooreds•1h ago

Comments

ChrisMarshallNY•42m ago
That's a thoughtful post, but I am skeptical of how "universal" her suggested Path Forward is. I suspect a hell of a lot of folks will have difficulty with the "people skills" stuff she mentions (and is almost certainly highly conversant in, herself).

> The most common answer from students when asked what they needed was a mentor who had just been in their shoes a few years ago, a surprising and heartening answer.

Mentoring is difficult; especially in today's world, where we are taught to despise older folks, and encouraged to treat everyone that we work with, as competitors.

For myself, I'm happily retired from the Rodent Rally, and find that LLMs have been a huge help, when learning new stuff.

pelagicAustral•35m ago
I think I would also ad to the mix that young folk these days are incredibly overconfident and averse to criticism. A few years back they got a junior dev in here, and I was supposed to help him get on our stack, and ultimately mentor him.

This kid would not accept seniority, would constantly and publicly try to divert from the stack we worked with, he would not take any input on his work without actively fighting the process and will crowd the conversation at team meetings with never-ending Reddit-tier takes that contributed to nothing other than fill his ego.

In the end I managed to convince my boss to get him out, and he now works in Cyber, which will probably cause even more damage in the long run, but at least I can now say "not my problem".

carlosjobim•27m ago
> young folk these days

You should have stopped to think about why such a person was hired in the first place, while there are an endless supply of very talented, hard working, and honest young people who would never be given a chance at all.

But if I guess right, hiring is not seen as the responsibility of your company. And that's the core of the problem.

elric•32m ago
> especially in today's world, where we are taught to despise older folks, and encouraged to treat everyone that we work with, as competitors

What world is this? This not match my experiences at all. Is this a common sentiment among your peers?

carlosjobim•31m ago
> where we are taught to despise older folks

9 times out of 10 it goes the other way around. Most young people have only had very negative interactions with their seniors, which has been wholly on the part of the senior. The current young generation is very respectful towards older people.

ChrisMarshallNY•29m ago
> The current young generation is very respectful towards older people.

This has not been my experience.

I worked for a company that prized seniority, and I regularly dealt with folks older than me, more experienced than me, more capable than me, and willing to help me out. I worked there for almost 27 years, and it was awesome.

In my experience, I'm usually written off as an "OK Boomer," before I've even had a chance to open my mouth to prove it (or not).

My fave, is when we have a really promising text-only relationship, then, the minute they see me, it goes south.

hiAndrewQuinn•12m ago
People skills are so important, I agree. Intergenerational people skills are especially important; in most things that matter, the old guard are the ones keeping their eye on the younger hires, pattern matching what they see over months of observation to who they've seen succeed before.
RicoElectrico•38m ago
The most frustrating thing about this whole junior position drought is how it simultaneously affects those who are passionate and get it, not only the opportunist bootcamp alumni who were lured by the prospect of high earnings.

If I were to graduate today, I'd be royally screwed.

ge96•34m ago
/r/cscareerquestions the horror eg. applied to 2000 jobs got 1 offer
Justsignedup•15m ago
Honestly, with the AI slop of resumes, I applied to dozens of jobs, and only got a callback to ones I had either a recruiter for or direct connections to, after 20 years of experience. Because I didn't have a big fat "worked at google for 10 years" on my resume. And I'd like to think of myself as someone who can take a very bad situation and make it look smooth.
mooreds•25m ago
> If I were to graduate today, I'd be royally screwed.

I feel that too. I am a self-taught dev. Got a degree, but not in CS. I don't know if I could get hired today.

Not sure how to fix it; feels like the entire industry is eating the seed corn.

buellerbueller•38m ago
Want to stand out in a world where all the job applications are AI slop? Network. The original kind.

Furthermore, this is why the humanities matter: because human relationships matter.

dkdcio•28m ago
genuinely asking, how do you network to get a job? esp. if you’re a new grad

where do you network? what do you network with these other humans on?

I do think I could get a job from my network because I’ve worked in the industry for years and done good work; I’m a little skeptical of advice to network to junior/new grads. I at least ignore those LinkedIn requests

rsaz•19m ago
- share your work online (twitter used to be the far-and-away best place for getting eyes, but this is a bit less clear now. youtube can work well, maybe also tiktok or sites like medium?)

- go to events/conventions/join clubs related to programming (need to be located near a large city for this)

- talk to other students/self-learners and wait for them to get to the next step

I’ve been unemployed a long time and have been thinking of improving at networking. These are what I came up with.

AnimalMuppet•16m ago
If you're a junior, develop connections with a few seniors.

If you're a senior, maintain relations with last year's graduating class (and with your placement services people).

If you get an internship, keep in touch with people there.

the_snooze•13m ago
For anyone still in school, networking is easy for students who take initiative. This doesn't mean going to networking events. It means actually doing things with actual people: get involved in undergraduate research, sports, arts, Greek life, volunteering, on-campus part-time jobs, etc. Universities have those low-barrier low-risk things going on that you can just try out. Students who do this get the inside track on opportunities that aren't broadly advertised, so they face far less competition and are likely better fits for those opportunities due to the experience they got by being involved.
buellerbueller•4m ago
The other responders have it: forego the "networking" apps like LinkeIn. (It's really just a graph analysis tool for salespeople.). Do thinks with actual face-to-face connection. That's what will make you stand out.

If you are a new grad: go to alumni events. Go to alumni events! GO TO ALUMNI EVENTS.

If you are still in school: talk to your alumni and career office; they will be able to connect you better.

If you are in High School: consider a university with a co-op program.

The value of fact-to-face connection should not be underestimated.

Again: this may be uncomfortable for some people, but it is the way of the world.

CSSer•33m ago
This article talks a lot about AI, but what I find odd is that in my relatively short (but long enough) ~9 yr career so far, this problem predates AI. I don't deny that it exacerbates it, but you don't kill a disease by addressing the symptoms. From the first time I was ever involved in the hiring process, senior leadership always encouraged me to hire more experienced staff, always most heavily scrutinized juniors, and had negotiations fall through with mid-level candidates the most. This was despite juniors passing technical screens with strong showings. This was not at a Fortune 500. This was a micro-cap subsidiary of a private, billion dollar company.

And although it hasn't discouraged me, I have to admit that I've been burned by juniors when caught in the middle between them and senior leadership on output expectations or strategy because frankly it's much more challenging to mentor how to navigate company politics than it is to mentor professional coding acumen. I want to be humble here. I don't think that's the junior's fault.

It feels like these problems go a lot deeper than AI. Most shops want software teams that are either silently embedded black boxes that you insert rough instructions into and get working software as output or an outsourced team. We've all experienced this. It seems silly to deny that it's directly related to why it's so hard to mentor or hire juniors.

1970-01-01•22m ago
Yes, AI isn't helping but the corporate world has been doing this for decades! Junior devs are second class citizens internally. I don't blame them for moving on after a few years.
CSSer•13m ago
I guess I should clarify too: I don't believe in junior titles. They handicap people into the position you describe where they must move on to progress. When I describe "junior" above, I generally mean a candidate with <=1.5 years of experience. When I say mid I mean any amount of experience greater but not senior according to technical review. And yep, I know this is not the best heuristic because there are definitely people with no working experience who have mid-senior coding skills (although they're rare). I think that's sort of part of the problem too. Senior management is disincentived from understanding the roles and growth trajectories, so our heuristics for hiring are totally warped and stomped on.
Herring•29m ago
We're still in the early days. It's gonna get a lot worse, if the LLM scaling laws are to be believed.

https://metr.org/blog/2025-03-19-measuring-ai-ability-to-com...

avidiax•28m ago
This isn't the first time that the industry has foot-gunned itself.

The continued reliance on say, COBOL, and the complete lack of those developers comes to mind.

Even before LLMs, there were periods recently where multiple companies had "senior only" hiring policies. That just inflated what "senior" was until it was basically 5 years of experience.

This time seems a bit different, however. There are both supply and demand side problems. The supply of students it tainted with AI "learning" now. Colleges haven't realized that they absolutely have to effectively crack down on AI, or the signal of their degrees will wither to nothing. The demand side is also low, of course, since the candidates aren't good, and AI seems to be a good substitute for a newly graduated hire, especially if that hire is just going to use the AI badly.

viraptor•10m ago
> The continued reliance on say, COBOL, and the complete lack of those developers comes to mind.

So the irony here is that LLMs are actually going to be decent at COBOL by default. And other uncommon/esoteric codebases. For example I vibe-ported some Apple ii assembly to modern C/SDL and... it works. It's stuff that I just wouldn't even attempt at manual development speed. It may be actually an easier path than training someone to do things, as long as you have a large enough test suite or detailed enough requirements.

hex4def6•28m ago
> We used to have a training ground for junior engineers, but now AI is increasingly automating away that work. Both studies I referenced above cited the same thing - AI is getting good at automating junior work while only augmenting senior work. So the evidence doesn’t show that AI is going to replace everyone; it’s just removing the apprenticeship ladder.

Was having a discussion the other day with someone, and we came to the same conclusion. You used to be able to make yourself useful by doing the easy / annoying tasks that had to be done, but more senior people didn't want to waste time dealing with. In exchange you got on-the-job experience, until you were able to handle more complex tasks and grow your skill set. AI means that those 'easy' tasks can be automated away, so there's less immediate value in hiring a new grad.

I feel the effects of this are going to take a while to be felt (5 years?); mid-level -> senior-level transitions will leave a hole behind that can't be filled internally. It's almost like the aftermath of a war killing off 18-30 year olds leaving a demographic hole, or the effect of covid on education for certain age ranges.

weatherlite•18m ago
> I feel the effects of this are going to take a while to be felt (5 years?);

Who knows if we'll even need senior devs in 5 years. We'll see what happens. I think the role of software development will change so much those years of technical experience as a senior won't be so relevant but that's just my 5 cents.

giancarlostoro•14m ago
The way I'm using claude code for personal projects, I feel like most devs will become moreso architects and testers of the output, and reviewers of the output. Which is good, plenty of us have said for ages, devs dont read code enough. Well now you get to read it. ;)

While the work seems to take similar amounts of time, I spend drastically less time fixing bugs, bugs that take me days or God forbid weeks, solved in minutes usually, sometimes maybe an hour if its obscure enough. You just have to feed the model enough context, full stack trace, every time.

tenacious_tuna•10m ago
> Well now you get to read it.

Man, I wish this was true. I've given the same feedback on a colleague's clearly LLM-generated PRs. Initially I put effort into explaining why I was flagging the issues, now I just tag them with a sadface and my colleague replies "oh, cursor forgot." Clearly he isn't reading the PRs before they make it to me; so long as it's past lint and our test suite he just sends the PR.

I'd worry less if the LLMs weren't prone to modifying the preconditions of the test whenever they fail such that the tests get neutered, rather than correctly resolving the logic issues.

devin-2030•13m ago
We might need a lot of young adults for war in the near future, according to some.
asdff•9m ago
“automate it away” ironically still requires a human in the chain to determine what to automate, how, and to maintain that automation. Whether it be derived from an ai or a systemd script or an Antikythera mechanism. Now if you leave that to seniors you just ate a big chunk of their day playing shephard to a dozen plus “automated” pipelines while they still have stuff to do outside the weeds. Now you need more seniors and pretty soon they want triple what you could pay a junior and I don’t think they are 3x more prolific if the junior is managed efficiently quite frankly.
xhrpost•6m ago
> AI means that those 'easy' tasks can be automated away, so there's less immediate value in hiring a new grad.

Not disagreeing that this is happening in the industry but it still feels like a missed opportunity to not hire juniors. Not only do you have the upcoming skill gap as you mention, but someone needs to instruct AI to do these menial/easy tasks. Perhaps it's only my opinion but I think it would be prudent to instead see this as just having junior engineers who can get more menial tasks done, instead of expecting to add it to the senior dev workflow at zero cost to output.

carlCarlCarlCar•23m ago
Maybe... that's fine?

We're not hiring a lot of rotary phone makers these days.

Who is hiring their own shoe-smith? It's been 30-ish years since my carpenter father last had work boots resoled.

It's almost as if... technology and economy evolve over time.

For all the arguments software people make about freedom to use their property as they see fit, they ignore non-programmers use of personal technology property is coupled to the opinions of programmers. Programmers ignore how they are middlemen of a sort they often deride as taking away the programmer's freedom! A very hypocritical group, them programmers.

What's so high tech about configuration of machines with lexical constructs as was the norm 60+ years ago? Seems a bit old fashioned.

Programmers are biology and biology has a tendency to be nostalgic, clingy, and self selecting. Which is all programmers are engaged in when they complain others won't need their skills.

frumplestlatz•21m ago
> Imagine a tech industry where relationship skills weren’t just nice-to-have but essential. Where navigating complex human systems was seen as a core competency.

If that were to actually happen, we'd wind up excluding many of our greatest technical performers while drowning in a sea of would-be middle managers. People skills matter, but so do many other strengths that don't always overlap with being naturally good at navigating interpersonal dynamics.

constantcrying•18m ago
The idea that the only reasonable path into a software related career is through networking may be true, but it obviously signals something deeply wrong with the culture around work.

It is also something which is likely to be quite harmful, since it selects for people who are great at networking over people who have good technical skills. Obviously interpersonal communication is important, but how well a 20 year old in University performs at it should not doom or make their career.

And even people with bad social skills deserve to exist and should be allowed into their chosen career. Being someone who does good work and is respectful, but not overly social, should be good enough.

j6m8•17m ago
This is neat — I do think this is relevant to more than just the software engineering space. See also, healthcare and law (I wrote more at length here, not to derail this comment thread [1]). Our junior training on-ramps for a lot of knowledge-work fields are in some semblance of equilibrium, but it's an unstable one.

[1] https://blog.jordan.matelsky.com/AI-doctors-bum-me-out/

beginnings•16m ago
this is the end game of capitalism, where the greed driven pursuit of profit wins over social maintenance and development. we see it very clearly with the incredibly socially damaging mass immigration to replenish the slave class and maintain the mythical GDP growth, which is only "necessary" because the native slave classes have been squeezed out of breeding

new grads will be fed to the meat grinder with no regards, its a closed shop unless you know someone

austin-cheney•16m ago
There are two problems here.

1. The industry cannot define the terms junior or senior.

2. Most seniors today are the prior generation’s juniors with almost no increase of capabilities, just more years on a resume.

The article asks about what happens when today’s seniors retire in the future. I would argue we are at that critical juncture now.

tptacek•15m ago
Over the timeline in this post, ZIRP and the pandemic seem like equally important factors to LLMs in explaining hiring trends.
alephnerd•14m ago
Sadly - as I've mentioned on HN a bunch - junior salaries need to fall dramatically (somewhere in the $60k-$100k range) to make it cost effective against automation/AI or offshoring.

The economics of providing every new grad a $150k TC offer just doesn't work in a world with the dual pressures of AI and async induced offshoring.

Heck, once you factor in YoE, salaries and TCs outside the new grad range have largely risen because having experienced developers really does matter and provides positive business outcomes.

State and local governments needs to play the same white collar subsidy game that the rest of the world is playing. This is why Hollywood shifted to the UK, Pharma shifted to Switzerland, and Software to India.

supportengineer•13m ago
My fear is that isn't low enough.
alephnerd•11m ago
Not really.

Building a GCC ends up costing around $60k-$100k per head in operating costs without subsidizes, and deploying vibe coding tools to fully replace an entire dev team end up in a similar price range.

stalfosknight•9m ago
This problem is not new. No one's wanted to give juniors the time of day since at least 2018 when it took me 8 months to land my first software developer role.
jmclnx•4m ago
> The social contract between large companies and employees has been broken for years now. US companies are optimized for quarterly earnings

I started in tech in the late 70s. I can say this break happened during the Reagan Years with a bit of help from the Nixon Years.