Field Notes

The key to setting up fans on the rpi.

sudo vi /boot/firmware/config.txt

dtoverlay=rpi-poe
dtparam=poe_fan_temp0=65000,poe_fan_temp0_hyst=5000
dtparam=poe_fan_temp1=70000,poe_fan_temp1_hyst=5000
dtparam=poe_fan_temp2=75000,poe_fan_temp2_hyst=5000
dtparam=poe_fan_temp3=80000,poe_fan_temp3_hyst=5000

Healthy tips for giving better feedback in design crits

It's time to continue learning...

Enter Figma MCP

I recently ran some tests to check if there's potential to remove the abiguity of designs needing to read code or engineers needing to be experts inspecting design in figma. Here's what I learned works well:

• auditing variables in use
• checking for text updates
• ensuring spacing decisions aren't left to the "eye"

There's more to learn, but so far I'm hopeful. Cheers!

Here's the thing: consistency itself doesn't make money.

What makes money is predictability.

Shoutout J Gibbens for the article and a different way to assess ROI particularly around design systems.

Written for Claude Code, need to test it out for Gemini. Should help with decision making before writing any code. WILL use more tokens.

Paste at the bottom of a prompt or workflow file:

- Serena for semantic code retrieval and editing tools
- Context7 for up-to-date documentation on third-party code
- Sequential Thinking for any decision-making
- Ultrathink (part of Claude's extended thinking model)