I’d say i had a pretty rare case, so take my next comments in context.
My bootcamp was a side opening to the main campus in NYC. The Philly campus received very little assistance as we lost a few on site roles while i was going through my camp. The curriculum was dated and support near non existent with no possibility for a refund just “you can take the course again” which was out of bounds for near everyone since it would be 6 months without being able to work.
All in all, the things i took away from the camp were a better understanding of how the web worked, how websites were built, and how to problem solve like a developer. These definitely helped me as i navigated toward my “next steps”
I heavily advocate for those to really know the camp they’re investing in. Know the curriculum in comparison to your local job market. Talk to as many alumni as possible. It’s easy to listen to marketing from internal employees and get wrapped in the “i can leave here making a lot of money” scheme.
I’m going to link you a video i recently recorded discussing some advice for bootcampers or people looking to jump into tech.
My advice for those in the middle of their “jump” is to find the resources that work, build out what you can, and be able to concretely deliver the how and why of what you’re doing. I think that gets lost sometimes in the excitement of trying something new and cramming to be “ready” enough for a job, which most times you’re not. You learn while in the midst of the issues, you can’t exactly prepare for all outcomes.
FINALLY just got around to listening to this. thanks for the link and sharing your story! loved your advice to use tutorials as a reference and building your own things, as well as the importance to know how to explain code you've written. now to implement irl!
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.