Paul DeVito

Great AI use case — easily add tracing and metrics that you may not have before.

YouTube video by ThePrimeTime DHH Is Right About Everything

It’s wild how many people feel entitled to OSS maintainer’s free work, especially at your scale.

DHH is on the money with it youtu.be/mTa2d3OLXhg?...

@ssalbdivad.dev you're amazing 🤩. Obviously WTF!? but in a good way 🤪

I could seriously see library maintainers starting to make skills for their libs though. Tempted to for some of my OSS libs 🤔

Been setting up skills in claude code today and the state management one is essentially a condensed version of @tkdodo.eu’s blog

What’s the ETA looking like these days? Siked for it!

Can’t wait to see the new docs!

Screenshot of various UI elements including textfield, date picker, select, tags, radios, slider, switch, checkbox, buttons, progress bar, table, number field, combobox, and menu.

Having a blast re-designing all the React Aria examples this week. Flat design is so over – bring back depth! 😃

From the Entrepreneur community on Reddit Explore this post and more from the Entrepreneur community

Auditing 47 Failed Startups for why they failed

www.reddit.com/r/Entreprene...

what i found in those 47 codebases: like 89% had zero database indexing. ZERO. your app is slow because youre searching through 100,000 records on every single request. thats not a bug thats just... why 76% were paying for like 8x more servers than they needed. the average is 13% utilization - youre paying for 100 servers and using 13 of them. burning $3k-15k a month for nothing 68% had auth vulnerabilities that would make any security person have a panic attack 91% had no automated tests at all. so every new feature is literally russian roulette

The OP goes on to note:

I get a feeling that working with multiple AI agents is something that comes VERY natural to most senior+ engineers or tech lead who worked at a large company

You already got used to overseeing parallel work (the goto code reviewer!) + making progress with small chunks of work

My personal anecdote on the impact of AI (aka Claude Code + Cursor)

There was this tool I wanted to build that would have helped my business a little bit at @pragmaticengineer.com, but not enough to

1. Do it myself (would have taken ~days)
2. Hire someone (too much onboarding)

But...

Abandon Vercel.

The Replit guys have a migration tool and they are they do not support the genocide.

Using the FakeTimeProvider example. See the real times on the left, and the time from the time provider on the right.

The `FakeTimeProvider` in #dotnet is excellent for testing time-based scenarios. You can advance time in increments, like a true Time Lord, to test tricky timing behaviors.

Get it in the "Microsoft.Extensions.TimeProvider.Testing” NuGet package.

You can add a "Create" option to a React Aria ComboBox in just a few lines of code.

stackblitz.com/edit/szjf6ul...

They have a zero bug policy

What components are they considering shifting to? Styled components always surprised me as part of their stack.

Listening to Careless People by Sarah Wynn-Williams

Hearing about the tools that engineers at Facebook made around censorship is absolutely wild. The complete lack of morals that leadership has is one thing, but the fact that all these other staff just execute it is crazy. I can’t imagine

I’d hope these are old setups. Anything new should just be using OTel with any of the several providers that you can view it with. Also other things like session replays but homerolling that sounds especially not fun.

.NET STS releases supported for 24 months - .NET Blog .NET STS releases will be supported for 24 months

.NET STS releases supported for 24 months

ift.tt/T7syaAf

#dotnet #support #microsoft

In favor of what? Curious what orgs are finding to be the best balance and workflow in this new world!

Easily*

That’s what mass transit is for! Haha

If you want a nice meal check out el Camino. Was easier our favorite meal during our stay there. Loved Prague ❤️

What are good alternatives to data fetching in Effects? Hide Details Writing fetch calls inside Effects is a popular way to fetch data, especially in fully client-side apps. This is, however, a very manual approach and it has significant downsides: Effects don’t run on the server. This means that the initial server-rendered HTML will only include a loading state with no data. The client computer will have to download all JavaScript and render your app only to discover that now it needs to load the data. This is not very efficient. Fetching directly in Effects makes it easy to create “network waterfalls”. You render the parent component, it fetches some data, renders the child components, and then they start fetching their data. If the network is not very fast, this is significantly slower than fetching all data in parallel. Fetching directly in Effects usually means you don’t preload or cache data. For example, if the component unmounts and then mounts again, it would have to fetch the data again. It’s not very ergonomic. There’s quite a bit of boilerplate code involved when writing fetch calls in a way that doesn’t suffer from bugs like race conditions. This list of downsides is not specific to React. It applies to fetching data on mount with any library. Like with routing, data fetching is not trivial to do well, so we recommend the following approaches: If you use a framework, use its built-in data fetching mechanism. Modern React frameworks have integrated data fetching mechanisms that are efficient and don’t suffer from the above pitfalls. Otherwise, consider using or building a client-side cache. Popular open source solutions include React Query, useSWR, and React Router 6.4+. You can build your own solution too, in which case you would use Effects under the hood, but add logic for deduplicating requests, caching responses, and avoiding network waterfalls (by preloading data or hoisting data requirements to routes).

I don't know who needs to hear this, but here are some alternatives to fetching data in useEffect:

v1.108 is rolling out today 🚚

Now live, at long last: Bookmarks, aka Saved Posts. For all those posts you'll definitely plan to come back to!

Update the app and give it a try. The button is right down there 👇

Three tweets from Aaron Boodman (@aboodman) dated 16 Aug 2021, reading: 1. Chrome was delivered without any sprints at all. The team came in at 9 and left at 5 (figuratively, people actually kept their own ~8h schedules) every workday for a couple years like clockwork. No drama. No broken marriages, no broken families. 2. It was one of the most formative experiences of my career. 3. I hear you asking, dear reader, how this miracle came to pass. How did chrome-team manage to deliver high quality software without death marches? Funny you ask... Turns out that software projects actually benefit strongly from having senior technical leadership deeply involved.

Seems like an appropriate time to re-share the @aaronboodman.com thread.

"Chrome was delivered without any sprints at all"

xcancel.com/aboodman/sta...

It’s the worst part of the .NET community IMHO. That and the repository fights every other day 🫠

And it's a day ending in "Y", so I'll say yet again that the over-emphasis on layering and abstraction from how people typically explain and use Clean/Onion/Hexagonal Architecture/Ports and Adapters has caused real harm in real world systems

Recreated the Apple Photos UI with React Aria in just ~200 lines! Complete with virtualized scrolling, view transitions, adjustable waterfall layout, folder tree, search, multi-selection, and accessible drag and drop.

Just one of the demos I'm planning for the new docs. 🙂

I decided to test whether EXIF data is removed from images sent over X's new encrypted chat feature like Signal and other messengers do.

I can confirm it is not. I was able to extract information including GPS coordinates from a test image sent to me.