shaftway

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.

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.

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.

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

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.

How is this different than having a merge commit?

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.

> 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.

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.

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.

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.

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.

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.

https://en.wikipedia.org/wiki/Synapse_Financial_Technologies

To use your example: 51076, you'd do `5*3 + 1 + 0*3 + 7 + 6*3 = 15 + 1 + 0 + 7 + 18 = 41`. The sixth digit would be 9 ((10 - (41 mod 10)) mod 10). If you were to transpose any two adjacent numbers the checksum would be off. 3 is chosen because it's the smallest number that is co-prime with 10.

At least with software I can go back and edit my past transgressions.