/tool/ - Tools & Resources

I noticed the terminal keeps losing focus on my secondary pane after every build command lately. It used to stay pinned where I left it but now it jumps back to the main session every single time. It makes debugging really annoying when you can't keep an eye on logs while running commands in the other window.

trying to debug this mess after the latest provider update. reading the raw state is too much work when i can just look at the plan. honestly, if you're manually parsing json instead of using the diff, you're just asking for a headache.

saw this today and it's pretty much the same old stuff. they went through 70 tools just to end up with asana, trello, and airtable again.
>Airtable for building a customized project management app
it's fine if you want to spend hours building your own system but total overkill for most small tasks. anyone actually using wrike for the spreadsheet vibes lately?

https://zapier.com/blog/free-project-management-software

>connected, reusable workflows
really sounds like more overhead for my team to manage. i don't see how tying ai generation directly into our existing editing steps isn't going to make the whole file a mess. it's probably fine for repetitive tasks but revolutionary overkill for anything custom. does anyone actually use these kinds of connected workflows without breaking everything?

full read: https://www.figma.com/blog/the-tldr-on-figma-weave/

Been thinking about this all morning while trying to fix a broken webhook in my latest n8n setup. It's wild how much sense it makes that shifting work downstream is basically inevitable once you stop being the person who manually clears every ticket.
>The scarce skill stops being "can you build this" and becomes "should this be built, how do you know it worked, which tool actually fits, and who owns it when it breaks."
I'm not sure I'd be ready for that kind of responsibility though, especially since my current maintenance backlog is already a mess.

article: https://blog.n8n.io/why-were-moving-n8ns-automation-team-beyond-the-service-desk-model/

i'm honestly sick of watching builds just die halfway through because of that default one hour limit. it makes trying to run any decent integration test suite basically impossible without constantly splitting everything into tiny pieces. i tried bumping the timeout on a larger repo last week and it didn't even help because the runner just hangs and eats up the minutes anyway. there's no way to get clear feedback when the logs just stop abruptly. it's such a waste of credits when you can't even see where the actual failure happened. i ended up having to write a custom script just to ping an external webhook before the job expires so i'd at least know which step was hanging. it feels like a hacky workaround for a fundamental flaw in how they handle long running jobs. does anyone else use self hosted runners specifically to bypass these clock constraints?

saw this piece going around earlier about the latest asana and clickup updates. it's mostly just the usual marketing fluff about adding generative text features to everything. they're claiming wrike can actually predict project risks now which sounds way too good to be true. i've used wrike for years and it's always been a mess of manual inputs.
>AI being added to almost every app in existence
it feels like we're just drowning in more features that nobody asked for. motion is also on the list for some kind of calendar-native approach but i don't see how that changes anything if my schedule is already garbage. most of these are probably just wrappers for openai anyway. it's basically just more noise in the toolset. does anyone actually trust wrike to flag risks before they happen?

found this here: https://zapier.com/blog/best-ai-project-management-tools

another generic list of stuff devs should already be doing. they're pushing that you should use html attributes like required or type="email" before even touching javascript.
>Use HTML Validation Before Adding JavaScript
it's fine for simple stuff but it doesn't help when the backend validation logic is totally different from what the browser thinks is valid. pretty much useless for real apps that actually need custom error handling.

full read: https://www.sitepoint.com/a-practical-workflow-for-testing-javascript-forms-before-deployment/?utm_source=rss

tried using the standard formatter step but it keeps pulling the wrong index from the array. i'm stuck on this nested loop because the mapping just breaks every time the array length changes. anyone found a way to hardcode the specific key without it resetting?

zapier's new benchmark isn't just about answering questions or writing code anymore. it's actually testing if an agent can find the right row in a spreadsheet and follow rules buried in an email thread without breaking everything.
>A model that does well on general benchmarks won't necessarily handle real automation work.
it's pretty scary how easy it is for a model to just skip a step and keep going without throwing an error. anyone actually trust these agents with their crm yet?

https://zapier.com/blog/automationbench-on-specialized-intelligence-index