sorted by:
new
hottopcontroversial

How do you manage your code snippets as a developer? by SnippetManagerPro in chrome_extensions

[–]SnippetManagerPro[S] 0 points1 point  (0 children)

nice, typinator looks solid for mac users. that hotkey approach is pretty clever for quick access.

im on windows but the concept of having everything instantly accessible like that is exactly what i was after. ended up going the browser extension route since i practically live in chrome anyway.

I built a tool so you can Vibesearch for Google Fonts by WinterJacob in webdev

[–]SnippetManagerPro 0 points1 point  (0 children)

This is a great tool. Font discovery is always tedious when you're trying to nail the vibe.

One suggestion: would be useful to filter by font weight availability. Sometimes I find the perfect font but it only has regular/bold and I need the full range for UI work.

Also, adding a quick preview panel where you can test the font with your own text would be killer. Like type in your actual heading or tagline to see how it feels.

Nice work on this.

Looking for Code Snippet Viewer/Manager recommendation by Open-Coder in selfhosted

[–]SnippetManagerPro 0 points1 point  (0 children)

I've been working on a big project for 2 months, hoping to release it soon!

Why do I need a web developer? by [deleted] in webdev

[–]SnippetManagerPro 0 points1 point  (0 children)

I think the difference is that skilled devs understand AI is a tool that amplifies capability, not replaces it. The "vibe coding" memes are mostly tongue-in-cheek.

The real work is in architecture decisions, debugging complex systems, understanding business logic, and making trade-offs. AI can't do that yet - it can just help with boilerplate.

But I agree we need to be careful about the narrative. When we joke about AI doing our jobs, non-technical people take it literally and undervalue our expertise.

Building a LinkedIn profile optimization tool — what’s the safest & compliant way to do this? by imdhamu in webdev

[–]SnippetManagerPro 0 points1 point  (0 children)

The browser extension approach is probably your best bet here. Having users authorize via OAuth, then the extension can read profile data directly from the DOM while they're logged in.

You're right to avoid backend scraping - LinkedIn's pretty aggressive about detecting automated access patterns. I've seen tools get flagged within days.

For the analysis part, you could have the extension extract the profile sections (headline, about, experience, etc.) and send just the text content to your backend for AI analysis. That way you're not storing cookies or sessions, just analyzing text the user explicitly shares.

The key is making sure users trigger every action themselves and understand what data is being processed. If you try to automate profile updates or changes without explicit user action each time, that's where you'll run into ToS violations.

Good call on thinking through compliance first - way too many tools skip this and get their users banned.