public_void

I used to work at a company that did self driving. The sensor setup was more complicated than Tesla (cameras, lidar, etc), but the fact that FSD can still work on this car despite the cameras being in a different place is really impressive to me. Our sensors were pretty sensitive to accurate calibration, and iirc any time we tried to move our sensor array to a new car it took a ton of work to reconfigure it to make the sensor fusion output work.

On small teams or projects, this attitude is probably fine.

One of the most frustrating experiences as an engineer is running up against a deadline and just staring at my CI with my finger on the re-run button because my coworkers can't be bothered to believe me when I tell them their tests are flaky.

Fixing your flaky tests is like putting your cart away - a little effort on your part makes a lot of peoples lives a little better.

Why did you need to use bazel?

Yeah I think the title is a little hyperbolic - the author is really saying "intermediate commits are useless, make sure you squash commit when you merge to main and have a good message there"

One of the reasons we didn't go with buildjet was their concurrency limits (https://buildjet.com/for-github-actions/docs/about/pricing#c...) and the pricing on extending those limits.

We are a small company but our autoscaling cluster for GitHub actions on aws will scale up to >500vcpus during the work day when there are a lot of prs going in.

I don't see it documented anywhere, what are your concurrency limits on accounts?

Looks like in theory it works similar to other solutions I've seen, although those rarely get the polish I see in the video (since they're internal tools).

Everywhere I've ever worked has built and maintained their own solution for this. Seems a bit silly, like maintaining your own CMS or something.

Hey congrats on the launch, clearly a lot of thought and effort went into this. I'm pretty new to this space, and maybe this is a dumb question but how does this differ from Mixpanel? Would I use this for something different?

> You will give me interesting or meaningful work

Have you ever worked on something interesting or meaningful at a job? You list a bunch of random topics, none of which are inherently interesting or meaningful. I've worked on flashy projects - most recently self driving at one of the bigger companies doing it. Guess what? In an eng org of hundreds, at least half the people were still doing shit work that had nothing to do with self driving.

Beyond that, if I want to hire you for interesting work, it falls into two buckets: mission critical, or irrelevant. I can't hire you for mission critical work because I have no confidence you can do the job, so I can only hire you for irrelevant work. If I hire you for irrelevant work, it makes me no money, so I pay you no money. Why even have this arrangement? Just go start your own side project - at least then you own it.

Consider this: join a company doing something you don't like (making an absurd amount of money because of the industry), demonstrate/develop your expertise, identify the parts of the company that are interesting to you, then go work on those. People doing interesting satisfying work didn't just get there accidentally.