HNHacker News
TopNewBestAskShowJobs

shaftway

2,246 karma · joined May 6, 2015

submissionscomments
shaftway··on 'Ghost jobs' could soon be illegal in New York
Would it though? Thanks to CA Prop 65 every place I go has a warning that I'll get cancer if I take one more step. If I'm walking into a nuclear waste storage facility I'll never know because of warning fatigue.
shaftway··on Home alone: Remote work, isolation, and mental health
Yeah, em-bee. You should just be not shy.

As a fellow shy person, I feel the pain when someone basically just tells you to get over it.

shaftway··on Google Hates You
As a user I actually appreciate it. But most of the stuff I google is coding questions.

Before if I asked a question, the top 3 results would be StackOverflow. I'd click into the first one and find out that the question was subtly different than mine making its answer useless, but it included a lot of similar words. Go back and click into the second one. It's exactly my problem, asked three years ago, no answer. Go back and click into the third one. Same question, but it's been answered. Great. But the accepted answer has a score of -3 and another answer has a score of 5. So which one do I follow? Whoops, it's actually neither of them, because the library has broken both of those workflows.

Now I get my answer right away 90% of the time. And if I don't then I scroll down and I'm not worse off than I was 2 years ago.

shaftway··on The Permanent Upper Crow
I think OP is referring to the 80's movie WarGames - https://en.wikipedia.org/wiki/WarGames

At the end a strategic defense computer is asked to play Tic Tac Toe against itself and suddenly "learns" about no-win scenarios. Then it does the same with nuclear launch scenarios, and finds that they're all no-win. It decides that nuclear war "is a strange game", and "the only winning move is not to play".

shaftway··on Google I/O
This is the result of systemic problems at Google:

- Launching is rewarded, keeping the lights on is not

- The hot new teams get far more resources than tried and true ones

You could sum this up in three words as "new is better".

This is why Google Home is getting worse. It worked well enough, but nobody gets promoted for keeping it like that. People get promoted for launching something new on that platform and cherry-picking statistics to show that they had "impact".

This is why everything at the keynote was AI. AI is the new hot dumpster fire that every resource is being poured into. And including AI in every product gives so many people the opportunity to launch new stuff, and demonstrate "impact".

And while I/O is for developers, you'd be foolish if you thought that Wall St. wasn't paying attention. Stock was down $10 for the day before I/O started, but during that keynote it gained $5. It didn't hold it, but clearly the keynote affected the stock price. Sundar knows this.

shaftway··on A History of IDEs at Google
I was at Block and there was an interesting problem around this.

A number of Google engineers had come over, and they pushed for a way to structure the codebase where you had a ton of tiny build targets. I think a "jumbo" build target would have more than 10 files in it. Under Blaze / Bazel this would have been absolutely fine, but they were still using Gradle for their Android builds, and Gradle does not like that. Doing a build of anything meant Gradle had to initialize tens of thousands of projects. A naive engineer trying to build a single project would have to wait for about an hour for everything to be structured.

There was a big push to move everything to Bazel, and the backend and iOS teams moved over just fine, but there was someone on the Android build team who had come from Gradle, and knew a lot of techniques to cut the build time down. I remember there was a tool you would run that would examine the project structure and set up an ignorelist of projects so that Gradle wouldn't have to load projects you didn't care about.

All of the tricks were a bandaid technique at best, and eventually that engineer left the team, but the damage had been done, and migrating to Bazel was a non-starter.

shaftway··on A History of IDEs at Google
I jumped from Google to Meta in 2022 (Worst. Timing. Ever.) and by that time Google's IDE had pretty much caught up. Android app development at Meta was super painful because of the repo size. My good morning routine was to kick off a 40 minute sync, and then get coffee and wander the building while I waited.
shaftway··on I want to live like Costco people
Yeah, I switched to a bike too. Way better quality of life, and lane splitting is a godsend. In my area not allowing a bike to pass is actually a ticketable offense (though I've never actually heard of anyone getting a ticket for it). Either way, the cars know what to expect and the cars in the left-most lane hug the left side of the lane to give you room.
shaftway··on I want to live like Costco people
That fancy Lamborghini is going to be sitting in the same traffic as my Honda.
shaftway··on GameStop makes $55.5B takeover offer for eBay
Oh yeah, not a barrier, but for the volume they'd want to enable it's not a complete loss.

Remember who uses GameStop. It's certainly not me, and it's probably not you. I'd guess that their core demographic is 14-25 year olds that are cash-strapped. You don't go to a GameStop for the experience, and their prices aren't any better than any other retailer. You go there because you don't have options or for their secondary market. And at that point, $5 in shipping fees matters.

Why would it be edge --> edge and not edge --> central --> edge? For common stuff keep half of it at the edge for local sales. For uncommon stuff or the other half ship it back to central so they can re-ship it quickly and easily. Including something in a shipment is orders of magnitude cheaper than shipping a single item, just in packaging costs and time alone.

They must have items going both directions (to handle overstock, returns, defectives, etc.). I assume those all go in a large box and are shipped together. At that point I'd need to see some actual numbers to agree that it's not pennies.

shaftway··on GameStop makes $55.5B takeover offer for eBay
> Ebay commissions are not that high, 13.25% for most items.

13.25% isn't zero.

> The barrier to listing [is] the amount of labor it takes to list and price everything

GameStop has a surprising amount of technology around their pawnshop activities. My son traded in his laptop last month and they had him wipe it, enable developer mode, and plug it in to do automated tests and make sure they knew what they were getting. They're already doing the labor to price everything. They're not going to have people type up listings, they'll just automate posting off of their inventory system.

> when you add in shipping costs it approaches the value of buying something new.

They get to skip the shipping costs. You could choose to have them ship the item to a GameStop near you which would cost them pennies. This is an advantage of having stores in every city with a population over 50,000 in the US.

And a huge amount of the stuff that GameStop buys and sells is out of print. Buying new is simply not an option when you're talking about a game that was released 6 years ago only on physical media.

> The way inventory is offloaded in bulk is in bulk pallets sold at auction, where people bid on them and then do all of the grunt work involved in photographing and listing and packing and shipping.

There must be money in the margins here. Otherwise people wouldn't do it. GameStop has all the technological ability to cut out this grunt work.

shaftway··on GameStop makes $55.5B takeover offer for eBay
You're right that there's no real advantage to eBay buying a pawnshop conglomerate, but a pawnshop conglomerate buying eBay gets a massive advantage. They're already sitting on a mountain of used inventory, and at some point a lot of it will be thrown away because there are no local buyers for it. Having a commission-free way to offload that inventory would be huge for them.
shaftway··on Let's Buy Spirit Air
> Most of modern life in America is an elaborate series of choices to maximize the distance between yourself and Spirit airlines passengers

So much this. I regret that I have but one upvote to give.

shaftway··on Why Not Venus?
What are you going to do 12 hours later when it's daytime again?
shaftway··on Musicians are manufacturing sold-out shows
The best concert experience I ever had was in the mid-90's. I went to a medium level band (frequent radio play at the time, but you probably wouldn't recognize the name now) at a smaller venue. But I guess nobody really promoted the show at all. Only 8 people showed up for the audience. The band didn't seem to care and rocked it anyway. During their most popular song the singer got down off the stage and passed the mic around, we all sang karaoke style.
shaftway··on I don't chain everything in JavaScript anymore
This is the difference between a command (which is discarded after it's executed), and production code (which you probably want to keep around for a little bit).

But I'm in the same boat. I love the expressiveness of chaining a whole thing into a single call, but I have to break it apart for my own sanity.

shaftway··on Running Tesla Model 3's computer on my desk using parts from crashed cars
In German that's called Wortbildungsfähigkeit, or in English, WordStructureCapability
shaftway··on The future of version control
> The conflict is no longer an ephemeral part of the merge that only ever lives as markup in the source files and is stomped by the resolution that's picked, but instead a part of history.

How is this different than having a merge commit?

shaftway··on The future of version control
Delayed conflict resolution in jj is valuable when you're rebasing a long chain of commits. If I rebase a chain of 10 commits and each of the commits has a conflict, I'm stuck in conflict resolution mode until I fix all 10 conflicts. Maybe something else came up, or maybe I got tired of doing conflict resolution and want to do something else. Git's answer is to finish or abandon.

Also, in jj it's pretty easy to rebase a lot of stuff all at once, giving you even more opportunities to create conflicts. Being able to delay resolution can be easier.

shaftway··on The future of version control
This is kind of how jj handles the situation. git won't let you move on from a rebase if there are conflicts. By comparison, jj will just put a marker in the log pointing out that there are conflicts in a branch. You resolve them whenever you feel like it, but all resolving them does is effectively remove the "conflict" marker and rebase all of the descendent commits (which may clean up merge conflicts, or make them worse).
shaftway··on I was interviewed by an AI bot for a job
Right, but if you clog up their pipeline with enough fake applicants, then they won't get any real ones. Same outcome.
shaftway··on I was interviewed by an AI bot for a job
The solution to this seems pretty clear. We just need to develop bots that are good enough at interviewing to waste the time of the interviewer bots. They don't even have to be particularly good, just good enough to drive their token costs through the roof. Make it too expensive to use.
shaftway··on We do not think Anthropic should be designated as a supply chain risk
https://en.wikipedia.org/wiki/Executive_Order_14347

> Among U.S. federal agencies, the order authorized the official use of the secondary title "Department of War" for the United States Department of Defense. The department now refers to itself as the "Department of War" for non-statutory purposes, but is still technically named the Department of Defense, as only an act of Congress can formally change the name of a federal department.

shaftway··on Layoffs at Block
It should be good. It's the third time he's written this exact same announcement, including "taking the blame" and "making the difficult choice to cut a large group instead of smaller cuts over time" and "thanking the expendables that got the company where it is."
shaftway··on Layoffs at Block
I've actually had really positive responses. I'm fairly senior (~20 years of experience). I was laid off by Meta in 2022, started at Block 3 months later. Laid off by Block in 2024, started at a smaller company 1 month later. Decided to leave that company in early 2025, contacted one company from a HN Who's Hiring post and took that job. That ended up being a poor fit, and I went back to a FAANG around July of 2025.

In the last three transitions I applied to a grand total of 5 companies.

Also, looking at the recruiter emails I've been getting, they've been ramping up over the last few months, and I'm back up to one or two cold emails per week.

But again, I'm fairly senior, and I have deep domain knowledge in a few key areas. I understand the market is brutal if you're early career or your knowledge isn't "T" shaped.

shaftway··on Tesla's 45 Austin Robotaxis now have 14 crashes on the books since June 2025
FSD automatically shuts off and relinquishes control to the user in an emergency. I bet the real number of FSD accidents is far far higher, but they're using this loophole to claim it's lower than it is. If you call them out on it, they just hide behind their "the driver must be in control at all times" legal shield.
shaftway··on Evolving Git for the Next Decade
I would have loved to see some discussion of mono- versus poly-repos and steps towards improving this situation.

I prefer mono-repos personally, but they have the downside of being very busy and bulky because of that. Doing a partial clone by folder is very clunky at best, and there is no per-folder notion of permissions, which makes this a total non-starter for my team. The result is that we have thousands of repos and tooling that helps you check them all out into the correct place to make builds across them work. And inevitably they get out of sync and the builds break.

Git submodules seem like a solid approach, allowing you to cobble a bunch of poly-repos into something that kind of looks like a mono-repo, but the tooling support around it just makes it super painful, and you still don't have the ability to have an atomic commit across the repos. And people *hate* submodules.

I don't know the solution, but I wish this was on the radar of people who know git better than I. For now I'll just bumble through the repos I need to touch.

shaftway··on Unsealed court documents show teen addiction was big tech's "top priority"
I think the reality for any product that has >7,000 employees working on it is that some people's job is to prioritize growth at all costs, some people's job is to prioritize the effects of on vulnerable people, and the vast majority of them have other jobs to be doing. This sounds appropriate to me; not everybody can be worried about mental health at all times, and somebody needs to focus on growth.

There are plenty of examples that the mental health people aren't being completely steamrolled. Parental controls allow you to block Shorts for your kids. That doesn't sound like a "growth at all costs" mindset.

shaftway··on Unsealed court documents show teen addiction was big tech's "top priority"
I feel like there are some key differences between the companies though.

The second one outlined for Meta is:

> Heavily-redacted undated internal document discussing “School Blasts” as a strategy for gaining more high school users (mass notifications sent during the school day).

This sounds a lot like Meta being intentionally disruptive.

The first one outlined for YouTube is:

> Slidedeck on the role that YouTube’s autoplay feature plays in “Tech Addiction” that concludes “Verdict: Autoplay could be potentially disrupting sleep patterns. Disabling or limiting Autoplay during the night could result in sleep savings.”

This sounds like YouTube proactively looking for solutions to a problem. And later on for YouTube:

> Discussing efforts to improve digital well-being, particularly among youth. Identified three concern areas impacting users 13-24 disproportionately: habitual heavy use, late night use, and unintentional use.

This sounds like YouTube taking actual steps to improve the situation.

shaftway··on China to ban hidden door handles on cars starting in 2027
The glass of the window does not have a frame. You want the glass to go into a rubber seal to really prevent air from getting in and whistling at high speeds. If there's a frame around it, then no problem, the seals move with the glass when you open the door. But if you don't have a frame then opening the door without retracting the glass will cause it to pull at the rubber seals. At best it'll wear the rubber faster, but eventually it'll pull the rubber seal out.

This is very common on cars where the windows don't have a frame. Before I had a Tesla I had a convertible Mustang. Because it was a soft top it didn't have the same kinds of seals. Instead it used lateral pressure to hold the window against some rubber. At freeway speeds the window would flex and let air in. Eventually the soft top started blocking the passenger side window from meeting the rubber, and there was always a 1/4" gap unless I rolled the window down a bit and then back up.

← PreviousPage 2 of 28Next →