r/softwareengineer • • Jun 22 '26

New Community Posting Rules

8 Upvotes

Lately, the community seems to be getting inundated with the same types of posts. Most of them revolve around AI and whether it's still worth pursuing a career in software engineering.

There are many factors that will influence that decision, and no one in this community can answer it for you. Your best bet is to do your own research and make the choice that best fits your circumstances. The future is unpredictable, so regardless of what anyone tells you here, it's ultimately just a guess.

Community Changes

  • We are creating a weekly Tuesday thread called Tuesday's Coffee Chat. Feel free to discuss whatever you'd like. As a trial run, we will allow topics and comments that would normally fall outside our community rules. If the thread gets abused, we will adjust the rules as needed.
  • We will no longer allow posts asking whether it's still worth pursuing a career in software engineering because of AI, whether AI is taking over software engineering, or similar questions about AI's impact on software engineering jobs. If you'd still like to discuss these topics, you are welcome to do so in Tuesday's Coffee Chat.
  • Some members are already in the field and are considering career or life changes. Rather than allowing separate posts for these topics, we encourage you to use Tuesday's Coffee Chat instead.
  • Many members are experiencing AI fatigue, so posts revolving around AI will be more heavily scrutinized. Posts should have depth and encourage meaningful discussion. Low-effort or repetitive posts will be removed.

r/softwareengineer • • 5d ago

Tuesday's Coffee Chat - November 17, 2026

3 Upvotes

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!


r/softwareengineer • • 1d ago

Manager "vibe-codes" broken apps with Claude over the weekend and expects us to own production

198 Upvotes

I recently joined a company as a software engineer. Over the past month, my manager has been pushing hard to ship AI projects quickly, which I’m normally fine with except for how he’s going about it.

Here is the pattern: he assigns a customer-facing project to our team, and while we are planning and building it properly, he spends the weekend "vibe-coding" his own POC using Claude. By Monday, he overwrites everything he even wiped our entire git history recently and tells us to move on to something else.

The problem is that his AI-generated code is a mess: hardcoded credentials/values, zero best practices, and fragile infrastructure (he spun up load balancers, caching, and databases purely through AI prompts). Nobody on the team knows where the data lives, which servers host the DBs, or what models/files are actually running including him.

Now, he has 3–4 of these projects scheduled to go live this year, and he wants someone from the team to take ownership and be on-call for production failures. Naturally, nobody wants to touch them because we didn't write the code, have zero context, and know it’s going to break.

We’ve tried asking him to step back from coding, but he’s high-level management and insists he just wants fast delivery.

How do we protect ourselves and handle this situation without tanking our careers?


r/softwareengineer • • 1d ago

Company putting hard limit cap on AI usage

178 Upvotes

Im a Technical Leader in a F500 company. The company I work for has announced yesterday that starting next week, there will be a hard limit cap on AI usage per employee.

This comes after 1+ year of management pushing to adopt AI development and AI workflows into pretty much everything, while also slicing teams and expecting more output out of everyone.

To be very honest, I haven't written a single line of code for almost 1 year now, and I sense some sort of skill atrophy both on my skills and my team's. It is not clear right now if the teams will come back to their original size (I highly doubt this) and/or the timelines will be extended and management won't be expecting the same productivity gains.

I should also mention that local models etc are completely blocked from corporate policies, we are allowed to use only the enterprise AI.

Has anyone been in the same position, and any ideas on how to go through this situation ?


r/softwareengineer • • 10h ago

I think we're overestimating what AI brings to software engineering (beyond productivity)

0 Upvotes

​

I've been thinking about the current AI hype in software development, and I have a feeling we're sometimes confusing the ability to produce code with the ability to engineer software.

Don't get me wrong. AI is incredibly useful. It can write code faster than most developers, implement features, refactor existing code, generate tests, explain unfamiliar technologies, and automate repetitive tasks.

I actually think the most effective way to use AI right now is as an assistant.

However, I think there is a fundamental distinction that gets overlooked.

Writing software and advancing software engineering aren't the same thing.

Most software developers use existing concepts to solve real-world problems. We use established algorithms, architectural patterns, programming paradigms, design principles, and technologies.

But where did those concepts come from?

They were developed by software engineers, researchers, and computer scientists who questioned existing approaches, identified limitations, and came up with new ways of thinking about software.

Think about object-oriented programming, functional programming, relational databases, distributed systems, type theory, and the many architectural concepts we rely on today.

These weren't simply implementations of existing ideas. They fundamentally changed how we approach software problems.

And this is where I have some doubts about current AI capabilities.

AI is very good at using existing knowledge, combining established patterns, modifying existing implementations, and generating solutions based on what it has learned.

But I'm not convinced that this is the same as independently identifying a fundamental limitation in an existing paradigm and developing an entirely new concept to overcome it.

Can AI generate something novel? Absolutely.

Can it contribute to research? Certainly.

But can it consistently demonstrate the kind of fundamental conceptual thinking that leads to entirely new engineering paradigms? I'm not convinced yet.

And I don't think we should assume that making AI better at generating code will automatically make it better at this kind of intellectual work.

There is another issue that concerns me even more: technical debt.

AI makes producing code significantly cheaper and faster. But understanding, reviewing, maintaining, and evolving that code hasn't become proportionally cheaper.

Imagine developers accepting AI-generated implementations simply because they work, pass tests, and follow existing patterns.

An implementation can be perfectly functional today while introducing unnecessary abstractions, tight coupling, duplicated logic, or architectural decisions that make future development harder.

Now imagine this happening across hundreds or thousands of changes in a project.

We could end up with codebases that grow faster than our ability to understand and maintain them.

In other words, AI might help us accelerate development while simultaneously accelerating the accumulation of technical debt.

I also think there's a long-term risk if developers become too dependent on AI for implementation without understanding the underlying concepts. We might become increasingly efficient at applying existing knowledge while investing less effort in understanding, questioning, and advancing it.

My current position is simple:

AI should help us implement good engineering decisions, not replace the thinking required to make those decisions.

Use it to accelerate development, explore alternatives, automate repetitive work, and improve productivity.

But architecture, conceptual design, technical trade-offs, and engineering responsibility still require genuine understanding.

I'm not saying AI will never reach a different level. I just think we're too quick to assume that better code generation means better software engineering.

What do you think?

\- Are we confusing code-generation capabilities with actual software engineering capabilities?

\- Do you think AI will eventually be able to create fundamentally new software concepts and paradigms, rather than primarily building upon existing knowledge?

\- Are we underestimating the technical debt that AI-assisted development could introduce?

\- Could excessive dependence on AI eventually weaken developers' ability to reason about software architecture and design?

I'd especially like to hear from experienced software engineers, architects, programming language researchers, and people working on foundational computer science.


r/softwareengineer • • 1d ago

10 years of self-taught programming, real-world experience, ADHD, and I still don’t know what I don’t know. How do I move forward?

0 Upvotes

I’m 23, from Bangladesh. I’m not even sure if this is the right subreddit, but I want to hear from engineers who’ve been through something similar.

Some background so you know where I’m coming from (You can skip this part if you want):

I started programming in 2016 with C, initially learning from my dad, and pretty much taught myself everything afterward. Never really followed a structured CS curriculum. I learned by getting interested in something, attempting to build it, getting stuck, and figuring things out. Started with a text-file database, experimented with grammar-based NLP, got into C#, Unity, and game development, spent time messing around with vehicle physics, friction, torque, and transmissions, then eventually moved into web development. Between 2021 and 2023, I worked with Linux servers, deployments, and Next.js. In 2024, I worked professionally on POS and warehouse-management software using React, TypeScript, Node.js, and related tooling. At one point, I had to move a React POS frontend to React Native in about a week. I’ve spent ridiculous amounts of time debugging things like React hooks breaking during Vike SSR module initialization, native Node dependencies failing to compile, and deployment environments behaving nothing like development. Later, I worked with ESP32, MQTT, and mobile/web applications for IoT systems. Got interested in cybersecurity too, spent time on web exploitation, SQL injection, network reconnaissance, and eventually Cloudflare origin-bypass research. In 2026, I started my own software business and built Bluemint, an AI-powered commerce platform using LLMs, retrieval, tool calling, PostgreSQL, and Meta’s messaging APIs, alongside order management, inventory, and other business operations. This introduced an entirely different set of problems. We had AI agents claiming orders were placed when they weren’t, duplicate orders, and inconsistent external order states. One integration was sending our internal order ID to an external ERP but polling with the provider’s UUID, returning 404s while order states silently diverged. Suddenly, things like idempotency, durable state, reconciliation, and transactional correctness weren’t just concepts to read about. They were actual production problems. We’ve handled thousands of real customer conversations and hundreds of orders, but commercially, things haven’t been nearly as successful. I’ve spent roughly $2,400 building the business and brought in around $2,500. And throughout all of this, financial problems, family responsibilities, unstable work, and personal circumstances repeatedly forced me to abandon whatever I was passionate about to focus on whatever would pay the bills.

Now here’s what I’m actually struggling with.

  1. I don’t know what I don’t know, and I’m terrified of starting over.

Because I’ve always learned through projects, my knowledge is incredibly fragmented.

I might understand how to design a system, deploy it, debug production issues, or reason about fairly complicated architecture. But then something requires a fundamental concept I never properly learned, and suddenly I feel like a complete beginner.

Recently, I got interested in post-quantum cryptography and started learning about NTTs. That eventually sent me all the way back to modular arithmetic and basic mathematics.

And I genuinely enjoyed understanding the math instead of just making something work.

But this keeps happening.

Every time I explore something deeply enough, I discover another layer of things I should already know.

How do you even identify those gaps when you never followed a curriculum? Do you go back and study CS from scratch? How do you distinguish something you genuinely need to understand from something you can learn when the work demands it?

And how do you do that while you still need to earn money?

The bigger problem is that I’ve become afraid of trying.

I’ve started over so many times. Every time I found something I loved, life required something else.

I’d spend months learning something, become reasonably competent, then have to leave it behind. Eventually, when I returned, I’d forgotten enough that getting back into it felt like starting from zero.

After repeating that cycle for years, I don’t even trust myself to finish what I start anymore.

It’s almost like I’ve conditioned myself to expect failure.
And I don’t know how to undo that.

2. AI has made me question my own competence.

Nowadays, I let Claude handle a lot of implementation and specifications. I spend more time thinking about architecture, edge cases, and reviewing what it produces.

Sometimes that’s genuinely productive.

Other times, I realize I haven’t actually thought through the implementation myself. And sometimes I get lazy about reviewing it too.

I’ve seen firsthand how confidently AI can produce something that’s completely wrong, especially when the problem involves state, business logic, or requirements it doesn’t fully understand.

Yet I still find myself depending on it.

So now I have another question: am I becoming a better engineer by working at a higher level of abstraction, or am I slowly losing the skills that made me an engineer in the first place?

How do you maintain technical depth while using tools that make it increasingly easy to avoid the difficult parts?

3. How does finding serious software clients actually work?
This is something I genuinely don’t understand.

I can build software. I’ve worked professionally, shipped things, dealt with production problems, and even built a business around it.

But finding paying customers consistently? Completely different story.

I’m not asking for the usual “go to Upwork,” “send 100 cold emails,” or “sell AI automation to local clinics” advice.

I want to understand how experienced independent engineers actually find opportunities.

How do you get into conversations with businesses that have real engineering problems? How do you build the kind of relationships where someone trusts you with a serious project? Where does that network even come from when you’re starting without connections?

And how do you figure out whether a problem is worth building a product around before spending months solving it?

Because apparently, being able to build something and knowing how to make a living from it are two very different skills.

4. How do you rebuild yourself when you no longer believe your own plans?

This is probably the hardest part.

I have ADHD, and consistency has always been a problem. But I don’t think ADHD alone explains everything anymore.

I’ve tried schedules, roadmaps, habit trackers, breaking goals into smaller tasks, forcing discipline, following my curiosity, ignoring my curiosity, focusing on one thing, juggling multiple things.

Sometimes it works. Sometimes brilliantly.

Then I lose momentum, something goes wrong, or life demands my attention elsewhere.

And the whole thing collapses.

The frustrating part is that I understand what I should be doing, at least in theory. But understanding it and actually doing it are completely different things.

I’m not looking to become a millionaire by 30. I’m not expecting to master every field in computer science.

I just want to be genuinely competent at something, make a stable living, and have the freedom to enjoy engineering again.

But after years of trying, failing, adapting, and starting over, I’m exhausted.

It’s not that I don’t want to improve. It’s that every new attempt feels like another promise to myself that I’m eventually going to break.

And I’m extremely pissed off about it.

So I guess what I’m really asking is:

How do you build a solid foundation when your entire career has been built around learning things out of order?

How do you choose a direction when you’ve repeatedly been forced to sacrifice your interests for survival?

And most importantly, how do you regain the confidence to commit to something when your own experiences have taught you not to trust yourself?

I’d especially appreciate hearing from self-taught engineers, people with ADHD, and those who’ve had to rebuild their careers under financial pressure.

What actually worked for you? Not motivational advice or another productivity framework, but something you experienced and can genuinely stand behind.

Thanks for reading.


r/softwareengineer • • 2d ago

I'm Being Pressured to Ship Slop!

108 Upvotes

I'm a senior software engineer with around 10 years of experience. I currently work at a startup where business leadership just wants to "ship fast." Meanwhile, other, less experienced engineers are opening 100 PRs a day full of AI-generated slop to show how productive they are.

Nobody has time to review all these PRs, so basically everything gets shipped without proper review. AI isn't doing a particularly good job either. The product is becoming increasingly unreliable, weird edge cases keep popping up, engineers have no idea what's going on, and clients are reporting all kinds of strange behavior. Yet people keep shipping because they want to look good in front of management.

I used to carefully review AI-generated code, refactor things, and worry about maintainability and performance. Lately, though, I feel like I'm becoming the slow guy compared to people who are literally vibe coding their way through everything.

Is this happening everywhere, or is it just my company? Should I start looking for another job, or is this the new reality of software engineering? I genuinely feel like I'm becoming a worse engineer by working in this environment.

The other day, I saw a post where someone argued that we need to learn to let go of code reviews. I wish we could, but I don't think we're there yet. Any experienced engineer knows how much can go wrong when nobody is actually reviewing what's being shipped.

Harvard also recently released a paper suggesting that AI isn't necessarily improving productivity across the entire software delivery lifecycle: https://fion.ac/jellyfish.pdf

I'd like to hear from other senior engineers. Are you experiencing the same thing?


r/softwareengineer • • 1d ago

2025 Graduate | 1.5 Years of Experience – Should I Switch from Legacy .NET to Cloud, Data Engineering or Another Domain? Need Career Advice.

1 Upvotes

Hi everyone,

I'm a 2025 graduate with around 1.5 years of experience working as a .NET Developer at a startup.

My current tech stack includes:

  • C#, ASP.NET Web Forms, ASP.NET MVC 5, .NET Framework 4.8.1
  • ASP.NET Web API, SQL Server, MySQL
  • JavaScript, jQuery, HTML, CSS, Bootstrap
  • database management, application maintenance and troubleshooting.

I primarily work on applications, handling frontend development, backend integration, database operations, application upgrades and deployment.

Honestly, I feel like I'm getting stuck. My current company offers very limited technical growth, and most of our technologies are outdated. I'm learning through real-world projects, but I'm concerned about whether these skills will help me move into good product-based companies in the future.

I don't want to spend the next few years maintaining legacy applications and struggle to switch later. My goal is to get into a top product-based company, build strong technical skills and achieve good salary growth.

I'm willing to invest 6–12 months in learning a completely new stack if needed.

I'm confused about which direction has the best long-term career opportunities, salary potential and demand.

I'd especially appreciate advice from senior developers, tech leads and people working in product-based companies:

  1. Would you recommend upgrading to modern .NET or switching domains completely?
  2. Which technology has better long-term opportunities and salary growth?
  3. What skills should I focus on for the next 6–12 months?
  4. What projects and certifications would actually make my resume stand out?
  5. What is the best roadmap to get into companies like Microsoft, Amazon, Google or other good product-based companies?

I'm not looking for shortcuts. I'm ready to put in the effort and take risks, but I want to invest my time in the right direction.

Please share your honest experiences, recommendations and mistakes I should avoid. Any guidance from people who have already gone through this journey would genuinely help me.

Thanks!


r/softwareengineer • • 1d ago

Want to learn but idk

0 Upvotes

I’m a software engineer with around 2 years of experience, but honestly, I feel like I’ve drifted quite far from actual coding because of how heavily my company relies on AI.

I’m starting to worry about my career, especially with all the layoffs happening. If I were to lose my job tomorrow, would I be prepared to crack interviews or land another job? Honestly, no.

My job pays well, and I work at a good company, so I’m not unhappy with where I am. But I’m worried that I’m not building the skills I should be building at this stage of my career.

After work, I’m usually so exhausted that I struggle to find the motivation to learn anything on my own. I keep procrastinating, and I know I need to break that cycle.
I want to start somewhere, but I’m confused about what to learn, how to structure it, and what actually matters in today’s job market. I’m even willing to pay for structured programs or live classes if having a fixed schedule and accountability will help me stay consistent.

I’d really appreciate advice from people who have been in a similar situation, gone through it, and managed to turn things around. What did you learn? Where did you start? What would you do differently if you were in my position today?

Thanks in advance for your responses!


r/softwareengineer • • 2d ago

AI makes coding faster, but I’m not convinced it always makes delivery faster

50 Upvotes

I’ve been working in software engineering for 14+ years, and one thing I’ve been thinking about lately is the difference between coding speed and actual delivery.
AI tools can help developers generate code quickly. But teams still need to review, test, debug, and maintain that code.
For me, the interesting question isn’t how many lines of code AI generates. It’s whether the team delivers reliable software faster without creating more problems later.
I’m curious how other engineering managers are approaching this.
Are you seeing improvements in overall delivery, or mainly in individual coding speed?


r/softwareengineer • • 2d ago

One 27 Inch or Two 24 inch Monitor ?

3 Upvotes

So I'm a software developer and want to build a setup at home to study and work both. What would you advice is better?

At office i have a single 24inch monitor paired with one linux ThinkPad.

At home I have an m3 air and I'm confused if I should replicate the office set-up or go for two medium ones.

Also recommendations for both are appreciated.


r/softwareengineer • • 1d ago

I’ve been programming for almost 10 years. Built everything from stupid scripts to ERP systems, got into hacking, started a company, and now I genuinely don’t know what the fuck I’m doing anymore.

0 Upvotes

I’m 23, from Bangladesh.

Started programming in 2016. My father introduced me to C, and one of my first projects was a database that stored records in text files.

I thought it was the coolest thing ever.

Then came C#, PHP, JavaScript, and a ridiculous number of side projects.

I built a PHP forum, Windows applications, and once made a program that would play GTA V by itself so the game would think I was still online.

Why? I don’t fucking know. I just thought it would be cool if my computer could do that.

Around 2018, I tried building my own AI assistant called Ellie.

There were no ChatGPTs back then. I barely understood NLP, so I used what I knew from school English grammar, tokenization, dictionaries, statistics, and a whole lot of questionable Python.

It could answer basic questions, look things up on Wikipedia, control media, and execute commands.
The architecture was probably horrifying. But it was mine.

Then I discovered cybersecurity.

Started with the usual Kali Linux, Nmap, SQLMap, Gobuster, SQL injection, and all that script-kiddie stuff.
But eventually I got more interested in understanding why things broke rather than just breaking them.

That led me into networking, Linux, server security, reverse engineering, and eventually cryptography.

Somewhere in between, I also built an OpenCV automation tool that processed over 1,500 student ID photos, worked on websites and backend systems, made mobile apps, POS software, and a bunch of other things.
And because apparently I couldn’t just enjoy drifting in GTA San Andreas and Forza, I started building my own car physics in Unity. Engine torque, friction, transmission, suspension, the whole thing.

I have this stupid habit of seeing something interesting and immediately wanting to build my own version of it.
Sometimes it works. Sometimes I spend weeks on something that nobody, including myself, actually needs.
My academic life hasn’t been particularly great either. I’ve struggled with university, motivation, consistency, burnout, and financial problems.

It’s honestly ridiculous that I can obsess over understanding a complicated technical concept for days but struggle with things normal people seem to manage just fine.

Anyway, around 2024, I started working professionally on more serious software projects. Built websites, business applications, backend systems, ERP stuff. Some were successful, some disappeared along with the businesses that owned them, and some simply weren’t good enough.

Eventually I thought, why the fuck am I building things for everyone else? Why not start something of my own?

So I did.

I started a company in Bangladesh building AI automation for Facebook commerce businesses.

The original idea was simple. Businesses receive thousands of Messenger conversations. Let’s make an AI that can understand customers, check actual product information, and take orders.

But then I thought, well, it needs inventory management.
And orders.
And POS.
And accounting.
And courier integrations.
And employee management.
And fraud detection.
And somehow I ended up building a fucking ERP system with an AI agent attached to it.

Classic me.

And surprisingly, it worked.

We got paying customers. The system handled over 130,000 messages, thousands of conversations, and hundreds of AI-captured orders.

I hired people. We had a team. For a while, things were actually going somewhere.

Until they weren’t.

Management issues, hiring mistakes, customer churn, inconsistent sales. Some things were my fault. Some things I simply wasn’t prepared for.

And every time something went wrong, I did what I knew best.

I wrote more code.

Customer doesn’t understand something? Redesign the dashboard.

Need more value? Add features.

Competitor launches something? Build a better version.
But somehow, with all those features, we still struggled to consistently acquire and retain customers.

I’ve spent around $2,400 on the business and made about $2,500 in revenue.

That’s $100 left. Before accounting for my own time.
And the funniest part is that a lot of the features I spent so much time developing haven’t even seen proper production usage.

Not because they necessarily don’t work. We simply don’t have enough customers using them.

I was measuring conversations and AI-captured orders before fully understanding how many became fulfilled, profitable sales.

That’s when it started hitting me.

Maybe I was solving technical problems that weren’t actually the business’s biggest problems.

And now AI has made everything even more confusing.

I use AI. I build with it. I run local models, experiment with agents, and test what they can and can’t do.

But every company seems to be moving toward the same thing.

AI agents, automation, business software, chatbots, everything.

Meta is building business agents. Smaller SaaS companies are doing similar things. Everyone can build software faster than ever.

And I’m sitting here wondering what the actual competitive advantage of being a good programmer is anymore if you can’t sell what you build.

Meanwhile, just recently, I’ve been learning number theory and NTT butterflies because I wanted to understand post-quantum cryptography.

I still want to learn reverse engineering properly.

I want to understand operating systems from the inside out.

I still have that stupid driving simulator idea.

And there’s a part of me that wants to forget entrepreneurship entirely and become a really good security researcher or engineer.

Another part of me wants to make the company work.

And another part just wants some financial stability and a normal fucking life.

I think this is where I’ve been going wrong.

For almost ten years, whenever I didn’t know what to do, I learned something new.

And whenever I encountered a problem, I built something.

That’s worked surprisingly well for learning engineering.

But I’m starting to suspect it’s a terrible way to run a business.

I’m not a genius. I’ve abandoned projects, overestimated my abilities, written awful code, wasted money, and confused working hard with making progress.

I genuinely love programming. I don’t think AI is going to kill it. That’s not really what scares me.

What scares me is spending another ten years getting better at things without figuring out what actually matters.

So, to the engineers who’ve been doing this longer than me, and especially those who became business owners:

What the fuck would you do in my position?

Stop building and learn how to sell?

Find a stable engineering job and keep the company on the side?

Forget SaaS and go deep into cybersecurity, systems engineering, or research?

Or am I just using my curiosity as an excuse to avoid committing to something?

I don’t need motivation. I need perspective from people who’ve actually been there.

Because I can figure out how to make a computer do almost anything.

Apparently, figuring out what I should do with my own life is a little harder.


r/softwareengineer • • 2d ago

How are you maintaining your codebases

2 Upvotes

Hello, with AI writing most the code now I’m curious as to how teams are maintaining their codebases, or whether they are at all.

I imagine there is a distribution of experiences here, to teams pushing code with no review to those who aren’t using AI at all.

Would appreciate advice on methods or processes teams are adopting to keep their codebases maintainable and healthy? Anything particularly effective?

Thanks!


r/softwareengineer • • 2d ago

What to do after being laid off??

7 Upvotes

As the title says


r/softwareengineer • • 2d ago

10+ years as a developer, not senior yet, want to become a solution architect. What would you do and focus on?

2 Upvotes

I'm a developer with 10+ years of experience in java and spring. I'm officially still mid-level. On nearly every project, an enterprise architect made the design decisions and I implemented within strict guidelines.

For about 10 years I had the wrong focus in my job. I measured myself on output ("did I build it?") and rarely asked why something needed to exist. I want to grow into a hands-on solution architect, but I don't get design responsibility at work yet, and I can't show anything concrete.

I can spend about 30 minutes per working day at home.

If you were in my position:

  1. What would you focus on first?
  2. What would you do at home to prepare and improve?
  3. What would you do at work to get closer to design responsibility?
  4. What would you skip?

r/softwareengineer • • 2d ago

Scope of work changed aggressively. Having serious trouble keeping the ball rolling. How to handle a new project that has nothing to do with your prior experience?

4 Upvotes

A few months ago, the project I was working on eliminated several positions, including mine. Instead of letting me go right away, management kept me on for a few weeks to see if I could move to another project, since my feedback had been very positive. They found one for me, and I've been working on it ever since.

The problem is that this job has nothing to do with what I'm used to. There is no coding at all, and not because Claude is doing it for me. We do analytics, tweak configs, investigate logs, and handle a few other things. At first glance, it looks easy, but it isn't. The project is huge, at a scale I've never worked with before, and navigating our systems and integrations feels like walking through a maze blindfolded. The team offers little to no support, so I'm essentially on my own.

I'm close to 8 years of experience. In that time, I've been through stack changes and framework upgrades, switched back and forth between frontend and backend, worked with difficult teams where communication was unclear, led some initiatives, and helped enable others. I'm far from a tech genius, but I like to think I'm quite competent at what I do. This experience is making me question my entire career.

Every day I start my computer at 9:00 AM with no idea what to do. I second-guess myself constantly, because the complexity is so immense that working out what's happening on my own is almost impossible. I've considered stepping back to study the existing systems before touching anything, but then the backlog grows, and peer pressure pushes me to keep assigning tickets to myself.

I think what shocks me most is the situation itself. Never in my career have I been this clueless about what to do. I've faced hard problems before, and the solutions weren't always obvious, but I always had some direction or an idea of what to try next. The feeling that I can no longer perform at the level I've sustained for almost a decade is eating me alive. Right now, all I do is try to get something done while waiting for my manager to call me into a "you're fired" meeting. I've thought about quitting, but the job market is so bad that it doesn't seem like a good move.

I don't even know if this post makes sense, but I have no one to vent to, and I'm completely lost on how to get out of this situation. Has anyone faced such a drastic change of scope? How do I navigate it? At the moment, all I can think of is quitting or eventually being fired for low performance.

in


r/softwareengineer • • 2d ago

I think we can find that old software feeling again

7 Upvotes

I've been working in ML / DS and software for about 10 years and I'm noticing that the sentiment around a lot of other engineers is incredibly bleak. I obviously understand why. There are so many posts that talk about people just being an AI reviewer now and feel like the job is not fun anymore. Of course that job isn't fun anymore.

But I think that there are people that are missing the bigger picture.

We love writing software because of what it allows us to build. Not the final product, but all the small intricate pieces. Like a high end Swiss watch. It is solving a big puzzle of how put together the components. How to make it more efficient, run faster, be more accurate. The battles with compilers on why something won't work. Non-engineers don't have to deal with the stress of wondering why something isn't working. My wife used to call it “coding eyes” when I would be talking to her, but she could see as she way trying to talk to me, I was really going through the entire program in my brain to figure out why my app wasn’t working.

That’s what we love: the agony of it all. We’re not happy people! We’re addicted to the struggle. It consumes our lives. Nothing worked, and that’s why it felt so good when you succeeded.

I don't have coding eyes anymore, but I am thinking differently about careers in software engineering now. We need a new dopamine hit. It would be like if we were the only person in a town 200 years ago who's job it was at making fire. Then someone comes along and introduces us to matches, but we're going on and on about how striking a match isn't as fulfilling as drawing smoke from rubbing sticks together.

The value we used to place on ourselves was the separation between people and their idea. We were the ones that could build it, and now that space has been flattened by AI. But that value is incorrect in the first place. There are so many skills that we learned from building software that a lot of others haven't endured. We're the real problem solvers here, and there are still a million problems out there that don't need

We might have to focus more on the part that we avoided for so long...the people using our tech.

Let's say that technology is now as easy as snapping your fingers (we all know it's not there yet, but maybe one day). There is no gained value by saying you can build an app. However, we're now entering a time where marketing and sales are going to be more important than ever.

LLM's proved that software is really just math in gibberish form. It's solvable. It's can be calculated by algorithms. It was really difficult and time consuming in the past, which is exactly what still 99% of the worlds problems are. This is like saying now that we have LLMs, politics will be solved. That's nowhere near being true tomorrow, nor do I think it will be that way in another 10 years. The real world problems are really difficult to solve, who do you think is best poised to solve them now that they have some more free time on their hands?

All of us that spent so much time and energy practicing and learning the skills to write software learned the actually valuable skills that a lot of the world hasn't had to do yet, which is persistence. By the way, that is not a very easy skill to learn either. That takes years, and we already have a HUGE head start.

I think we are getting to the next chapter in the software engineer stage. Maybe our titles will be completely different, maybe we won't be working in consoles and instead using MCPs, maybe we won't need to do PRs or study for technical exams, but at the end of the day we're still all going to be working on hard problems that will hopefully give us the same rush as it did when we were doing the late night coding sessions.

I'm looking for the new dopamine hit. I hope you find yours too.


r/softwareengineer • • 2d ago

No deployments on Fridays. Smart practice or outdated thinking?

0 Upvotes

I’ve worked with teams where Friday deployments were basically forbidden. The reasoning was simple: nobody wants to spend their Friday evening or weekend fixing something that broke in production.
But with modern CI/CD pipelines, automated testing, feature flags, and rollback mechanisms, I’m wondering if this rule is becoming outdated.
Personally, I think it depends more on how mature your deployment process is than what day of the week it is.
Still, there’s something nice about having a peaceful Friday. 😄
Curious how other engineering teams handle this.
Do you still follow the “no Friday deployments” rule, or do you deploy whenever something is ready?
And has anyone actually regretted removing that restriction?


r/softwareengineer • • 2d ago

What Does a Day in the Life of a Real AI Engineer Look Like?

1 Upvotes

What does a real AI Engineer do in a company every day?


r/softwareengineer • • 3d ago

PIP - help around the process.

6 Upvotes

I have been a software developer for over 28 years and have been issued a PIP. The company is a private company with around 300 people.

I am competent staff engineer, my manager is not technical. Thanks to Claude the leadership wants employees to 10x and that was fine with me as I enjoyed working etc. My manager was losing it as now he had responsibilities that he needed to be accountable for. Being the lead he kept pushing everything on me and I was fine if it was technology related. I however needed him to make decisions for cross team asks and decisions for say releases and going to the CAB meeting.

I just asked him, "hey manager who do you suggest". He went on a DM and instead of responding bullied me into my expectations etc. I wasn't ready to put with the crap as he was being unstable and asked him that I needed help in cross team coordination and project decisions.

He didn't respond to any updates after that and he today on my 1:1 put me on pip. I have a timeline based on slack chats about what all I did etc.

The improvement listed is totally subjective and has nothing concrete. Can I ask him to make the pip objective? Looks like there is no way to get out of it as he has used vague goals.

Appreciate any pointers, I am the only working person in my family and my wife is disabled and a teenage kid who just started highschool. This really affects me, I am trying to start looking elsewhere too but this market sucks.


r/softwareengineer • • 3d ago

Felon trying to become a software engineer again.

7 Upvotes

Hey guys! I am currently 25 and just finished up my prison bid for wire fraud. I know I am at fault here but I wanted to ask is there a way to still become a software engineer again?

I have a computer science degree and also have worked as an engineer. Would like to get back on track, relearn, regrind leetcode, but wanted to see if there was any advice for me.


r/softwareengineer • • 4d ago

Any real software architecture courses?

4 Upvotes

I've been looking for a real software architecture or system design course online, but all I see are courses made by people who aren't even active architects, or who barely made it in tech and rely on online courses to survive. Almost all of them are so repetitive that all of their course outlines are the same. Talking about the basic stuff and clearly do not have any experience on such kind of things.

Anyone here who has found an ACTUAL software architecture or system design course that actually talks about the techy stuff, not just the shallow stuff that you barely can't use at an enterprise level?

I mean something real I can apply at work, because I am having a hard time keeping up with architectural decisions/talks during meetings, and I want to supplement my skills or my knowledge in it. Would appreciate it a lot!


r/softwareengineer • • 3d ago

Did somebody read Latency, by Pekka Enberg

1 Upvotes

I want honest reviews about this book. I saw some guys saying that the book is incorrect/inaccurate on some technical concepts, so some feedback could be really nice.


r/softwareengineer • • 3d ago

Implicitly converting from double to decimal

1 Upvotes

Hi Guys, maybe you can relate or even help:

I‘ve been developing in vb.net (.net 8 still) for years now - and I know vb is fucked and .net8 is out of support, next year I‘m going to migrate to C# on .net10 (legacy code) - and it was always possible to declare a variable as decimal and implicitly initialize a double value ( like Dim var as Decimal = 1.5).

This has worked since I‘ve been on the project.
Now, last week I switched to VS2026, and from then on this wasn‘t possible anymore.

For the example above, the value of var would be something like 1.49999889789.

Funny thing is, It still works the old way for my coworker - same Ide, same sdk

Has anyone an explanation for said behaviour or, even better, knows if/how I can get back to the way I‘m used to?

I would really appreciate it.

It‘s a Winforms Application for Windows by the way.