Adi Li

DOJ eating good today

Tell a friend

1.0 RC release! 🎉 We're getting close. github.com/solidjs/solid-…

Red flags in a React codebase 🚩 functions named handleClick,handleSubmit 🚩 preventDefault 🚩 useMemo 🚩 fetch inside useEffect 🚩 <div onClick/> 🚩 a "hooks" directory 🚩 css files 🚩 icon library in package.json

Risk: team size is too small to move fast, and Zig is not yet well adapted. Opportunity: more people would learn zig.

Vercel Blob, our frontend-friendly solution for storing and serving files, is now available in public beta for Hobby and Pro customers. vercel.com/changelog/verc…

Just got my ticket for @Nextjs Conf — claim yours! nextjs.org/conf/ticket/ad…

Rails is good for prototyping, but lacking of type information is bad when the team grows.

@vercel always do things fast 👍🏻

Use react query for sever state for sure. For the client state, @jotaijs is a great option in addition to redux.

Just did a quick test of Bun 1.0 on Create T3 App vs pnpm pnpm: 27.23s Bun: 0.35s 🤯

Imagine what AI will do to legal work harvey.ai

Story Points don't work. Even Ron Jeffries, who invented them, said he was sorry years ago. And not only did he apologize, but he called the whole estimation idea "Evil." Unfortunately, too many teams still use these points to estimate their work. Story Points is a made-up metric to estimate work effort, not time. The goal was to prevent management from misusing estimates. But it didn't work. Every team I've ever met keeps a conversion table to translate back and forth between points and time. Some will never admit it, but go and talk to the folks doing the work. Look at me and tell me I'm wrong. But it gets worse: Teams use points to decide how much work they can finish. But how can they do that without talking about time? The effort to do something is not the same as the time it will take to finish it. This is especially true when planning an iteration with many people and tasks. It's clear now: Story Points don't work. What's the alternative? I'll let the people who manage projects for a living offer their alternatives, but I can tell you what I've done. As I got older and wiser, I stopped with the estimation charade altogether. I had my teams focus on short iterations with constant feedback from stakeholders. From the "scope, budget, and time" triangle, I always tried to keep two of them variable and fix the third one. If the customer was looking for a specific scope, we had a variable timeline and budget to finish it. We kept the scope and time flexible if the budget was non-negotiable. And if we had to deliver by a specific date, the scope and budget were on the table. Every company is different, and this doesn't work for everyone. But if it does, I hope you stop the charade. I'd love to hear about your experience estimating software. What crazy things does your company make you do?

I literally just took a top post off /r/programmerhumor, this shit is too easy

To help you take on Shadow Mewtwo, we’re giving away codes for Purified Gems if we reach 150k RT! To participate: Follow us on Twitter RT this post with #ShadowRaids Receive confirmation reply If we reach our target, we’ll send participants a code for Shadow Raid–themed items!

Worth to take a look, @reactjs got competitor again

Arc @arcinternet, a broswer that allows you to group the tabs into Space, and clip web info to the notes, and even create simple boost plugin to simplify your daily browsing experience. Thanks @browsercompany arc.net/gift/36ed56db

Interesting tool, may be good to make a #chatgptplugins to run #javascript project webcontainers.io

Create @nextjs using @typescript with @tailwindcss easily! create.t3.gg

Pocketbase, an interesting database service for beta/small projects pocketbase.io it used #sqlite under the hood