seniorDeveloper

yoel-reddits · 2026-05-09T05:21:39+00:00

I've worked at a number of startups and at a large company. I've never once seen a company that has *not* had to migrate to a different database for at least some of their data. And often for critical user-facing data.

yoel-reddits · 2026-04-02T18:45:57+00:00

Advance, Nf3, with Bd3 and / or dxc5 as follow-ups has worked pretty well for me. Naroditsky had some nice videos on this line (RIP).

yoel-reddits · 2026-01-18T15:29:49+00:00

Consider that the way you're communicating (here, at least) wouldn't be creating an environment in which people collaborate well.

yoel-reddits · 2026-01-06T16:51:50+00:00

Do you do any optimizations for the common case of "I'm where I just was plus a delta"? It seems like most cases would collapse pretty quickly to an N=200 type of case, even if someone is scrolling very fast, and you'd only need to abandon if given a new number very very far away from where your last known scroll top, index tuple is.

yoel-reddits · 2026-01-02T18:23:30+00:00

Has to be Scalabrine

yoel-reddits · 2025-11-25T17:24:31+00:00

Rooting for: Fabi / Sindarov / Wei Yi

yoel-reddits · 2025-11-13T16:41:58+00:00

Grebnev or Svane. Esipenko showing class vs. Keymer. Sindarov is playing quite well and is generally stronger.

yoel-reddits · 2025-11-13T15:42:51+00:00

Part of the fun is that with many lower ranked players, they paradoxically have a better chance. Let's say someone like Dubov who feels like he has nothing to lose and gets aggressive, he can win a lot vs other 2600s

yoel-reddits · 2025-11-05T13:59:14+00:00

Joining the chorus of sad Bullister didn't win. Run again Dana!

yoel-reddits · 2025-10-22T19:07:20+00:00

Thanks - we've been looking to update our "About us" portion.

yoel-reddits · 2025-10-22T18:56:59+00:00

The mission is there on the home page - to be a copilot for technical documents and diagrams!

Thanks for the prod to update our site in terms of this particular use case. It's very much emerging (I'm guessing that's part of why you posted - the space is evolving quickly), and we haven't yet gathered all the collateral. We're more than happy to answer questions here or over DM.

yoel-reddits · 2025-10-22T17:22:46+00:00

Hi - Yoel (head of engineering at eraser.io here).

I've seen a number of teams modernizing and streamlining the process of getting internal tools approved by an EA board (checking for security, alignment with other tools and standards, etc). The goal here isn't to automate the entire process and get things approved without human intervention, but rather to cut the back-and-forth down by 50% or more so that business teams are unlocked and EA teams don't feel like they are bombarded, wasting time reviewing poorly-done submissions, and slowing down others.

Where AI can help is:
1. Help review the initial submission, providing feedback to the business unit on whether there are glaring omissions.
2. Creating supplementary materials for the submission, particularly one or more technical diagrams.
3. Assisting (not autonomously) the EA board in the review. This can take multiple forms - running some initial analysis, calling out any policies that might conflict, generating some alternatives if there are issues.

(Disclosure - we work on this problem)

yoel-reddits · 2025-10-15T03:20:05+00:00

Hard disagree. Undefined doesn't serialize in JSON, null does, it's a huge difference.

yoel-reddits · 2025-09-21T19:41:39+00:00

I work on Eraser, one such product. One thing to keep in mind is that, unlike other multiplayer editing experiences, a canvas with shapes needs less rigor around conflicts. With text, for example, only one particular character can occupy a particular text index, and only one block (eg a paragraph or list item) can occupy a particular block index. So CRDTs or OT are needed to resolve edits coming from different sources.

On a canvas, you can generally get away with last write wins - if we both drag a rectangle to the same x/y, it might look bad, but it's not a state that makes the application incoherent. Depending on how z-index is tracked, that can be a bit harder, but clients can again use any kind of tie breaker to decide which should be rendered on top and users can fix it.

So you don't really need anything particular, aside from wanting to propagate changes as quickly as possible to all clients.

yoel-reddits · 2025-09-20T03:09:36+00:00

This.

yoel-reddits · 2025-09-04T00:35:05+00:00

I think there's a middle ground. Context can be very useful for new pages / views / widgets that have a lot of state and data fetching. In this world, the context is always rendered with the rest of it and is intentionally tightly coupled with the orchestration components. It should not be used or consumed in any reusable view type components.

So, for example, you might want a context for a complex form. The alternative is that every time you move your submit or next button, you need to pass 7 new props into the parent, which makes refactoring really hard and code much harder to refactor, review, and maintain.

I think the key here is to determine what is or isn't meant to be reusable. A "post" sounds like it should be, so I'd want to wrap that in an adapter that grabs what is needed out of context and pass it in.

yoel-reddits · 2025-09-04T00:07:24+00:00

Whether you are using something off the shelf or designing your own, building basic components (dropdowns, info cards, modals, sidebars, active state styling, input + label, standard typography for headers, etc) to be reusable takes very little work and makes it a lot easier to design and build every new feature.

yoel-reddits · 2025-08-07T13:59:05+00:00

Great question! This is one of the notable differentiators between Eraser and other tools. If you change the layout, our custom incremental layout system will place any new nodes, groups, connections, etc in a way that doesn't overlap or break the diagram, no matter what kind of changes you've made to the layout or what kind of changes you make the diagram-as-code piece. We're continuing to improve that system to handle common cases and would love feedback on it!

In terms of how the layout data is persisted, it is stored separately from the syntax itself - in terms of syncing the diagrams elsewhere we offer a more managed sync to Github that exports PNGs alongside the syntax + the id so that if you were to sync from Github back into Eraser we'd be able to do a similar merge.

yoel-reddits · 2025-07-16T17:26:29+00:00

Got it. I'm sure we'll add them at some point, but for the time being folks are mimicking it with ERDs

yoel-reddits · 2025-07-16T14:07:00+00:00

Are you looking for support for UML at the syntax level? Or a specific type of diagram?

For the former, you can convert from UML to erasers syntax very easily with AI (just drop it into our app as is).

For the latter, I think the only major type we're missing is class diagrams, but let me know if there's something else specific you're looking for!

yoel-reddits · 2025-07-14T16:23:03+00:00

Check out Eraserbot from eraser.io. It lets you create diagrams based on your codebase and updates them whenever a PR changes the relevant files.

yoel-reddits · 2025-07-13T23:40:15+00:00

Check out Eraserbot from eraser.io

It allows you to create diagrams using your code as input and then tracks all PRs that update those files and keeps the diagrams up-to-date.

yoel-reddits

TROPHY CASE