kettro

One big point that would be useful is to help the fired engineer find another job. A lot of this is, as Aqua mentioned, an exercise for their conscience. The best way to alleviate it is to "do right" by the fired engineer and help them find another position. Likely would have been about as much work as this whole spiel.

Of course, OP has no requirement to do anything for them, but the easiest way to make yourself feel less bad is to make the results less bad for the person affected. Doing all of this did nothing for the person fired, except get them fired.

This would only really be feasible for a small team, such as this.

Goethe’s was always my favourite rendition (ignoring pt2). Just enough romance and woe

(I'm a Google SWE, though in firmware) I've had good experiences with Meet, both internally and externally. At least internally/gsuite, the background blur is really quite good. The public/free version doesn't itself have either background replacements, though.

If they’re going to deactivate old., I imagine they’ll kill the api too.

r/rust appears to be a decent community; lots of very good posts.

Soul of a New Machine is a great book about DG. Was required reading in my EE degree.

Not all terminals support emojis. AFAIR, xterm doesn’t. I was stuck on xterm at my last job (only terminal that really worked on that system). Emojis are for SMS, and that should be it. Use emoticons.

Tmux is great for persistence. It’s also basically required for working remotely. Allows you to, across sessions, to reconnect to the same flow. I have it set up to have multiple views of the same set of windows, so I can scroll through them independently.

I’d say it is one of the best utilities I use.

Exceptions form a secondary, unseen form of control flow. A program can exit via ‘return’ calls (as normal), or at any time by some internal function way down the stack throwing an exception for something that could have been an error code.

Exceptions are not Structured Programming: they are worse than goto, because at least goto is scope-local. If, maybe, the language enforced that all throwable exceptions are declared by the prototype, then it’d be alright. But I don’t know of any that do. So, given a function call, will it error out? Can you know without inspecting the source, if you even have it?

When I worked at Garmin, a guiding principle was “reset, and reset often”. Embedded products that you have to push out the door quickly have too much internal state to track.

I just adopted a 1yr old cat. It’s been wonderful. He’s a little monster, but he’s also on a routine, and is someone else to care for. It keeps me in sync, and I’ve been much better for it.

It’s obviously a long commitment, but I had been wanting a cat for a while.

At the same time, I’ve been actually getting help psychiatrically, which has been life changing.

Rastafarianism is a religion. I assume religious attire is not restricted.

Nim is garbage collected, Zig is manual

An important distinction is Embedded and Real-time. Embedded is the all-encompassing tent, while Real-time is a subset thereof.

Embedded includes things with GUIs, like fridges. We're not dealing with 128k of RAM. These can run basic GC'd apps just fine. Pauses really aren't any more of a concern than on desktop, or even less so.

Great post, especially for the embedded crowd. I'm looking to start using Rust in FW development but hit a couple pain points.

* First, bit field descriptors is a huge pain - where, in C, you would define an enum for the task, there isn't a real equal in vanilla Rust, other than a litany of constant variables. * Second, the over-reliance on nightly is a tough sell for - having inline asm gated makes it very hard. * Third, while format is great, it's also very heavyweight. Not having (AFAIK) variadic arguments is hard, and there isn't really an equal to printf.

I would love to be proven wrong, because I have an OS to write, and would love to use Rust.

They sorta are, if you actually read the context of each.

They're generalizing from different ends: one is saying that there are _some_ people who are not friendly if you're not white; the other is saying that _most_ people are friendly. The implication is that there is a subset of the populace that is unfriendly, and a subset that is friendly. Both comments say basically the same thing.

We've been using "shots" as a synonym for ages. I don't think it's really an issue.

I agree. Taking more than the requisite ~6 hours to do a full on-site for interview is a non-starter. I can do a take-home over the weekend, but my job has deadlines, and I don't want to be noticed.

Especially if I'm in full-on hunt-mode, I might be doing a couple interviews a week. This is totally infeasible.

I'm all for ditching the canned CTCI rigamarole, but please point to something that respects the candidate.

When I worked for Garmin, we deliberately designed products to work for as long as possible offline - the Bike Speed & Cadence Monitors (~2018) are able to work for 1 year, riding every day, then a battery change, and then another year, all before a sync to a device is required. All of the rides should be stored on-device.

Scots is not technically the same as English - they diverged about 900 years ago, and differences like ken are common (compare to French connaître, or German kennen).

you still have to get approval. But the approval is pretty rubber-stampy - my buddy applied for "tasking rtos in rust", which was accepted, despite that being incredibly general. The other side is that "if it is so trivial, why upload it?".

Macros are the lifeblood of embedded C. I have a use case where I need to read, shift, and OR a value, then write back. If I need to do that for more than 1 thing, sure as shit I'll write a macro.

The video showing that is pretty clear that none of that happened. They drove around a corner and into the crowd.

I'm someone who loves vim, and uses it every day, but I'll admit there are a couple things that are a pain (especially to learn). Coming to mind right now is buffer management. I've been able to patch over it with plugins (wintabs is great), but that's not really the best solution, usually.

I'd likely buy a small CAN chip and just connect over SPI. CAN as a protocol is a complicated mess, so having HW support is important.

The one feature I need on stable is inline assembly. It's something that should not be sidelined to the nightly compiler, and makes Rust a harder sell for the embedded world.

Yes, I know that I can just use .S files for my assembly, but sometimes I just need to access a CSR.

Been following Pigweed for a while now internally. Great testing infrastructure!

Gibbons v Ogden (1824) — states may pass quarantine laws under the interstate commerce clause.

A huge benefit of tmux is session management, where you can resume a session on a different terminal. I use it on my desktop, so I can ssh in on my laptop when working from home, and immediately pick up where I left off.

Yeah, the go/ is a shortener for goto.google.com/, and is the main way of sharing links internally.