|
|
|
|
|
|
by yizhang7210
2148 days ago
|
|
|
1. What's your goal of learning to code? If you want to be a professional software engineer (which you may or may not need more data to decide), then perhaps some kind of education is necessary. Bootcamp can work. A completely new undergraduate obviously works. If your education is close enough maybe you can get into a CS/SE masters program and go from there. 2. If your goal is to have deeper technical conversations with engineers, perhaps you can ask to "pair program" with them if there are engineers at where you work and you'll learn about what their jobs involve. 3. If you just want to be more of the engineers community, then I'd say being able to actually code is not required. You can go to a bunch of different events to get to know more of them. Hackathons, various career/hiring events, board game sessions etc etc. 4. If your goal is something else, then there are other options. There's codacedemy, there's udemy, there's freecodecamp etc. If you want to be more hands on, maybe you can join one of your engineer friends on one of their side projects and let them teach you in that concrete situation. |
|
|
Have a lot of engineer & founder friends I talk to regularly. I think overall goal would be to go one step up from connecting and actually be a peer in some respects.
Build up skillset to be a founder-operator in the future. Along the way, I'm sure it's helpful to the day job in investing.
Re: 1. Definitely not this. I've realized my skillset / interests don't coincide with writing code at Big_Tech for a living.
RE 4. Have tried a lot of those programs. They don't click after the beginning stages, and don't do a good job graduating you or tracking you. Also intrinsic motivation is a problem -- i'd like to take a half year off to just do that.
RE 2 and 3: These are good ideas. Have been doing them to some extent. But taking next step of being in community -> contributing to it.