@yonatanbdi
iAccount based inIsrael
About this account
- Account based in
- Israel
- Connected via
- Israel Android App
Account-level information from X, not a live location or the device used for a specific post.
Software is cheap, relationships are expensive
Israel
Joined August 2018
- Tweets911
- Following50
- Followers249
- Likes5.6K
quickly recognizing AI slop is a much needed skill
1. em dashes
2. Too much text
3. Too many fonts
4. ?
Sponsor @vanilagy mediabunny lib
Too many comapnies relay on it
I've been a little sad the last couple of days. Mediabunny's first, longest and most loyal sponsor, Gling, stopped their gold sponsorship of Mediabunny this week. Their CTO @yonatanbd left the company, and they're now restructuring their efforts and cutting costs where they can. An understandable move from their part, and it's got nothing to do with me.
I'm deeply grateful for the years of Yonatan's support; he alone was the basically the reason Mediabunny even got started and he supported me through its development for half a year before I released the version to the public. Thanks to his encouragement and financial support (as well as the support of @konstipaulus), I had the courage the quit my job back then and to focus on building cool media stuff for the web full time!
On the financial side, I'd be lying if I said losing a gold sponsor doesn't hurt. It does, a little. I'm still alright though! GitHub Sponsorships are my main way of making a living at the moment. If you or your company have gotten considerable value from Mediabunny, consider a donation! I'm sure your logo would look beautiful on the Mediabunny home page ;)
I'm working on super cool upcoming stuff that I haven't shared yet, and I'd love to keep working on it. People still haven't experienced the true power of web-based media processing!
Bottom up strategy usually works better
Start simple, and if you see a pattern generalize and abstract, not vice versa
I did the same mistake (overabstraction) twice in a row now. For a project of mine, I needed both shared-memory multithreading and SIMD operations in JavaScript, and these felt like gaps in the ecosystem so I built both of them as standalone libraries. I even announced them on X, how foolish of me!
They both fell short when actually using them in a real project. The shared memory JavaScript was hard to reason about (classic), and the SIMD library worked well for standalone operations but didn't compose well. Or well, it did compose well, but the composition would underperform.
I now dropped both efforts and added only what my project needed. Complexity is way down and any design is immediately reality-checked against the true constraints of the project.
I still think libraries here are absolutely possible, and I have many ideas about how to make the SIMD library work well, but it's a lot of time I'd invest into something that isn't a priority for me right now.
Part of it is true
But for me the code I wrote never matter, but the process of building and solving problems
AI helps me do it faster
Every software that will be built can be cheaply copied
The incentive to write a closed source for profit software is now very low
Using @OpenSpec_ and the model is acting much more like a senior architect
Every product that will be developed can be copied easily
Therefor if you build a new product, there is a very high probability it will be easily copied with few prompts, instead of paying you for that product
The question is what can not be copied, or will not make sense financially to copy?
My thoughts are: Relationships with clients, deep tech (frontier models, etc.) and hardware
FeatureMap (free and open source) - Create a visibility layer for your AI agent and for you on what is going on in your product
A detailed list of your product features, backed by evidence from your code base
github.com/yonathan06/featur…
did the same in the new @gling_ai beta
Replying to @konstipaulus
Prompt 3:
Create a Lottie animation from the SVG path in github.com/JaceThings/SF-Hel…. Reveal the path with an animation that follows the natural path direction. Apply a premium apple themed gradient to the path. Use ease-in-out timing, a transparent background, and preserve the original SVG geometry.
Looking for a @claudeai skill/plugin that smartly knows when to clear context? I find myself running /clear constantly to keep the LLM focused.