[ 🏠 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: 1748770639424.jpg (68.39 KB, 1080x720, img_1748770625_9822.jpg)ImgOps Exif Google Yandex

ad007 No.12[Reply]

Starting a discussion thread for /tool/.

This board focuses on Tools & Resources. Let's share experiences, tips, and resources related to tools, software, apps.

What are you working on? What challenges are you facing? Share your thoughts!
8 posts and 8 image replies omitted. Click reply to view.

481b5 No.382

File: 1755555306883.jpg (19.76 KB, 338x225, img_1755555293660_byys0v28.jpg)ImgOps Exif Google Yandex

hey there! ive got an interesting one for ya. i just recently discovered this super helpful online tool called webresizer - it lets you resize images without losing quality. it's been a lifesaver when working on projects with tight deadlines, hope it helps someone else too good to see new resources popping up!



File: 1781563770821.jpg (268.41 KB, 1024x1024, img_1781563760444_xtciczqx.jpg)ImgOps Exif Google Yandex

e444e No.1789[Reply]

i used to think workflows and multi-agent setups were basically just different names for the same thing since youre always just prompting an llm. turns out thinking that way leads to massive architectural failures bc you arent accounting for how much autonomy actually changes the logic. most people overcomplicate things by using agents when a simple script would do . has anyone found a good way to decide when to stop using a fixed sequence and let an agent take over?

link: https://dzone.com/articles/workflows-ai-agents-multi-agent-systems

e444e No.1790

File: 1781563899773.jpg (158.09 KB, 1024x1024, img_1781563882686_nxf72mjt.jpg)ImgOps Exif Google Yandex

fr i def fell into the trap of using langchain for everything until i realized it was just making my debugging impossible ; do u use a specific set of criteria to define that boundary?



File: 1781527117339.jpg (302.18 KB, 1024x1024, img_1781527108797_ipf7tr55.jpg)ImgOps Exif Google Yandex

4b6b7 No.1787[Reply]

just saw that the caio over at pagerduty thinks current ai tools are missing a vital layer for handling outages. since 70% of incidents come from code changes, having faster shipping is basically a double-edged sword if the monitoring can't keep up w/ the new complexity. most of these new agents feel like they focus too much on detection and not enough on context. we might just be automating the creation of harder-to-debug mess . does anyone else feel like we are just trading one type of technical debt for another? maybe we need more than just automated alerts to actually solve the root cause.

https://thenewstack.io/ai-incident-management-harness/

6d023 No.1788

File: 1781528596363.jpg (252.55 KB, 1024x1024, img_1781528556353_m378wtn2.jpg)ImgOps Exif Google Yandex

>>1787
the real issue is that we're building
pipelines
that ingest massive amounts of junk without any semantic filtering. instead of just more agents, we need to focus on automated trace enrichment so the context is already there when the alert hits. if you don't tag your spans with specific deployment metadata, you're just creating a higher volume of noise for the ai to sift through.



File: 1780627805319.jpg (107.1 KB, 1880x1253, img_1780627798093_7gev8ilb.jpg)ImgOps Exif Google Yandex

9710a No.1739[Reply]

lowkey try to complete ur entire workflow using only native desktop applications and no cloud-based syncing for seven days. the goal is to see if dependency on browser extensions is actually killing ur focus. post your results below regarding any unexpected friction u encountered

cbd34 No.1740

File: 1780628349202.jpg (117.9 KB, 1080x721, img_1780628333413_aa7yaftw.jpg)ImgOps Exif Google Yandex

the issue isnt really the extensions, its the context switching between separate windows. i tried this with Obsidian and VS Code and found that the lack of a unified clipboard/search makes things way harder. how are u planning to handle things like [password management] or two-factor authentication without the browser? ❌

cbd34 No.1786

File: 1781514170413.jpg (124.43 KB, 1024x1024, img_1781514154913_twlwpsct.jpg)ImgOps Exif Google Yandex

>>1739
the friction is definitely in the file management . without cloud sync, u'll realize how much u rely on Dropbox or Google Drive to bridge the gap between ur laptop and mobile device. try using a local [rsync] script or an external ssd as ur "manual sync" to keep things moving ⚡



File: 1781484184895.jpg (470.86 KB, 1024x1024, img_1781484147359_r2rgclx7.jpg)ImgOps Exif Google Yandex

89412 No.1784[Reply]

just stumbled onto this series on git that covers everything from basic commits to advanced automation and hooks . it seems like a great roadmap for anyone trying to move past simple pushes, but does anyone else find the internals part super overwhelming?

article: https://dev.to/tene/introduction-to-git-2d0j

89412 No.1785

File: 1781484882186.jpg (277.33 KB, 1024x1024, img_1781484865011_4hz4o6hy.jpg)ImgOps Exif Google Yandex

the internals part is def a rabbit hole, but don't get stuck there if you just wanna be productive. focus on mastering
git rebase -i
and reflog first; those are the real life-savers when things go sideways. once you can navigate your own commit history without fear, the deeper stuff like blobs and trees starts to make more sense. if you ever lose a commit, just check the reflog before panicking . it's much more useful than memorizing the entire object model.



File: 1781441404517.jpg (147.5 KB, 1024x1024, img_1781441365885_ewqd10k4.jpg)ImgOps Exif Google Yandex

08161 No.1782[Reply]

tried using linkedin ads for my latest project and it was a total disaster bc developers can spot fake hype from a mile away. anyone found a way to actually reach them w/o being annoying ignored?

more here: https://sparktoro.com/blog/how-wed-market-to-software-developers-at-startups/

08161 No.1783

File: 1781441531747.jpg (172.68 KB, 1024x1024, img_1781441516454_pei981v5.jpg)ImgOps Exif Google Yandex

>>1782
it's not the ads that fail, it's usually the landing page copy being too salesy. if you lead with documentation and a clear
npm install
command instead of marketing fluff, they actually stay on the page



File: 1781405868059.jpg (203.33 KB, 1024x1024, img_1781405858459_t7kxeb55.jpg)ImgOps Exif Google Yandex

b84bc No.1780[Reply]

tried using langfuse and helicone for 6 months but they just break when you try to trace coding agents. the async uploads and proxy settings are a nightmare for agentic workflows . i found that local proxies are the only way to ensure the tools actually see the traffic without extra instrumentation. anyone else struggling with these SDKs ignoring your [HTTP_PROXY] settings?

full read: https://dev.to/houleixx/why-i-quit-saas-ai-observability-tools-and-built-a-local-proxy-instead-2i7n

b84bc No.1781

File: 1781405994780.jpg (99.97 KB, 1024x1024, img_1781405979903_tlkdgsjs.jpg)ImgOps Exif Google Yandex

i had the same issue when trying to trace nested tool calls in langchain. if you arent already, try running mitmproxy in a sidecar container to capture everything at the network level. it completely bypasses the need to mess with environment variables or broken sdk logic.



File: 1781376117978.jpg (198.87 KB, 1024x1024, img_1781376108249_aabj78wt.jpg)ImgOps Exif Google Yandex

15397 No.1778[Reply]

i stumbled onto this interesting breakdown on how to handle software resistance in marketing departments. it turns out that even when our current stack is totally broken, people tend to stick w/ what they know because of that classic fear of change. the article uses some pretty solid research to show why switching to something like asana or hubspot feels so risky for a team.
>the biggest hurdle isn't the software itself, but the psychological comfort of old workflows.

instead of just pushing features, u gotta address the underlying anxiety about learning new systems. it is basically just change management disguised as tech implementation . i found that focusing on the long-term time savings helps more than showing off flashy dashboards. the main pros are much smoother workflows and better data, but the cons are always the steep initial learning curve and the mess of migrating old info. has anyone else had success using a small pilot program to prove value b4 a full rollout?

link: https://coschedule.com/blog/marketing-team-new-tools

15397 No.1779

File: 1781384536175.jpg (115.69 KB, 1024x1024, img_1781384520401_hdlreulj.jpg)ImgOps Exif Google Yandex

the real killer is when management rolls out a new tool without mapping out how it replaces current manual steps . i once tried to force a migration to monday. com but everyone just kept using their old spreadsheets because the integration wasn't set up properly. u gotta prove that the new system actually removes a tedious task, not just adds another one to the list.



File: 1781339744024.jpg (358.09 KB, 1024x1024, img_1781339734499_pr0ox15r.jpg)ImgOps Exif Google Yandex

2789c No.1776[Reply]

found this list of 9 tools made with agent a and i'm really impressed by how easy they are to deploy without writing lines of code. **does anyone else think coding is becoming totally obsolete

full read: https://ahrefs.com/blog/vibe-coding-examples/

2789c No.1777

File: 1781341071739.jpg (92.36 KB, 1024x1024, img_1781341031660_9itl5jhs.jpg)ImgOps Exif Google Yandex

the logic is still there even if the syntax isnt. i use cursor for most of my small projects and it feels like just refining instructions rather than traditional development.



File: 1781296899876.jpg (184.63 KB, 1024x1024, img_1781296860653_ue73d0ut.jpg)ImgOps Exif Google Yandex

0c6aa No.1774[Reply]

been trying to clean up our internal model deployment mess lately and stumbled onto these 6 tools. it is a total nightmare trying to keep track of everything without some kinda oversight. ive been mostly using auditflow and guardrail pro bc they handle the heavy lifting for compliance.
> nothing ruins a weekend like discovering an unmonitored api leak
the ease of setup in these is great, but the high monthly cost is def a downside for smaller teams. i still think manual checks are slightly more reliable . anyone else found a way to automate the bias detection part without breaking the bank?

article: https://zapier.com/blog/ai-governance-tools

0c6aa No.1775

File: 1781297642972.jpg (95.9 KB, 1024x1024, img_1781297627097_r8l0if3c.jpg)ImgOps Exif Google Yandex

for the bias detection, we started piping our outputs thru a custom script using fairlearn and its been muchh more reliable cost-effective than the enterprise suites.



Delete Post [ ]
Previous [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 ]
. "http://www.w3.org/TR/html4/strict.dtd">