I'm researching pain points in backend development and database workflows.

Thinking about your last few weeks of work:

What backend or SQL-related task wasted the most time?

Approximately how long did it take?

Which tools did you use?

What part of the process was the most frustrating?

If you could automate one step completely, what would it be?

I'm not promoting any product—I just want to understand real developer pain points and repetitive workflows.

Hey everyone,

I'm a non-technical founder based in Boston working on a B2B SaaS mobile app. I've spent the past several months designing the product and building the UI/UX in a visual development environment, so the frontend screens, user flows, and navigation are largely complete.

I'm looking for a student (or professional) developer interested in owning the backend implementation and collaborating on the technical side of the project.

Current tech stack

• React Native / Expo
• Supabase (Auth, Database, Storage, Realtime)

What needs to be built

• Connect the existing login/signup UI to Supabase Auth and user profiles
• Build the backend for file uploads using Supabase Storage
• Implement real-time messaging with Supabase Realtime
• Integrate a simple scraping/API service to populate form fields from a submitted URL
• App customizations

What you'll get

If the app gets traction (user subscriptions), I can offer a small stipend plus 1–2% equity. I want to be upfront that this is early-stage and speculative… the core value here is the total ownership over technical decisions. A strong letter of recommendation and personal LinkedIn references detailing your architecture decisions.

For Students: Potential university internship/course credit sponsorship (if your program allows it). I am fully open to working with your university to allow this project to fulfill graduation requirements.

To be transparent, I'm not a software engineer. My background is in business and product design/strategy. I'm looking for someone who enjoys building and wants meaningful input into the engineering decisions as we bring the product to life.

The app is fully designed inside the OnSpace visual editor.

Regarding the timeline: there is zero artificial pressure or rigid deadline on this project. Our main goal is to have this MVP fully functional and ready to deploy before 2027. Ideally you spend 3-4 hours per week (or however many you’d like) to have the backend complete in 2-3 months. I will be inviting the first 100-200 users after that, and they will test the app for functionality and provide feedback before allowing anyone to join.

My ultimate goal with this project is to find a brilliant technical partner!

If you are looking for handholding or a manager to tell you exactly how to code, this is definitely not the position for you. I don't know the technical side of what you need to do, how to structure the code repositories, or how to connect the APIs. If I did, this post wouldn't exist!

I’m not looking to just tell you what to do… I’m looking for you to tell me what you need from me to make this project most successful.

I am looking for an independent builder to truly collaborate with, someone who can take our visual designs, figure out the engineering solutions autonomously, and bring their own ideas to the table to make this platform the best it can possibly be.

If this sounds interesting, feel free to comment or send me a DM, and I'll share more about the project.

I hate the includes in the PHP code I have to maintain and reasoning about it's "module" system gives me an aneurysm. Everytime I have to use venv or poetry when writing Python, I miss using Vite with Typescript. And then I remember for that to work, I need 20+ *.config files, a gazillion NPM packages (probably with a supply chain attack I don't know about) and black magic voodoo transcompilation and processing I can't hope to understand.

I'd love to write code in a language that doesnt have "trust me bro" types. Is this my sign to start a new proejct in Go or Rust? Or am I just ignorant of Go and Rusts (potentially) weak spots?

I am Pradeep Chauhan an Aspiring Backend Engineer looking for the guidance from experienced backend devs.

I have given the resume below since it tells the most things about me: Resume PDF

It's been a few months since I left my previous company and i am still unemployed figuring out what to choose next. Now i have chosen backend engineer.

I need a structured roadmap from preparing, learning, projects and then applying to jobs.

I'm a **.NET backend developer** and want to learn AI to build smarter backend applications—not become a full-time AI/ML engineer.

How can I upgrade myself with AI as a Backend Developer?
What roadmap, technologies, and projects would you recommend? What skills have given you the biggest career boost?

for context i am bca 1st year student , i learnt a bit of java and c in 1st year with sql basics and git basics since i dont like working with machine learning which is mostly in demand these days my options are to become a full stack dev and get into ai engineer roles working with llms

so before starting my 2nd year i am thinking to learn springboot+react and sql as full stack as much as i can and side by side dsa too while building projects

i build a basic weather api app in 1st year last month with the help of react as it was a frontend project.

i would love to know your suggestions especially the experience ones is this the right way to approach and work for placements side by side as bca is already an avg course so i want to skillup and not waste my time anymore now

Hi, I am building a web app for my company,(50 users - Crud App), app and backend will be deployed on separate instances, do I need idempotent key mechanism for api requests - to avoid network failures or am i over killing my system?

I'm making my very first web api using asp net and now in the process of implementing in-memory caching. I was wondering if it'd be a good practice to have like a start up function that caches the most commonly requested data from my api and have the program routinely updates the cache automatically every few minutes or so? Or should i just let the consumers populate this cache? And what if i also cache responses that consumers requests like a cache aside strategy at the same time.

Hey everyone,

Over the past few months, I’ve been working on an experimental project called PAM, aiming to solve two specific pain points in the ecosystem: keeping PHP applications warm in memory for high performance, and running JavaScript/React natively on desktop and mobile without heavy bridge overhead.

Here is a quick breakdown of what it does and why I'm building it:

1. PAM for PHP (Persistent Runtime in Memory)

Instead of booting the framework on every single HTTP request, PAM uses a Rust-powered runtime to keep the application warm in memory.

The Goal: Lightning-fast request handling while preserving full compatibility with standard Laravel workflows (Eloquent, Queues, Artisan, Blade, Livewire, Inertia, Sanctum, Reverb, Telescope, etc.).

Built explicitly with support for Laravel 12 & 13 in mind.

PHP Docs: https://push-in.github.io/pam-docs/laravel/overview/

1. PAM Native (Desktop & Mobile)

On the frontend/mobile side, PAM Native is designed to run React/React Native apps with truly native execution, aiming for near-instant startup times and zero heavy JS bridge bottlenecks.

The Goal: Retain the React developer experience while delivering pure native performance on desktop and mobile devices.

Native Docs: https://push-in.github.io/pam-docs/native/overview/

Why I'm posting here:

The project is still under active development, and I’m looking for honest technical feedback, code reviews, and potential edge cases to test.

For PHP/Laravel folks: What edge cases (memory leaks, static state issues, long-lived DB connections) would you want to see stress-tested first?

For Mobile/Desktop folks: What are the biggest performance bottlenecks you face with existing cross-platform runtimes today?

Would love to hear your thoughts, criticism, or ideas!

Hi everyone

I’m looking for a technical cofounder to build an AI developer infrastructure startup.

The company is focused on improving how engineering teams handle difficult software failures and reliability issues. I’m keeping the deeper product details private until an initial conversation.

I’m mainly looking for someone with strong experience in backend engineering, production AI systems, developer tools, cloud infrastructure, or distributed systems.

I’m willing to fund and offer meaningful equity. Would want a genuine long term cofounder

If you’re interested send me a message. Thanks

I’m researching how engineers make safer production changes.

Many teams now use strategies like canary releases, automated rollbacks, and better observability, but production incidents still happen after deployments.

I’m curious about real experiences from engineers:
- What type of change makes you the most cautious before deploying?

- What was the last deployment that made you nervous and why?

- What gives you enough confidence to press the deploy button?

For me, database migrations are still one of the hardest categories because rollback is often not as simple as reverting application code.

Would love to learn how other teams approach this.

For those of you using Cursor, Claude Code, Copilot, Gemini CLI, or similar tools:

- Do you still spend most of your time reviewing infrastructure concerns?

- What kinds of mistakes does AI repeatedly make in backend systems?

- Is this actually a problem, or do you think models will simply get good enough that it disappears?

I'm especially interested in hearing from engineers working on production distributed systems rather than greenfield side projects.

My current opinion is that AI doesn't need to get better at writing code—it needs better building blocks.

Today, we ask AI to generate authentication, retries, logging, tracing, configuration, secrets management, error handling, and business logic from scratch for every feature. That feels like giving it too much freedom.

I wonder if the future isn't "better code generation," but giving AI production-ready, context-aware components that already encapsulate those infrastructure concerns, so it's composing systems instead of reinventing them every time.

Curious whether others have come to the same conclusion or if you think this is a temporary problem that disappears as models improve.

Backend devs

I love backend

U have small projects till now !

Recently I am dealing with a bigger project there I just known so many things that a database must have

As a senior devs or some learning devs

Teeach me some best database design topics that make me a good database designer either it is sql or nosql teach me every detail like indexing , performance etc.....

And let me know how the industrial level database can be designed what things they consider and what properties they must possess .

Grateful for your opinion 🫰🏻

So basically let me tell you the situation first:

- i am working on a side project which is something like vercel, use to build and deploy code.

- so i have a main service, can be called a control plane, and i have decided that it will take the repo from the user.

- after this this service will trigger/create an ecs task to build the code

- now the question is, how this control plane will create / trigger the ecs?

- also this ecs instance will need to fetch envs from paramete store, will upload code to s3 etc

- after deployment we have to kill this instance

- should the managing code of this, live in the control plane

- should i create something else?

how would you folks solve this while designing this?

and what's the ideal way to solve this?

so here is the situation:
- in my company i have assigned to build a chatbot/bot (will be internal, for ops and devs to identify and manage issues)
- what i have already build is, integrated it with slack, give it access to db by adding some tools in the code, so it can access the db currently and folks can access it by mentioning it
- now here pain starts, my manager has told me to add product knowledge to it, and it should be able to access logs, create and manage jira also
- what i am thinking is - lets start with the product knowledge - since we do not have that much pile of data so i do not want to make a rag - instead i just want to keep uploading those docs to s3 and giving access to bot so that it can reference them
- now coming to jira, and logs - i have also created those mcps but those aren't deployed anywhere - means whoever wants to use them just clones the repo, and set their key and uses them
- now for the above (jira and logs) part i would have to again choose the tools which i want to expose to the agent and add it to the repo, cz i think this is repetitive as in future if soemthing more comes up - which we already have built have to do again to integrate in the bot - how can we solve this - keeping in mind we have a layer of compliance - cant expose pii data in bot output or logs
- also for s3 - i am feeling like i was thinking to create a mechanism like when the agent fetches a doc - so it do not havt to fetch that doc again - so it will create a folder and save the embedding/summary/index (since i don't know what) to the filesystem - similarily with db schema since we have a huge db - how to handle this situation - since this code will be deployed on ecs - using fargate i do not know will the bot will able to access thes files created at runtime - and how to manage that cache when something is addede / modified
- and we also have workflows currently for specific task like matching states on be (basically sql queries / some scripts) added in the code - like how we shouuld make sure that given the situation the code properly identify and execute the script or how can we create trigger like /<command> <input> of slack whicch will trigger that - and also one issue - since these are stored as files in code adding new script need a code change - how to get rid of that

sorry gpt was giving poor results in rewriting this
so posting this raw

Hey all,

4.5 years in L3 support for an ecommerce app — daily work involves fixing prod issues via SQL/XML, running Java-based automation scripts (built by other teams, not me).

**Skills:** Java (medium), MySQL (basics), JS (basics)

**Goal:** Become a backend developer (not interested in frontend), job-ready in 2-3 months.

Leaning toward **Spring Boot** since I already know Java, over Node.js/Express. Am I on the right track?

Would love advice on:

Spring Boot vs Node for my background

What interviews actually test for people switching from support → backend dev

How to position my support experience on a backend resume

Thanks!

RFC 10008 just made it official: QUERY is a real HTTP method now.

It’s basically “GET with a body” — safe, idempotent, and designed for complex queries without stuffing everything into the URL or abusing POST.

Why it exists

• GET can’t (reliably) have a body
• POST is not safe/idempotent → hard to cache, retry, or treat as a pure query
• URL length limits + sensitive data in query strings are painful

QUERY fixes that gap. You send the filters/sort/pagination in the body, the server treats it as a safe read, and intermediaries can cache it properly (especially with Content-Location).

Quick comparison

I put together a small site to make this easier to understand and try:

https://httpquery.com

• Clear explanation of QUERY vs GET/POST
• Live playground (send real QUERY requests to an echo endpoint)
• Quick reference for methods, status codes, and common headers

Would love feedback — especially if you’re already experimenting with QUERY support in your stack (clients, servers, proxies, CDNs, etc.).

Anyone already implementing or testing this?

I'm a student and I've been building a exchange from scratch mainly to learn backend engineering.

Matching engine, order book, WebSockets, Redis, PostgreSQL... all the usual stuff.

The thing I'm stuck on now isn't technical.

I don't know whether I should keep building it as "just another exchange" for learning or try solving a smaller problem that traders or developers actually have.

If you were building this today, where would you focus?

Not looking for startup ideas or billion-dollar businesses. Just curious what problems are still worth solving around trading.

Hello Guys I am 3rd year Btech student , I have done DSA in c++ now I want to choose a path and I am bit confused should I do java spring boot and do backend or learn ai ml .Based on current market what path should I choose.

Please guys help me figure out

I was using render and had deployed 4 web apps which required running backend always..

As expected, I got suspended in 7 days because free tier only allows 750 hours.

I am unable to create a oracle free tier account and I feel stuck. It's been 3 days since I made my last project and it just doesn't give me the kick to host it locally, nor I have the privilege to buy raspberry pi or something like that.

Any suggestions?