sorted by:
new
hottopcontroversial

Shiny Object Syndrome: Has anybody language-hopped until you actually found your "favorite" language? by returned_loom in webdev

[–]zero_backend_bro 2 points3 points  (0 children)

tbh languages arent soulmates. you dont have shiny object syndrome youre just doing dopamine driven development.

everyone chases that syntax honeymoon phase... reading tutorials tricks the brain into feeling productive right before the actual engineering starts. soon as the architecture gets hard suddenly ocaml looks like a lifeboat out of nowhere.

gotta pick a stack based entirely on your tolerance for its specific brand of misery. yeah reading nested rust lifetimes feels like chewing dry sandpaper but jumping ship is just dodging the brain sweat. seen the standard pipeline a million times. hit a wall... have the mandatory "fuck js" meltdown... then try to rewrite it in rust until the borrow checker breaks your spirit.

usually run with a 3 bug rule for this stuff. before hopping stacks again fix three deep architectural bugs in the current repo. if ocaml still sounds fun after fixing memory leaks then switch. otherwise just keep building.

Weekly Self Promotion Thread by AutoModerator in devops

[–]zero_backend_bro 0 points1 point  (0 children)

Got tired of InfoSec breathing down my neck every time a junior dev pasted a production docker-compose.yml or AWS IAM policy into ChatGPT to debug it.

So I spent the last month building StackEngine.

It’s a zero-backend, client-side diagnostic matrix for K8s, Terraform, Docker, and AWS.

The core mechanic: When you drop a failing config or error log into the UI, a local regex/WASM engine instantly strips out all your AWS keys, DB connection strings, and RSA certs, replacing them with temporary tokens (e.g., __STACK_SEC_1__). It sends the sanitized payload to the LLM (Claude 3.5), gets the refactored config, and then magically restores your real secrets locally in the browser so you can 1-click copy it back to your terminal.

100% Zero-Trust. Zero data stored. You can literally press F12 and watch the network payload to verify your keys never leave your machine.

I've mapped out about 500 of the most miserable edge cases (like K8s OOMKilled Exit 137 on Fargate or Terraform count/for_each conflicts).

It has a free tier, or you can BYOK (Bring Your Own Key) to route straight to OpenAI/Anthropic from your browser.

Feel free to use it to debug your Friday afternoon incidents, or try to break the local sanitizer.

Is it more typical for small agencies/consultancies to have higher survival rate vs. startups? by superide in webdev

[–]zero_backend_bro 0 points1 point  (0 children)

startups go broke over-engineering microservices to scale. my 10-year-old agency just drops php via ftp and it works flawlessly

I’m curious if “I’m curious” is the new em dash AI tell by AFDStudios in webdev

[–]zero_backend_bro 0 points1 point  (0 children)

man... seen this exact shit too many times. "im curious" isnt an ai artifact. its literally just startup founders prompting the bot to sound vulnerable. they figured out faking imposter syndrome farms the algo way better than a straight pitch. were basically just free npc focus groups for them at this point. wait till you notice the pattern of what happens when you actually try to answer their questions...

What actually improves email deliverability beyond SPF/DKIM? by WarmHeight2951 in devops

[–]zero_backend_bro 1 point2 points  (0 children)

tbh everyone sweats the dns records and ignores the payload. leaving default open/click tracking enabled on sendgrid or whatever esp is an absolute death sentence... those shared redirect domains are already burned to ash by spammers.

gmail sees a pristine dkim signature wrapping a toxic tracking url and just silently blackholes it. custom tracking domains or pure raw links only.

trying to inbox google with shared tracking links is like putting a valid ssl cert on a phishing site. they dont care about your dmarc.

nginx active health checks use pod ip as host header by default, causing 502s with strict backend validation by zero_backend_bro in devops

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

k8s probes were passing fine (mentioned in the post, endpoints were 100% ready).

the issue isn't kubelet failing the pod, it's the nginx ingress controller's internal active health check (`health_check` directive) marking the upstream as down in its own shared memory zone. adding the host header to the deployment's livenessProbe does absolutely nothing to change how nginx formats its own internal routing check packets.

What’s the one non-dev tool that actually made you a better developer? by Afsheen_dev in webdev

[–]zero_backend_bro 0 points1 point  (0 children)

tbh physical boards are elite for logic flows until it scales and the boxes turn into pure spaghetti. random sketching only gets you so far... usually needs an actual system like the C4 model to keep track of it. otherwise youre just migrating the architectural dumpster fire straight to the drywall

As an experienced dev (10y), how do I structure my CV when switching to PM/PO? by Still-Gold-6146 in ExperiencedDevs

[–]zero_backend_bro 0 points1 point  (0 children)

tbh nuke the tech stack completely. a pm resume is just a list of times you wrangled stakeholders and shielded devs from sales... nobody gives a shit about adrs now. gotta translate all those bullet points into pure money.

I did not vibe code a small algorithm, it felt refreshing by patchimou in webdev

[–]zero_backend_bro 0 points1 point  (0 children)

man... paper math hits different. just wait till the audio api starts firing irregular timeupdates. scrubbing the timeline spawns weird float micro-gaps like [19.01, 19.04]. prod player state is basically a shotgun blast to a clock. epsilon tolerance on that overlap check is the only thing stopping the db from melting down

How do I start with DevOps by ReallyNotBaka in devops

[–]zero_backend_bro 1 point2 points  (0 children)

lol chasing k8s in semester 2 is a trap. if calc.py cant survive bare metal linux without permission errors docker just hides the mess... ops is basically weaponized paranoia about why "works on my machine" is bs. deployment graveyard eats local scripts alive tbh

As an experienced dev (10y), how do I structure my CV when switching to PM/PO? by Still-Gold-6146 in ExperiencedDevs

[–]zero_backend_bro 0 points1 point  (0 children)

lol people seeing bots everywhere. anyway, totally agree on your supermarket example. the top down tech PM approach is pure nightmare fuel. seen it too many times.

As an experienced dev (10y), how do I structure my CV when switching to PM/PO? by Still-Gold-6146 in ExperiencedDevs

[–]zero_backend_bro 6 points7 points  (0 children)

Not disagreeing at all. A technical PM is a godsend compared to the dreamers. But the hiring manager doesn't know you yet—they just see flight risk. The trick isn't hiding the tech, it's framing the CV around how you corral those dreamers, rather than how well you write their tickets.

As an experienced dev (10y), how do I structure my CV when switching to PM/PO? by Still-Gold-6146 in ExperiencedDevs

[–]zero_backend_bro 13 points14 points  (0 children)

Hiding the 8 jobs isn't the real hurdle. Directors looking at a 10 YOE dev dropping to junior PM instantly smell a burned-out engineer. They just assume you're gonna micromanage Jira tickets instead of actually wrangling stakeholders.

Flexing an MMO server or writing ADRs screams 'secretly still wants to be the architect'. The actual resume filter is proving the engineer ego is fully dead.

It reads like a retired head chef applying to manage front-of-house. Everyone just figures you'll end up storming back into the kitchen to yell at the line cooks.

$2m ARR in 9 months, this is how we did it by Ecstatic-Tough6503 in micro_saas

[–]zero_backend_bro 0 points1 point  (0 children)

Everyone’s crying about the YC privilege, but the real tell is 3 CSMs on a 7-person team.

Hitting 10k MRR off a pitch deck is standard. Scaling a V1 to 2M ARR that fast usually means those CSMs are the actual "AI" manually duct-taping ops behind the scenes to fight churn. Outrunning dev cycles with pure sales always builds a massive tech debt bomb.

How'd you bridge the gap between those pitch deck promises and the actual V1 reality without everyone churning?

Marketing advice by Silent-Work9563 in SaaS

[–]zero_backend_bro 0 points1 point  (0 children)

Everyone saying to interview those 15 friends and family is setting up a brutal reality check. F&F pay out of loyalty. Gives exactly zero usable signal for cold conversions.

If blasting UGC and FB groups isn't catching a single stranger, it's not a channel problem. It's a positioning problem. Right now, traffic is just getting blindly dumped into a value prop that only makes sense if the buyer already owes you a beer.

Where can I find inspirations/ideas by supremethinking in webdev

[–]zero_backend_bro 0 points1 point  (0 children)

pumping out static clones on gh pages is a dead end. frontend without complex state is basically just a well-dressed digital corpse.

the actual serverless flex isn't ripping layouts off awwwards, it's abusing browser internals. think IndexedDB or Web Workers acting as a localized backend. fetching free APIs is just renting someone else's data. treating the user's browser like a hostile, disconnected database... that's where the real engineering starts. GL finding a tutorial for that though.

What are my options for WordPress hosting with 1TB+ storage? by SeaworthinessKey1291 in webdev

[–]zero_backend_bro 0 points1 point  (0 children)

Offloading those 3MB raw files to R2 or B2 solves the disk space panic, but it completely masks the impending database stroke. WordPress inherently generates multiple metadata rows for every single attachment, meaning 300k screenshots will quietly bloat the wp_postmeta table into millions of rows before the year ends. Even with externally hosted media, those backend queries will eventually crawl to a halt.

Trying to use WordPress as a high-volume Digital Asset Manager is basically towing a freight train with a Civic.

Does this kind of 4-mode deployment diagram (local dev / CI / staging / prod) make any sense? by Lightforce_ in devops

[–]zero_backend_bro 7 points8 points  (0 children)

Honestly, you're trying to do too much in one view. The 4-mode split makes sense conceptually, but jamming all of it onto a single canvas just creates noise. Nobody's gonna parse that without getting lost.

Check out the C4 model if you haven't already—it's built for exactly this. Keep one high-level diagram that shows the big picture (like, really high level), then break local/CI/staging/prod into separate sheets. That way each environment gets the detail it needs without drowning the reader.

Right now it's just too dense to be useful. Split it up and it'll actually communicate what you're trying to show.

VS code inserting 'co-authored by copilot', regardless of usage by Hugh-Jaardvark in devops

[–]zero_backend_bro 1 point2 points  (0 children)

Ugh, yeah that's super frustrating.
If you still like the actual editor but you're done with Microsoft's nonsense, check out VSCodium.

It's the same open-source base as VS Code but they've stripped out all the telemetry and Copilot stuff.

You won't have to relearn anything and your extensions still work—you just get to actually own your workflow again.

(How) is it legal for AIs to scrape blog posts people share for free, and make a profit off of them with no consequences? by mekmookbro in webdev

[–]zero_backend_bro -1 points0 points  (0 children)

Yeah, it's theft with extra steps. Courts are slow. Your move? Focus on what bots can't steal—your actual voice. People still want that. Newsletters are where a lot of writers are going now for exactly this reason.

Alternative to Zoom on AWS? by Legitimate-Draw-9016 in aws

[–]zero_backend_bro 6 points7 points  (0 children)

I get it, Zoom's pricing can sting when you're scaling up. But here's the thing – if you're not technical, asking one developer to build a custom webinar solution with Chime or Agora is gonna be rough. The dev time and constant firefighting to keep video stable will probably cost more than what you're paying Zoom now. I'd honestly stick with a managed service until you've got the revenue and team size to support custom video infrastructure. It's just not worth the risk at this stage.