connordoner

There’s a tool that I’ve used at other companies that I absolutely love. It has features that few other products have and I’m a lot more productive with it than with those other products.

Wile there are efforts by open-source contributors, it’s no longer maintained by its original developers and hasn’t been for approximately two years.

I’m thinking of using it at my startup, but I worry that it’ll end up with me focusing more on managing the risk that comes with legacy software more than on my core product.

Does anybody please have advice either way?

I have an employee who I’ll call B. B joined us and got off to a good start but has recently faltered - having missed an all-hands and two weekly 1:1s with me - and is now producing no output at all.

I’ve asked B repeatedly - both as their boss and their friend (”never hire friends” feels true here!) - what’s wrong and if I can help, and I’ve had another employee who leads on admin, including HR, do the same.

We’ve received little in the way of responses. Examples include:

* “there’s not much to talk about”

* “i’m not sure i’m in the mood to talk about it right now” (which didn’t change days later)

* “it’s just so much i can’t even be arsed to explain tbh”

* “i just don’t even think there’s much to talk about”

* “I don’t really feel like going into it, it just feels quite foggy to me at the moment”

I’m erring on the side of just firing them, because I’ve made a concerted effort to get to the bottom of it and it’s an immense distraction from building our MVP, but I feel like I’m missing something. Any thoughts?

I can't believe that I'm having to resort to this, but does anybody have a support contact at GitHub?

I've had a Sev 2 support request relating to the accidental deletion of an organisation unanswered for a week now.