|
On the topic of people just being there for the money: Obviously, that's the primary reason for just about any job, but I think I get what you mean. Your team treats your project, which you've sunk a lot into, like a chore to work on. If you want more of a sense of community, that's doable. It's just harder with a remote team. With an on-site team, it's easy to take everyone out for coffee on Mondays, occasionally show a movie in the conference room, or just shoot the shit on a break. With a remote team, it's more difficult but doable. Add a few off-topic Slack channels to encourage less formal and strictly work-oriented conversations between team members (within reason of course). Topics like games, programming languages people are interested in learning, etc. And on the topic of learning languages, a lot of devs want two things out of a job: money and learning opportunities. No, you probably can't integrate every new language or framework someone is interested in into your stack. You can still encourage learning for its own sake. Let's say I'm really into Elixir, but my employer is a Ruby shop. If they encourage me to better myself for my own sake, I have a lot more incentive to stay on, and make sure I'm hitting the targets I need to. If I have a place to talk about my side projects with my coworkers, it feels much less like my interests are at odds with the company's interests. --- The other big thing here is that it sounds like you have a lot of stress which nobody else in the company really feels. It's hard for me to give concrete advice here. The two things I can think of are delegating some of your responsibilities to a qualified dev on your team, and spending more time talking with other technical founders at other companies. You need to vent somewhere. |