Tootfinder

The thesis I was reading spent the majority of it's time focused on John Boyd's OODA loop as a tool for critical analysis in high pressure or constrained situations. Table top exercises could also benefit from using these steps to slow down the thought process, expose what's actually happening, and sharpen these tools.
So each step could start by observing (which is generally what the GM will tell you, but you may ask additional questions to refine observational thinking). What do you look for in any given situation? How do you gather data? What sources do you use?
Next you would orient. Talk through this out loud. What does that data mean? How this fit what you already know, or does it challenge your assumptions? Are you observing something related to a previous action? What does that tell you about your previous action or actions? How do you turn the data you observed into intelligence you can act on? How do your observations narrow the options for the next possible action?
Then you decide your action. But you're not simply deciding, you're coming up with a hypothesis that your action will test. Anything you do is an opportunity to learn something about the world, about your situation, about the accuracy of the model you're using to make decisions. What belief does your next action imply? How will you know if that action was correct or incorrect? What observations would challenge your hypothesis? What observations would confirm it? Are those mutually exclusive, or are there additional observations or actions you must make to clarify things?
Then act. Finish your turn by choosing your action or actions (individually or collectively). Perhaps take a moment to write down notes, like what your observations, your hypothesis, and if you think your previous hypothesis was confirmed or refuted. You can review these all later to refine your thinking.
By exploring these ideas in a safe environment, you can train your brain to run through the process at high speed when under pressure. This helps you avoid panic. It's a lot like slowly practicing marshal arts moves until they become muscle memory, which then just happen without thought when needed.

I'm getting into #IKEAHacking and #DIY, making some cabinet doors, raised garden beds, and "boxing in" existing IKEA wardrobes.
Don't have a huge budget, but what power tools should I prioritise? I have a drill, thinking some kind of saw, maybe a router? Hoping for advice from the hive mind!

Fascists, cryptobros, young men who play tons of video games and have very little ethical thinking skill and frame everything as a competition to be won, seasoned software engineers, accelerationists, business guys, Business Guy Grifters, hyper-neoliberal technocrats, wannabe software engineers, kids who dream of creating video games, product designers who want to prototype things, capitalist hangers-on and investmentbros who are looking for the next gamble for their money, Chinese tech company employees, third world techies who use these tools to be able to play at the rich countries tech industry table, edgy young men who want to “decensor" everything including open models, tech enthusiasts who want to try every new thing.
And very, _very_ few women. And very, very few experts.

Thinking about making a suite of FPGA (and i guess potentially ASIC) debug IPs that integrate with ngscopeclient. In part because Efinix's debug tools are... Suboptimal.
The flow will be ADIv5 esque but not exclusively JTAG/SWD centric.
At a high level my concept is to root with a bridge from various external interfaces (starting with UART) to APB. The bridge will offer commands for 32 bit read and write, getting some kind of id code / version, and querying the base address o…

In summary then, it is indeed quite like being at school. Half hour lessons on things that probably won't ever actually be useful to know in your particular job of varying levels of interest. Mostly pretty low interest honestly. Bumping into colleagues between lessons.
Learned the names of a couple of tools I might try. One google search would have gotten me those but I guess it's a question of thinking to look for them.
If you can judge the mood of an industry from a random selection of talks from a single conference then the industry is very optimistic that they can make AI write a lot of software.
It seems to think this is likely to mean fewer programmers rather than there being more software meaning more workers.
It wasn't as AI heavy as I thought when I first glanced at the program. Managed to mostly be not-ai I think.
Nobody talking about the ethical implications or suggesting joining a union and only one talk about the environment issue at all, it not really noting how much power the industry is about to take.
Liked having a few meals in amserdam with colleagues I never usually see (mostly remote workers, including me). The boss is pretty good at picking people really.
Get a day or so of holiday now too.
#devWorld