Hello Reddit community!

I'm an entrepreneur from Cameroon, and I'm currently looking for talented and passionate software developers, programmers, and technical co-founders who would be interested in joining me to build an exciting new technology project called WeGoApp.

I have a vision for this application and have been working on developing the concept, its features, and its overall business direction. However, I am now looking for the right technical people who can help turn this idea into a real, functional application.

Who am I looking for?

• Mobile app developers (Android and iOS).

• Full-stack developers.

• Backend and frontend engineers.

• UI/UX designers.

• Software architects.

• Experienced programmers who enjoy building products from the ground up.

What I'm looking for:

I'm interested in meeting serious, creative, committed people who want to work on an ambitious project and potentially grow with it.

Whether you're an experienced developer or a talented programmer looking for an interesting opportunity, I'd love to hear from you.

A few things about the project:

• Project name: WeGoApp.

• Location: Cameroon, with ambitions to reach international markets.

• Current stage: Idea and planning stage.

• Looking for: Developers, programmers, and potential technical co-founders.

I'm open to discussing different collaboration arrangements, including partnerships and compensation structures.

If you're interested, please comment below or send me a private message. Tell me about your experience, the technologies you work with, and any projects you've built.

Let's connect, discuss the vision, and see what we can build together!

Thank you!

Hey everyone!

I'm looking for ideas for my next open-source project, and instead of building something based on my own assumptions, I'd rather hear directly from other developers.

What's something that genuinely frustrates you during your development workflow?

It could be anything:

• A repetitive task you wish could be automated.

• A tool that exists but is unnecessarily complicated.

• Something missing from your current development workflow.

• A problem with debugging, testing, deployment, or monitoring.

• A CLI utility or library you wish existed.

• An annoying limitation in tools or technologies you regularly use.

It doesn't have to be a groundbreaking idea. Even a small, specific annoyance is worth discussing.

Here's what I have in mind:

I'll go through the suggestions, look for problems that are worth solving, pick one (or a few), build a working prototype, and release it publicly on GitHub so others can try it, use it, and hopefully contribute.

I'm particularly interested in problems that other developers experience too, rather than something useful to just one person.

I'd love to hear:

1. What is the problem?

2. How do you currently deal with it?

3. What would your ideal solution look like?

Feel free to share even the smallest frustrations. You never know which one might turn into a useful open-source tool.

Thanks!

Any student coder in Miami area looking to work together? I’m not an experienced coder, but have extensive government experience. I’m specifically interested in projects at the intersection of AI and government, but open to things outside of that. Send me a dm with what you’re working on and what roadblocks you’re facing/what assets you need to overcome it. I’m in it for the love of the game and learning more. This doesn’t have to be the next great startup. Even some sort of open-source resource for everyday people would be great.

A thing I’ve noticed (and I think it applies to human reviewers as much as AI ones): style opinions often get phrased as problems. “This function is too long.” “Consider a more descriptive name.” “Prefer composition here.” Sometimes they’re right. Often they’re just the reviewer’s default taste, which may not match what your team has agreed on.

The test I’d use: is there something outside the reviewer’s head that backs the comment? A linter rule, a style guide, a past decision in the repo, a bug that this pattern caused before. If nothing does, it’s an opinion. Opinions are allowed, but I think they should be labeled as such, shouldn’t block a merge, and shouldn’t crowd out the comments that matter.

It seems to matter more with AI reviewers, because every comment arrives in the same confident voice. A naming nitpick and a claim about a concurrency bug sound equally sure, and fluency isn’t evidence. With a human, you calibrate by knowing who they are and how often they’ve been right. With a tool, you have to do that sorting yourself.

Where it gets hard: sometimes a “taste” comment is pointing at a real maintainability problem, and a team without written conventions has no way to settle it. And over-policing taste has a cost too, because it can make reviews feel adversarial.

This is one of five kinds of “sounds right, isn’t anchored” AI review comments I wrote about. I’m the author, and the article also mentions a paid playbook of mine near the end, so the link is optional: https://medium.com/@nagatomopedro05/five-kinds-of-ai-code-review-comments-that-sound-right-and-arent-0d02b3fb9ec6

How do you handle it in your team: written conventions, a “nit:” prefix, or just judgment in the moment?

Hi guys, I’m 25 years old and recently discovered that I liked programming by programming some small games and small projects. I did some research about some good programmers and they pretty much did some discrete math which enhanced their thinking and problem solving skill. My goal is to become a really good programmer which means having the skill of solving problems and apply the method (algorithm) in a programming language. So I decided to start learning discrete math with the book: Discrete mathematics and its applications. How long does it take to learn the concepts and be good at it? (I have 6h per day of free time). Any advice or method on how to learn the subjects with the goal in mind that I will learn those subjects only to help me be good in programming? I don’t have any teachers so any advice on how to use AI? Or any forum to share my thoughts with? Thanks for the help!

I'm part of the team behind ALGO Skills, an early-stage practice platform. Instead of isolated exercises, you implement simplified versions of real systems (a Unix shell, HTTP server, rate limiter, key-value store, up to a Raft consensus model) and handle edge cases and failure, like what a rate limiter does on request 1,001.

It's early and I'm not claiming it's finished or proven. I'm looking for a few people who want to try it and tell me honestly:

where you got stuck or confused

whether the challenges teach what they claim to

what you'd change or drop

Ideal testers: students, recent grads or early-career engineers who are comfortable coding and willing to attempt a few challenges, not just browse.

Early access is free and by request: ALGO

If you'd rather not sign up, comment with what you'd want from a platform like this, which helps too.

Is it possible to get a job in AI/ML without having a background in backend and working a backend job?

I really like AI/ML BUT I didn’t work in backend or fullstack just internships, can I get an internship or a job opportunity, or do I need masters?

Thank you all

So I am a college student we are learning JavaScript and making websites and applications. I’m ok with understanding individual lines and going piece by piece and understanding a script. But when it comes to understanding architecture I get confused and lost so easy. I don’t know what to study to become better at understanding the architecture of projects?

Currently working as a fullstack developer ( 2.5 YOE) , but since the start i have felt coding to be boring and with the rise of AI scared as well.

So i was thinking to learn about hardware a little about ESP32, Raspberry , do some handful of projects in my freetime. But how difficult woll kt be to switch from a pure software to a little bit about hardware and maybe change career as well.

As for my background I am a Computer Engineer graduate.

Looking for programmers

Everyone talks about becoming a software engineer, learning programming languages, mastering frameworks, building projects, and landing that first job.

But I think we don't talk enough about the hardest part: Taking the first step.

For someone starting today, the journey can feel overwhelming.

You open YouTube and find hundreds of programming tutorials. You explore GitHub and see projects that look impossibly complicated. You visit LinkedIn and see people announcing new jobs, promotions, and achievements. Then you open Reddit and read posts from developers worried about layoffs, AI replacing jobs, and an uncertain future.

Eventually, you start asking yourself:

• Am I learning the right programming language?

• Is it too late to enter the software industry?

• Should I learn web development, mobile development, AI, or something else?

• How much do I need to know before applying for my first job?

• What if I spend years learning and still cannot get hired?

• How do I compete with people who already have years of experience?

And perhaps the most dangerous question:

What if I'm simply not good enough to become a software engineer?

Here's what I believe: Nobody starts as an experienced developer. Every senior engineer once struggled with their first variable, their first error message, their first project, and their first technical interview.

The industry is changing. AI is changing how we write software. Expectations are changing. Competition is real.

But the ability to identify problems, think logically, understand systems, make decisions, and build useful solutions is still incredibly important.

We shouldn't pretend the journey is easy, but we also shouldn't convince beginners that the door is already closed.

I'd love to hear from this community:

For beginners:

1. What is stopping you from taking your first step?

2. Are you confused about what to learn because there are too many technologies?

3. What is your biggest fear about entering the software industry?

For experienced developers:
4. Looking back, what was the most important decision you made at the beginning of your career?
5. What would you tell someone who is starting from absolute zero in 2026?
6. If you could start again, what would you learn first, and what would you completely ignore?

For people who recently landed their first developer job:
7. What actually helped you get hired?
8. What did you waste time learning that wasn't as important as you initially thought?

One final question:

If you could give just ONE piece of advice to someone who wants to become a software engineer but is afraid to take the first step, what would it be?

Let's make this thread useful for the next generation of developers.

Not everyone here needs motivation. Some people need direction, some need honest advice, and some just need to know they're not alone in this journey.

Let's help each other take that first step.

So I've been thinking of kinda posting around on social media about tech, maybe blogs if that works well. Now usually the common options, Youtube and Instagram are way too crowded and difficult to get discovered.

So i was curious, what social media or blogging platforms do y'all use to read about tech?

substack? x? reddit even? Let me know

and if you're someone who already does content creation, blogs, tutorials, something else, maybe we could connect

I have actually spent last 6 months of unemployment under depressive rage on studying all this shit.

So i would love to share my take here:

We are actually observing a converging of software right now.

Software as you see come in 3 layers as far as i have seen:

1. The CRUDs - This one is basically cooked with AI, if you are playing here you are competing with LLMs. Here, 1 developer or 2 just get things done now with swarms. Surely, you will come with your "but hey hey look at that vibe coder's web token was stolen & he forgot to secure his file serving endpoint" and give yourself some hope but market doesnt give a shi.

2. The INFRAs - Spark, VMwares, Kubernetes, Databases, OS, Languages - their development is largely going to be solved by LLMs and is somewhat already working. The Operational layer of these is still requires human & will require humans as here you require accountability which requires experience of fucking around with these systems.

3. The HardTech - Defense, Research & Robotics(i dont know much about these to comment about it tbh but what i studied it seems they use programming languages that LLMs dont get to train on easily)

I believe all CRUD softwares are going to be just chatbox something like hark or muse or grokbot.

The startups that are building "niche harness" are going to fail. They are funded by Y comb to boost application layer for so called Big AI valuation justification upon IPO, Great correction is going to happen.

Winners will be spacexai, meta & google.

The Infra layer will still require people, but ofcourse barrier to entry will be high, and with HardTech much higher.

We are nowhere for robotics btw, so physical skills are still open for next 20 years until big guys find a way to solve for energy without it robotics at scale is impossible.

So, to sum up guys the river is drying, take your boats out & run to some other river

Hey everyone,

I'm 18, finished 12th grade with only basic coding knowledge (Python/SQL Basic level school stuff). I am currently enrolled in Computer Science and want to eventually land roles in

Al/ML or cybersecurity.

I don't want to be the person who only knows how to use ChatGPT

I want to become genuinely skilled, understand the fundamentals deeply, and be competitive for jobs.

Looking for practical advice on:

How to structure the next 1-2 years of learning

Best order of topics for someone starting almost from scratch

How to "break the Al bubble" i.e., use Al as a tool without becoming dependent and still build real competence

Concrete projects, resources, platforms, certs, or habits that actually matter for Al/ML vs cybersecurity paths

Realistic timeline and what entry-level / internship roles look like right now

Any honest advice, roadmaps, mistakes to avoid, or personal stories appreciated. Thanks!

Something interesting is happening in the developer community.

I'm seeing more and more developers expressing hopelessness about their future. Experienced engineers are questioning their careers. Junior developers are wondering whether learning to code is still worth it. People who spent years mastering programming languages, frameworks, algorithms, and software architecture are suddenly questioning the value of their skills.

And honestly, I think we need to have a deeper conversation about this.

Let's put the AI hype aside for a moment.

The real question isn't whether AI can write code. It clearly can, and it's getting better.

The real question is:

If writing code becomes increasingly cheap, what makes a developer valuable?

For decades, programming was largely about translating human intentions into instructions that machines could execute. We learned languages, mastered frameworks, understood architectures, debugged complicated systems, and built things that previously seemed impossible.

But perhaps we're approaching a world where producing code is no longer the biggest challenge.

Maybe the scarce skills of tomorrow will be:

• Understanding problems that nobody has clearly defined.

• Knowing what should be built, not just how to build it.

• Designing reliable systems rather than simply generating code.

• Understanding users, businesses, security, and real-world consequences.

• Making good technical decisions when AI gives us ten possible solutions.

• Taking responsibility for systems that must actually work.

However, I don't want to romanticize this transition.

There are real concerns:

• What happens to junior developers who need experience to become senior engineers?

• How will new developers enter an industry that increasingly expects them to be productive from day one?

• Will companies use AI to empower engineers or simply reduce engineering teams?

• What happens to people whose livelihoods depend on skills that are becoming automated?

• Will software engineering become more accessible, or will opportunities become concentrated among fewer people?

These aren't imaginary problems. They deserve honest discussion.

But I want to ask something beyond the usual AI-versus-developers debate.

Perhaps the biggest risk isn't that AI will replace developers. Perhaps it's that developers will continue preparing for a future that no longer exists.

If you were starting your developer journey today, knowing everything you know about the current direction of technology, what would you do differently?

Would you still spend years mastering programming languages? Would you focus on systems engineering, AI, product development, cybersecurity, entrepreneurship, or something completely different?

And for experienced developers: What do you believe will distinguish a genuinely valuable engineer from someone who simply knows how to produce code?

I'd love to hear real experiences, uncomfortable opinions, disagreements, and predictions.

Let's have a conversation that goes beyond saying "AI won't replace developers" or "developers are doomed."

The future of software engineering is being rewritten. Instead of only worrying about whether we belong in it, perhaps we should start discussing what we want our profession to become.

Hey everyone,

I built an e-commerce platform solo with Next.js, Supabase, Redis (for real-time stock reservations and rate limiting), and Razorpay: https://newtownbay.com/

Or https://www.newtownbay.in

I’d appreciate technical critique on:

• Client-side bundle responsiveness and Core Web Vitals

• Cart drawer and inventory hold mechanism

• Error handling and edge-case behavior across the checkout flow

If you spot bugs, console errors, or performance bottlenecks, you can report them using the floating "Feedback" button in the bottom right corner (or leave a comment here).

Thanks for checking it out!

I'm currently studying AI-powered full stack development, with a particular focus on understanding business workflows before introducing automation.

One principle I'm exploring is that automating an inefficient process doesn't necessarily improve it. Sometimes, it simply makes the inefficiency happen faster.

Before selecting an automation tool, I'm learning to map workflows using five elements:

1. Trigger: What initiates the process?

2. Steps: What activities are performed?

3. Decisions: Where are choices or approvals required?

4. Handoffs: Where does responsibility move between people or systems?

5. Output: What result should the process produce?

My thinking is that once these elements are clear, it becomes easier to identify unnecessary steps, simplify the workflow, and determine which repetitive, rule-based tasks are worth automating.

However, I'm interested in understanding how this approach works in real business environments.

For developers, automation specialists, and business consultants:

Is this five-part framework a practical starting point, or do you use a different method?

What important elements am I overlooking?

And when evaluating a small business for automation, what's the first thing you examine before recommending a solution?

I'd appreciate practical examples, alternative frameworks, and lessons learned from real projects.

My goal is to develop a problem-first approach grounded in trustworthiness, accountability, and continuous growth.

Solving complex logic puzzles, understanding system architecture, and writing clean code is satisfying. Today most devs relies on AI, its fast and helpful but I think It is not that good in terms of dopamine shot on every blocker that you solved.

Or am I just aging -_-

Hey everyone!
I’m a student who enjoys programming, and I’ve been working on a personal project called WasmStudio.
The idea came from wanting a simple way to write and run code directly in a browser, without having to install a traditional IDE every time.
So I decided to build one myself!
What it currently supports:
C
C++
Python
Java
A built-in code editor and output panel
It’s still a work in progress, and I’m constantly trying to improve it.
I’d genuinely appreciate some feedback:
What do you think of the interface?
What features would you add?
Would you actually use something like this for learning or quick coding?
This is one of my personal projects, and I’d love to hear honest opinions, including criticism.
I’ll share the project link in the comments if anyone wants to check it out.
Thanks for reading!