kettro

Growing up in Toronto, I used to watch the show Mighty Machines[0]. I loved it - it would show construction vehicles and airplanes, and I ogled at it for hours. I can still remember the theme song. Makes me so very happy right now remembering it.

[0] https://en.wikipedia.org/wiki/Mighty_Machines

Those aren’t builtin macros, no. There is “assert.h”, which has an ‘assert’ function/macros/thing. The LENGTHOF macro I’m not as sure. There are ARRAY_LEN macros that I’ve seen — being sizeof(x)/sizeof(x[0]) — but that’s all compile time, and wouldn’t lend itself here too well.

For C, almost everything is written by you, especially when it comes to macros. There are some “basics” that you pick up here and there, which you can copy-paste more or less.

The C preprocessor is a beautiful thing, but can get a bit tedious. Sometimes a lot tedious. But shit is textual replacement powerful!

I’ve been using an 1800 keyboard for the past few years (Leopold 980C), and think the size is perfect. I have access to all of the keys I need, all in a compact package. Add to that a programmable controller from Hasu, and it’s the perfect board for me. I never need to actually use the arrow keys, as I put them under a layer under hjkl. I also use a trackball (Kensington Slimblade), so I don’t need to have too much space to the right side of the keyboard.

This is mostly untrue (IME) - a 20% project is strongly encouraged, and is used during the performance review. Taking time off of the main projects is expected.

Ex Garmin employee: The amount of 1st party software in those watches is astounding. And it almost all gets processed on-watch.

The 3rd party app support is laughably poor, but the APIs are there. ConnectIQ apps are written in their own language (MonkeyC, which is kinda hard to use), which hinders adoption, and are generally slow and feature-poor.

But the good thing for Garmin is that the 1st party software more than makes up for the lack of 3rd party support. The music-enabled watches (eg FR645) have Spotify support, GPS, and Bluetooth music, last for an eon, and are hardy as all hell.

I write C every day in embedded RISC-V. I think Rust looks neat, and would find it cool to use. But I just convinced the team to move off of gnu90, and a huge amount of my work is in assembly.

Rust offers the idea of safety and security, but at the same time hedges itself with unsafe - fine, sure. However, my work would be nearly 100% in unsafe. So it results in an unpredictable, complex, unsafe language - a non starter.

Having just done what you suggested (Calgary -> SF), healthcare _is_ that big of a deal. When you are from the states, you honestly can’t know how massive it is to never have to worry about paying for healthcare. It is truly transformative.

It’s not even just tech companies - one of my good friends is a video editor at one of the big cable news networks, and has been a 40-hour contractor for 7 years now, with others in the team being there longer.