3 ms·
>Er... reading this, I would rather suspect the author of "not being a team player" If he's in charge of the project's direction and has a specific vision that
by Applejinx 3y ago
>Er... reading this, I would rather suspect the author of "not being a team player"
If he's in charge of the project's direction and has a specific vision that must be accomplished, that's not his job.
Unfortunately, if random people passing by are able to steer the project into the ditch and cause it to fail its most basic requirements (as he describes) then he's bad at his job (which isn't 'being a team player').
He's bad at his job because what he describes seems like a total inability to sell people on WHY to pursue his end goals. If proliferation of devs leads to the project going more and more off the rails, he's getting people who are drawn in by something or other, and feel no connection to the basic purpose of the software. That's on him. His job is to make them understand why his purpose matters, and it's like he's producing a codebase easily adapted to other purposes, but it somehow doesn't get across his purpose.
Maybe he needs to hire a writer, not devs :)
- bayindirh 3y agoMaybe he's a great team player and loves his projects with a passion and doesn't want people to touch what he builds for himself, no? He's talking about his personal projects, and many comments are projecting how he behaves for his personal projects to his career? Does everyone know who he's personally and I'm the only stranger?
- tuxie_ 3y ago> Maybe he's a great team player (...) and doesn't want people to touch what he builds for himself Isn't that the exact opposite of being a great team player? I had a boss who was "a great team player" once. We were both working for a rapidly growing startup and he was very open to suggestions on how to improve the system. So naturally when he started his own project I was very much eager to work with him again. Turns out that it's easy to be a great team player when you are spending someone else's money and changing someone else's code. When I proposed changes to the system he built himself he took it very personal and all of a sudden he was not so open anymore. It's easy to be generous with other people's money.
- pdimitar 3y ago> Isn't that the exact opposite of being a great team player? You're projecting as well which is visible by the example you give which has next-to-nothing in common with what's being discussed here. You don't have to want to share governing of your personal idea project. You can be open to contributions that align with your goals BUT reject those that don't. Both can be true at the same time and the latter does not make you a bad team player. It makes you a "if you want to help me build my shed in my back yard I'll welcome you but if you turn out to want to build a garage then I'll show you the door" person. Or in other words, it makes a fairly normal Homo Sapiens.
- bayindirh 3y ago> Isn't that the exact opposite of being a great team player? No. The anecdote you shared shows a different part of being human: Knowing thyself. He let you in before he was mentally and emotionally ready to let go of his code, and as someone else noted in this thread, it has nothing to do what we talk about here. Again, it's not about "people's money". It's about being ready to share and let go of control.
- phkahler 3y agoI got the impression he didn't seek help at all, and this was just unsolicited offers to help take it in various directions. He should probably make his goals clear to avoid that.
- foobarian 3y ago> then he's bad at his job (which isn't 'being a team player'). the job being, being a Linus :-)