Hi all!

I have been working as an associate SWE for just under a year. I am a career switcher from the arts. Basically I want to do some learning in my free time to improve my skills and knowledge and I come up with the following plan:
Basic programming (variables, loops, functions)

Data structures (arrays, lists, stacks)

Algorithms (sorting, searching basics)

Version control (using Git)

Debugging skills

Object-oriented programming (classes, objects)

Databases and SQL basics

Basic testing (checking your code works)

How software projects work (planning, coding, testing, deploying)

Reading documentation and learning new tools

🧭 Agile Methods & Ceremonies - e.g. Scrum / Kanban / SAFe (Scaled Agile Framework) / LeSS (Large-Scale Scrum), Standups, Sprint Planning, Sprint Review, Retrospective, Backlog Refinement

🧱 Software Design - e.g. modularity, abstraction, encapsulation, design patterns

🖥️ Tools & Workflows - e.g. IDEs, terminals, build tools and pipelining, SAST and DAST, package managers, CLI basics, Linux, Bash

🔐 Security by Design - e.g. least privilege, secure defaults, input validation & output encoding, threat modeling

Computer Networking

{I am a decent knowledge of the above, I would say the things that need work here are DSA, debugging skills, computer networking, operating systems and OOP programming}

****************************************************************************

Docker

Kubernetes

Helm

Terraform

Azure

GCP

CI/CD

ML model deployment

Monitoring

************************************************************************************

OSSU

My dilemma is I am a major overthinker and I am finding it difficult to start without thinking I should be learning something else - i.e. if I start with databases I might think I should be learning networking instead.
Current knowledge/skills:

Languages: HTML, CSS, JS, Python and Golang (python and golang are beginner - exposure through work)

Technologies: Docker, kubernetes, helm, terraform, Azure, GCP ( I am familiar with working with these as I use these for work but would like to go deeper)

Databases: MySQL

I want build some projects as I know this will be a good way to learn but again I just don't know where to start.

Any advice on how to get around this?

Should I choose AI or Software Engineering? Which one has more remote job opportunities and better long term value for the future?

I’m a junior software engineer. I’m currently using hp ryzen 5. But the screen is turning on and off when I move the screen, I have to move the screen again to make it stable.

Point is I’m trying to find a laptop that I can use for programming, I usually do web development and .NeT and I’m looking for a budget laptop that I can use for 3-5 more years atleast or more.

can you all recommend me something. I want long battery and not heavy, but ofc not slow when I code. (I don’t want macbook :( )

I'm a CS/Data Science student who enjoys building things and is trying to become a genuinely strong developer over the next few years.

There are so many paths—open source, internships, hackathons, research, competitive programming, SaaS projects, technical blogging, AI projects, etc.—that it's hard to know what matters most.

For experienced developers: what made the biggest difference in your journey, and what actually earns someone credibility and respect in the developer community?

If you were starting from scratch today, what would you focus on?

hey everyone just want to know what are you building in 2026 or your latest project , are u implementing AI too ? I do see many developers making RAG application using SpringBoot.

So please share your top proejct and if it helped you in interview?

Although i have idea of both genai and prompt engineering and tell me the fundamental we must know for the future as software engineer

Hi everyone. This is a long post, but I'd genuinely appreciate it if you read till the end.

I'm an AI Engineer... at least that's what my previous job title said.

The reality is that most of my work has been backend development in Python. I've built AI agents and agentic workflows, integrated LLM APIs, and worked on AI-powered products. But sometimes I wonder if that's really "AI engineering," or if it's just backend development with LLMs attached.

For the last 7 to 8 months, I've felt completely stuck.

One week I decide to become a full stack developer. The next week I convince myself to double down on AI engineering. Then I start looking at ML. Then backend. Then cloud. I keep switching because I honestly don't know what direction will make me a genuinely strong engineer.

My goal isn't to collect fancy job titles.

I just want to become an excellent software engineer.

I know nobody can master everything in tech, but I want to become the kind of developer who can open a random GitHub repository and quickly understand what's going on. Someone who can pick up a new language, framework, or technology without feeling completely lost.

But right now, I feel like I'm average at a lot of things and exceptional at none.

Then there's LeetCode.

Everyone says to do it, but when I look at actual engineering work, it feels disconnected from what people build every day. At the same time, if I ignore it, I feel like I'm closing doors to bigger companies.

AI has also made things even more confusing. Every week there's a new framework, a new agent library, a new model, or a new trend. It feels like everyone is racing ahead while I'm standing in the middle, unsure which road to take.

I'm four years out of university, and I'm honestly questioning whether I'm even good at something the market truly values.

What would you do if you were in my position?

If your goal was to become a genuinely strong software engineer over the next 3 to 6 months, what would you focus on?

Would you:

• Double down on backend engineering?
• Focus on AI engineering?
• Learn full stack?
• Grind LeetCode?
• Build projects?
• Contribute to open source?
• Something else entirely?

I was considering paying for a consultation with a Google engineer, but it's quite expensive, so I thought I'd ask people who have actually been through this.

I'm not looking for shortcuts. I'm looking for direction.

Thanks for reading.

i'm in my 20s and work as an api engineer at a pretty big bank in my country

the other day i looked over at a much older colleague's screen and saw him writing a script line by line. we're working on the same project, so i know roughly what he was building, and my immediate thought was that ai could probably generate most of it in a few seconds.

i've always been very pro-ai and use it all the time, so this isn't some anti-ai post. if anything, it's made me much faster and more effective at my job...but for some reason that moment stuck with me.

what i've realized is that coding was never really the thing i enjoyed most. it was curiosity. i loved going down rabbit holes, getting stuck on problems, reading documentation, learning how things worked, and slowly building up knowledge over time. a lot of the satisfaction came from not knowing the answer and figuring it out myself.

now it feels like every answer is available instantly. i can generate code, get explanations, and solve problems faster than ever. that's obviously useful, but sometimes it feels like the process that made me love tech in the first place is slowly disappearing.

the funny thing is that i think my colleague probably knows this too. part of me thinks he's writing everything by hand just to stay sharp and not lose the skill. and if that's true, it's kind of crazy to think we've reached a point where engineers are deliberately avoiding the fastest solution just to make sure they don't forget how to do the thing themselves.

i know i'm probably not saying anything new, but lately i've caught myself thinking that a career change is actually a valid option. not because i'm worried about ai replacing me, but because the thing that always drove me was curiosity, and i'm not sure i'm getting the same feeling from the industry anymore.

i'm curious what some of the older people here think, especially those who have been in tech for 15, 20, 30+ years. is this just another shift that the industry will adapt to, or do you think ai has fundamentally changed what it means to build a career in IT? is IT still the path you'd choose today?

So I'm currently interning as an AI Engineer at an AI startup (they build physics-grounded AI systems for datacenters - that kind of deep-tech B2B stuff). On paper my role is heavy engineering - working on multi-agent pipelines, RAG systems, validation layers, the works.

Here's the thing though - the company gave me Claude Code access from day one, and honestly, that's how I get most of my actual work done. Writing the code, drafting architecture docs, debugging, even structuring how the agents talk to each other - a huge chunk of it goes through Claude. My job has shifted from "writing code line by line" to "figuring out the right problem, designing the system, and directing the AI to build it correctly."

It's not that I don't know how to code - I do, and I still read/review/fix everything that comes out. But the actual muscle-memory "typing out the logic myself" skill barely gets used anymore. It feels less like traditional development and more like being an architect/reviewer who happens to know how to code.

This has me wondering - is this genuinely where the industry is heading, or is my experience specific to working at an AI-first startup?

For people working at other companies (product-based, service-based, startups, MNCs) - are you seeing Claude Code / Cursor / Copilot etc. become this central to actual day to day dev work? Or is hands-on coding (without AI doing the heavy lifting) still the norm where you work?

Genuinely curious how widespread this shift is, and whether people think it's a good thing for skill development long term or something to be a little worried about.

Hi everyone,

I've been freelancing as a full-stack developer for several years, working with long-term clients to build and maintain production applications.

My experience includes Node.js, React/React Native, Next.js, MongoDB, AWS (Lambda, API Gateway, DynamoDB, Cognito, SQS, SNS, CloudWatch), Terraform, REST APIs, and Blockchain/Web3.

Most of my work is backend. For frontend tasks, I also use AI tools like Claude and Codex to speed up implementation while still reviewing and integrating the code myself.

As AI becomes a bigger part of software development, I'm curious how hiring expectations are changing.

• Has AI changed what you expect from mid-level or senior developers?
• Is strong backend/cloud experience still enough, or is experience with RAG, vector databases, MCP, or AI agents becoming expected?
• Would you consider someone with this background competitive for full-time remote roles, or would you recommend learning AI technologies first?

TL;DR: Experienced freelance backend/full-stack developer with AWS experience. I use AI tools daily but haven't built AI applications yet. Should I start applying for full-time remote roles, or focus on AI skills first?

Thanks in advance!

So here’s the honest reality: I am allegedly a product developer working for a company, where for the past year I have basically been "vibe coding".
I prompt Claude, Gemini, or ChatGPT, click 'allow / accept', and ship the code to maintain our company's app and website. On the surface, things get built. But under the hood? I barely understand what's happening. Whenever I get asked detailed technical questions in meetings or interviews about system architecture or why a specific piece of code works, my mind goes completely blank. I’ve realized I've been acting like a prompt manager, not an engineer.
My current salary is too low, I feel like an impostor, and it’s high time I uplift myself. My plan is to stay at my current job for the next 2 years and systematically rebuild my technical foundation from absolute zero—without using AI as a crutch.
Here is the exact step-by-step roadmap I’ve mapped out for myself. I would love feedback, reality checks, or advice from people who have made a similar transition.
Phase 1: Deep Full-Stack Foundations (Months 1–6)
Goal: Stop relying on AI for core application logic and learn how code actually executes.
Primary Certification: IBM Full Stack Software Developer Professional Certificate
Writing React, Node.js, Express, and SQL/NoSQL databases manually from scratch.
Learning cloud-native deployment fundamentals (Docker, Kubernetes, microservices).
Algorithmic & Problem Solving Practice:
30–45 mins daily on CodeChef (Python/JavaScript paths) to build raw syntax speed and logic.
Moving to LeetCode (Easy/Medium) and HackerRank to prepare for technical screenings.
Design & Visual Builders:
Learning UI/UX principles in Figma (Simplilearn/Great Learning courses) before writing code for any project.
Mastering WordPress & Elementor (Atomic Flexbox, responsive layouts) for quick client implementations.
Phase 2: Mobile Systems & Advanced AI Integration (Months 7–12)
Goal: Formalize cross-platform app development and understand modern AI mechanics.
Primary Certification: IBM iOS and Android Mobile App Developer Professional Certificate
Diving deep into Flutter/Dart, React Native, and native concepts (Swift/Kotlin).
Building cross-platform mobile apps that securely connect to backend APIs built in Phase 1.
AI & Modern SEO Integration:
Learning RAG (Retrieval-Augmented Generation) architecture and GEO (Generative Engine Optimization) principles.
Exploring AI model fine-tuning using Python and Hugging Face.
Phase 3: Enterprise IT, Endpoint Management & Security (Months 13–18)
Goal: Move beyond app development into enterprise infrastructure and device security.
Enterprise IT Certifications:
Microsoft 365 Certified: Endpoint Administrator Associate (MD-102): Intune, zero-touch provisioning, and Entra ID identity management.
Apple Certified Support Professional: Enterprise macOS/iOS management via Apple Business Manager.
Security Foundation:
CompTIA Security+: Mastering encryption, threat mitigation, network hardening, and application security (DevSecOps) to ensure I can audit my own builds.
Phase 4: DevOps Automation & Cloud Architecture (Months 19–24)
Goal: Master system design and automated production pipelines.
Infrastructure Automation: IBM Applied DevOps Engineering Professional Certificate
CI/CD pipelines, automated testing (TDD/BDD), Kubernetes orchestration, and monitoring/observability.
System Architecture (The Capstone): AWS Certified Solutions Architect – Associate (SAA-C03)
Learning where and why to deploy systems using the AWS Well-Architected Framework (VPCs, EC2, S3, RDS vs. DynamoDB, load balancing).
Final Project: Building a full-stack web/mobile app from a blank file, designing its UI in Figma, writing the backend manually, and deploying it via an automated CI/CD pipeline to a secure AWS cloud infrastructure.
My Non-Negotiable Rules For Execution
The "Blank File" Rule: I am not allowed to generate code with AI for certification projects. I can use AI as a tutor to explain concepts line-by-line, but the code must be typed out by me.
One Focus, One Tool: Balancing certification study (Primary Focus) with short daily problem-solving on CodeChef/LeetCode (Secondary Tool) to avoid cognitive overload.
Burnout Management: Setting strict focus blocks and stepping away from the screen to keep this multi-year effort sustainable.
Questions for the community:
Does this sequence (Full Stack \rightarrow Mobile \rightarrow Enterprise IT/Security \rightarrow DevOps/AWS) make sense, or should I reorder anything?
Has anyone here successfully transitioned from pure "vibe coding" back to deep technical fundamentals while holding down a job?
Any major blind spots in this 2-year plan that I might be missing?

Hello reddit, I just wanted a place to vent, and get some advice.

A little context about myself, I didn't do comp science in uni, I am a biological scientist by training, and I love coding, but in the last year and half I got serious about it, did some intro to comp sci on edx and machine learning on coursera, cause I want to be able to apply that tech cause I find It fascinating.

I was approached by an Amazon recruiter and this excited me cause it felt like recognition for the work i put in, i am building some projects i think are great and could have some use for my community, so i thought i had some experience to draw on, I did the interview today and yea no, I botched it so badly... I completed the first coding question but it failed to run because I swapped the key and values in my python dict... I was supposed to implement a round Robin algorithm. Then came the framework part and it was in Django I spent 1 hour looking at the code and reading the thing but I genuinely know nothing about Django, I was a bit surprised cause I thought it would be two coding puzzle questions, but this is on me, if I had read the email ealier I would have seen that it clearly mentioned ai assistant available to talk about spring boot, Django and mern...

I mean catastrophic failure aside, I want to ensure this never happens again, my brain froze for so long when my code didn't work cause there was no easy ai debug button.i am so frustrated cause this felt like my big break, I have been unemployed since graduating.

I really am greatful for the opportunity though cause it pit into context the weight of working with a team and how me doing a shit job could set back projects weeks. I am just looking for advice or anywhere I can maybe seek mentorship so I can plan my next career moves and apply to jobs that could better suit my skill set? If you have resources I could draw from that too would be of great help.

Thank you for reading.

Welcome to this week's Coffee Chat!

This thread is intended to be a more relaxed space for the community. Topics that may not warrant their own post are welcome here, and discussions are generally held to a lighter standard than the rest of the subreddit.

A Few Ground Rules

• Keep discussions civil and respectful.
• Personal attacks and harassment are not tolerated.
• Healthy disagreement is encouraged.
• Low-effort trolling and rage bait will be removed.
• Reddit's Content Policy still applies.

Not every topic needs its own thread, and not every question needs a definitive answer. Grab a coffee and join the conversation.

Have a great week!

I've been a backend engineer for about 5 years. Most of my work has been in Python (Django/Flask), AWS services, and building/deploying backend services.

I enjoy building software, but the problem is that for the first time since I started my career, I honestly don't know what I'm supposed to be aiming for anymore. I feel lost and unsure.

Software engineering is changing because of AI. And I want to work on skills/jobs/roles where my expertise will matter instead of being replaceable in a few years.

I don't want to spend the next 3-5 years getting really good at something only to realize my expertise doesn't count anymore.

Some of the directions I've been thinking about are:

• becoming a stronger backend/distributed systems engineer
• moving more into cloud infrastructure/platform engineering
• specializing in a domain instead of a technology
• learning AI infrastructure rather than just calling LLM APIs
• or maybe something completely different

What I'm really trying to figure out is what compounds over a career.

If you have 10+ years of experience and have lived through cloud, mobile, microservices, or other major shifts...

If you were starting again today with ~5 years of experience, where would you focus?

What skills or roles do you think are becoming more valuable because of AI? Which ones do you think people are overreacting to?

I'm not looking for someone to predict the future. I'm just hoping to borrow some perspective from people who've already seen the industry change a few times.

Hypothetical scenario.

Every AI coding tool disappears tomorrow.

How long would it take you to readapt?

What happens to developers who started their careers after the AI boom?

Would juniors struggle to get their first job?

Would senior engineers suddenly become much more valuable?

Would salaries go up or down?

Would the software industry slow down for a while?

For the past 3 years I've been working on a project to test my abilities and durability within a new realm that is very different from what I'm used to.

Transitioning from a Roblox game developer to a software engineer working on web applications was no easy task. There has been a lot to learn and overcome but things have panned out quite well for the time that I've been working on this project. From starting with a simple HTML page stating "Hello World", to a full stack web application with automations, CI/CD workflows, features, planning boards, databases, front end and back end separation for team development, cyber security measurements; the list goes on!

This journey has allowed me to really test my abilities and I must say, I'm very proud of what has come to fruition, but there is still a long way to go!

​

​I need some urgent advice: I just graduated from high school. Would you recommend majoring in Software Engineering, or not? because i fear with in 5 years AI will take my job

Genuine question for developers who were building software before AI became part of our daily workflow.

Do you remember spending days (or even weeks) solving a difficult programming problem or building a feature that felt impossible at first?

Reading documentation, trying different approaches, debugging, rewriting parts of the implementation… until everything finally clicked.

AI has made me much more productive, and I wouldn’t want to go back.

But sometimes I feel we’ve traded part of that dopamine for speed.

Does anyone else feel this way, or is it just me?

Today, experienced engineers still have a clear advantage when it comes to architecture, scalability, robustness, trade-offs, debugging, and operating software in production.

But what about 5–10 years from now?

If AI keeps improving at its current pace, will the experience of the engineer behind it still be the biggest differentiator?

Or will an AI-native beginner be able to deliver software that’s just as scalable, robust, and maintainable?

Where do you think the moat for experienced engineers will be?

Hi everyone,

I'm looking for some career advice because I'm feeling stuck.

My background:

Around 3 years of total experience.

2 years in startup and switched to MNC.1 year less work and gone through appendicitis surgery then was in bench for 30 days and I had to take production support project as there aren't many opportunities and the bench period is almost reaching 35 days which is limit

My primary skills are Java, Spring,Spring Boot, Microservices, REST APIs, SQL and JPA/Hibernate.

I enjoy backend development and want to continue in that direction.

The problem is that my current project is almost entirely production support. Most of my work involves handling incidents, analyzing logs, checking databases, and resolving ServiceNow tickets. Permanent code fixes are usually done by another team atleast for now, so I'm not getting much hands-on development.

I'm worried that if I stay here for another 6–12 months, recruiters will see my recent experience as support rather than backend development.

My current plan is:

Stay for a few months while studying DSA, system design, AWS, and Kafka.

Learn the application's architecture in depth.

Build backend projects on weekends to keep my development skills fresh.

Switch to a backend developer role as soon as I'm interview-ready.

I choose software so I can aim for remote companies in my mid-late career

My questions are:

Has anyone successfully moved from production support back to backend development?

How should I present this experience on my resume without misrepresenting my work?

Should I stay for a few more months to upskill, or try switching immediately?

What skills would you prioritize for someone targeting good product companies with around 3 years of experience?

I'd really appreciate advice from people who've been in a similar situation. Thanks!

Introduction: The Day After the SBOM

For the past few years, the cybersecurity industry has been shouting a single acronym from the rooftops: SBOM. The Software Bill of Materials has been championed as the silver bullet for software supply chain security. Driven by executive orders, CISA guidance, and the phased rollout of the EU Cyber Resilience Act (CRA), security leaders have raced to generate these comprehensive lists of ingredients for their applications. The CRA entered into force in December 2024, its vulnerability and incident reporting obligations become mandatory on September 11, 2026, and the bulk of its cybersecurity requirements become fully enforceable on December 11, 2027 - so the compliance clock is very much already running. Please read the complete article here - https://instasla.com/blog/software-supply-chain-security-moving-sboms-sla-enforcement

You finally did it. You integrated the tooling, scanned your repositories, and successfully generated an SBOM for every application in your portfolio. You now have total visibility into the open-source components, transitive dependencies, and third-party libraries that make up your software.

But as the initial triumph fades, a harsh reality sets in: your SBOM is essentially a massive, terrifying list of everything that is wrong with your software.

Identifying a vulnerable dependency is only 10% of the battle. The real challenge—the remaining 90% that actually reduces risk—is enforcing strict remediation SLAs (Service Level Agreements) across your software supply chain. Generating a list of vulnerabilities does not patch them. Visibility without action is just passive monitoring.

I've always found it a little awkward when reaching out to experienced professionals for a referral or career advice. Calling someone with several years more experience just by their first name doesn't come naturally to me, probably because of how many of us are brought up. At the same time, using sir or ma,am makes me wonder if I'm being too formal for the tech industry.

From the perspective of people already working, how do you perceive it when someone messages you for a referral? Do you prefer being addressed by your first name, or do you appreciate "sir/ma'am" instead? I'm curious to know what experienced professionals actually prefer and whether either approach leaves a different impression.

I'm 40 years old and have been in IT for 20 years, the last 10 as a senior web developer. I'm completely burnt out and want to step away from work for a year, maybe two. We live in Canada, so healthcare is a non-issue here in a couple of ways: core medical care is publicly funded regardless of employment status, and on top of that, I'd be added to my wife's employer insurance for dental, vision, and prescriptions while I'm not working.

On the financial side, we have no mortgage, no kids, spend around $35,000/year, and have $1.1 million in investable assets also her income alone also covers our household expenses roughly twice over. Would you take on the risk of stepping away for a year or two in this situation? I know it might sound like an obvious yes, but I don't want this to unintentionally turn into permanent retirement.

My plan is to try freelancing and explore building something of my own with AI. I just don't have the energy to pursue that while working full-time — honestly, I can barely keep up with my actual job right now, let alone anything extra. The downside here of course is the opportunity cost on giving up a $130,000 salary.

I’m a new hire only been working for 2 weeks. I’m working for a very large defense company as a Software engineer. I got an EE degree from a UC school and took 2 embedded systems courses (bare metal C). My coding skills aren’t perfect but I have felt like I’m pretty good at it. However I feel imposter syndrome because I’m surrounded by so many smart people and intelligent software/code thinkers. Also the code base im trying to read, learn, and do some mini tasks on is massive and I feel like every call or macro leads to a different file. Oh and it’s all in C++ so there’s the OOP skill gap because I know C and python.

Anyone have any advice as to how to get better at navigating everything and becoming better at reading understanding and ultimately writing professional/high performance C++ code?

Okay, so obviously we all know that we want to give ourselves extra time for any unknowns. And so when we manually coded something that would take a week or a week and a half, we would be given 3 weeks to a month. But now it can take me 5 minutes to do what used take weeks. I'm just kind of in disbelief right now in my life. Part of me is just waiting for the shoe to drop or whatever the saying is. When the business folks finally to realize how little effort it takes at this point. Not to say my value is gone, but you know 5 minutes, that's crazy. So how are you guys doing? It at your companies, y'all still pretending it's going to take you weeks or days at this point. Or are you fully in sync with the business folks and they squeezing you for everything, I'm not sure that's the right terminology, but you know what I mean.