krschultz

5 ms·

1.
by krschultz 1y ago
The Highlanders are testing vehicles: https://zoox.com/journal/autonomous-zoox-testing-vehicle
2.
Zoox robotaxi launches in Las Vegas(zoox.com)
184 points by krschultz 1y ago|233 comments
3.
by krschultz 1y ago
You don't make breaking changes. You provide the new API and the old API at the same time, and absorb the additional complexity as the library owner. Best case scenario everyone migrates to the new API and eventually remove the old one
4.
by krschultz 3y ago
Because they make more money using their servers for their own products than they would renting them to other people. Meta has an operating margin of 41% AFTER they burn a ton on Reality Labs, while AWS has a 21% margin with more discipline
5.
by krschultz 3y ago
That's not universally true. The sewer system in my town was overbuilt in anticipation of a development that fell through. That's why sewer / water bonds are typically up for vote separately from property taxes because there&
6.
by krschultz 3y ago
Huh? You have to pay property taxes now and those could end up being too high for subsequent generations to afford. That happens all the time and is a common reason why property gets subdivided. This is simply a question of whether the valu
7.
by krschultz 3y ago
Threads is already GDPR compliant, that's not the only regulation the EU has made that covers these kinds of apps.
8.
by krschultz 3y ago
I would heavily consider this type of system once build times become a major pain point. That often happens somewhere around 20-50 people working in one codebase. So I think this is a problem space for medium sized companies. Truly small co
9.
by krschultz 3y ago
IMO one of the nice things about Buck or Bazel is that once you learn it, switching languages doesn't require you to learn a completely new tool. Obviously the cost of learning it the first time is high and if you are used to one ecosy
10.
by krschultz 3y ago
It's honestly hard to measure at the scale of Meta. Just making everything compatible with Bazel would be a non-trivial undertaking. Also that seems an interesting thing an independent person could write about, but whatever claims Meta
11.
by krschultz 3y ago
At the time that FB started writing Buck, Bazel was not open source. I believe it did exist as Blaze internally at Google before FB started writing Buck. Facebook open sourced Buck before Google open sourced Blaze as Bazel. Over time Facebo
12.
by krschultz 3y ago
There are fewer forced sellers now that remote work is more common.
13.
by krschultz 4y ago
I don't think they balked, they failed.
14.
by krschultz 4y ago
At Meta many engineers tried management and then went back to being an individual contributor. I'm not sure of the exact numbers but it was a very common career path. It did build up empathy for management on the senior IC side and mea
15.
by krschultz 4y ago
A question to answer: is the enjoyment coming from actually being the machinist, or is it coming from assembling something you designed? The answer could be either. But if you just want to bring something you designed to physical fruition a
16.
by krschultz 4y ago
The grinding discs shatter. Wear a full face shield.
17.
by krschultz 4y ago
I do not think the outcome is only Uber / Lyft but with AI, but if that is the outcome I still think it would be a win. Today supply of Uber / Lyft in my area at off hours is spotty, and that makes it unreliable. I have gotten stu
18.
by krschultz 4y ago
How many software engineering projects are CRUD apps or yet another ETL pipeline?
19.
by krschultz 4y ago
For many years my "big question" has been "why do software engineering projects fail at a disproportionally higher rate than other engineering fields?" Though I have to say the other engineering fields are not doing so h
20.
by krschultz 4y ago
I'm not at all interested in finance / stock picking but found this to be one of the best walkthroughs of an ML system end-to-end that I've ever read. I'm not in the field of ML but I'm interested in learning more a
21.
by krschultz 4y ago
As an owner of a vacation home and a large donor to homeless charities: this is completely divorced from the reality on the ground. It's a false dichotomy proposed as a way to block solving the problem of limited housing where it'
22.
by krschultz 4y ago
FB is pretty much on V1 of its GraphQL API with tens of thousands of engineers editing it for over a decade. Every single query is its own version, that's the point. If you want to change the semantics of a field, make a new field and
23.
by krschultz 4y ago
It shifts the complexity to the server side. The additional logic you are describing currently lives on the client, where it's harder to update and likely duplicative across platforms.
24.
by krschultz 4y ago
Every company I've worked for in the last 10 years had multiple apps across several platforms, each with many versions, all running in production at once. Even if you only care about the next version you are shipping and a handful in p
25.
by krschultz 4y ago
- It shifts the complexity where it belongs - out of native apps deployed to user's phones and onto the backend that you control. It doesn't eliminate any complexity. - There's really no need for API versioning in GraphQL. Ju
26.
by krschultz 4y ago
Are you counting the equity at a large public company to be lottery tickets? Because it's absolutely not. Every quarter a bunch of real money appears in an account with my name on it, that's not a lottery ticket.
27.
by krschultz 4y ago
Spoken like someone that's never been a manager.
28.
by krschultz 5y ago
We use the same principle on some of the frameworks I have worked on, it pushes you to make the API more explicit and keep the context localized. That makes codemods easier. This can sometimes lead to a more verbose / less magical API,
29.
by krschultz 6y ago
FWIW this was ~2015ish, I'm not sure what the state of OpenAPI was at the time. > Was it simply aggregating results of multiple requests? Pretty much. The company I was at was an early proponent of microservices so we had to have a
30.
by krschultz 6y ago
The backend for frontend pattern is exactly why I got sold on GraphQL. We had a pile of relatively low value server code that could be replaced a GraphQL resolver and the client got all of the advantages of that pattern. The move to GraphQL

More ›