Ben Nelson

He's right. Typescript is the correct thing to learn in 2025. Knowing JS isn't bad; there's a lot of code written in it, but TS is the better language to work in, especially for new projects. I ran OKC.js for about a decade, and I've given numerous technical talks on JS (possibly the most in Oklahoma) over the years and I am co-signing this, you need to know it now.

8

1 Comment

I'm incredibly excited for this talk. Top K queries are the backbone of search engines, which have historically been NoSQL databases unable to execute JOINs. We're fixing this with ParadeDB. Highly recommend attending, I promise you'll learn something!

36

If you think in systems, not just tools - this list is for you. These aren’t beginner tips. Each of these helped me step out of the tools and think at the architecture level. ☑ Why You Need Systems Thinking Now Helps you avoid “local optimizations” that quietly damage the larger system. 🔗 https://lnkd.in/egak7xuY ☑ The State of AI: Rewiring to Capture Value Shows where scaling fails - missing KPIs, weak adoption loops, no operating cadence. 🔗 https://lnkd.in/eMRbKW5U ☑ AI Index Report Enterprise-level snapshot of where AI adoption and governance actually are - not just where they could be. 🔗 https://lnkd.in/eJCUq95Z ☑ AI Privacy & Security Overview (Airtable) Practical guide to thinking about AI inside your systems of record - controls, training limits, admin visibility. 🔗 https://lnkd.in/ePp6KEW5 I’m always looking for things that stretch my thinking a bit. Send me yours if you’ve got one worth reading, feel free to drop it in the comments.

4

I use Claude Code all day as a Product Manager. I built 18 custom Claude Code commands that I'm giving away for free. See comments for the link. I use these in Nimbalyst as its the best way to work with Claude Code - https://nimbalyst.com, but these custom commands will work however you use Claude Code: /plan - Feature planning /prd - Create structured PRDs /strategy - Strategy documents /competitive - Competitive analysis /research - Market research synthesis /customer-interview - Customer interview guides /customer-interview-simulate - Simulate customer interviews /feedback-analyze - Analyze customer feedback patterns /understand-feature - Examine codebase for feature context /mockup - Generate UI mockups /documentation - Create documentation /edge-cases - Identify edge cases /bug-report - Document bugs /triage-requests - Triage incoming requests /status - Development status updates /github-status - GitHub progress summaries /launch - Launch announcements /sales-enablement - Sales enablement materials

176

29 Comments

🔥 Curiosity about useState drove me into the world of Fiber and reconciliation I started learning about the useState hook and how the React team actually built this thing. It looks like everything is tightly connected with Fiber. The hook logic lives inside Fiber, and the whole idea of custom hooks is just to reuse logic anywhere you want. The only rule is the function name must start with use*, but inside we just write normal JavaScript logic. When I checked how useState is implemented, I noticed they use Fiber heavily. Then I fell into the rabbit hole of Fiber and reconciliation. Very interesting stuff. Before React 16, they used something called stack reconciliation. It was fully synchronous, no priorities, no way to pause, and everything executed through the JavaScript call stack (LIFO), which caused a lot of problems for big apps. Then Fiber came and completely changed this. Instead of relying on the JS call stack, React now has its own Fiber nodes. Whenever you update something, React creates a separate work-in-progress Fiber tree in the background (a detached copy of the current one). After all the work is done, React commits it, and the Fiber root starts pointing to the newly committed tree. That’s basically how modern React avoids blocking the UI and handles priorities. People still say React “Virtual DOM” because it’s easy and they don’t understand Fiber architecture or how React really works internally after React 16 btw latest version is (19.x). Pretty interesting right ? #ReactArchitecture #DeepDive #TechExplained #ReactFiber #ReactReconciliation

3

1 Comment

After exiting Drivably - Acquired by ACV Auctions (NASDAQ: ACVA), I came to Utah to look for the companies Trent Mano is asking about. What startups were all substance, no hype? What startups were simply creating motion, not heat or noise? Local awareness of your startup can be driven by community ties (e.g. you have local investors), product type (e.g. you're building consumer or startup B2B SaaS), or actual traction (this is or should be your real goal). Hype, heat, and noise can help you secure your initial product, investors, and customers. Some social awareness is desirable: you want awareness with the customers who will give you ARR, the investors who will give you runway, and with the talented people who will build the company when you're not in the room. But too often, heat and noise are the unintended byproducts of systems designed to produce something else entirely. Light. Motion. Acceleration. What kind of systems are we trying to build here? For many startups, broad social awareness is NOT what gets you to the magical product, true fans, and TAM dominance. What gets you there is focus. Focus on uncomfortably narrow, intensely specific groups of people that no one else is focused on the way you are. It requires getting used to flying under a general purpose radar. Getting used to explaining, "So what exactly do you do again?" For much of Savi's life, we've been so far under the general purpose radar, we weren't just in stealth mode, we were in exile. Turns out, exile is the perfect place to build something dangerous for a small group of people. Exile is where Savi sat down with fast-growing Utah brands and operators like Swig, Gourmandise, and Savory Fund, and designed and built the vision AI operating system for restaurant and retail. Exile is where we found Next Coast Ventures and other investors that shared our conviction about AI transforming Main Street businesses. So, get on the radar that matters for you. Focus on the small, sub-scale groups of people that matter to your startup. And maybe your time off-the-radar will be the reason you get on-the-radar in the ways that matter.

33

6 Comments