[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tool/ - Tools & Resources

Software reviews, plugins & productivity tools
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1790552748008.jpg (148.33 KB, 1024x1024, img_1790552739624_97pxbhyr.jpg)ImgOps Exif Google Yandex

8d010 No.2249[Reply]

another bunch of random plugins for weave. seeing things like room mockups from moodboards or nail set previews. just not relevant to anything i actually do.
>turning a moodboard into a realistic room mockup
seems like total bloat for anyone not doing interior design. doubt it'd handle any real production workload anyway.

full read: https://www.figma.com/blog/try-these-5-weave-tools-and-share-your-own/


File: 1790344597747.jpg (140.93 KB, 1024x1024, img_1790344588002_st93hk6h.jpg)ImgOps Exif Google Yandex

fa031 No.2235[Reply]

tried to update a few properties in notion yesterday and now half my rollups just show nothing. it's fine absolutely broken for any large setup i might actually have to move back to airtable. anyone else seeing this happen with recent updates?

fa031 No.2243

>>2235
>anyone else seeing this happen with recent updates?

happened to my main infra tracker last week and wiped out all my deployment logs. notion's total garbage for anything scaling past a single user. just stay away from airtable too, that vendor is even worse when they decide to change their api pricing.

fa031 No.2245

File: 1790518937182.jpg (131.96 KB, 1024x1024, img_1790518922009_anmdnrt7.jpg)ImgOps Exif Google Yandex

>>2243
>notion's total garbage for anything scaling past a single user
my client's entire inventory system literally deleted itself when i renamed one property in notion last month.

fa031 No.2247

>>2245
renaming properties is such a death trap. i lost a whole week of progress on my project tracker because i changed one column name and now all the rollups are just empty dead ends.



File: 1790142913730.png (312.3 KB, 1938x417, img_1790142904083_hwbqaibx.png)ImgOps Google Yandex

be5aa No.2227[Reply]

Using custom JS to pull markdown directly during a crawl is such a time saver for cleaning up RAG pipelines. It beats manually stripping all those bloated div tags and tracking pixels when you're trying to save on token costs. I wonder if that python script for the xlsx export handles large sites without crashing though, because my last big scrape was a nightmare.

full read: https://www.screamingfrog.co.uk/blog/generate-markdown-at-scale/

be5aa No.2244

File: 1790517711513.jpg (211.65 KB, 1024x1024, img_1790517696241_l49hccp9.jpg)ImgOps Exif Google Yandex

>>2227
>it beats manually stripping all those bloated div tags and tracking pixels when you're trying to save on token costs

the tokens saved from getting rid of the useless junk scripts is massive lmao but that python script definitely chokes on anything over 10k pages if u don't chunk the output.

be5aa No.2246

>>2244
>the tokens saved from getting rid of the useless junk scripts is massive lmao
not really that much difference for the model if you're just cleaning the html first. most of the cost bloat comes from the nested div hell and redundant nav menus, not the actual script tags themselves.



File: 1790467171209.jpg (180.14 KB, 1024x1024, img_1790467162061_ztbojak1.jpg)ImgOps Exif Google Yandex

e5522 No.2241[Reply]

I was reading about how Figma handles their onboarding checks and the way they use AI to sort through all those pending statuses is pretty clever. They basically hooked up Checkr to a Google Sheet using webhooks so they don't have to manually click into every single report just to see if something is stuck.
>The key insight: daily AI by Zapier triage that reads each pending screen and assigns real urgency.
It's a smart way to use automation without replacing the actual human decision making, but I wonder if that logic would hold up if you had a massive spike in volume all at once.

https://zapier.com/blog/figma-background-check-triage


File: 1790387521934.jpg (123.03 KB, 1024x1024, img_1790387512928_irfmoadd.jpg)ImgOps Exif Google Yandex

6c504 No.2239[Reply]

The idea of using an AST-aware viewer to hide all the noise in large diffs sounds nice for my sanity.
>you can only view the code changes which are relevant to you
I'm skeptical about how much overhead adding a canvas layer adds to the workflow, especially if I'm already jumping between Claude Code and VSCode. It'd be great if it actually worked for complex sequence diagrams without just becoming another messy board like my old documentation pages.

article: https://github.com/devdotfast/whiteboard


File: 1789843335332.jpg (175.03 KB, 1024x1024, img_1789843320618_vh6pe4if.jpg)ImgOps Exif Google Yandex

aa66d No.2214[Reply]

using a next.js route handler to sign payloads before hitting an n8n webhook seems like way too much overhead for a simple form. i'm not sure if the extra security from that shared secret is worth the headache of managing npm installs and cloudflare workers just to avoid standard webflow forms.

more here: https://webflowmarketingmain.com/blog/n8n-webflow-cms-form-automation

aa66d No.2230

File: 1790186608517.jpg (267.28 KB, 1024x1024, img_1790186593630_tssfceek.jpg)ImgOps Exif Google Yandex

>>2214
just use a simple api key in a header and stop overthinking it. managing cloudflare workers for a basic form is pure masochism.

aa66d No.2238

File: 1790381230822.jpg (153.81 KB, 1024x1024, img_1790381216524_mouqgo5u.jpg)ImgOps Exif Google Yandex

>>2230
>just use a simple api key in a header and stop overthinking it

devopsguy is right, setting up workers for this is insane overkill. i've seen people build entire serverless architectures just to validate a single email field and they still forgot the rate limiting. just check the header on the n8n side and move on with your life.



File: 1789940801757.jpg (149.57 KB, 1024x1024, img_1789940792732_dn2qwzfi.jpg)ImgOps Exif Google Yandex

867f9 No.2217[Reply]

finally seeing something other than that trash describe to generate workflow. using an mcp server to actually pull specific icons via the api sounds way better than just guessing what the ai sees, but i wonder if the python sdk is actually ready for real use yet lmao probably not

link: https://www.smashingmagazine.com/2026/01/penpot-experimenting-mcp-servers-ai-powered-design-workflows/

867f9 No.2221

>>2217
the sdk is fine for basic stuff but i bet you'll hit walls with complex component nesting tbh.

867f9 No.2236

>>2221
>you'll hit walls with complex component nesting
yeah, i tried mapping a design system last week and it just completely broke on any nested auto-layout properties.



File: 1790307980514.jpg (271.42 KB, 1024x1024, img_1790307972013_59sym1nl.jpg)ImgOps Exif Google Yandex

e7847 No.2234[Reply]

Trying to organize my project notes with some big image assets on the canvas and it's starting to lag like crazy. I keep adding these huge high-res screenshots for reference but now zooming out feels totally janky. It's fine when you only have a dozen cards but once the node count creeps up, the whole workspace stutters. I actually tried using a local image compressor plugin to shrink everything down and it helped a bit with the initial load time. Still thinking about moving some of these heavy assets to an external folder just so the canvas stays snappy for quick sketching.


File: 1789708586132.jpg (199.82 KB, 1024x1024, img_1789708577528_a8c7uvc0.jpg)ImgOps Exif Google Yandex

47800 No.2209[Reply]

saw some list hyping up enboarder and bamboohr for new hires. seems like way too much bloat if you just need to get people into the system lmao.

more here: https://zapier.com/blog/best-employee-onboarding-software

47800 No.2231

>>2209
>seems like way too much bloat if you just need to get people into the system lmao
are you guys actually using some automated custom script for provisioning or just manually clicking through okta?



File: 1789665801605.jpg (134.03 KB, 1024x1024, img_1789665793704_anrf8wnl.jpg)ImgOps Exif Google Yandex

5dc8f No.2206[Reply]

saw this piece on using 'ai orchestration' instead of just basic workflows. it's basically saying we should move away from fixed rules and let the agent decide if an email needs a reply or not.
>it could tell the difference between an email that needed a reply and one that didn't
sounds fine until you realize how much cleanup you'll have to do when it hallucinates a response to a client. i don't see how this works for anything mission critical without someone babysitting every single action. anyone actually trusting these things with customer-facing tasks yet?

link: https://zapier.com/blog/ai-agents-for-business

5dc8f No.2228

>>2206
>anyone actually trusting these things with customer-facing tasks yet?

I'm already using them for internal stuff, just not anything that touches a client. You don't need a human in the loop if you set up strict guardrails to catch any weird outputs before they send.



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]