kevsim

Co-founder here. Bananas in good way, I hope? :p

Co-founder at Kitemaker here. You're exactly right. However, when people start micro-splitting deliverables down into tasks, those metrics and outcomes tend to get lost in the shuffle.

The way we're structuring things in Kitemaker (large, collaboratively edited work items) is an attempt to prevent that. But of course it's not the only way to achieve it.

Awesome if you can make it work in your current tool of choice! As the article mentions, another way teams have solved this is by augmenting their issue tracker with a document-based tool like Notion or even Google docs and motivating their team to stay on top of those outcomes.

Definitely feel your pain. We did a full OT implementation for our startup [0] and it was a beast. We based it on Slate.js which has a nice concept of operations that maps nicely to OT, but it was still a lot of work to get it working well (and there are still rough edges we try to improve all of the time). We did base it on Postgres in the backend so really looking forward to what the Supabase team comes up with going forward and seeing if they can help us delete some complex code :-)

Happy to have a chat on collaborative editing anytime if that'd be helpful (email in profile).

0: https://kitemaker.co

I've also moved over to a self-hosted solution, but when using Medium previously, I just embedded GitHub gists for code blocks. Looks nice, has good syntax highlights, can get the raw gist, etc. Not ideal, but not terrible.

Faker looks cool! We've been using Casual [0] for ages but Faker looks more featureful and more actively maintained.

0: https://github.com/boo1ean/casual

Funny thing is after looking at it for a bit, I'd _swear_ HN is changing colors now.

According to the help page:

> Akedo uses a beginner friendly language that is similar to many professional languages but is aimed at producing readable and understandable code.

I think if they lifted the diagram from the docs [0] to the front page it would make things a lot more clear.

0: https://deepkit.io/framework

That's the point. Since it can't actually parse the file, this is as good as it gets. It at least gets something on the screen that says "Python >= 3.6 is required" which is better than nothing.

Spent some time at Nokia when I was fresh out of university. The thrill of getting "hello world" on the screen in Symbian/S60 is not something I'll ever forget. Took ages of battling CodeWarrior and I think even a simple app was something like 6 files, but seeing code I wrote running on a phone in 2004 was pretty awesome.

Exactly. In fact, it's even a bit of validation that maybe the market you're trying to address actually exists.

CloudFlare just announced their own relational DB for workers today: https://blog.cloudflare.com/introducing-d1

On HN: https://news.ycombinator.com/item?id=31339299

Supabase recently announced something in the "realtime" space https://supabase.com/blog/2022/04/01/supabase-realtime-with-...

Like to keep up-to-date on this stuff because we ended up building the realtime/multiplayer part of Kitemaker [0] from scratch on top of GraphQL so I'm always curious what's coming along to make things easier.

0: https://kitemaker.co

Looks cool! How does this compare to something like Firebase/Supabase?

I'd say if your competitors are relying on looking at your roadmap to compete with you, then they're in trouble. Single features are often easy to copy but it's a losing battle if your competitor is way out in front of you and you're trying to copy them feature-by-feature.

Similar argument with open sourcing your product. Couldn't your competitors look at your code? Sure they could, but if that's how they're trying to compete, they're going to lose. Plus, their engineers will probably look at your code and think they can do better anyway ;-)

Additionally more junior teammates probably had a harder time getting mentoring time from more senior teammates, for example.

Ngrok is one of those things that I know isn't that complex but I gladly pay for it year after year because I just don't want to deal with that stuff and it rarely lets me down.

Or they've made an SPA and are trying to make use of the history API and just have a bug. Don't assume bad intentions.

Wow if you can “cheat” during an interview - meaning either that they’re asking trivial, google-able stuff or that they’re so bad at interviewing that they can’t tell if you actually know your stuff - then their hiring process is pretty bad.

This is cool!

It's kind of similar to what the RICE/ICE frameworks are trying to help achieve [0].

We built some scoring of impact/effort into our tool Kitemaker [1] and allow teams to prioritize their work by these things. We ended up going with really simple scores like S/M/L since it's super hard to know the difference between a 6 and a 7 (and it probably doesn't really matter anyway).

0: https://medium.com/glidr/how-opportunity-scoring-can-help-pr...

1: https://kitemaker.co

Kitemaker (YC W21) | Founding marketing and community manager | Remote

Kitemaker is building the tool for the best product development teams in the industry. It replaces project management tools and issue trackers with a fast and collaborative alternative. We're looking for a marketing and community manager to join our founding team.

Fully remote but should have some decent workday overlap with GMT+1 timezone.

Find out more at https://careers.kitemaker.co

You can check out our LaunchHN here: https://careers.kitemaker.co/0a5a1c6caf37487ea03b95e3b312e23...

Kitemaker (YC W21) | Fullstack engineer | Remote | Full-time Kitemaker is reinventing the product development tool to help every team work like the world's best product teams. We're looking for founding members who can not only help us shape our product, but also shape the company itself. We're building everything in TypeScript top-to-bottom (Node, React), our API uses GraphQL and we're working on a bunch of fun integrations (GitHub, GitLab, Slack, etc.).

Fully remote but should have some decent workday overlap with GMT+1 timezone.

Find out more at https://careers.kitemaker.co

You can check out our LaunchHN here: https://news.ycombinator.com/item?id=26540692

Kitemaker (YC W21) | Fullstack engineer | Remote | Full-time

Kitemaker is reinventing the product development tool to help every team work like the world's best product teams. We're looking for founding members who can not only help us shape our product, but also shape the company itself. We're building everything in TypeScript top-to-bottom (Node, React), our API uses GraphQL and we're working on a bunch of fun integrations (GitHub, GitLab, Slack, etc.).

Fully remote but should have some decent workday overlap with GMT+1 timezone.

Find out more at https://careers.kitemaker.co

You can check out our LaunchHN here: https://news.ycombinator.com/item?id=26540692

Qt5 was release in 2012. Qt6 was released in 2020.

https://en.wikipedia.org/wiki/Qt_version_history

> Qt from 5 - where I ported one of my apps - and bang we're already at Qt6 now ffs!

It was 8 years between the release of Qt5 and Qt6. Qt's one the things I consider quite stable compared to many other frameworks these days.

We've certainly had our battles. When we first made Kitemaker[0], we were using the "old" pre 0.5 version of Slate and we built a lot of functionality on that.

When they did the total rewrite, we put off upgrading for a long time and that was probably a mistake because we just kept building up new things that needed to be ported.

Earlier this year we bit the bullet and ported things over to the newest version. I like the API a lot and it works quite well for us. The best part is that internally slate is "ready" for building a collaborative editor, so that's what we did. Work items in Kitemaker are fully collaborative, using operational transformation.

Downsides of slate for me are:

- Docs are lacking still. They were better before the re-write IMO and still catching up

- Memoization of leaf nodes doesn't work properly so you get a lot of unnecessary re-rendering (at least in the version we're using)

0: https://kitemaker.co

Looks very cool! Did you base it on an opensource editor or did you build it from scratch?

Asking because my startup has invested a lot into building our editor with SlateJS, so I'm always curious what other teams settle on.

Or ForestAdmin

Super cool! Any plans for webhooks? We trigger a lot of stuff off of GitHub webhooks (like when a commit occurs) so it would be interesting to hear how Sturdy will tackle this.

This looks great! People interested in generally cutting out distractions that lead to procrastination should also check out “indistractable” by Nir Eyal. I found it both entertaining and useful for cutting down on unwanted distractions (like too much HN browsing)