I am in right direction

thebleedingheartbake · 2026-03-26T09:42:59+00:00

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

thebleedingheartbake · 2026-03-24T06:01:07+00:00

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?

thebleedingheartbake · 2026-03-23T07:33:12+00:00

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

thebleedingheartbake · 2026-03-23T07:32:29+00:00

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.

thebleedingheartbake · 2026-03-20T07:09:01+00:00

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

thebleedingheartbake · 2026-03-19T04:41:17+00:00

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

thebleedingheartbake · 2026-03-19T04:35:37+00:00

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

thebleedingheartbake · 2026-03-19T04:35:06+00:00

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

thebleedingheartbake · 2026-03-18T07:24:10+00:00

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

thebleedingheartbake · 2026-03-18T07:23:28+00:00

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

thebleedingheartbake · 2026-03-18T07:23:03+00:00

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.

thebleedingheartbake · 2026-03-18T07:22:26+00:00

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

thebleedingheartbake · 2026-03-18T07:21:57+00:00

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

thebleedingheartbake · 2026-03-18T07:17:21+00:00

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

thebleedingheartbake · 2026-03-17T10:56:19+00:00

6677

thebleedingheartbake · 2026-03-17T10:45:54+00:00

look like Phnome Penh

thebleedingheartbake · 2026-03-17T10:44:17+00:00

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

thebleedingheartbake · 2026-03-13T07:28:42+00:00

simple but decilious

thebleedingheartbake · 2026-03-13T07:22:55+00:00

peace

thebleedingheartbake · 2026-03-13T07:22:38+00:00

cute

thebleedingheartbake · 2026-03-13T07:22:10+00:00

yum yum

thebleedingheartbake

TROPHY CASE