Vincent Taverna

Developer and Cook, Open Sourcing your grandmas tomato sauce

[Vincent Taverna @KidtheFlash]

@wesbos The total loss was ~2.8 million. Those who responded at 3am were able to prevent another 5 million from evaporating. The response time wasn’t too bad once we were aware of the issue, tops 20m.

The hidden lesson is to not let your internal admin tools rot as your business grows.

[Vincent Taverna @KidtheFlash]

@venir_dev @andonov_t @ZachSents @passle_ @iLuvBridgeFires I’ve heard GitHub doesn’t know what deleted means so you could be in luck 😉

[Vincent Taverna @KidtheFlash]

@mattpocockuk I have always found it rather strange that the vscode extension api for reading an editors document returns the entire contents as a string rather than a stream.

[Vincent Taverna @KidtheFlash]

@meesrutten @JoshWComeau To the intern at Google who shipped the dark mode feature on Gmail, your intentions were in the right place, but you’ve created so much pain

[Vincent Taverna @KidtheFlash]

@mootoday @71iQz @simnalamburt @luke_is Same when linting.

Lint and format check a partial set of files, they run quickly, giving you feedback.

Then lint and format check all files in CI to ensure quality is kept before the change lands. People break local environments 100x more than CI on main

[Vincent Taverna @KidtheFlash]

@jlongster @kentcdodds In case someone can’t afford a flight out, you might want to check out https://t.co/sz0HNNJcmY for cheap flights in sept, although full-warning I am one of the few people building it.

[Vincent Taverna @KidtheFlash]

@mattpocockuk Can’t believe this is getting fixed after all this time. Dependency trees have been so much harder to manage because of this issue. I haven’t seen a single one with a top level await either.

[Vincent Taverna @KidtheFlash]

@ryanflorence So many people here are misreading this. You said “They”. This was a group effort, and always is at an org as large as Google. The quality of the new login is poor, and this is just one example.

[Vincent Taverna @KidtheFlash]

@mattpocockuk Mind deleting this? You’re taking away my job security here

[Andrew Clark @acdlite]

e2e tests continue to be underrated. Yes, they are slower to run than unit tests, and usually take longer to write, but a good e2e test lasts forever, no matter how often you change the implementation. It's the only kind of test I want to write anymore. It's worth the extra work.

[Vincent Taverna @KidtheFlash]

@HaloSupport looks like you could use my help, your react app is crashing.

[Vincent Taverna @KidtheFlash]

@kentcdodds I’d love to see some competition in this space. The current implementation from Next leaves a giant gap that is asking to be filled.

[Vincent Taverna @KidtheFlash]

@mattpocockuk @edumaxsantos More on this here: https://t.co/w2wiaeUOgs

[Vincent Taverna @KidtheFlash]

@JLarky Now add `as Using`, since of course useUsing was typed as any 🔥

[Vincent Taverna @KidtheFlash]

@tomus_sherman @BenKingNTU @acemarke I agree with you, this isn’t a breaking change. However, I consider most of what RSC offers today dead on arrival, as the majority of third party libraries aren’t able to develop for it. It’s clear work is needed, and the RFC for RSC even mentions this missing functionality.

[Mark Erikson @acemarke]

As a library maintainer in the React ecosystem, I'm getting pretty frustrated by the churn around React Server Components.

Really starting to question whether the touted benefits are worth the pain being inflicted on lib maintainers:

https://t.co/4kIeJJtGYa

[Vincent Taverna @KidtheFlash]

@sebmarkbage @rauchg Notoriously difficult to nail down issues, such as memory leaks, or cache invalidation bugs are in this category for me.

[Vincent Taverna @KidtheFlash]

@acdlite In fact, it’s killing me