Great article to help set expectations. A few other notes if I might....
-- Someone will be looking at your code at some point in the future. Assume whoever wrote that legacy code you're fixing/enhancing did the best they could with the tools/techniques available at that time. In bootcamp there is no time machine.
-- You'll have to run automated tests to prove your changes didn't break anything. In bootcamp there is no regression testing because there is no legacy code.
-- Sometimes you will spend more time writing automated tests than you do writing "real" code. In bootcamp there is rarely have enough time for comprehensive testing (let alone automated with CI/CD).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great article to help set expectations. A few other notes if I might....
-- Someone will be looking at your code at some point in the future. Assume whoever wrote that legacy code you're fixing/enhancing did the best they could with the tools/techniques available at that time. In bootcamp there is no time machine.
-- You'll have to run automated tests to prove your changes didn't break anything. In bootcamp there is no regression testing because there is no legacy code.
-- Sometimes you will spend more time writing automated tests than you do writing "real" code. In bootcamp there is rarely have enough time for comprehensive testing (let alone automated with CI/CD).