CodeShare.io Reviews

Kitemaker Reviews

CodeShare.io mentions (29)

• I never thought I would say this but I understand why a lot of companies do LC type questions during the process.

  As for LeetCode-like problems, I used to use codeshare.io and ask junior to mid front-end devs to take a fixed width/height box class/element and center it in an HTML div tag any way they know how to. Source: about 1 year ago

• Building a Live Code Sharing Platform With Dyte and React

  Codeshare.io is one such example. But today, we're going to roll up our sleeves and build our very own code sharing playground using Dyte.io. - Source: dev.to / about 1 year ago

• Pinescript code - need help!

  It's my bed time now but I'd be glad to help if you're still having problems with this, I'll be online around 9 AM to 12 AM CST and we can work through it. Hit me up with some clean formatted code, try codeshare.io. Source: over 1 year ago

• Best Websites For Coders

  Code share : Share code in real-time with other developers. - Source: dev.to / over 1 year ago

• [coding] tf.strings.operations raises TypeError: Value passed to parameter 'input' has DataType string not in list of allowed

  Could you format your code better? It's quite hard to read. You can also use: https://codeshare.io/ to share your code. It's a lot easier than having to format your code inside a reddit post. Source: over 1 year ago

Kitemaker mentions (13)

• You Might Not Need a CRDT: Document Sync in the Wild [video]

  When we built Kitemaker [0] we elected to not use CRDTs. We built our sync engine after reading the blog article Figma wrote about they didn't need CRDTs because they have the server arbitrating any conflicts. We ended up taking the same approach. It's worked out very well for us though in a tool like our "last one in wins" generally works fine and doesn't lead to a lot of surprises. For documents, we had to do... - Source: Hacker News / 4 months ago

• How to write great one-pagers, PRDs, Specs, and more

  There is no one-size-fits-all approach to writing descriptions, so you need to figure out what works best for you and your team. However, seeing real-world examples might inspire you to find new ways to write them. Here are some examples from descriptions we have written for Kitemaker. - Source: dev.to / over 1 year ago

• free-for.dev

  Kitemaker.co - Collaborate through all phases of the product development process and keep track of work across Slack, Discord, Figma, and Github. Unlimited users, unlimited spaces. Free plan up to 250 work items. - Source: dev.to / over 1 year ago

• Lessons learned from moving to Recoil.js

  At Kitemaker, we recently made the leap to Recoil.js for our React state management needs. Before using Recoil, Kitemaker used a simple state management solution built upon useReducer(). We built Kitemaker to be super fast, responding to every user interaction instantly. However, in organizations with lots of data, we sometimes had a difficult time achieving this due to unnecessary re-renders. Kitemaker has a sync... - Source: dev.to / over 1 year ago

• Realtime: Multiplayer Edition

  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... - Source: Hacker News / almost 2 years ago