4 ms·

I do the later so I don't get stuck, i.e. if I have mastery over language/framework/etc then I'll not get stuck, because when I do get stuck my stress goes to c

I do the later so I don't get stuck, i.e. if I have mastery over language/framework/etc then I'll not get stuck, because when I do get stuck my stress goes to cloud 9 and rapidly start losing hope. Spend days alternating between procrastinating and trying things which feels like putting hands on sizzling pan. But "the PROS" I've seen encounter bigger problems and move past them in a day or two, without going through entire cycle of despair.

raydiatian 4y ago
How long have you been in tech if you don’t mind my asking? I’ve found that (surprise) confidence is a function of experience. The kids that started early (age 8 to 13) always seemed to have a leg up on the rest of us, but it’s because they’ve got a solid 5-10 years “experience” (YMMV in terms of quality of course). If you’re still junior in your career, just pay attention. If you’re getting senior level but you’re not getting enough work, start doing more personal projects that require you to “own” the whole thing from end to end.
- techsin101 4y ago
  about 7 years
  - raydiatian 4y ago
    Does that include education (uni/boot camp)? Because honestly I think unless you went to a school in a tech hub city, they didn’t teach you everything you need to know about CS. Have you read the seminal literature (the thing they didn’t teach you in ugrad)? Gang of Four OOP design patterns, Patterns of enterprise architecture? You might ask your employer for a subscription to O’reilly books online.
toast0 4y ago
Take this for the Internet advice that it is, but... Dealing with problems that you don't know the answers to right away is part of the job, and it's one that stresses you out. By doing extensive prep, you're avoiding some number of stressful incidents, but you're also making sure that the incidents you do have are higher stakes. You might try doing a less detailed read of documentation before you start, then if you get stuck, you can expect to look at the documentation to get you unstuck. Maybe it will, maybe it won't, but you'll practice getting unstuck and it will hopefully be less stressful. Some of us just despair on the inside.

raydiatian 4y ago

How long have you been in tech if you don’t mind my asking? I’ve found that (surprise) confidence is a function of experience. The kids that started early (age 8 to 13) always seemed to have a leg up on the rest of us, but it’s because they’ve got a solid 5-10 years “experience” (YMMV in terms of quality of course). If you’re still junior in your career, just pay attention. If you’re getting senior level but you’re not getting enough work, start doing more personal projects that require you to “own” the whole thing from end to end.

techsin101 4y ago
about 7 years
- raydiatian 4y ago
  Does that include education (uni/boot camp)? Because honestly I think unless you went to a school in a tech hub city, they didn’t teach you everything you need to know about CS. Have you read the seminal literature (the thing they didn’t teach you in ugrad)? Gang of Four OOP design patterns, Patterns of enterprise architecture? You might ask your employer for a subscription to O’reilly books online.

toast0 4y ago

Take this for the Internet advice that it is, but... Dealing with problems that you don't know the answers to right away is part of the job, and it's one that stresses you out. By doing extensive prep, you're avoiding some number of stressful incidents, but you're also making sure that the incidents you do have are higher stakes. You might try doing a less detailed read of documentation before you start, then if you get stuck, you can expect to look at the documentation to get you unstuck. Maybe it will, maybe it won't, but you'll practice getting unstuck and it will hopefully be less stressful. Some of us just despair on the inside.