breaker-and-a-half

@breakerandahalf@fedi.tali.network
9 Followers
25 Following
186 Posts

Writing bios is hard, largely because succinctly describing oneself to an extent that allows others to see oneself to the same extent as one sees themselves is impossible. What follows should be a serviceable approximation.

In brief, I am a computer science student, amateur radio operator, electronics hobbyist, technical theatre person, railfan, electric power transmission appreciator, cyclist, and nerd.

Header image by Harvey S. Rice or Craig Holstine and avatar image by Robert C. Stewart. Both are from the Historical American Engineering Record project, which produces documentation singularly amazing in breadth and depth.

Posts and boosts may sometimes include strong language. I don't post or boost NSFW content (in the traditional sense—occupational safety hazards are sometimes discussed, though).

I welcome disagreement, criticism, feedback, and debate, but do not tolerate hatred or bigotry. If you engage me in good faith, I will gladly reciprocate (provided I have the time to engage at all).

Pronounshe/him
TimezoneAmerica/Los_Angeles
LocationPortland, OR, USA
breaker-and-a-half3d ago
Show threadbreaker-and-a-half3d ago
Corollary: calling your own argument "speculative" is a succinct way to be honest about the foundation of your arguments/predictions, and steers others towards examining whether your assumptions and speculation are correct or not. It can thus be very useful in the right sort of discussion.
Show threadbreaker-and-a-half3d ago
Corollary: calling your own argument "speculative" is a succinct way to be honest about the foundation of your arguments/predictions, and steers others towards examining whether your assumptions and speculation are correct or not. It can thus be very useful in the right sort of discussion.
breaker-and-a-half5d ago
BET IT ALL ON DOSKELJun 28
the fediverse is the only platform where i could find other people who have recreationally read the DoT Manual on Uniform Traffic Control Devices
breaker-and-a-halfJun 21

Argument tip: if an argument relies on a prediction about the future or present that you doubt, the best way to counter that argument diplomatically could be to call it "speculative". This is a good way of pointing out that that argument relies on information that is unlikely to be true without directly accusing the maker of the argument with lying or arguing untruths. It also carries with it the implication that it's prudent not to rely on the truth of speculation that could be wrong. (You may want to state the latter implication aloud for the avoidance of doubt or to strengthen your argument.)

If someone is suggesting a course of action that relies on an unduly speculative prediction to work, then you may want to suggest an alternative that assumes that the speculative prediction will not come to pass and acts accordingly, but provides for the suggested course of action to be followed if the prediction is correct.

breaker-and-a-halfJun 20
Robert RoskamJun 20

Kernighan's Law summarized: Debugging is twice as hard as writing code. If you write code as cleverly as possible, you are not smart enough to debug it.

The most clever solution is rarely the best for a team environment.

Code is read far more than written. Choose clarity over cleverness. Your future self will thank you.

breaker-and-a-halfJun 11
The only SI ↔ US Customary unit conversion that I know is 1 in == 25.4 mm, and I know that because of constantly seeing parts whose lead pitch is quoted as "2.54 mm (0.1in)" or the like.
breaker-and-a-halfJun 11
JPJun 9
digging around in my 2K Marin-era (2008-ish) archives and came across this outstanding error message, props to whatever IT(?) person decided to phrase a simple seat license conflict as "Human Combat Required":
breaker-and-a-halfMay 8
I made this edit of a World War II-era poster (original here) that turns it into a reminder about Kerckhoffs's principle, the rule that security of a system must not depend on maintaining the secrecy of the system's design. "Security through obscurity" is just a fancy name for hiding your problems instead of fixing them.
File:"An ostrich only thinks he "covers up." - NARA - 513846.tif - Wikimedia Commons

Show threadbreaker-and-a-halfApr 30
I feel like weaving lies outside the canon of things that I can expect my nerd friends to be interested in, and this has always felt odd because weaving has amazing art, science, engineering, and history behind it. It wasn't something I was particularly familiar with until about a year ago, and it wasn't until recently that I started reading about it. (From what I've read of it thus far, the Mechanism of Weaving, published 1911, provides a good overview of the mechanical aspects of weaving in that era.)
breaker-and-a-halfApr 30

Do you self-identify as a technology or engineering enthusiast and know or research anything having to do with weaving as a part of this enthusiasm?

(context given below.)

Engineering enthusiast; interested in weaving
100%
Engineering enthusiast; not interested
0%
Not engineering enthusiast; interested
0%
Not engineering enthusiast; not interested
0%
Poll ended at .
Weaving - Wikipedia