I love to work and decide alone most of the time, and I remember how stressful some pair programming sessions have been. On the other hand, without any regular team mate, assistant, or reviewer, I have to make an extra effort to get inspiration, feedback, and code review before going astray and wasting too much time following fallacies.
But working in a team does not guarantee code quality and productivity either. Teams can waste their time in meetings, insist on following unhelpful advice, or distract each other with unrelated tasks or personal problems. So it depends a lot: on the colleagues but also on team leaders or company policies.
There is a lot of discussion about AI and other kinds of automated assistance. I have not found anything useful from chatGPT (yet), and even GitHub Copilot seemed to get in my way and distract me with unhelpful advice in too many lines of code, but then again I have a lot of experience and developed strategies to search and find on Google, on StackOverflow and bulletin boards, and in GitHub issues.
What helps me a lot when working alone: taking and reviewing notes, creating codepens, template repositories, and writing DEV posts to get my thoughts in order and publish my knowledge so that I can find it again when googling the same error message one year later. I also use automated tools below the current "AI" hype, like tabnine, which also used machine learning, but restricts its output to short snippets with different options aligned with the IDE's code completion suggestions, and static code analysis like eslint, stylelint, and phpstan. I also get better code suggestions and documentation excerpts thanks to TypeScript, JSDoc annotations, and better tooling built into IDEs like PhpStorm / WebStorm.
Conclusion: working alone is fine for focus and peace of mind, but one brain is not good enough to ensure high quality software and web development.
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.
I love to work and decide alone most of the time, and I remember how stressful some pair programming sessions have been. On the other hand, without any regular team mate, assistant, or reviewer, I have to make an extra effort to get inspiration, feedback, and code review before going astray and wasting too much time following fallacies.
But working in a team does not guarantee code quality and productivity either. Teams can waste their time in meetings, insist on following unhelpful advice, or distract each other with unrelated tasks or personal problems. So it depends a lot: on the colleagues but also on team leaders or company policies.
There is a lot of discussion about AI and other kinds of automated assistance. I have not found anything useful from chatGPT (yet), and even GitHub Copilot seemed to get in my way and distract me with unhelpful advice in too many lines of code, but then again I have a lot of experience and developed strategies to search and find on Google, on StackOverflow and bulletin boards, and in GitHub issues.
What helps me a lot when working alone: taking and reviewing notes, creating codepens, template repositories, and writing DEV posts to get my thoughts in order and publish my knowledge so that I can find it again when googling the same error message one year later. I also use automated tools below the current "AI" hype, like tabnine, which also used machine learning, but restricts its output to short snippets with different options aligned with the IDE's code completion suggestions, and static code analysis like eslint, stylelint, and phpstan. I also get better code suggestions and documentation excerpts thanks to TypeScript, JSDoc annotations, and better tooling built into IDEs like PhpStorm / WebStorm.
Conclusion: working alone is fine for focus and peace of mind, but one brain is not good enough to ensure high quality software and web development.