π» Software Engineer π« Proud Member of #100devs
Tweet about studying tips, my journey with #100devs, and JavaScript
Need a website? π Click here
@bascodes Thank you for your time and the insights you shared! Likewise, you're great to talk to, and if anything, you're times more efficient in terms of thinking than I am! π
Hey #100devs
Had a very insightful coffee chat with @bascodes
We discussed:
- Proficiency > Quantity
- When am I ready for a job? (smaller companies)
- Important step to enter tech field (No CS degree)
- Bucket list of companies
π§΅π
[1/6]
[Bucket list of companies 1/2]
Make a list of companies/fields that you'd like to work for/in when you're ready. You can find them by reaching out to companies/their employees (networking) and asking questions about what they do, tech stack, working culture and etc.
[6/6]
[Important step to enter tech field (No CS degree)]
Showcase your projects (on github, twitter, etc.) This not only lets others know that you're building them and learning out of your own effort, but it also helps you establish credibility as a software engineer.
[5/6]
[How to ask better questions? 3/3]
Asking open questions: Dwell on the subject, as these types of questions usually come from experience. Example: There's this particular practice in JS, why are we doing this?
[10/10]
Hey, #100devs
Had an amazing coffee chat with @thegokhale
Today we've covered:
- (Networking) How to establish meaningful connections with people?
- How to avoid burning out?
- (Networking/Job) How to ask better questions?
Read the π§΅ below if you're interested
[1/10]
[How to ask better questions? 2/3]
2 types of questions: open and closed. Closed questions are usually easier to answer, whereas open questions can be a bit of a rabbit hole. So, try to ask open questions.
[9/10]