Slashdot was somewhere between a well curated tech subreddit and Hacker News.
It had its own in-jokes like: This is finally "the year of the Linux Desktop" and Jonathan "CowboyNeal" Pater, the site's moderator who often posted polls and commented.
In the late 2000s, most migrated their Slashdot reflex to Digg - and then eventually the YC-backed Reddit when there was a disastrous rollout of Digg v4 (in 2010)
Reddit then became less of a technology-focused site as it gained popularity, and HN became the defacto "tech news" aggregator with a well rounded comment section that resembled the early days of Slashdot, Digg, and Reddit.
Lyra Energy | lyra-energy.com | Hybrid, Los Angeles, CA | Full-time & Contractors
Lyra is a Los Angeles based technology company launching an electric two-wheeler vehicle platform. The tight-knit team here is composed of seasoned veterans from the EV manufacturing industry in California with expertise in high power battery, thermal, and electronics development.
- Firmware Engineer (CONTRACTOR) comp depends on experience
We’re looking for a Senior Firmware Engineer to continue to shape the core embedded systems that power our vehicles. In this role, you’ll take ownership of firmware development for connected vehicle systems, battery management systems, and infotainment. Your work will directly impact the first generation of Lyra vehicles going to market and help define the software and hardware stack that will scale with the company. You’ll be joining an established team with deep experience from the EV industry, and work closely with electrical, mechanical, and software engineers.
Email me stan (at) lyra-energy.com if you're interested. I'm our Head of Software, so reach out to me directly and tell me how your experience might match what we're looking for. Please include "Hacker News June 2025" in the subject line.
I wouldn’t say that. JetBrains is incredibly bloated and has significantly less community support.
I’ll agree on Teams being crap though, mostly for how dumb it is that they’ve rewritten it multiple times and created a confusing slate of weird versions like “Teams (work or school)”
the military gets what it wants in DC, and the pilots were too comfortable and on different radio systems (helo can’t hear airplanes and vice versa, air traffic control is their intermediary)
A disaster waiting to happen in retrospect. Similar issues at other airports like runway incursions, especially at crowded small airports like SFO and LaGuardia with antiquated runway layouts.
Let's wait for the investigation to complete before we opine on what is or isn't a "disaster waiting to happen." The entire aviation system is a "disaster waiting to happen" unless you assume a baseline level of aircrew competence, and the question will be whether or not the aircrew fell victim to a systematic risk inherent in what they were doing, or whether they just screwed up.
Sad to say, as a former aviator, I have seen it before where people died and families lost loved ones ultimately because of a systematic risk inherent in what they were doing, but also other times because someone flat-out just screwed up.
data recently analyzed by the board revealed that National Airport was the site of at least one near collision between an airplane and a helicopter each month from 2011 to 2024
I would say that statistic in and of itself qualifies as a "disaster waiting to happen". I agree that we should wait for the full report, but I don't think the GP is using hyperbole in this case.
One near collision every month (minimum) for 13 years? How is that a disaster waiting to happen, as much as it is a case of wilful criminal negligence? How many near collisions are needed for the authorities recognize that it's an unacceptable risk? How did they let this happen?
One of the biggest challenges for the FAA et al. is preventing both individuals and organizations from developing this kind of complacency, where something extremely dangerous becomes "just how we do it here, and it's fine".
Unfortunately, they don't always succeed. Every crash is a lesson learned too late. We endeavor to learn earlier than that, and when we don't, we make sure we learn in the aftermath.
That line really stood out to me. One would hope that someone would realize this was a disaster waiting to happen and make changes before it actually happened.
Relying on seeing another aircraft in the air at night is pretty much a disaster waiting to happen.
You don't see aircraft at night, you see lights. And they're over a city--a gazillion lights. Thus all you really see are moving lights. But if two objects are on a steady collision path neither moves relative to the other. Thus both sets of pilots would simply have seen stationary lights, invisible against a sea of stationary lights.
Having had some former coworkers that ended up at various dating platforms, dating is fascinating, I still think dating is something that needs a better modern solution than what “the apps” offer. Every dating app has a few fundamental flaws. There’s the human element too.
What worked for me was hacking Tinder circa 2014 by faking my geolocation and hypertargeting certain places and neighborhoods I knew would be up my dating alley and spamming posts on social media sites like Reddit and Craigslist.
It’s tough because some people don’t even know what they’re looking for in a partner.
It costs more time and money to set up these walls vs not bothering. And there was a time when they didn’t bother and hacking was easy. Not just in cars but any consumer facing product running software.
Blame management structure. They hire out security devs because its expected they have a security team like other companies or shareholders pillory them. These security devs trot off doing the expected work they are all trained to do from school or their work at other companies. You end up with the inevitable locked down shitware everyone was hired to make and will make. No one asked for this. They only asked for something one level deeper into the abstraction (shareholders want company to look like other companies to price it appropriately, managers want security team to appease shareholders, security team head wants to see certain things they saw at their last job, security dev wants to deliver and get a raise) but what they got was the chain reaction leading to the user hostile app.
