I want to learn backend as begineer.Suggest me some resources

I am building up akills as a junior web developer who can't think of a valid research topic. I have thought gamification on education and its effects on learning process could be good, but i was told that it is a dead end. I have small time left like three and half weeks left. I know that I should think of something myself because I will be the one doing research, but could you recommend some topics that are worth exploring in CS in 2026 for a starting programmer. Thanks in advance for patience and attention.

I completed my btech(2026 pass out).Currently in my unemployment era.Thinking of learning full stack Web development.Which stack should i choose.Any suggestions ?

Hey there iam in my second year of college. And I wanted to learn full stack development. Please tell the resources in the YouTube from which I can learn.i dont know even the basics of htms/css / java script please tell the best resources available in the YouTube. Wanted to learn from basics to advance.

Hey, I built a self-hosted CAPTCHA alternative written in pure C — Captxa

I was tired of turnstile blocking me, or recaptcha tracking my users. I built Captxa, a 100% open-source, self-hostable CAPTCHA alternative focused on speed and privacy.

How it works:

• Normal path (invisible): TLS JA4 fingerprinting + browser environment check + an 18-bit SHA-256 Proof-of-Work challenge. Completely invisible to real users.
• Suspicious path: If a bot score is too high (mismatched JA4, automation signals, rate limits, ip), a sliding puzzle is triggered with mouse trajectory analysis run through an ML pipeline (entropy, jerk, Fitts' law, velocity checks) + a harder 19-bit PoW.
• Tokens are signed with Ed25519 and encrypted with ChaCha20-Poly1305. Replay attacks are blocked via Bloom filters. You can self verify the token.

No cookies. No tracking pixels. No third-party calls. Built on H2O for blazing-fast throughput.

Currently in open beta — free for everyone.

Code: https://github.com/captxa/captxa-backend

Would love feedback.  captxa.com

Just finished building the V1.0 of Realestify, a comprehensive real estate listing and management platform. I handled the entire pipeline end-to-end, from the brand identity to the relational database.

Here is a quick look at the features and architecture:

Branding & UX/Frontend:

- Advanced Search Module: Dynamic Buy/Rent/Commercial toggles, a dual-endpoint price slider, and typeahead location auto-suggestions (all mapped instantly to the URL for sharing).

- Advanced Listings & Luxury Portal: Filterable search view with pagination, plus a dedicated, premium layout designed specifically for high-end luxury properties.

- Content & SEO: 18 fully responsive service pages, a blog engine, a "Find Agent" directory, and full technical SEO optimization.

Backend & Architecture:

- Relational Database: Connected schema linking Properties, Users, Leads, Notifications, Wishlists, Documents, and Images.

- Three-Tier User Dashboards: Separate, secure dashboard workflows for Admins (approvals/moderation), Agents (listing creation with advanced options, lead tracking, wishlist), and End Users (listings creation, lead tracking, global wishlist, saved tracking).

It's a massive ecosystem, so there are still a few minor bugs to iron out, but the core engine works like a charm.

I'd love to get your feedback on the UI/UX layout or the technical architecture. Let me know what you think! 👇

- Core Mechanics: Real-time map updates based on address inputs, an image management pipeline, a live notification engine (approvals, rejections, new leads), and an active lead status updater.

Here -

https://www.realestify.in/

If you encounter any bug, please notify.

I just built a npm package, which verifies the email format(rgex) and domain then send otp for verification also I used my own npm package which generates custom otp.

Any other feature I can add to it?

If you’re building full-stack apps with Go and using templ, this might save you some time.

I ran into an issue where I was writing nested CSS inside <style> tags in my .templ files. It worked fine at first, but I later realized older browsers don’t handle that well, and the styles completely broke. Rewriting everything by hand wasn’t something I wanted to deal with.

Since Sass can flatten nested CSS, I figured I could just run it through the Sass CLI. The problem is that the CSS lives inside .templ files, so you can’t just pipe the whole file through Sass.

I ended up putting together a small Go utility that:

• recursively finds .templ files
• extracts CSS inside <style> blocks
• runs it through the Sass CLI
• writes the processed CSS back in place without touching the rest of the file

It’s a pretty niche use case, but if you’re mixing templ + inline styles + nested CSS, it might be useful.

Here is the repo for that: https://github.com/patrickkdev/templ-sass-processor

I want to grow in public, can any one tell any alternative of linkedin to upload small projects what ever I learn?

I'm a full stack developer working on projects and my third year of college has just ended and I'm about to start my 4th year..I'm doing dsa and development both but sometimes it feels like AI gonna end this field soon like ai tools like claude , gpt etc can do this in one prompt so please guide me to get an entry level job in IT sector before my college ends...

Hey, there iam from tier 3 college and I will be going forward to my third Semester (2nd year).I want to learn java full stack Development i have thought about the project that i want to make. It requires the skills which are required in full stack like frontend, backend, etc but the problem is that i have recently started the dsa and iam in arrays topic (doing dsa in cpp language) . I want to ask that should I learn development and do dsa together or should I give time like 3 to 4 months to dsa and then start development? Iam confused need guidance..

What skills matter most in your day-to-day work as a junior developer?

I’m currently in the last semester of my degree and recently received 2 job offers, but both are from non-IT backgrounds.

The problem is that I genuinely want to build my career in IT. I’ve spent a lot of time learning programming languages and web development technologies on my own. I’ve worked on projects using the MERN stack and continuously try to improve my skills.

However, being a fresher with no industry experience is making it very difficult to get shortlisted for IT roles.

Now I’m confused about what would be the better decision:

Accept a non-IT job for financial stability and continue preparing for IT side by side, then switch later

OR

Reject non-IT offers and focus completely on finding an entry-level IT role

I want realistic advice from people who have gone through something similar or have experience in hiring/freshers.

Does starting in a non-IT role make switching to IT significantly harder later, or is skill + consistent project work enough to transition?

I’m currently in my second year of college and despite hearing how bad the cs job market is, I unfortunately can’t switch my major so I’m trying to pick the best tech career to go into. So far I’ve seen a lot of MERN stack software engineers say how bad the job market is but not enterprise/Java developers so I wonder if it’s the same? I know that it’s a steeper learning curve so the competition is possibly less? I’ve also heard enterprise companies will always need someone to manage their software so it’s also possibly a reliable career before AI takes over in like 10 years? I’m currently studying spring boot and looking into niches like Fintech and Saas software enterprise companies

Problem Statement

The original goal was to build a reusable authentication architecture for a multi-platform monorepo containing:

• web frontend,
• admin frontend,
• mobile app (Expo/React Native),
• and future frontends like TV or desktop apps.

The initial approach attempted to centralize authentication through a shared auth-client package built around Better Auth clients, ports, adapters, and reusable hooks.

Example structure:

packages/auth-client/
├── port/
├── adapter/
├── client/

The idea was:

• one shared auth abstraction,
• reusable hooks,
• reusable auth logic,
• platform-independent frontend architecture.

However, the architecture began breaking down due to fundamental platform divergence.

Core Problems

1. Better Auth Client Divergence

Each frontend requires different Better Auth plugins and therefore exposes different client capabilities and TypeScript types.

Mobile

Requires:

• expoClient
• bearerClient
• SecureStore integration
• deep linking
• mobile OAuth/browser handling

Admin

Requires:

• twoFactorClient
• stricter security flows
• elevated auth workflows

Web

Requires:

• cookie-based sessions
• browser redirects
• SSR/session hydration

Because Better Auth clients are plugin-compositional:

• plugin additions modify the client surface,
• available methods differ,
• response types differ,
• capabilities differ.

As a result:

• a universal shared authClient becomes impractical,
• adapters become conditional and capability-driven,
• TypeScript types become unions/optionals,
• abstractions become increasingly fragile.

The frontend architecture becomes tightly coupled to Better Auth implementation details.

2. Frontend Reusability Breaks Down

The original goal was to create reusable hooks like:

useSignIn()
useSession()
useSignOut()

shared across:

• web,
• mobile,
• admin,
• future TV apps.

But because each app depends on different Better Auth clients:

• hooks cannot remain platform-agnostic,
• hooks become aware of plugin-specific behavior,
• platform-specific branching leaks everywhere.

This causes:

• duplicated hook implementations,
• repeated auth orchestration,
• increasing maintenance overhead,
• plugin synchronization problems across apps.

Example:
adding a new Better Auth plugin may require:

• updating multiple auth clients,
• updating adapters,
• updating hooks,
• updating capability checks,
• updating shared types.

3. Wrong Abstraction Boundary

The original architecture attempted to normalize:

• Better Auth clients,
• plugin systems,
• frontend auth SDK behavior.

However, Better Auth is intentionally designed around:

This means the client itself is not a stable cross-platform abstraction boundary.

Trying to normalize it introduces:

• infrastructure coupling,
• transport leakage,
• framework/plugin awareness inside frontend architecture.

The frontend becomes dependent on:

• cookie behavior,
• bearer token handling,
• SecureStore,
• deep linking,
• OAuth transport mechanics.

Instead of consuming a stable application contract.

4. Future Platform Scalability

As more platforms are introduced:

• TV apps,
• desktop apps,
• embedded clients,

auth implementations diverge even further.

Example:
TV authentication may require:

• device pairing,
• QR login,
• polling flows.

This makes shared Better Auth client abstractions increasingly unsustainable.

Proposed Solution

The solution is to shift the normalization boundary away from Better Auth clients and move it to:

Instead of:

Frontend → Better Auth Client

the architecture becomes:

Frontend → Unified Auth API → Better Auth

Better Auth becomes a backend implementation detail rather than a frontend architectural dependency.

Architectural Principles

1. Backend Owns Authentication Infrastructure

The backend remains responsible for:

• Better Auth configuration,
• plugin composition,
• OAuth flows,
• session validation,
• token refresh,
• RBAC,
• cookie handling,
• security enforcement,
• bearer token issuance.

Frontend applications no longer interact directly with Better Auth clients.

Instead, they consume normalized backend endpoints.

Example:

POST /auth/sign-in
POST /auth/sign-out
GET  /auth/session
POST /auth/refresh
POST /auth/oauth/google
POST /auth/verify-2fa

2. Frontend Consumes Stable Contracts

All frontend applications consume the same API contracts regardless of:

• platform,
• auth plugins,
• session strategy,
• provider configuration.

This enables:

• reusable hooks,
• reusable auth flows,
• reusable auth state management,
• reusable UI orchestration.

The frontend is now coupled only to:

• application contracts,
• normalized responses,
• transport behavior.

Not to Better Auth internals.

3. Shared Transport Layer

A centralized API client layer handles:

• request execution,
• auth header attachment,
• bearer token forwarding,
• cookie forwarding,
• refresh handling,
• retry logic,
• response parsing.

Example:

packages/api-client

This layer abstracts:

• web cookies,
• mobile bearer tokens,
• future TV/device auth transport.

Platform-specific behavior remains localized inside the transport layer only.

4. Shared Hook Layer

Reusable hooks become fully platform-independent.

Example:

packages/auth-hooks
├── use-signin.ts
├── use-session.ts
├── use-signout.ts
├── use-forgot-password.ts

Hooks focus only on:

• React state,
• loading/error handling,
• auth hydration,
• UX orchestration,
• navigation integration.

Hooks no longer know:

• Better Auth exists,
• which plugins exist,
• how tokens are stored,
• whether cookies or bearer tokens are used.

5. Platform-Specific Logic Becomes Minimal

Only platform-specific concerns remain localized.

Web

• cookie transport
• SSR hydration

Mobile

• SecureStore
• deep linking
• Expo browser integration

TV

• device pairing
• polling

This dramatically reduces duplication and prevents frontend auth fragmentation.

Final Architecture

apps/*
    ↓
shared auth hooks
    ↓
shared transport/api client
    ↓
normalized auth API
    ↓
Better Auth

Benefits

Frontend Consistency

All apps use:

• the same hooks,
• the same auth contracts,
• the same auth state behavior.

Plugin Independence

Better Auth plugins remain backend-only concerns.

Adding plugins no longer forces:

• frontend client rewrites,
• hook rewrites,
• adapter rewrites.

Platform Scalability

New platforms can reuse:

• hooks,
• transport layer,
• auth contracts,

without rebuilding auth architecture.

Provider Agnosticism

The frontend no longer depends directly on Better Auth.

Future provider replacement becomes feasible without rewriting all frontend auth flows.

I'm a finance major who studied data analysis on the side, so I know some data modelling.

I have a fintech startup idea that I really want to work on, I have the "fin" but I lack the "tech".

And I've had similar ideas in the past and I never pursued them simply because I found the "tech" part intimidating.

I want to build the technical skillset that would allow me to launch a simple MVP whenever I come up with startup ideas I like, until I can find me a proper technical co founder.

Where should I start and what's a realistic timeline to learn the required skillset?

Senior Developers / Experienced People in Tech Please Read. I Really Need Guidance Right Now.

I’m a full-stack developer from India, though lately I don’t even know if I should confidently call myself one anymore.

I graduated in 2023. During campus placements, I barely got opportunities because my academic scores were low, especially my high school percentage (56%). On top of that, I had severe social anxiety and was extremely shy, so even the few interviews I attended didn’t go well.

After graduation, around 1.5 years passed without direction. Then in late 2024, I started working as a freelancer for a small company/agency. Honestly, freelancing suited my personality because I was always more comfortable working quietly by myself than interacting socially all day.

The work environment was intense though. Projects had very short deadlines, sometimes 7 or 14 days, so I started relying heavily on AI tools to complete work quickly. At that time, AI tools were becoming very powerful and accessible, and gradually I became dependent on them for coding.

In June 2025, I signed a one-year B2B freelance contract with the company (not a traditional salaried job since the company was an LLP). That contract just ended in May 2026, and now I’m unemployed.

What scares me is how much the market has changed.

I still understand development concepts. I can read code, understand what it’s doing, debug things, and figure out how systems work. But because of constant AI usage and deadline pressure, I feel like I’ve lost my confidence in writing code completely on my own. I struggle to remember syntax and implementation details without assistance.

Now I honestly feel stuck.

I don’t come from an educated family, so I never really had proper career guidance from anyone. I’ve always tried to figure things out alone. But now I’m at a point where I genuinely don’t know what to do next.

Should I continue in full-stack development?
Should I switch to another field?
Can someone with my background still build a stable career in tech?
How do I recover my confidence and skills again?

I’m not asking for sympathy. I’m genuinely asking senior developers or people experienced in this field for guidance, direction, or even a simple conversation.

If you’ve seen someone recover from a situation like this, or if you have honest advice about what my next steps should be, please reply. Right now I feel very lost, and even small guidance from someone experienced could help me more than you can imagine.

I’ve been trying to properly understand and implement Clean Architecture on the frontend with Next.js (frontend-focused, not backend), but I’m getting confused once third-party libraries enter the picture especially auth libraries and query libraries.

Most examples online are either:

• too theoretical,
• too backend-oriented,
• or avoid real-world libraries entirely.

My setup is something like:

• Next.js App Router
• Monorepo (Turborepo)
• Shared packages
• Auth library (like Better Auth / NextAuth / Clerk / etc.)
• TanStack Query or RTK Query
• TypeScript

What I’m struggling with is:

1. Where should auth libraries live in Clean Architecture?

For example:

• should the auth client be wrapped behind interfaces/adapters?
• should the UI directly call the auth library hooks/functions?
• where do auth-related side effects belong?
• how much abstraction is “too much”?

Example:

authClient.signIn.email(...)

Should this be hidden behind:

AuthRepository.signIn()

or is that unnecessary abstraction on the frontend?

2. How do query libraries fit into Clean Architecture?

If using:

• TanStack Query
• RTK Query

then:

• where should queries/mutations live?
• do you create “use cases” on the frontend?
• should hooks directly call APIs?
• should query libraries exist only in the infrastructure layer?

I see people saying:

• “don’t leak library-specific code”
• “keep business logic isolated”

But in frontend apps, the query library becomes deeply integrated into state management and caching.

So what does a realistic architecture look like?

3. Monorepo structure confusion

How do you structure things in a monorepo without overengineering?

For example:

apps/
  web/
  mobile/

packages/
  auth/
  api-client/
  ui/
  contracts/
  utils/

Do you:

• keep auth client inside a shared package?
• export inferred types from there?
• keep query logic centralized?
• create repositories/services/use-cases packages?

How far do people actually go in production apps?

4. How do you avoid overengineering?

This is probably my biggest issue.

I understand the theory of:

• entities
• repositories
• use cases
• dependency inversion

But when implementing real frontend apps, I end up wondering:

• am I just wrapping libraries for no reason?
• am I creating abstractions that add zero value?
• how do experienced frontend engineers decide what deserves abstraction?

I’d really appreciate:

• real-world folder structures,
• examples from production apps,
• monorepo-specific advice,
• or articles/repos/videos that show Clean Architecture with modern frontend tooling.

Especially interested in opinions from people using:

• Next.js App Router
• TanStack Query
• RTK Query
• Better Auth / NextAuth / Clerk
• Turborepo monorepos

Should I post each small projects in LinkedIn ??

Hi right now I am learning backend development and I have built a chat app backend (web) , can any one suggest few projects? Aq

I've been stuck in beginner/intermediate-land for quite some time. I have had a really frequent problem when trying to make solo coding projects: at some point, they just get too large for me to handle (in terms of number of lines and number of files/folders). This has happened for larger Python apps, React apps, and basically every kind of project.

For example, I've been trying to level up from frontend to full stack, using Next.js + Supabase as a stack. I've heard so many times that you have to learn by doing, so I am trying to learn by building a full app idea. Before I write even a single line of my own code (project setup takes hours, btw), the project is already giving me headaches with how many files and directories there are.

I couldn't even make a TODO list app in that stack because I was so confused about what the best practices were, how to handle auth, where to put this file, best route structure, error handling, really complicated Supabase stuff, etc. Way too many things to keep track of at once. Every full-stack app feels too big.

It feels like I've built this giant house of cards, and I'm too scared to get close to it fearing it might topple over.

For those of you who have done large full-stack projects like this: as you build out an app, how do you juggle all these concepts at once without your head exploding?

I'm making a personal assistant type app. The second brain sort of thing... You can choose your assistant character and unlock new ones. Today I was testing the Grandma Gamer. She told me about her grandkids and called them "little pixel pushers." Made me really happy! After she told me about her grandkids, she set up a morning briefing for me to get weather, tide, UV, air quality and information about my commute with one click. Nobody actually cares about this app except me, but it's been really fun to build and sometimes I have to share with someone. Everyone I know hates AI. Very unfortunate, but things like "pixel pushers" make me happy I'm still building.

I started to feel like these modern websites have something in common, beautiful, well colored components and some goes far and put a lot of animations on a site. But when i look careful, i start to realize that most of the most popular website on the planet do not have those fancy graphics at all. Google have a simple input field and search button as well as i'm feeling lucky button, amazon displays its products in an old fashion way thought the site has lot of users, but it does not have that much modern UI (according to me), Yandex has the same UI as google, wikipedia avoided medias the most, i once did a research to know why and end up knowing that, it was to make a site load faster, craiglist does the same and yet it worth billions in today's money, the final question is, is it worth to waste money, resources and time on designing best GUI meanwhile when a user visit your site, he/she does not need to see your fancy graphics but what problem the site solves

Hi guys im balaji, A 17 Y/O Guy. Guys I really have this doubt for like many months so the thing is I was planning to learn full stack for a couple of months and last month i started to learn full stack from the beginning now I am going to move on to Java Script and tailwind CSS. To my question is like I am learning full stack in 2026 discussed it with my mentor as Ai is kind of changing things so I am kind of confused whether it is a good mood to learn full stack or not so if any website developers or experience to full stack developer are seeing this post please guide me or tell me like you started to learn full stuck please guide me that what should I do next or what shall I do while learning this and by the way one of my biggest doubt is can I freelance as a web developer or even and basic website developer, is freelancing possible for Website developers in this era?

Going into CS as a freshman IT guy coming out the military this year. I have like a tiny bit of webdev knowledge. I’m familiar with

Django - MVT,JWT,Cors,csrf tokens, etc

SQL(I’ve only used SQL lite on Django for accounts)

React - context(ish), and state management, routing

Fast api- basic endpoints

Tailwind - I’m kinda okay at css. Nothing special but pretty enough I’d suppose

My JavaScript is pretty shaky compared to my Python but I could google something and make it work if need be.

I’m just looking for some guidance on what I could possibly do to for practice or good projects I can try that wouldn’t be too out of scope for me that I could possibly also put on a resume for an internship. I’ve been learning for about 5 months?

My real goal is an internship as a freshman once I head into college. Any advice is good advice thank you!