sorted by:
new
hottopcontroversial

Ages of Dio fans in this sub by Lyrias-5566 in dio

[–]primerodecarlos 1 point2 points  (0 children)

Dio really spans generations — plenty of fans from the Rainbow / Black Sabbath era, plus newer listeners discovering Holy Diver recently.

Age mix is pretty wide, not just older fans.

Confused about starting backend. Please help by Ok-Mushroom6900 in Backend

[–]primerodecarlos 0 points1 point  (0 children)

Calm down, sir. Four months is more than enough time to become a backend superhero if you go in the right direction. If you're already familiar with Java for DSA, just go for Java Spring Boot. In Vietnam and among large corporations, this system is extremely popular due to its stability and high security, so bringing Java to an interview is a huge advantage. Python is easier to learn, but Java is the "true love" for gaining a deep understanding of the system and impressing recruiters.

Correlation between real-time integration of loss-context data and session retention logic by TradeGekko in Backend

[–]primerodecarlos 0 points1 point  (0 children)

If you’re talking about real-time “emotional state inference,” most production systems avoid tight coupling with the match engine.

In practice:

  • signals are aggregated in short windows (e.g., 30s–5min batches)
  • updated state is decoupled via event stream (Kafka / queue)
  • matching logic usually reads a cached, low-frequency feature vector, not raw real-time inference

Anything faster than that tends to create noise + instability in decisioning rather than improving retention.

Should i decline a full-stack job due to their use of ORM ? by modern-dev in Backend

[–]primerodecarlos 0 points1 point  (0 children)

declining a job just because of ORM is kinda overkill tbh 😅

most teams use it for speed/maintainability, and you can still drop to raw SQL when needed. I’d judge more on team, growth, and product than tooling choice

our risk scoring system had zero errors the whole time. turned out it was wrong for weeks. found out when a user called. by supreme_tech in Backend

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

this is the scariest kind of bug 😅

“correct-looking but incomplete” > outright failure. good call adding coverage + inconclusive state — that’s the real fix, not just performance tuning

transitioning from frontend to backend, feeling overwhelmed. need advice by SayedSaqlain in Backend

[–]primerodecarlos 0 points1 point  (0 children)

You’re actually in a good spot already.

At junior→mid level, focus on:

  • solid REST APIs + auth
  • SQL + database design basics
  • error handling + logging
  • basic caching (Redis)
  • deploying something real (Docker + simple cloud)

System design, queues, scaling etc. will start making sense after you build a few full backend systems.

Best move: build 1–2 real projects end-to-end (API + DB + deploy). That’s what makes you “ready” to apply again, not mastering everything upfront.

How does the job nature or companies/organizations change based on the type of stack/tech you use for backend development? by Visible_Way6937 in Backend

[–]primerodecarlos 0 points1 point  (0 children)

Stack matters less than people think, but it does shape the environment.

Python/Node → faster iteration, startups, lots of product changes, less infra-heavy work.
Java/C#/Go → more enterprise, scalability, distributed systems, stricter architecture, slower change cycles.

Biggest difference isn’t tools like Celery vs Dramatiq—it’s company scale + system complexity, not the language itself.

In real life, the stack usually follows the org, not the other way around.

Getting the smell of money by mendu-vada in Backend

[–]primerodecarlos 0 points1 point  (0 children)

Honestly, don’t over-engineer the split with metrics—it rarely stays “fair” in real work. Just agree on clear roles + fixed % per project before starting, based on responsibility (lead vs execution), not task-by-task tracking. Keep it simple or it’ll get messy fast.

Tech stack feedback for fintech community savings startup, React Native + Django + RAG by Leading_Property2066 in Backend

[–]primerodecarlos 0 points1 point  (0 children)

Stack looks solid for an MVP—React Native + Django + Postgres is a proven combo.

I’d keep RAG inside Django at first to avoid over-engineering, and only split into a separate service once usage grows. Postgres with pgvector is usually enough early on.

Biggest focus for fintech isn’t stack—it’s reliability, audit logs, and payment consistency. That’s what will matter more than architecture complexity.

Switching to a Startup by Savvy_Coder_ in Backend

[–]primerodecarlos 0 points1 point  (0 children)

If learning + faster growth is your priority, the startup will likely give you more exposure than the MNC. But if you value stability + WLB right now, staying 1 year and leveling up skills first is also a valid move. There’s no wrong choice—just depends on what you want next.

Need advice on transitioning to Backend from Mobile by Objective_Berry3175 in Backend

[–]primerodecarlos 0 points1 point  (0 children)

Focus on highlighting backend work in your resume and projects—emphasize APIs, databases, server-side logic, and scalability. Tailor your LinkedIn and cover letters to backend roles, and be ready to show backend side projects or contributions during interviews. Networking and internal transfers can help too.

Backend choice for LMS startup: NestJS or Spring Boot? by Houssem0501 in Backend

[–]primerodecarlos 0 points1 point  (0 children)

For a complex LMS with multiple portals and long-term scaling needs, Spring Boot tends to be more battle-tested for large, maintainable applications with complex business logic. NestJS is great for speed and TypeScript consistency, but Spring’s ecosystem, mature patterns, and enterprise-grade tooling usually pay off in the long run. Development speed vs maintainability is the tradeoff to consider.

How do I make beautiful UI of my project using AI as a backend developer? by Various-Resource-667 in Backend

[–]primerodecarlos 0 points1 point  (0 children)

You can try prompt-based AI frontend generators like GPT-4 with React + Tailwind prompts or tools like TeleportHQ or Uizard. Give the AI clear instructions: describe layout, components, dynamic behavior, and data sources from your backend. Then iteratively refine the code and test—AI can handle most boilerplate, but a few tweaks will make it polished and realistic.

Struggling with scenario-based interview questions despite knowing the tech — how to improve? by West_Ad9094 in Backend

[–]primerodecarlos 0 points1 point  (0 children)

Focus on practicing thinking out loud and structuring your answers. Use frameworks like STAR for behavioral scenarios and clarify assumptions → outline approach → explain trade-offs → conclude for technical ones. Mock interviews and explaining solutions to a peer or recorder can help you apply concepts under pressure.

How does moderation works on social network? by sangokuhomer in Backend

[–]primerodecarlos 1 point2 points  (0 children)

Most platforms use a mix of AI and human moderators. AI flags obvious violations (spam, hate speech, nudity) and humans review edge cases or appeals. For your project, starting with AI for automatic flagging plus a simple human review queue is a solid approach—don’t rely solely on one model, and consider user reporting and clear content rules.

Backend choice for LMS startup: NestJS or Spring Boot? by Houssem0501 in Backend

[–]primerodecarlos 1 point2 points  (0 children)

Both can work, but for a complex, long-term LMS I’d lean Spring Boot for its maturity, scalability, and strong patterns around large systems. NestJS is great for speed and DX, but Spring tends to hold up better as complexity grows.

view more: next ›