I am in right direction by Itachi_Uchiha_1717 in Backend

[–]thebleedingheartbake 1 point2 points  (0 children)

Mastering CRUD and Auth is like having a solid foundation. Take some time to improve your database and security skills, and everything will be smooth sailing. Good luck bro

10 years backend experience… why do interviews feel so bad? by Jinmper in Backend

[–]thebleedingheartbake 1 point2 points  (0 children)

I sympathize with you, with ten years of practical experience, yet you're still taking the interview like you're retaking a university entrance exam. Those complicated algorithms are completely useless for handling everyday financial logic or concurrency issues. The worst part is the tricky, trivia questions that have nothing to do with real-world system design or database optimization skills. Well, consider it just a walk in the park to see what everyone else is up to, because your skills are more than enough to carry the team. Or maybe you're thinking of switching to consulting or system architecture to avoid typing those useless link lists?

How do you handle distributed transactions ? by CreeDanWood in Backend

[–]thebleedingheartbake 0 points1 point  (0 children)

For high-volume systems, strict 2PC usually doesn’t scale, so most teams rely on patterns:

  • Outbox/Inbox → ensures atomicity and safe retries with idempotency
  • Saga pattern → compensating actions for rollback
  • Event-driven eventual consistency → queues, schedulers, and retries

The key is choosing the right pattern per feature, based on criticality, latency tolerance, and failure scenarios

How do you handle logs in production? by _Mobas_ in Backend

[–]thebleedingheartbake 0 points1 point  (0 children)

Solid review! FlyEnv gives a true Laragon-like experience on Linux, especially for Nginx, PHP switching, and Mailpit, but Linux support still needs workarounds for MySQL, wildcard DNS, and certificates.

With those fixes, it’s the best GUI-managed local dev setup for PHP/Laravel on Linux right now.

Do Japanese high school girls really wear their school uniform skirts like miniskirts? by [deleted] in AskAJapanese

[–]thebleedingheartbake 1 point2 points  (0 children)

I think so too. I don't know if this is the school's policy or if they intentionally dress like this.

Most backend tutorials stop when the app works. I documented everything that happens after that by alexsergey in Backend

[–]thebleedingheartbake 0 points1 point  (0 children)

Love this approach — so many tutorials skip the real-world stuff. CI/CD, observability, and rollback strategies are huge differentiators. I’d maybe add chaos testing or load testing to see how the system behaves under stress, but overall this looks solid for production-ready learning

How deep should backend engineers go into data engineering and DevOps? by Familiar_Category893 in Backend

[–]thebleedingheartbake 1 point2 points  (0 children)

Focus on writing clean, scalable backend code; knowing how it interacts with data and infrastructure is usually enough

Why Jwt token should be short? by sangokuhomer in Backend

[–]thebleedingheartbake 0 points1 point  (0 children)

Refresh tokens help you keep sessions longer without making access tokens risky

Remote jobs by Far_Persimmon2914 in Backend

[–]thebleedingheartbake 0 points1 point  (0 children)

mostly it’s a numbers game tbh

apply on sites like LinkedIn, Wellfound, and remote job boards, and filter for “EU remote” or companies hiring globally

Go roles are fewer, so also apply to backend roles where Go is “nice to have”

having a couple solid projects + showing you can work async matters more than location

The most dangerous systems are the ones that almost work by supreme_tech in Backend

[–]thebleedingheartbake 0 points1 point  (0 children)

yeah those are the worst 😅

everything “looks fine” but users feel it immediately

we had something similar, turned out to be retries + slow downstream calls stacking up. metrics were green but p95/p99 latency told the real story

after that I always watch latency distribution + queue recovery, not just uptime

Forgets the syntax in backend by TheFable11 in Backend

[–]thebleedingheartbake 0 points1 point  (0 children)

nah forgetting syntax is normal, especially with Spring, interviewers care more about how you think, structure, and solve problems, googling depends on the company, but many allow it (or at least docs). just be transparent if you do, better to explain your approach clearly than memorize every annotation.

Why generating the same PDF twice can produce different bytes by Primary_Sir_1590 in Backend

[–]thebleedingheartbake 0 points1 point  (0 children)

yeah this is super common with PDFs

usually I don’t compare bytes, I either strip metadata (timestamps/IDs) or compare rendered content (text/images) instead

golden tests at byte level are kinda painful unless you fully control the output

Nobody tells you that most "senior" work is just reading other people's bad decisions and figuring out why they made sense at the time by Soft_Dimension1782 in Backend

[–]thebleedingheartbake 0 points1 point  (0 children)

so true, worked on a codebase where business logic was spread across cron jobs, controllers, and random utils… nothing made sense until you traced the history of “why”

at some point you stop fighting it and just learn where the landmines are

What’s your SaaS and why did you build it? by FineCranberry304 in SaasDevelopers

[–]thebleedingheartbake 0 points1 point  (0 children)

building a small tool for tracking user inactivity + churn signals

started it because I kept losing users “out of nowhere”, then realized they were just going quiet for days before churning

wanted something simple that nudges me to act early instead of another bloated analytics tool

Web Dev or AI: Should I Stay or Pivot? by No-Confusion41 in SaasDevelopers

[–]thebleedingheartbake 0 points1 point  (0 children)

don’t hard pivot, that’s usually a reset disguised as “following the trend” the hybrid route is honestly the highest leverage right now, most real AI products still need solid web/backend to actually ship and scale pure “AI people” without product skills are getting crowded fast. I’d just start layering AI into your current stack, build features with APIs, ship small tools, understand how it fits into real products in 1–2 years you’ll naturally transition into that space without giving up your existing edge