alsodumb

I feel like a lot of issues you mention will eventually point to an ambiguous spec. I’ve had great success with interview style spec generation where I ask agent to grill me on any and all parts of the spec/plan that’s ambiguous and then note my responses. It takes like 10 mins but the end product is always exactly what I expect and most of the things you mention get resolved in this interview phase.

My hand writing is so bad I don't know if a really want a font out of it lol (love the project though!)

It takes hundreds of millions to build a warehouse. Amazon has tons of them. Retrofitting things is capital intensive.

Honestly I don't think Anthropic cares about you moving over to them - it's pretty evident that they already have more demand than they can handle.

I've always had better experience with Claude in day-to-day coding and text writing, and looking at public forums that largely seems to be the case.

1X is different. This is purely a hardware demo, they are doing pure teleop on the software side, no AI in the demo (except maybe RL for walking). 1X's bit thing was always their mechanically compliant safe hardware.

It's teleop, they are pretty open about it. It's not autonomous.

They do have an RL controller running for the legs, but it's just an intermediate controller and it probably get high level commands from a teleoperator. The upper body is purely teleop.

When Valve came out with their VR headset that had base stations, everybody thought that’d be the holy grail, that you can never achieve better localization and tracking without base stations, and a base station free method can never be better than that.

Well, Meta poured a shit ton of money into making Quest base station free and they got there. We use to use valve setup for our robotics applications but we swapped it out with Quest cause honestly Quest was as good but much more easy to setup and operate.

The bitter lesson is that don’t bet against data or compute. Also, I don’t think you’d have to train a AI model for each location at every time in the future. Things get more efficient, etc.

Vanilla vscode has some version of this in the debugging mode, you'd perhaps need to install their Python extensions but that's about it.

I am not the hiring manager, and unfortunately a lot of interviews and hiring decisions happen at org level or at my manager level. These are mostly sophomores/juniors - folks who went through school in post-COVID, post-LLM era with a lot of virtual classes.

I tried my best to explain it to them, and nudge them to using docs. I did live debugging sessions with them to try and 'teach' them how to use docs. Ultimately, it was taking away too much of my time for little to no return. I only started working in the industry like a month ago and it's my first time having interns that I didn't pick (back in school, I had undergad research assistants that I interviewed/selected, and they were all excellent) - still learning the ropes.

I agree that they weren't explicitly meant to represent geography, but implicitly they do, right? Are there cases where this is violated?

In other words, is it safe to assume that for entity in a zip code is less than x distance away from the closest entity in the same zip code?

Route 4 (the helicopter route along the river) has a maximum altitude of 200 feet for helicopter. From the crash it seemed like the helicopter pilot wasn't strictly following the ceiling.

Unfortunately it's not gonna happen. The traffic at DCA only keeps going up, and I've heard chatter that it's because a lot of congressman and senators prefer taking flights from DCA instead of driving to Dulles or BWI.