This is an incredible price. Lucky students.
Readit Newssteveruizok commented on MacBook Neo apple.com/newsroom/2026/0... · Posted by u/dm
steveruizok commented on Move tests to closed source repo github.com/tldraw/tldraw/... · Posted by u/nilsbunger
That's from this comment here: https://github.com/tldraw/tldraw/issues/8082#issuecomment-39...
Well that's embarrassing! I reported it as if it wasn't a joke. I thought the joke issue was this one about translating everything to Chinese: https://github.com/tldraw/tldraw/issues/8092
Sorry Simon, I honestly didn't expect this to be posted anywhere https://x.com/just_be_dev/status/2026419663505072195
steveruizok commented on Move tests to closed source repo github.com/tldraw/tldraw/... · Posted by u/nilsbunger
I'm thinking of migrating to ExcaliDraw or Xournal++ next time I need a whiteboard.
The performative closing of public contributions citing the slop scare felt disingenuous from the start. You couldn't be bothered to implement _any_ mitigations that leave the community engaged with the project?
Writing a contributor karma bot, moving to a non-social or obscure git forge (most slop contributors are resume farming and GitHub is the only forge the HR cares about), newbie-unfriendly non-public workflows like git send-mail, or references from Discord... This isn't an AGI on the other side of the screen, planning the perfect strategy to infiltrate your project; it's a sub-script-kiddie trying to fill a portfolio with quick "contributions" doing the more annoying version of "fixing typos" in docs.
We're in chats with the GitHub team, they're taking it really seriously. I consider our pause on contributions similar to pi's open source vacation, we'll figure it out. https://github.com/badlogic/pi-mono/blob/main/packages/codin...
Deleted Comment
steveruizok commented on Stay Away from My Trash tldraw.dev/blog/stay-away... · Posted by u/EvgeniyZh
IMO, you’re not really an open source project if you’re not accepting contributions with reasonably low friction.
I’ll call this what it is: a commercial product (they have a pricing page) that uses open source as marketing to sell more licenses.
The only PRs they want are ones that offer free professional level labor.
They’re too uncaring about the benefits of an open community to come up with a workflow to adapt to AI.
It honestly gives me a lack of confidence that they can maintain their own code quality standards with their own employees.
Think about it: when/if this company grows to a larger size, if they can’t handle AI slop from contributors how can they handle AI slop from a large employee base?
Author here. tldraw is not an open source project. It used to be but we switched to a commercial license for our v2 in 2023. The old v1 is still available under MIT; and I try to put as much as we can under MIT license where it makes sense, but the core needs to be licensed in a way that allows us to sell it. We've always been majority source available and still accept community contributions, even though the default is to close external PRs. I care about OSS. I wish the economics of it made sense for us.
> Think about it: when/if this company grows to a larger size, if they can’t handle AI slop from contributors how can they handle AI slop from a large employee base?
god help us
steveruizok commented on Stay Away from My Trash tldraw.dev/blog/stay-away... · Posted by u/EvgeniyZh
> Authors would solve a problem in a way that ignored existing patterns
if you’re not writing your code why do you expect people to read it and follow your lead for whatever your preference is for a convention.
I get people who hand write being fussy about this but you start the article off devaluing coding entirely then pivot to how your codebase is written having value that needs to be followed.
It’s either low value or it isn’t but you can’t approach it as worthless then complain when others view your code as worthless and not worth reading too
(author here) Code quality matters a lot—we make an SDK, we sell our code. I'm writing my own code with the assistance of AI tools. When I'm asking an agent to step in, I can recognize when the tools are producing poor results, I can pause the work, correct it, or take the wheel in order to get things going in the right direction. Programming is still important, quality and care perhaps more important than ever, given how much of it we can do when tool-assisted.
steveruizok commented on Stay Away from My Trash tldraw.dev/blog/stay-away... · Posted by u/EvgeniyZh
Guy uses his project's GitHub issues as personal TODO list, realizes his one line GitHub issues look unprofessional, uses AI to hallucinate them into fake but realistic looking issues, and then complains when he gets AI slop PRs.
An alternative idea: Use a TODO list and stop using GitHub Issues as your personal dumping ground, whether you use AI to pad them or not. If the issue requires discussion or more detail and would warrant a proper issue, then make a proper issue.
(author here) To be fair, we also were getting plenty of poor PRs that implemented well-described issues. Or hey, maybe they were poor and maybe they weren't, but they were someone else's "claude please fix" and I don't think it's important for me to review them.
But you're right about the todos... except that the majority of times my little /issue command actually produces really great issues and digs up root causes very well. I still need to read and bless them though. Maybe we need a "potentially slop" label.
steveruizok commented on Stay Away from My Trash tldraw.dev/blog/stay-away... · Posted by u/EvgeniyZh
>As a high-powered tech CEO, I'm
cough linkedin cringe cough
OP here: /s
steveruizok commented on Stay Away from My Trash tldraw.dev/blog/stay-away... · Posted by u/EvgeniyZh
> AI changed all of that. My low-effort issues were becoming low-effort pull requests, with AI doing both sides of the work. My poor Claude had produced a nonsense issue causing the contributor's poor Claude to produce a nonsense solution.
The thing is, my shitty AI issue was providing value.
Seems like shitty AI issue did more harm than good?
Hey, OP here. Shitty issue command is fine in a world where I have time to review it and expand it, just like I would have before; except now, there's a 80% chance that actually the AI got it right and I have a well-researched issue that can be immediately worked on. The only problem is if someone without any content comes by and feeds it into cursor to make a PR.
Maybe it would have been better to keep the original no-body "fix truncate in sidebar text" style issues, though I quite like my little /issue command. I'm sure I'll have something else in a month.