Our AI Agents provide detailed and specific video understanding. This yields intelligent support and automation. Redefine Human/AI collaboration with adaptive, context-aware AI. https://t.co/7JNqINnuqC
#AI#AIagents#AgenticAI#videoai#LLM
years ago i had a mindset that most engineers have
i believed if i produced a good product then marketing was not necessary
my bar was very high - good meant people loved it and were telling their friends about it
this isn't completely wrong but if you visualize a funnel this does not consider the absolute top
why would someone going about their day drop everything and try my product long enough that they hit the aha moment
what made it click for me is this video by veritasium (link in reply)
he's a youtuber that makes genuinely great content. it's not debatable and very few people produce anything at that level
he talks about how much effort he puts into packaging his work and thinking about how to get people excited to watch it
seeing someone that good still have to consider these things made it really clear what was going on
i was afraid of marketing, an area that was unfamiliar and unnatural, so i adopted a pretentious view of things to avoid confronting that fact
i'm on the other side of this journey now and it's painfully obvious how the majority of people are stuck in the exact same place i was
I just realized there's a fundamental memory issue in the re-render model I didn't think about:
1. Let's say there's a component whose closure retains a lot of memory, maybe the props are heavy, maybe something else.
2. You have 10 useCallbacks in this component.
3. Each useCallback references something from the closure.
4. The component is re-rendered 10 times.
5. At each re-render a different one of those useCallbacks is invalidated and re-computed.
6. Now you are not retaining in memory just the last heavy closure, you are retaining in memory the last 10 heavy closures.
Like it's not just that the VDOM is heavy, you are also paying the memory cost of stuff retained across N re-executions of each component, each kept alive by something that hasn't been refreshed yet.
Good luck optimizing that away, you basically can't.
Now imagine how much easier this is if each component instance is only ever called once and never re-rendered.
@fabiospampinato@RobbieSpeed Last year I wrote on that. There was a discussion afterwards. Would be worth a second look. Article from last year https://t.co/NcEHpjnyS9
@sixmiodollarman@BenniOderSoo 😑 Kommt bisschen auf bleibende Schäden an. Was macht man mit 2,5m, wenn man nicht mehr laufen kann. Oder Arterie getroffen. Risky.
Had an off-by-one error which generated 23 million rows in my db. Total extra cost: 0 EUR.
I shall name this as “that one time self-hosting saved my ass”.
Thanks @heyandras for allowing a zer0 like me to self-host with Coolify.
The worst take about the web is that you should not use JS/React/etc because HTML alone is good enough.
It's an 'austerity mind virus' that has captured even some smart engineers. The idea that the web is for 'documents' and if it stays in its own little box like 1995 it's going to somehow be better for the world.
This is how we ended up with Safari having the most obnoxious limitations, including a back/forward navigation gesture that makes the web feel like a horrendous 'digital book' of sorts.
No, the web is also for dynamic, rich, interactive applications. JS is a key ingredient in the recipe, otherwise every click and interaction will have to hit a server, feel slow, and we'll always be a second class citizen.
The web's developer freedom & better deployment model will win in the end, but it can't come at the expense of quality.
- Be @shadcn
- Make a modular component lib
- Lib goes viral
- LLMs learn to use it
- Shadcn is now the default component lib for LLMs
- Majority of code will be written by LLMs in coming years, especially for new websites
- Shadcn is spared
Designing great shortcuts for applications is harder than one would think. I was really impressed with @excalidraw when I first started using it. @linear also great with those double combos. What other apps should I check out?
@YuJian920 Well, you’re in for a surprise. That is normal JavaScript behavior. 😄 Here’s a JS article that came out a bit after mine: https://t.co/yEIaivjLk9
I always felt that server-side makes the most sense for public consumer apps with sporadic engagement and high SEO requirements, like eCommerce. Anything that targets white collar office workers (including dev tools/SaaS) or has longer engagement: Why not optimize payload and offload render work to powerful laptops?
The whole discussion around WHAT you’re actually building is underserved. It’s often just solution_x vs. solution_y for all the things.
And, of course, the server story universally makes a lot of sense for infra providers like Vercel. But I also don’t generally get my nutrition advice from the bakery. 😄