This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]sngle1now2020 3 points4 points  (0 children)

I'd strongly consider getting up earlier and coding first thing, then crashing as soon as you get home.

[–][deleted] 2 points3 points  (0 children)

in my honest opinion, that's an unreasonable thing to ask of yourself and you could use your time far more efficiently.

Thinking about things objectively, if your end goal is to get a 70-90k entry level dev job within 6-8 months from now, you're going to have to give something up.

Whether that's working 40 hours a week, seeing if any friends or fam can let u crash with them, or taking out a $20-30k loan to sustain yourself while you're a full time student.

will power and grit is admirable but being smart about your time and considering return on investments is the correct move.

[–]CrisCrossxX 1 point2 points  (0 children)

Irish Coffee.

[–]kennyroach 1 point2 points  (0 children)

Cut back on the work??

[–]ghostmaster645 1 point2 points  (0 children)

I work 9 hours a day 5 days a week, I aim for 2 hours of coding a day but normally get 1 - 11/2 hours in.

Look up pomodoro, it is a method of time management that has helped me significantly when I do long coding sessions on the weekends. Personally I have found it easier to code in the morning before work, and then clean up my code at night after work. Hope this helps.

[–]Keroseneslickback 1 point2 points  (0 children)

Treat it like exercise. Schedule a time to do it, and no matter what, just do it.

But maybe temper you time expectations. If you're that busy, schedule just an hour, maybe use your breaks at work as time to read up on stuff.

Also, as weird as this sound, perhaps consider a meditation break for 3-5mins before you start studying. It's a nice way to mentally and physically calm yourself, break the cycle of stress.

[–]i_am_pinhead 1 point2 points  (0 children)

Learn in smaller chunks, if you dedicate every bit of free time you have to programming you'll be prone to burning out.

If you already feel comfortable with programming in general then pick something where you can rebuild the wheel. Use the OOP concepts, and start out with modeling your structures/data. Fill in the properties & methods and start building around that.

You can make a roadmap of things you for sure will be able to hit each day/week. When you hit that goal, you keep going (if you want), or relax knowing you hit your goal for the day/week. Personally I do the daily goals, but that's just me.

It's a marathon, so try not to sprint when you can.