this post was submitted on 09 Jul 2025
29 points (91.4% liked)

Programming

21537 readers
461 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
 

Hey everyone — I'm a final-year student, and I’ve been wondering this a lot lately. We always hear that “you need a good project to land a job”, but most students I know either copy from GitHub, get stuck, or just... give up. We’re doing a small open survey to understand this from both sides — students and educators. If you've ever: Built or struggled with a final-year project

Helped someone else do it (educator/mentor)

Wanted to sell or learn from real-world projects

We’d love to hear your honest experience. 🙏 It’s just 2–3 mins, totally anonymous. 📄 Survey Link – for students & educators

We’ll be using the insights to create open resources and maybe a system that actually helps. Thanks in advance if you participate — or drop a comment about your experience.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 10 points 3 days ago* (last edited 3 days ago)

Yeah, it's easy to underestimate how big of a leap it is from a toy application to real-world usability. Not just in terms of security, but also:

  • useful error messages
  • logging / monitoring
  • configuration
  • building a distribution
  • deploying in a reproducible way
  • documentation
  • integration with existing infrastructure
  • data migration strategies
  • etc.

This adds a lot of complexity, so you'll need to learn additional complexity to be able to deal with it at all:

  • modularization
  • version control systems
  • software specifications (via unit/integration tests)
  • team communication
  • helper tooling, like package managers, linters etc.

Learning about all this stuff takes years, especially if no one in your surroundings has much experience with any of it either. Professors don't have the time to gain or retain this experience, since they already have a different full-time job.

My advice would be to get students to do internships or to take a job as a working student in a company/organization. Sometimes, these can be shitty for the students, but they can often provide significantly more real-world context than college ever could.