markrages

By "industry" you mean "electronics hobbyists"?

> one of the industries greatest hardware designers

Is this meant sarcastically?

Is this related to skidl https://github.com/devbisme/skidl ?

I did this a while back:

https://hackaday.com/2005/10/25/audio-output-from-a-serial-p...

(Looks like somebody mirrored it to github at https://github.com/koniu/ttyplay)

"Creativity is the residue of time wasted" -- dubiously attributed to Einstein

You can load Black Magic Probe firmware on a bluepill and have JTAG for about $2. I also ported it to nRF52840 if you have an extra dongle laying around. Or esp8266 for debugging over wifi (wireless JTAG is super useful sometimes.)

Segger has been really successful at marketing "JTAG == JLink" but it is just not true.

Scott Devine, YouTube bass teacher, wears a glove while playing. It's a hack to get around focal dystonia. He discusses it at https://youtu.be/a4KFCDIYEQM

Modern Python is sure ugly.

, and

> disallows the ascii slash

Netcraft confirms!

The centralized alternative is called 'github' and while it has not entirely taken over, it has certainly made some inroads.

I remember when Python was simple.

The traditional approach to proprietary printer drivers is to found a software movement that reimplements the entire operating system from scratch, and invent licenses that prevent distributors from keeping their changes to the system secret.

This approach has been somewhat successful.

This is how layers of process accrete around an organization, each to address a previous screwup. Until nothing gets done at all, except fulfilling the requirements of the process.

There is a tradeoff between frequency and severity of screwups and rate of progress. This tradeoff should be made deliberately; just going from "screwups always bad" will not reach the best balance for the health of the organization.

I second this advice, and would add another reason: Buy an analog scope while you can still find them for cheap! They don't make good ones anymore. The analog scope is a lifetime purchase.

But the calibration point still applies. On my Tek 454, there are calibration knobs built right into the UI. The user is expected to tweak and calibrate as they go, and depending on the measurement. (Often the shape of the waveform is all you are trying to see.)

A DMM is a precision tool. Especially a good 6.5 digit desktop one.

An oscilloscope is fantastically useful, but it is not a precision tool. Calibration is just OK, and most use 8-bit converters.

Maybe I was thinking of Arrow.

As of my order last week, Mouser no longer offers economy shipping.

Most of my orders from Mouser are things that are out-of-stock at Digi-Key. Maybe this is how they lose and join the also-ran, only-for-big-companies distributors like Allied and Newark.

I seem to remember depletion-node FETs were available in the late 90s, which could have solved this problem in a more elegant way than a "lifetime" battery.

In my last 20 years of using emacs, I have spent about 45 minutes total fiddling with the config. (Before that I spent a little more time getting it set up.) Am I missing out on something?

Remember -Wall isn't all. -Wall -Wextra is the new -Wall.

I recommend asan too, where possible.

I tried it up to last month in Ubuntu 22.04. I changed back because I got tired of the broken focus-follows-mouse and Ubuntu tracks the bug but doesn't fix it.

sloppy-focus-follows-mouse is the feature that keeps me on X. A basic Unix feature forever, completely broken in Ubuntu's Wayland.

Scrum works best if you can find a true Scotsman to be the Scrum Master.

The examples given are more "what" changed than "why" it was changed. These are low-value commit messages because they are redundant with the content of the commit itself.

It is almost like signing all your commits with your name or the current date. (Yes, I had a coworker who did this.)

Better commit messages tell you what the situation was around the commit: Ticket number, or who wanted the change, or any other context that might tell you why the code was changed the way it was.

Consider the dev accessing your commit through "blame". What does that user need to hear? Not which file or subsystem was changed. But the reason there is a change in the first place.

My habit has been to prepare longer commit messages, a paragraph or two of explanatory text for that future developer, who is most likely future me.

Policy at my company now squashes all my carefully-prepared commit messages into the one-liner "Merged $BRANCHNAME into main". I will probably just switch to the three character commit message "WIP" like my coworkers have done.

By definition, since it won't run on a supported runtime.

If I don't take notes I instantly tune out of the meeting.

I just type into org-mode. The notes are rarely useful later, but I keep them in a folder that I can grep through.

Oven-stabilized crystal oscillators are a time-honored technique for precision electronics.

It turns out that no matter how carefully you stabilize a circuit for temperature changes, it gets much more stable when held at a controlled temperature.

Arrangements for this go from simple (gluing the component to a PTC thermistor driven at constant voltage) to elaborate (thermocouple-controlled PID heater in multiple styrofoam insulating enclosures). There are some pictures at https://en.wikipedia.org/wiki/Crystal_oven

I've never seen PCB traces used for this, but I've always wanted to try making a clock from a piece of LCD color-change material laminated to a PCB with traces in seven-segment patterns.

The modified version is saying that ChatGPT is the non-native speaker, not the original poster. It is a different meaning.

It is probably wrong too. ChatGPT is a native English speaker as far as I can tell.