Member Avatar for Checkerboz

Okay first of all I am not sure if this is the right part of the forum for this but...

I am currently 19 and I kinda took some wrong turns with my education so I either sit on my butt and do nothing for about one year or I'll find some work(for one year).

Since I do not feel qualified to work with the stuff I want to work with the idea of getting a job feels kind of "meh". I am in other words trying to convince myself if there's a way to educate myself at home for the upcoming months...


Anyway I am basically looking for suggestions on what to do. I want to work with something IT related but that's not very specific. I *think* I like the idea of "something network something" but I feel like I can't really be much more specific.

Like should I learn programming languages or focus on something else(such as what, learning how to handle servers or something?)?


So yeah, do you guys have any suggestions, tips or well... anything? :p

Thanks!

Might as well mention that the education I am applying for next year (if I had done things properly it would've been this year) is university level computer science.

Edit: I probably should've mention that I'm not just looking for something to waste time on. I'm out to learn stuff.

Edited by Checkerboz because: n/a
  • 2 Contributors
  • 1 Reply
  • 188 Views
  • 8 Hours Discussion Span
  • Latest Post Latest Post by popin

Dani AI

Generated

For — a gap year can be turned into concrete skills rather than “wasted time.” ’s suggestion to get a job is sound: paid work gives money and real-world problems to solve. The most valuable thing over 12 months is a mix of hands‑on practice, a few focused learning goals, and a public record of what was built.

Start with repeatable, practical foundations: get comfortable with the command line, basic hardware troubleshooting, and one scripting language (Python is ideal for beginners). Build a home lab (use an old PC or VirtualBox/VMware) and install a Linux server. Do small, measurable projects: automate a backup, host a simple website, push code to GitHub. Weekly or biweekly milestones stop learning from being vague.

After that, focus on networking and system basics: understand IP/subnetting, DNS, DHCP, routing vs switching, and basic firewall rules. Use tools like Wireshark to inspect traffic and try a firewall distro (pfSense) or a small router project in a VM. Learn version control (git) and basic service administration (SSH, nginx/Apache, cron, logs). Certifications (CompTIA A+/Network+, vendor certs) can structure study, but prioritize demonstrable projects over paper certificates.

In the final months, make a portfolio: a public GitHub, short writeups of each project, and a one‑page summary of outcomes (what was built, what problems were solved). Seek part‑time helpdesk, volunteer IT for a local group, or short internships to turn projects into experience. Also spend some time refreshing discrete math and basic algorithms to be ready for CS studies. Keep goals measurable, document progress, and focus on a few solid projects rather than trying to learn everything. This approach builds skills, confidence, and things to show on applications or interviews.

Member Avatar for popin

I'd get a job if you sit around 'intending' to learn you'll likely end up doing less than you should, look for work in a computer shop or something u'l learn a little (as generally u get a few teckheads to every computer outlet) and you'll make a little money. (i don't know where you live (country only) but in Britain part-time employment has skyrocketed due to rescission and advantageous to the employer of employing part timers, that would give you time to study as well)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.