Anyone talking about the responsibilities that you have towards your coworkers? Saying you like to work solo because you can make decisions more quickly is like saying you like to drive over the speed limit because it gets faster where you need to go. It works when you don't make any mistakes.
The thing is though: we do make mistakes and bad decisions from time to time. I've seen several "solo developers" who think themselves great coders, but when it's time to pass on the project to somebody else, all hell breaks loose.
While I prefer to do assignments by myself as much as possible, I try my best to have coworkers do sanity checks on my decisions before I make them.
As an example: I made the DRY-est of email sending logic I could ever imagine. It was extremely generic and could pretty much turn every model you pushed in to it into a proper email. Push a model into the machine and it would automatically map names, map addresses, map dates and more, as long as your models just inherited the right interfaces.
Then came the day that my coworker had to send an email using this system. Because it wasn't that simple. After several hours of trying to get my coworker to understand how to send a simple email, we pretty much gave up and found that this generic contraption wasn't quite as clever as we thought. It was all according to the programming principles, but I had forgotten the human aspect of coding: everybody has to be able to understand it.
So yeah, while solo working is cool, please consider your fellow devs while doing it.
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.
Anyone talking about the responsibilities that you have towards your coworkers? Saying you like to work solo because you can make decisions more quickly is like saying you like to drive over the speed limit because it gets faster where you need to go. It works when you don't make any mistakes.
The thing is though: we do make mistakes and bad decisions from time to time. I've seen several "solo developers" who think themselves great coders, but when it's time to pass on the project to somebody else, all hell breaks loose.
While I prefer to do assignments by myself as much as possible, I try my best to have coworkers do sanity checks on my decisions before I make them.
As an example: I made the DRY-est of email sending logic I could ever imagine. It was extremely generic and could pretty much turn every model you pushed in to it into a proper email. Push a model into the machine and it would automatically map names, map addresses, map dates and more, as long as your models just inherited the right interfaces.
Then came the day that my coworker had to send an email using this system. Because it wasn't that simple. After several hours of trying to get my coworker to understand how to send a simple email, we pretty much gave up and found that this generic contraption wasn't quite as clever as we thought. It was all according to the programming principles, but I had forgotten the human aspect of coding: everybody has to be able to understand it.
So yeah, while solo working is cool, please consider your fellow devs while doing it.