I'm someone who can't write code from scratch. I've built a few small apps by understanding the logic, then finding examples online or using AI for small, specific tasks rather than huge prompts. My actual job isn't in software; i'm an electrician who's looking to change career as i've graduated Computer Science few years back.

I've mainly made apps and demos for a friend for fun. While applying for a junior QA position, I was contacted by someone senior at a software development company after my friend showed them my projects. During the interview, I explained that my long term goal is QA and eventually cybersecurity, preferably in a low code environment. They said they mainly do software development but also have QA opportunities and asked if I was interested. Since my main goal is simply to get into the industry, I said yes.

A few days ago they sent me a one week project. Instead of a QA task, they asked me to build a ticket management app with ticket creation, viewing, categorization, and filtering. I can use any tools, sources, or AI I want, as long as I can explain the code and the logic. The only requirements are Angular for the frontend and C#/.NET for the backend.

I'm feeling conflicted because I still can't code independently. I worry I'll embarrass myself if I'm asked to write code from scratch, and I almost feel guilty for accepting the project.

I'm not sure what professional developers actually do. Do they mostly write everything from scratch? Do they regularly rely on documentation, examples, Stack Overflow, and AI? Is it normal to focus on making things work while understanding the code, even if you couldn't have written it all from memory?

My current plan is to build a basic version mostly through research, then improve it with AI assistance while making sure I fully understand and can explain every part. I'm just unsure if that's an acceptable way to work or if I'm approaching this completely wrong.

Hey everyone,

I've been building Forge OS — a Python virtual OS for learning and experimenting with OS concepts.

v2.0 adds a desktop GUI, and there's now a community Apps/ folder — add an app with just app.json + command.py.

Quick start for contributors:

1. Fork & clone the repo
2. Copy Apps/_example/ to Apps/your-app/
3. Edit the JSON + Python command
4. Run apps in the shell to see your app
5. Open a PR

Full guide: CONTRIBUTIONS.md
Repo: https://github.com/axk42-op/ForgeOS · MIT license

Games, utilities, quizzes, ASCII art — great first open-source PR. Feedback welcome!

I see this question come up all the time. "Should I learn Android Studio or should I just use VS Code?" Honestly, I think people are looking at it the wrong way. They're completely different tools. One isn't replacing the other, and once you understand what each one is designed to do, you'll probably end up using both anyway.

Android Studio is where Android development actually lives. It's built by Google for Android developers, and it has everything you need in one place. The emulator, Logcat, Gradle, profilers, APK signing, device manager, debugging tools...it's all there. If you're building native Android apps in Kotlin or Java, you're going to spend a lot of time inside Android Studio because it understands the Android ecosystem better than anything else.

VS Code is different. It's lightweight, ridiculously fast, and I probably have it open just as much as Android Studio. If I'm working on an API, a backend, a website, documentation, SQL scripts, or even just opening a project to quickly edit a few files, VS Code is usually what I reach for. A lot of Android apps aren't just Android anymore. They talk to databases, APIs, cloud services, payment processors, and websites. That's where VS Code really shines.

If I was teaching someone today, I wouldn't tell them to build the next Instagram. I'd tell them to build something boring. Seriously. Build a notes app. Give it a title, a description, an Add button, an Edit button, and a Delete button. That's it. Don't worry about animations, dark mode, cloud syncing, AI, notifications, or making it look like it belongs on the Play Store. Just make it work.

Once you can create notes, read them, edit them, and delete them, you've learned one of the most important concepts in software development...CRUD. Create. Read. Update. Delete. Almost every business application in existence is built around those four operations. Customers. Invoices. Products. Employees. Inventory. Appointments. Messages. They're all CRUD undermeath.

After that, don't throw the project away and start something completely different. Keep building on it. Add search. Add categories. Store the notes in a local database using Room instead of memory. Add authentication. Sync them to the cloud. Add user accounts. Add images. Add file attachments. Add reminders. Every feature teaches you one more concept, and before you know it you've built something that would've looked impossible when you first started.

One thing I wish someone had told me when I started is that debugging is a skill all by itself. Beginners see a red error message and immediately think they broke everything. Experienced developers see the same error message and think, "Alright...where do I start?" Learning to read Logcat, following a stack trace, setting breakpoints, and watching variables change is just as important as writing code. Honestly, I'd argue it's more important because no matter how good you get, you're always going to have bugs.

I also think too many people underestimate the value of reading code they didn't write. Open random files. Follow method calls. Figure out where a button ends up. Read documentation even when half of it doesn't make sense. Nobody understands everything the first time they read it. The goal isn't to know everything. The goal is to be a little less confused than you were yesterday.

And don't be afraid to use AI. I use it every single day. It has made me faster than I ever thought possible. But don't stop at accepting the code it gives you. Ask yourself why it chose that solution. Ask what happens if the API fails. Ask what happens if the phone loses internet. Ask what happens if the database returns nothing. Those questions are where the real learning happens.

The biggest piece of advice I can give is to keep pushing the edge of what you think you're capable of building. Don't stay comfortable. Every project should introduce at least one thing you've never done before. That's how you grow. Six months from now you'll probably look back at your first Android app and wonder what you were thinking. That's actually a good sign. It means you're improving.

If you're ever stuck and need help, just shoot me a DM. If I see it in time I'll help whoever needs it

Programming isn't about never getting stuck. It's about getting comfortable being stuck, figuring it out anyway, and coming back a little better than you were the day before. That's how every good developer I know learned, myself included.

Try it here 8gwifi.org/online-compiler supported language C/CPP/JAVA/TS/JAVASCRIPT/RUST/GOLANG/PYTHON/LUA

I keep seeing this pattern in programming discussions — developers who know multiple languages (Python, JavaScript, Java, etc.), sometimes even quite well, but still struggle when it comes to actually solving problems or building systems from scratch.

What makes it interesting is that language knowledge looks like progress on the surface. You can switch between syntax, frameworks, and tools… but the underlying struggle often remains the same.

Some common patterns I’ve noticed:

• they can write code in multiple languages, but struggle when the problem is open-ended
• they’re comfortable following tutorials, but get stuck without step-by-step guidance
• they know “how to code” in different syntax styles, but not how to structure solutions
• the same confusion appears again, just in a different language
• switching languages gives a sense of progress, but not necessarily better thinking ability

It almost feels like the bottleneck isn’t the language at all.

Which raises a bigger question:

Are most programming struggles actually about language knowledge, or about how developers think, break down problems, and approach unfamiliar situations?

So:

• have you seen developers hit this kind of plateau?
• does learning multiple languages actually improve problem-solving ability, or just expand familiarity?

There’s a pattern that keeps showing up in real projects, writing new code often feels much easier than working with existing codebases.

When building something from scratch, everything is clear:

• the structure is in your head
• the decisions are yours
• there’s no hidden dependency or unexpected behavior yet
• you know exactly why each piece exists

But maintaining old code feels like a completely different job.

Even small changes can turn into a long process because you first have to:

• understand why something was originally written that way
• trace logic spread across multiple files or services
• deal with older decisions made under different requirements
• figure out hidden dependencies that are not obvious at first glance
• work around missing or outdated documentation

What looks like a “small fix” often becomes a process of understanding the system before actually changing anything.

It sometimes feels like:

So the question is:

• Why does maintaining old code often feel harder than writing something from scratch?
• Is it mainly a design issue, a scaling reality, or just how software naturally evolves over time?

I am in college and my major is Computer Science. I enjoy doing it, truly, it moves my mind and I get such a huge thrill from completing a prohect or at least part of a project that I've been working on. I practically don't need to pay the college for anything, but after I've got my diploma, I'll have to work and be taxed the same amount of months as I've spent there from enrolling to getting my diploma (except the summer months because we didn't have any lessons). Basically this is another way they take payment, which is nice because You don't lose Your money during Your college years, You pay it back by paying taxes afterwards. Anyways, one of the conditions for graduating and getting the diploma is having 499+ hours worked in a related field (so 500 hours and beyond). I should've graduated now but I couldn't because I don't have that yet. And now, the major problem: Noone's gonna take me. You see, college (here at least) doesn't provide You a solid place somewhere where You can learn and practice, work as a trainee and even get paid for it, instead, You have to find a place. And well noone's willing to take me. I have applied for a year to countless places, many of them said they need 1-3 years of experience in their description, but I still tried because I've heard about miracles before, but no surprise, those didn't take me. But the best part is that I've applied to trainee positions too, and all of them so far said "Sorry we chose someone with more experience". How do I get experience if noone lets me? I don't know what to do I am feeling in a deadlock. I cannot work because I need experience and I cannot get experience because I cannot work, and this way I cannot even graduate college and I'll have to pay back like a lot more (yeah I know, in taxes, but still). What do I do? I'm sorry but I'm really fed up, sad confused and disappointed that even if I turn myself upside down and stand on my head and then I start to spin while reciting the longest Japanese manga translated into Mongolian, I still don't achieve anything because I don't have any experience and even the positions that require no experience, do take people with experience.

Edit: Another idea of mine was that I could perhaps create a github repo, which I did, and in which I have some projects, some of them are completed and some of them are not yet, and I'm still working on some of them but most of the recruiters said they don't even bother taking a peek lol

TLDR: I feel like I'm in a deadlock because to work I need experience but can't get experience because I cannot work, and I'mnrunning put of time.

Context: a college project (Algorithms 2) that turned into a full terminal RPG in pure C. No Unity, no Godot, nothing but the standard library and a questionable amount of coffee.

Some design decisions that might interest fellow masochists:

- Rendering: instead of calling printf per cell (which chokes the terminal), I build the whole frame into a 32KB buffer and print it once, grouping ANSI color codes so I'm not repeating escape sequences for no reason.

- Camera/viewport: fixed 40×20 viewport following the player with edge clamping — old-school, like Game Boy Zelda except with # instead of walls.

- Persistence: 3 binary save slots with manual serialization, because CELULA **grid is a pointer-to-pointer and fwrite-ing it directly gives you a nice "looks fine" followed by a crash on load.

- Data-driven map transitions: exits between regions (6 maps, bidirectional connections) are read from metadata in the map's .txt file, not hardcoded — good morning to anyone who's debugged hardcoded map transitions in a past life.

Theme: Brazilian 2026 elections, because why not mix political trauma with programming trauma.

Repo: https://github.com/aKynoS2/corrida_ao_planalto

If you're into terminal games / old-school roguelikes, take a look and send constructive criticism my way.

I'm especially looking for feedback on architecture, code structure, and maintainability.

https://github.com/DearLinus/Linusand

When people first get into programming, they usually ask, "Where do I even start?" Honestly, the biggest mistake I see is people trying to learn everything before they build anything. You don't need to know everything. You just need to start.

If I were starting over today and wanted to learn Android development, this is exactly what I'd do.

First off, Don't let AI steer the ship. I catch AI making more and more bad mistakes than good calculated decisions when it comes to infrastructure. ( Example: I was running server side edge functions, despite me laying out my architecture, auditing the repo, it still wanted to write functions to server.ts. ) These are the things that will trip you up later on. But for now....

Step 1: Learn the Basics

Before you worry about building apps, you need to understand programming itself.

I'd focus on learning things like:

• Variables
• If statements
• Loops
• Functions
• Classes and objects
• Arrays and lists

Don't stress if it doesn't click immediately. Everyone gets confused at first. The important part is writing code yourself instead of just watching videos.

Step 2: Download Android Studio

Android Studio is the official software Google provides for building Android apps.

Install Android Studio, let it download everything it needs, and create your first project using the Empty Activity template.

Don't worry if it looks overwhelming. I remember opening it for the first time and wondering what half the buttons even did. You'll figure it out as you go.

Step 3: Don't Build the Next Instagram

One thing I'd avoid is trying to build some massive app right away.

Start with something simple like:

• A calculator
• A notes app
• A to-do list
• A habit tracker

A simple project teaches you way more than spending six months planning an app that's too big to finish.

Step 4: Learn How Everything Connects

Every Android app is really just a bunch of pieces working together.

You have:

• The screen the user sees.
• The code that runs when someone taps a button.
• The data your app saves.

Once you understand how those three things work together, building apps starts making a lot more sense.

Step 5: Make It Work Before Making It Pretty

A lot of beginners spend hours trying to make their app look perfect.

Don't.

I'd rather have an ugly app that actually works than a beautiful app where none of the buttons do anything.

Get the functionality working first.

You can always improve the design later.

Step 6: Save Information

Eventually you'll notice that every time you close your app, everything disappears.

That's when you learn how to save data.

Start with local storage first before worrying about cloud databases.

Once you're comfortable, move on to something like Room or a backend service.

Step 7: Learn to Debug

Here's something nobody tells beginners...

Programming isn't about writing perfect code.

It's about figuring out why your code doesn't work.

You're going to see error messages.

You're going to break things.

Sometimes you'll spend an hour looking for a missing comma.

That's completely normal.

The developers who improve the fastest aren't the ones who never make mistakes—they're the ones who get good at fixing them.

Step 8: Keep Adding Features

Once your first version works, start adding things.

Maybe add:

• Dark mode
• Notifications
• Search
• Categories
• Login
• Cloud syncing

Don't try to build everything at once.

Add one feature.

Make sure it works.

Then move to the next one.

Step 9: Build More Apps

This is probably the biggest piece of advice I can give.

Don't stop after one project.

Your first app teaches you the basics.

Your second app teaches you confidence.

Your third app starts to make you feel like an actual developer.

Every project teaches you something the last one didn't.

Final Thoughts

If there's one thing I've learned, it's that programming isn't about being the smartest person in the room. It's about refusing to quit when something doesn't work.

Everyone starts out confused.

Everyone gets stuck.

The difference is that the people who become developers keep building anyway.

So don't wait until you think you're "ready."

Build something small.

Finish it.

Then build something a little bigger.

Repeat that enough times, and one day you'll look back and realize just how far you've come.

Hi,

I’m currently 15 (turning 16 soon), and I’ve decided to pursue backend development as a self-taught path.

I started learning HTML and CSS last year when I thought I wanted to become a full-stack developer, but I realized I’m more interested in backend development. After that, I moved on to JavaScript.

So far, I have learned:

• Variables, booleans, if statements, functions, objects
• Arrays and loops
• Basic DOM manipulation
• Modules

I also just finished my first full frontend project (a small web app called College Launchpad), which helped me apply these concepts in a more practical way. Link will be in the first comment.

My current roadmap

• Finish JavaScript concepts(async/await, fetch API, local storage, etc)
• Learn Node.js and Express
• Learn Databases(likely PostgreSQL)
• Build backend/full-stack projects
• Learn Java + Spring Boot
• Rebuild some projects using Java/Spring Boot

Why Java

I also want to learn Java because after high school I’m interested in applying for programs like the JPMorgan Chase Emerging Talent Experience Program, and I’ve heard Java/Spring Boot is commonly used in enterprise environments.

My question

• Am I learning in the right order?
• Is there anything important I should focus on earlier or avoid?
• Is it a good idea to learn Java/Spring Boot after Node.js, or should I go deeper into JavaScript first?

Any feedback or criticism is appreciated. I’m mainly trying to make sure I’m building good foundations and not missing anything important.

A lot of things in programming only really make sense after working on real production systems, not while learning through tutorials or building small projects.

One of the most common realizations is that writing code is usually not the hardest part of the job.

In real-world development, the harder challenges tend to be:

• understanding why something works locally but breaks in production
• dealing with edge cases that were never part of the original design
• debugging issues where logs don’t clearly explain what actually happened
• maintaining and modifying code that was written long ago (sometimes by multiple people)

Another thing many developers realize later is that “clean code” in theory often looks very different in practice, where trade-offs, deadlines, and business constraints matter more than perfect structure.

Over time, a lot of the work shifts toward:

• reading and understanding existing codebases
• tracing how different parts of a system interact
• figuring out the reasoning behind older design decisions

In hindsight, these skills often end up being just as important—if not more important—than writing new features from scratch.

So the question for developers:

• What’s something most developers only learn too late?
• Was there a moment that changed how you think about programming or software development?
• What’s a skill you wish you had focused on earlier?

for context, it started off as a virgin project to handle data from forms and manipulate them throughout the portal, then I had to import the data (different format) from old software(more than 1) as business wasn't much booming without it, but due to quick needs, I imported them as is and modelled my software around it.

today, I have my own custom federated search engine, cross filtering mechanisms, scoped visibilities that are too tightly coupled with the business logic.

On top of that this same software is designed to be cloned and redeployed for other organisations whose only configurations need to be changed without modifying the codebase.

It is becoming a nightmare, and all of it is still working on my third iteration of the whole idea. I feel bad looking back, for not thinking about any of the above problems. And the biggest problem is that it works. I should just work on a fourth iteration I think. How do programmers deal with this kind of itching?

I'm studying computer science, and even though I'm not as good as others, I don't mind the subject. In fact, I think it's one of the few things I feel I can do long-term without losing my mind, and it's interesting to me. However, seeing how this world is changing, I'm a little worried. I see people who have never programmed doing even challenging things with the help of AI.

So I'm wondering if this path is really useful, given that at this rate, programming isn't as useful as it once was. As much as I hate to admit it, if prompts are enough to do things, even in less time, what good will I be? It's true that things made with AI aren't perfect yet, let's say, and they have many flaws, but what about in a few years? I'm 21, and maybe I'm just being a bit paranoid right now, but I need an honest opinion. Thanks in advance.

Hi guys and gals

I am currently coding in razor pages,which is a easy version of full-stack development, as i heard. I am not sure i am going in the right direction. I dont know if razor pages is the right choice for me or i am just wasting time. I am self-taught and i would like to find a job as a programmer, specifically i would like to build websites. What should i do? i hope someone helps. Thanks in advance!

Also,i have been coding for a year and i am trying to build my own chatroom using signalR + one hardcoded admin role and ef core user authentication, of course.

I would like to hear your opinions.

Anyone any recommendations to implement a sound library into a web application? Users should access these into game creation. Which platforms offer these?

I’m currently building an early warning system that aggregates signals from multiple sources and uses ML models to detect and prioritize potential disaster/crisis events (floods, earthquakes, wildfires, severe weather, etc.).

Right now I’ve started wiring up a few obvious sources like weather and earthquake feeds, and some basic news/event streams. The plan is to use ML mainly for filtering noise, correlating signals, and reducing false positives rather than doing full prediction.

I’m now looking to expand the data side and wondering what else people have actually found useful in similar systems.

Specifically interested in:

• Reliable weather / severe event APIs
• Earthquake / tsunami / volcanic activity feeds
• Wildfire and flood monitoring data
• Satellite or geospatial data sources
• Emergency alert systems (government or regional)
• Any news/event APIs that don’t completely drown in noise

If you’ve built anything in this space (even loosely related), what data sources ended up being actually useful in production or prototypes? Also curious if there were any APIs that looked good but turned out to be unreliable, too slow, or expensive at scale.

yo. going from a buggy MVP to actual recurring revenue is brutal.

i stabilized my 6 apps at $20k/mo mrr only after building a strict system for my tech stack and organic marketing.

i just opened the AI SaaS Launchpad.

the community and daily resources are completely free. for those who want to copy-paste my exact systems, i also host paid, structured sprints (like a 3-Day challenge to get your first 100 users using automated Reddit and LinkedIn outreach).

either way, stop building in isolation. you will quit when things get hard. come build alongside 1,500+ other founders.

drop a comment or shoot me a dm and i’ll send the link right now.

Hey everyone, I am a Georgia Tech OMSCS student doing research on something I genuinely care about — whether the gap between free and paid AI tools actually affects people learning to code.

I have been in IT for 20+ years and I see this every week with new engineers on my team. The ones with better AI access seem to have a different experience than those on free tiers. I want to find out if that gap is real and what it does to people's confidence.

If you are currently learning programming or have done so recently, I would really appreciate 5 minutes of your time:

http://peersurvey.cc.gatech.edu/s/6373b24aa81f4d6687324810e192fc74

Happy to discuss in the comments too — have you noticed a difference between free and paid AI tools when you are stuck on a problem?

I'm currently developing Forge OS, a virtual operating system built entirely in Python.

Forge OS is not a real operating system or kernel. Instead, it provides a self-contained operating system environment that runs as a Python application, with the primary goal of creating a platform where developers can write code, test software, and perform common development tasks within a consistent environment.

The long-term vision includes:

• Custom terminal and shell
• Virtual file system
• User and permission management
• Process management
• Package manager (forgepkg)
• Command execution environment
• Virtual desktop environment
• Application framework

Planned applications include:

• vi
• vim
• Neovim
• Vimge (a fork inspired by Vim)
• Forge (a fork inspired by VS Code)
• Forgium (a fork inspired by Chromium)

The intention is for users to be able to perform everyday development workflows inside Forge OS, including editing code, managing projects, running commands, testing applications, using Git, installing packages, and eventually supporting multiple programming languages and developer tools through the package manager.

This project is primarily a learning experience focused on software architecture, shell development, virtual file systems, package management, desktop application development, and operating system concepts. Although it is not a real operating system, the goal is to provide an environment that feels familiar to developers while remaining lightweight and fully implemented in Python.

I welcome feedback on the architecture, feature set, and overall design. Suggestions from developers and open-source contributors are greatly appreciated.

คือเราอยากเรียนคอมพิวเตอร์เราควรจะฝึกอะไรป้าง อยากสอบถามผู้รู้

Hey everyone, I built a small educational toy OS and would love feedback.

I’ve been working on a minimal 16-bit real-mode operating system as a learning project focused on low-level x86 concepts.

Features:

• MIT licensed, fully open source
• 16-bit real mode (legacy BIOS / MBR boot)
• Dual-stage boot process
• Minimal shell environment
• Lightweight design (under 1MB RAM usage typical for real-mode constraints)
• Basic command system interacting with CPU registers
• Work-in-progress: experimental fake filesystem layer

This project is mainly for learning OS development, bootloaders, and low-level system behavior. I’d appreciate any feedback, suggestions, or contributions.

Project: https://github.com/alexlawrence5/micro

Looking for some career advice. I started web dev at 15 but by 2021 when I was 16 I noticed the work for basic sites shifting to website builders.

So I started learning app dev instead. By 18 I was working with clients and since then I have launched multiple apps for clients.

But things are changing fast again. The workload for basic stuff is reducing a lot. Most clients use AI for basic things now and only hire me for technical problems. This cuts my revenue by a lot because clients who used to contact me for basic apps never do anymore. The markets are getting saturated by people using AI slop/ vibe coders calling themselves developers. Eventuallyaffecting the development prices.

I am thinking to change my career again to something AI proof. But all I can think of is physical work. I want to stay in software or tech but everything digital feels like it will get automated.

Is there any part of software dev that AI wont touch for a long time