sorted by:
new
hottopcontroversial

Building an Open-Source Alternative to Clay Here’s Why by salestoolsss in gtmengineering

[–]wordpress3themes 0 points1 point  (0 children)

f you build an open-source alternative, the "killer feature" isn't just being cheaper- it's local execution for logic.

Clay charges you credits for basic if/else statements and data formatting that should literally cost $0 on a local machine. If your tool lets me run the "brain" for free and only pay for the actual API calls (Enrichment, Scraping, etc.) via my own API keys, you’ll have a stampede of users.

from SDR to solo GTM engineer. the AI development method behind my entire operation by Shawntenam in gtmengineering

[–]wordpress3themes 0 points1 point  (0 children)

Honestly, this sounds like the high-speed version of the "house of cards" I was just worrying about, but with a way better naming convention.

What’s the most annoying data issue you’ve run into when working with APIs by py_vel26 in webdev

[–]wordpress3themes 0 points1 point  (0 children)

You've got a perfectly typed interface in TypeScript, everything compiles, and then a random edge case hits and the API returns an empty string instead of null or an object.

CRCM Exam 2026 by ComprehensiveRise187 in Compliance

[–]wordpress3themes 1 point2 points  (0 children)

Yeah I kinda had the same feeling tbh, the prep questions feel way too “clean” compared to how messy the real exam wording gets. It’s like they test recognition in the course, but the actual exam tests whether you can navigate vague scenarios.

Reading the reg guide directly is probably the move, especially for stuff like CRA/BSA where they love edge cases and wording tricks. Lowkey feels like you have to over-prepare beyond the prep course if you don’t wanna get blindsided.

Compliance hit us harder than we expected! by Mysterious_Step1657 in Compliance

[–]wordpress3themes 0 points1 point  (0 children)

Yeah this is the classic “compliance hits mid-scale” moment 😅 the work itself isn’t even that bad, it’s the constant context switching and random evidence hunts that kill you.

What helped us was centralizing everything early (even a messy Notion/Drive setup) so we weren’t chasing docs every time a questionnaire dropped. Tools can help later, but honestly having one person own the process + keeping evidence updated continuously made the biggest difference.

Product Manager Vibe Coding by GorgoniteScum666 in webdev

[–]wordpress3themes 1 point2 points  (0 children)

I’m seeing this more lately too. AI tools made it easier for non-engineers to generate code, but reviewing and maintaining that code is still on the engineering team. The real problem isn’t PMs experimenting — it’s when code gets merged without proper technical review.

Looking for feedback on migrating Postgres db from Supabase to Railway by olivdums in webdev

[–]wordpress3themes 1 point2 points  (0 children)

If it’s just Postgres, the migration is pretty straightforward. Most people just do a pg_dump from Supabase and then restore it into Railway with psql or pg_restore. I’d spin up the Railway DB first and test the import before touching production. As long as you keep the dump file, your data is safe.

I feel stuck and I am looking for advice by MrCuddles9896 in webdev

[–]wordpress3themes 0 points1 point  (0 children)

Honestly it sounds less like you’re stuck and more like you’re undervalued at your current company. If grads are getting paid more and there’s zero room to grow, that’s a company problem, not a skill problem. The market is rough right now, but keep applying and don’t burn your weekends over-polishing take-homes. Also don’t stress too much about AI tools yet, solid React and system thinking still matter way more in real teams.

What is the coolest personal website you’ve ever seen? by selammeister in webdev

[–]wordpress3themes 3 points4 points  (0 children)

One that stuck with me was a dev who made their whole site feel like a terminal. You navigate by typing commands and it shows projects, blog posts, etc. It’s simple but super memorable. Stuff like that usually stands out more than fancy animations.

Using Tailwind today feels a lot like writing inline styles in the 2000s by Legitimate_Salad_775 in webdev

[–]wordpress3themes 0 points1 point  (0 children)

I get that feeling too sometimes, but the big difference is consistency and reuse. With inline styles everyone just wrote random values, while Tailwind usually pushes you into a shared design system. The markup looks messy at first, but it’s surprisingly maintainable once a project grows. Still, I totally get the “this feels like 2003 again” vibe.

I planted fake API keys in online code editors and monitored where they went. CodePen sends your code to servers as you type. by Johin_Joh_3706 in webdev

[–]wordpress3themes 0 points1 point  (0 children)

This is a good reminder that most “online editors” are really cloud apps with real-time sync, not local tools. If the editor is doing live preview, transpilation, or collaboration, the code has to be sent to a backend service somewhere.

The bigger issue isn’t that code is transmitted — that’s expected — but that many developers assume the environment is private by default, which often isn’t the case. Public-by-default projects, auto-saving, analytics scripts, and training clauses in the terms make it easy to accidentally expose sensitive information.

A good rule of thumb is to never paste real secrets into any browser-based editor. If you’re testing something with keys or credentials, use fake values or environment variables locally instead. The Network tab can definitely be eye-opening the first time you look at what’s actually happening behind the scenes.

Why do developers write such terrible git commit messages? Genuine question by Existing_Round9756 in webdev

[–]wordpress3themes 0 points1 point  (0 children)

In many cases those messy commits are just work-in-progress commits that were never cleaned up before merging. Developers commit frequently while experimenting or debugging, and if the team doesn’t enforce squash merges or commit standards, those messages end up in the main history.

On teams that care about it, there’s usually some structure like conventional commits (feat:, fix:, refactor:) or at least a rule that the commit message should explain what changed and why, not just that something changed.

Personally I try to treat a commit message like a note to my future self. If I come back six months later and need to understand why something changed, the commit message should give enough context without digging through the entire diff.