u/InTheDarkDancing wrote (the comment Michael replied to):
So the first issue I see is that the first line in areas for improvement clearly says "you got quiet upon hitting errors". Codesmith is HUGE on technical communication and it probably outweighs you getting a right answer. Your post gives the impression that you think the rejectio
u/michaelnovatireplied·★ FEATURED
This ^^^
The advice to talk more though isn’t enough on its own though. Talking more about your ideas is a good starting point to go from zero to not zero but if you want to get to 1 you need to approach algorithms problems with a solid mental framework. We (Formation) have one called “The Engineering Method” and there are many others, but following a pattern can help you tremendously instead of whack a mole talking, debugging, and pseudo coding.
u/witheredartery wrote (the comment Michael replied to):
i do not like their obsession with pseudo coding though
u/michaelnovatireplied·★ FEATURED
You don't have to pseudo necessarily, are they telling you that?
This is the Formation method. (disclosure: I'm the co-founder there but I am not soliciting you to join or anything, we work with people much farther along in their journeys - after bootcamps and after working, just a relevant resource to help you)
[https://formation.dev/blog/the-engineering-method/](https://formation.dev/blog/the-engineering-method/)
We don't have the word pseudo code anywhere in there, but we also don't suggest to start writing final code until later in the process.
u/witheredartery wrote (the comment Michael replied to):
They are. I kinda feel she held it against me because I was explaining all my problems. Talking while being stuck I find it hard because my brain gotta do PnC in the head, very difficult to talk during that
u/michaelnovatireplied·★ FEATURED
So one of the downsides to Codesmith is that most of the day to day teachers are senior students, Fellows, alumni hired as full time instructions, and none of them have worked in industry yet. What Codesmith does well though is they propogate their "way of doing things" through the staff very well and consistently. So it's a little like "just trust the Codesmith way and do it our way" vibe.... and it works pretty well, but there ARE other ways of doing things haha and if their way doesn't work for you then go to a different program that does and don't feel bad about ruining your application streak :D
u/witheredartery wrote (the comment Michael replied to):
Wow this is a mjor red flag to me. People do this in India also. Like you compare content from fresh graduates and them people like kent c dodds, tyler mcginnis. THERE'S an ocean worth of difference.
This boot camp game to a degree feels really stupid. Because I don't find them
u/michaelnovatireplied·★ FEATURED
There are a lot of benefits to this too though, I just want to make it clear I'm not judging this but just pointing it out so you can find a style that works for you.
Springboard for example, has all outside mentors, and they have a lot of weaknesses with that approach too because if the content is a bit dated, and the mentors are not senior enough or experienced enough teaching, it doesn't work great.
Rithm caps classes at 18 because the leaders want to directly teach students personally, but they aren't as aggressive as Codesmith on the job hunting part.
u/witheredartery wrote (the comment Michael replied to):
I kinda want to go the self taught way, I am almost there,
https://github.com/antariksh17 I struggle at building projects from scratch
and I am kinda doubting I will get to learn that in any bootcamp
u/michaelnovatireplied·★ FEATURED
HackReactor you build a lot of projects too, might be an option
Springboard’s job gaurantee only applies if you follow their strict rules, like proving you apply for certain number of jobs and documenting and stuff. So the way it works is it forces to not make excuses and be very very aggressive in your job hunt, which helps you get a job :)