I'm a 17-year-old beginner developer working with Java and Kotlin for backend development, plus TypeScript and React for frontend work. I've completed several hackathon projects and built one personal full-stack application using a Java backend with a React and shadcn-based frontend. That project already meets my own needs, so I'm unsure what to do next. I don't have a long-term project idea, and I don't know which open-source projects would be approachable for a beginner. How can I continue practicing and improving?
5 Answers
You can practice without committing to a multi-year project. Whenever a technical topic interests you, build a small experiment around it. Read about something unfamiliar, make a short prototype, and then expand it only if it stays interesting. The goal is to regularly apply what you learn, not to force every project into a product.
Build tools that solve problems you actually have, or make your current project public and turn it into an open-source project. Clean up the README, document local setup, add contribution guidelines, and make it easy for others to run. A real constraint—like supporting a new data source, improving a slow operation, or designing a more complex interface—will usually teach you more than adding random features.
You don't need to invent a huge long-term idea. Start with a small MVP, then gradually add features without designing the entire future in advance. Changing requirements are a major part of real software development, so let the project evolve and practice refactoring it when new needs make the original design awkward.
Focus on production-style improvements rather than starting another beginner CRUD app. Try deployment, Docker, authentication, automated tests, CI/CD, logging, monitoring, backups, and handling failures. These are useful skills that small personal projects often skip. Small documentation fixes or bug fixes in open-source projects are also good first contributions.
Just because a project is finished for your own use doesn't mean it has to be shelved. Put it online, let a few other people try it, and see where they get confused or break things. Fix those issues, add regression tests, improve the documentation, and make setup easier. User feedback can naturally give you the next set of problems to solve.
You could also extend your existing app with a feature you don't personally need, such as persistent dark mode or notifications. The edge cases and maintenance work will teach you more than another tutorial project.