/tool/ - Tools & Resources

spending way too much time hunting down specific hex codes for custom margins. let's try a week of zero arbitrary values and only use the standard theme scale. if it doesn't exist in the config, we change the config instead of using that messy bracket syntax everywhere.

theme: {extend: {spacing: {'13': '3.25rem'}}}

tbh it makes the build cleaner.

i've been messing around with obsidian canvas all morning trying to map out my weekly sprints. it's way better than a flat list when you can actually see the dependencies between tasks visually. i tried dragging some markdown files directly onto the board and it really helps me spot where I'm bottlenecking. honestly, the card feature is the real winner here for quick notes. i think we should all try moving one single project into a canvas view this week to see if it actually clears the mental fog. it might just be a fancy way to procrastinate

Spent too much time lately trying to avoid custom glue code for our infrastructure provisioning. This list mentions Jenkins for CI/CD but focuses more on making sure everything actually connects without breaking the stack. I'm always worried about the maintenance overhead once you start adding layers for monitoring and orchestration.

https://blog.n8n.io/devops-automation-tools/

great, another thing to fix because github decided node 20 is dead. gotta hunt down every single action.yml that still has runs. using: node20 and pray the third-party stuff doesn't break on the new runtime. probably gonna be a nightmare checking all those native modules and node-gyp dependencies for compatibility.

more here: https://www.sitepoint.com/node-20-github-actions-deprecation-migration-guide/?utm_source=rss

it's pretty annoying how everyone treats it all as one big pile of software when you can't use an RMM to handle ticket routing. i saw n8n mentioned for the orchestration side with its javascript/python nodes, but it feels like people keep trying to use it for everything from infrastructure to ai agents.
>tools for both tend get lumped together as IT automation software

article: https://blog.n8n.io/it-automation-software/

Saw this list of free writing apps earlier and it's kind of wild how much stuff they threw in there. They have Wispr Flow in there for brainstorming out loud which sounds pretty cool if you're tired of typing everything manually. I also noticed Hemingway Editor and Grammarly on the list, but that feels a bit redundant since most people are already using those to death. It's weird seeing Miro categorized as writing software though. I usually just use it for mapping out complex logic flows or messy diagrams. Also saw GPTZero mentioned for checking AI content which is always a fun rabbit hole to fall down when you're paranoid about detectors. I've been playing around with some new markdown plugins lately that basically do half of this stuff anyway without needing a separate app open. It's getting hard to keep track of which tool does what when everything has its own little ecosystem. I still can't live without Google Docs for anything important

full read: https://zapier.com/blog/writing-editing-apps

tried running my local dev server with the same token but it's still hitting that weird unauthorized error on every single fetch request. i've already checked the scp scopes and re-authenticated the session, yet nothing changes.

{"error": "invalid_token","message": "the provided access token is expired or invalid"}

anyone know if figma changed how they handle localhost requests recently?

tried to spin up more ephemeral runners for a heavy build yesterday and the latency is ridiculous. it took nearly five minutes just to register the new instance in the pool. honestly feels like the autoscaling logic is basically broken lately.

finally seeing some actual implementation for that experimental webmcp stuff in playwright 1.64. looks like you have to manually pass the -enable-features=WebMCP flag to chromium or nothing works. i'm curious if it'll break our existing CI pipelines since we'd need a specific docker image with that flag enabled. hope the browser api stabilizes before we actually commit to it

article: https://www.sitepoint.com/playwright-1-64-webmcp-testing/?utm_source=rss

HubSpot's naming scheme is getting ridiculous. They just rebranded everything under Breeze and swapped Agent Builder for Agent Hub, so it's another mess to untangle.
>Breeze Studio became Agent Builder, Breeze Agents became Agent Hub
I remember when we used the old setup for that client's CRM integration and now I'll probably have to relearn where everything lives. It's fine if the features actually improve, but it's a headache for anyone trying to maintain documentation. **Good luck finding anything in the UI tomorrow

more here: https://zapier.com/blog/hubspot-ai-tools