(no title)
ichbinlegion | 3 years ago
Just as an example, let me tell you that we currently have a (self-taught) intern which is years ahead of two developers from bootcamps which have been working with us for over a year.
Getting a job position doesn't automatically mean you are suited for that job, or that you're good at it.
And while there are good dev bootcamps, getting out of one and finding a job, doesn't make you a developer (or an "engineer" either, which in my country is a regulated title)
sanitycheck|3 years ago
100% agree that getting a job doesn't mean you're good at it - but getting paid to do programming is the easiest way to keep learning. Maybe a good way to get people improving quicker could be to give them self-contained individual projects and allow them to get stuck and solve their own problems, I don't know? I do see devs spending days asking each other for help on stuff they could probably solve if they thought hard for an hour. Collaboration is good, sure, reinventing the wheel is bad, yes - but just diving in and wrestling with a problem is good practice and (eventually) fun.
I also won't call myself an Engineer for similar reasons, though an American company did give me that job title once.