kevsim

We use the certs automatically issued by GCP, which are also letsencrypt issued.

It is also that and there was quite the rumble on Twitter a while back where the CEO of Clubhouse the issue tracker was getting hatred targeted at the CEO of Clubhouse the audio chat thing.

That's a great question. Most of the companies using us today are small. They range from a single dev team to a small handful of dev teams. We're now starting to work with companies "one step up" from there that are coming with requirements about how to connect things across teams. Early days for this work, but we're trying to be really careful to keep this a tool that teams want to collaborate in and not a tool only a product manager would use.

We definitely have come close to the scale you're discussing but I look forward to finding out! That said, we have had a number of smaller companies drop Jira for Kitemaker.

Thanks! Just so I'm clear - it is Kitemaker or Clubhouse you're having networking problems with?

That's fair enough. The language that's there originally came from the fact that we see many teams where engineers are left out of the loop when it comes to the early stages of planning initiatives/features. One of the benefits teams have told us they get from Kitemaker is getting the whole team involved earlier, rather than PMs doing too much of the planning themselves and then just splitting tasks out to engineers.

But we'll revisit it!

We think Linear's a beautifully designed app that does Jira better than Jira for some teams.

That being said, we're trying to be a bit different. Teams using us tend not to split things down into micro tasks, but instead leverage the document-like structure of our work items to bring the whole team into a single workspace, thinking about and working on features/initiatives together. I think we also think about integrations a bit differently, but I don't have a ton of experience with Linear's integrations.

We're also a bit more crazy about hotkeys I think. Seriously, we're pretty obsessed ;-)

Exactly! 100 work items that haven't either been archived or deleted. For a small team this usually translates to more than a month of trying it out since teams tend to make slightly larger work items than they would issues in some other tools.

Thanks!

And thanks for the feedback on the video. We'll check it out. Which browser/os are you using?

That's actually a great suggestion. We'll add that!

This would be amazing! Please reach out to kevin@kitemaker.co

GitLab is our next planned integration.

One of our paying customers uses Mattermost so we've started the process of peeking at their API to see what we're up against. Since we've already got Discord/Slack it probably won't be super tough. That being said, there were plenty of gotchas added Discord after we already had slack since their API was different enough to be a bit annoying at times.

GitLab is our next planned integration and one of our current paying customers is using mattermost so it's something we're strongly considering.

And this HN launch has given us a lot to think about in terms of self hosting!

My hunch is it's somewhat related to the companies who have been using us thus far (other startups, mainly) and also that people are pretty used to it since many of our competitors don't offer a self hosted option.

That being said, maybe it's an interesting way for us to stand out from the crowd.

Great question! Our pricing is definitely something we think about a lot, so feedback like this is super helpful. The free plan usually gives a small team more than a month to try it out since teams tend to larger (and thus fewer) work items than they might in another tool.

We definitely think it’s a huge market and it’s undeniable that products like clubhouse will keep having success. But for us, we’ve set out to build something that changes how teams think about these types of tools. That’s why we’re pushing to get the whole team engaged and really make use of the document-like aspect of Kitemaker (which teams tend to use a bit differently than stories in clubhouse). It’s early days still, but initial feedback has been really positive and quite a few teams are paying us already.

Thanks very much for the feedback. It's always a bit of a struggle with landing page copy and positioning. But super useful to hear when something doesn't resonate.

Thanks so much for using it. We really appreciate it.

There's a little toggle down in the profile menu in the bottom left (or do cmd+k -> hotkey hints) if you want Kitemaker to give you more hints to help you learn the hotkeys. Basically it bugs you whenever you use the mouse!

Thanks for the feedback!

What we find is that the document-ish interface of Kitemaker lends itself to people sizing their work items a bit bigger than they would in Jira or GitHub issues, and then breaking them down a bit with todos inside. We have a lot of improvements planned around our todos to make this even nicer.

We also have themes (kinda like epics in Jira) for grouping larger initiatives together.

Thanks for reporting this! We'll take a look.

And thanks for trying it out. We really appreciate it.

GitLab is our next planned integration so hopefully you won't need to wait much longer!

Very cool! We tried Phabricator years and years ago but haven't had much experience since then. GitLab is next on our list, but then we'll see what comes after that. We've gotten a few BitBucket requests.

Any idea how popular Phabricator is these days?

We've been waiting on this a bit to see if there's much demand for this and so far the answer has been "not much" but we're open to the idea. So the answer is "not right now".

Good news I don't think it would be super tough for us since we're built using pretty boring tech (i.e. not a lot of dependencies on a particular cloud vendor), don't have a bajillion microservices, etc.

Even the browser vendors have given up on do-not-track though. Apple even removed support for it from Safari.

We connected with Tom just as we were getting ready to build webhooks into our product (Kitemaker W21). We had a few teams asking for webhooks but didn’t have much time to dedicate to it right now so we were in the market for something like Diahook.

It ended up taking us one afternoon (this afternoon in fact!) to integrate Diahook. Was super straightforward and Tom was highly responsive.

I really like this concept. I think for me one of the things that kills me about Slack is the way people write tiny little stream of consciousness messages. These are way less thought through even than they would be if you were having a normal conversation and serve as a distraction when it comes to the constant notifications.

I think asking people to stop and think a little bit (which I believe recording a video does) is great. I'll take one thoughtful video over 50 incoherent messages any day of the week.

Also thinking about trying this for a daily sync/standup since we often hear that people are not really listening to their teammates during these but instead are thinking of what they're going to say instead, which is of course entirely self defeating. Taking a minute to record your own video and then being able to consume your teams videos in an non-distracted way sounds spot on.

Look great and congrats on the success!

Minor feedback on the landing page - I found the "Contact us at" button floating under "By joining Poliglota you will" a bit confusing. Makes it hard to understand that heading goes with the contents to the right of it.

Ha! I guess my point was that when those companies started up, searching for those terms was bound to result in some businesses popping up, though I'm sure they made the call that "hey, they're not in the payments/analytics/whatever space, so no worries"

Does that really work though? What about mega companies with very common word names? Segment, Zoom, Stripe, etc.

Local files like that are fine, just keep them in your .gitignore

How different is the React.PureComponent behavior from the "wrap stuff in React.memo()" behavior?

I think I'd even take it a step further and not rely on the fact that it's been imported (which sounds a bit fragile and language specific). The number of times I have a new local that I don't want to add is far far smaller than the number of times I have a new local file that I forgot to add, so I'd want to be warned whenever I'm pushing with unstaged local files.

We use a git hook for this currently and it's super useful.