This. Please, we don't need any more wage slaves in this industry. I already work with a bunch of people who don't have any interest in correct solutions but would rather just ship code. Feedback is non-existent or unwelcome. If their code is wrong, it's not, you're wrong. I'm 10-years professional and I have never met such a rude and entitled generation of bootcampers who think they deserve six-figures for figuring how how to return an array,
Rant over.
Please join tech or engineering because it genuinely excites or interests you. Not because the wages are higher.
I have 10 years of experience. I can say with authority that I know very little. The only thing I learned is to recognise faster when my code sucks (I still struggle to write a good code)
I identify with this, a bit. I’m getting more serious about writing testing, and it seems to give me some confidence.
I recommend a few books. Growing Object Oriented software guided by tests. It lays out a clear plan on starting and how one can approach building tests.
Next would be dependency injection: principles and practices.
Maybe try the GOOS book first and see if it resonates with you.
Comments
This. Please, we don't need any more wage slaves in this industry. I already work with a bunch of people who don't have any interest in correct solutions but would rather just ship code. Feedback is non-existent or unwelcome. If their code is wrong, it's not, you're wrong. I'm 10-years professional and I have never met such a rude and entitled generation of bootcampers who think they deserve six-figures for figuring how how to return an array,
Rant over.
Please join tech or engineering because it genuinely excites or interests you. Not because the wages are higher.
I have 10 years of experience. I can say with authority that I know very little. The only thing I learned is to recognise faster when my code sucks (I still struggle to write a good code)
I identify with this, a bit. I’m getting more serious about writing testing, and it seems to give me some confidence.
I recommend a few books. Growing Object Oriented software guided by tests. It lays out a clear plan on starting and how one can approach building tests.
Next would be dependency injection: principles and practices.
Maybe try the GOOS book first and see if it resonates with you.