flambojones

3 ms·

1.
by flambojones 7mo ago
I worked in mobile robotics for a defense contractor in the early-mid 2000s and we had a homegrown Lidar (though we always called it ladar) that was large, heavy, and cost $250k to make. I remember a year out of college driving 2 hours to a
2.
by flambojones 9mo ago
Having been at Microsoft when we had SDETs for everything (and I miss it greatly, though the way we could write a feature and then just toss it to test was ridiculous), I think things have swung too far away. On one hand, engineers needed t
3.
by flambojones 11mo ago
Sounds like an opportunity for the person who sent it to learn to improve their prompts. I've set my default claude rules to emphasize doing small-contained commits and use a stacking tool like Graphite to help them get reviewed.
4.
by flambojones 1y ago
Ahh good call. My $200k vs. your $200k doesn't really matter with a given year.
5.
by flambojones 1y ago
Salaries aren't a one-time expense, so is the amortization rolling? Like, year 1, you pay me $200k and deduct $40k. In year 2, you pay me another $200k, do you get to deduct $40k for year 1's salary and $40k for year 2's sala
6.
by flambojones 1y ago
+1 - a universal way of doing this via markdown beats learning whatever app-specific hotkeys I have to do to make an H3 or whatever. I don't have any particular feelings about markdown as a format for data, but as a universal set of sh
7.
by flambojones 4y ago
I’ve completely been there. I burnt out hard, not from overwork, but from this type of stuff. I started to think maybe I enjoyed software engineering but not the business of software engineering. I took a break and did a lot of reflecting.
8.
by flambojones 4y ago
I went through this for a few years up to about two years ago, though the cause of my burnout was less overwork and more politics and things like that. I don’t feel comfortable giving advice, but here’s what I did: 1. Therapy - it turns out