Can't agree more, I like the driver analogy.
I'll just add that developers don't write unit tests until they work in a team.
Until then, you can have control on the base code. It will be fine, unless you forgot something, but, hey, that's not that often.
But, when a coworker mess with your code and change how it behave, unit test is the only way to keep controle
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.
Can't agree more, I like the driver analogy.
I'll just add that developers don't write unit tests until they work in a team.
Until then, you can have control on the base code. It will be fine, unless you forgot something, but, hey, that's not that often.
But, when a coworker mess with your code and change how it behave, unit test is the only way to keep controle