we prevent people from gambling on early stage startups and risky investments by limiting investment to "accredited investors". same thing should apply to gambling.
I believe some countries/casinos in Southeast Asia have policies that you either have to show a foreign passport, or put a deposit of $500-1000 down to enter the casino, that you get back when you leave, with the theory (easily exploitable, I'm sure) being that you can't leave the casino penniless.
in my experience it (announcing to people in your network that you are job hunting) is precisely what you should be doing. Some might even point you to the next opportunity. I understand your concern though and have personally only shared it with close contacts (guess it is an ego thing).
> 2. FAANGMANGAMEME never hired that many truly exceptional people in the first place and you've fallen for corporate propaganda.
in my experience, FAANGMANGAMEME hires good people but they get placed on a weird career trajectory.
they learn how to work experience in enormous well funded company that has spent a fortune building fancy in-house tools for their dev experience, spend their time thinking about scaling problems that no other company will likely ever face, and all covered in ten layers of bureaucracy and "process".
if you hire a faang employee into your startup or normal mid-sized business, there needs to be a bit of a detox period where they have to learn what software dev is like for the rest of us mere mortals.
I don't doubt there are exceptional people working at BigCo at any role you or I can name, but by definition, it isn't possible that _everyone_ working there is exceptional.
First, this is true - learning or doing anything does change your brain. This article isn't talking about just that.
I personally don't think it's meant to scare-monger, either - although I'm sure opinions may differ on the subject.
What is unique about being a dad is having a living breathing creature depend on you. There are hormones exchanged. AND you're learning and doing something. AND you're remembering (and having to deal with) your own childhood memories. And realizing that in your memories, you were the kid ... now you're the adult. It's different.
I always love RTS games and am sad to see how they've largely disappeared.
some of my first experiences 'hacking' were modifying .ini files for command and conquer to make a new version of the game for my friends. it was... very unbalanced
all around me in the northeast are decaying little towns and attractions that used to be vacation getaways for the first half of the twentieth century.
they say that airtravel killed the catskills resorts (ala dirty dancing) because why spend a few hours in teh car when you could go someplace so much more exotic with a few hours on the plane? and now there's a second-wave killing it with social media travel photos. everybody feels like they need to travel to the same handful of farflung locales that have been deemed 'the best'. basically, people with the means to travel have decided that regional travel isn't cool enough to impress their friends, so they let it die.
i think that's a terrible mistake for everybody. people dont have a fun, affordable place to go on a little weekend jaunt. towns that could scrape by on their natrual beauty have been left to decay (and once there's no way to monetize the natural beauty, local development sees no reason to preserve it).
i've seen a number of articles claiming things like "devs self report they'er +x% more productive with AI, but actually they're -y% LESS efficient!". and i think that this is explanation for why.
as a boss (or researcher) i'm going to measure productivity based on amount of output per hour that i'm paying you; as a workers, i'm going to measure productivity based on amount of output relative to the amount of effort i'm putting in.
so what may be happening is that bosses see that output is at 80% (productivity down!) but workers see that they can give that 80% output with 40% effort (productivity up!).
Not sure among devs, but I do know that in other positions in typical corporate bureaucracy, people have a propensity to not report their own automations or productivity gains upward, because the reward structure isn't there.
Early on in my days as a sysadmin, I automated a ton of my role when the rest of the team was still doing ClickOps. The reward for doing so was more work and expectations without the additional pay increase to justify my new found productivity. That happens all over the workforce, and so people will just keep it to themselves. I learned my lesson at that first job real fast that if I'm able to have the same, or greater output, for half the time, I keep that to myself so I can use the automation to free up my own time instead of have it filled by the company.
I wonder how much of that is happening now with AI in non-technical roles.
> so what may be happening is that bosses see that output is at 80% (productivity down!)
If an initiative produces only 80% of the previous results and you’re paying large token bills on top of the same wages, the AI is going to get cut off.
> i've seen a number of articles claiming things like "devs self report they'er +x% more productive with AI, but actually they're -y% LESS efficient!".
Are you thinking of the old METR evals? Their more recent evals showed an actual performance improvement.
The old report is still circulated as bait for AI skeptics.
I think the old report you're referencing is this [1] from July 2025, but I can't find a new report. This [2] links to a new dataset at the bottom (that maybe shows improvements?) but it seems like they chose not to write it up because of perceived flaws in their study. Is there a more relevant report I'm missing?
> so what may be happening is that bosses see that output is at 80% (productivity down!) but workers see that they can give that 80% output with 40% effort (productivity up!).
So why is it that the bosses are the ones that are so enthusiastic about adoption?
Well the obvious is that, monkey-see-monkey-do, and they don't want to miss out. But the insidious externality is that they are the most likely ones (and higher ups) to be invested in nvidia and others, so when they push you to use, it creates a viscous cycle.
i know series hybrids aren't as efficient as parallel hybrids (thanks technology connections!), but i wonder if they'd be a good candidate for fun restomods.
drop in a tiny, powerful electric motor and a small battery (crammed in whatever location is best for weight distribution), and then wire up a little genny powered off your existing fuel tank that can jump in as a range extender
Series hybrids can compete with parallel hybrids, because the full decoupling of the engine from the wheels claws back some of the efficiency you lose through the energy conversion. It's series-parallel hybrids they can't really compete with, because those are able to do the same trick, but they also lose less energy in conversion, because the engine does some of the heavy lifting.
Series hybrids are great for packaging, though. Parallel and series-parallel commit to certain packaging decisions like having a transmission, or a long, monolithic unit, because it's the mechanical coupling that buys them smaller motors and potentially better efficiency. Series hybrids don't care about any of that, so even though you have bigger motors and potentially higher losses, you have more freedom over where things go.
Personally, I think there's a massive untapped market in converting old cars to hybrid engines. You wouldn't try to upgrade the old engine, you'd design a smaller and more power dense package and rip all of the original gear out. Because electrification lets you cut the size of the engine down so aggressively, this is probably a feasible strategy. As you pointed out, series hybrids are probably best suited to this because of their packaging flexibility. As others have pointed out, there's tremendous potential there for replicating original driving characteristics using software and the electric motor. And if we're being honest, off-road vehicles probably should get rid of the transmission and low range, because electric motor torque is just better. As is, the potential for cars is enormous, but we're getting the worst possible outcomes thanks to legislation.
i dont think jira (or linear or any other ticketing platform) is about saving anybody time. they know on some level that they are all a burden.
but they will gladly take the productivity hit from that time sink because it gives them teh ability to track employees. they'd rather know that everybody is working at 80% productivity than release that burden and just trust them. it's either this or filling out frustrating timesheets.
The previous place I worked had the Head of Product become VP of Engineering after the CTO left (don't ask, it's a long story).
They literally implemented the most orthodox scrum you can imagine, with the one exception that they could sit on the sprint planning meetings and override the teams pulling tickets off the backlog into sprints (technical debt of course started to pile up).
The kicker is that after a few months of this, productivity slowed to a crawl. The retrospectives showed that the planning wasn't working because the planned work rarely got done - because we were always fighting fires. Work also slowed due to all the overhead that was added to implement scrum (I also had to participate, despite being in an DevOps role - that at the best of times is inherently interrupt driven and I'm servicing the work of developers). Despite the fact that the powers that be knew things were not working as well as they used to, no amount of feedback could loosen the reigns - probably because it inherently meant losing some control. We had to try everything else to get back to where we were, when empowered developers could make decisions. Things got worse of course as within 6 months we lost half our most experienced talent that wasn't going to put up with it (this was the peak 2022 tech hiring levels).
Eventually there was some mild "improvement" as we were allowed a "15% time" to work on what we thought was best, which still had to be justified and it was still the lowest priority during any given sprint. I still shake my head at the whole situation.
