You need to have a goal

You need to have a goal

Especially if you are trying to learn while working full-time. It is easy to let your learning drag on and on if you don’t have any external pressure pushing you. So you need to create internal pressure. 

Your goal should be simple and quantitative. You should do enough research to come up with a reasonable goal

8 STASHED

1 LIKE

How I went from newbie to Software Engineer in 9 months while working full time

medium.com

MORE IDEAS FROM THE ARTICLE

  • Find out what motivates you and use it to your advantage. If you are not motivated to reach your goal, then nothing else matters because you won’t finish.
  • Make goals and meet them. Monthly goals to make sure you are on track to meet your main goal, and daily goals to make sure that you actually make daily progress. 
  • Go to meetups way before you think you are ready.
  • Contribute to open source way before you think you are ready
  • Start applying way before you think you are ready. You will not know when to apply. So you might as well start now. 

7 STASHED

Once you have a goal, you need a plan to help you get there. This is where you consume as many success stories as you can.

None of them will match your exact situation, but you can take some advice from each one.

7 STASHED

Most people only started to attend meetups when they were looking for a job, but at that point it is almost too late. There are so many reasons to start early. To name a few:

  • Developing relationships takes a long time. Starting early means that you have connections who can vouch for you when looking for a job later
  • Talking about programming with strangers is a great way to prepare for interviews
  • You can learn new frameworks, tools, and learning resources from people who are ahead of you. This can influence your future learning plan.

7 STASHED

Deepstash helps you become inspired, wiser and productive, through bite-sized ideas from the best articles, books and videos out there.

GET THE APP:

RELATED IDEAS

  1. Screening call or on-site interview: lengthy when done by HR and short when it’s someone technical, also not a good time to fire all your questions.
  2. Technical interview: where your knowledge is assessed by professionals of the field.
  3. Technical assessment, homework or pair programming: a practical test of your skills.
  4. Final interview: meeting the rest of the team or company leaders.
  5. Offer.

179 STASHED

1 LIKE

How to interview your interviewers when you're looking for a job

medium.freecodecamp.org

Kakeibo

Kakeibo translates as "household financial ledger" and is a simple approach to managing your finances.

For the past 116 years, kakeibo has been effective in helping people make smarter financial decisions.

610 STASHED

3 LIKES

I tried 'Kakeibo': The Japanese art of saving money-and it completely changed how I spend my money

cnbc.com

1. The user is an idiot

The user is not an expert. My doc doesn't require me to know the difference between low-density and high-density lipoproteions. 

Don't assume user should know what kind of browser they use or what is the best flow to use the app. 

But yes, no matter how much you think of it, sometimes the user demand feature that seem pointless and he can have difficulties with functions that seem to be self-explanatory.

14 STASHED

4 Mistakes I Made as a Programmer, but I Had To Become a CTO To See Them

betterprogramming.pub