Vincent

Vincent

@vinnymac.dev

Staff Eng @ Pointhound Open saucing your grandmothers tomato recipes. Some call me a Squishy Claude

77 followers150 following420 posts

People often talk about engineering spaces, such as the software or civil spaces. But what of the space engineering space? And more importantly do they use tabs?

Vincent reposted

PSA: H3 Stable and Nitro RC are imminent. Closing the last-minute gaps. Sorry for all the delays, but every single one was worth it. Nitro is becoming a MINIMAL, FAST, UNOPINIONATED/AGNOSTIC Swiss Army knife for building any web app. Your agents are gonna LOVE it.

Just because your project is open source does not make it acceptable to cold email developers for exposure and ask for contributions. Especially if that project is at the core of a for-profit business. Be respectful

My ISP just emailed me for the second time this year that they are “upgrading” my internet speed free of charge, I went from 300Mbps to 600Mbps to 1Gbps. At this rate we will achieve FTL in ~26 years

If you `! touch AKAMAI` and then prompt Claude Fable to `git status`, it will fallback to Opus as if you’ve just broken into the pentagon itself.

Every car should come with an open weight model that runs fully offline in case of an emergency and you have no connectivity and need to Macgyver yourself to safety. This is gonna be a thing even if you don't like it.

Vincent reposted

Rust is moving toward a formal LLM contribution policy after months of heated internal debate, driven by a wave of low-effort "slop PRs" straining maintainers. The proposal bans LLM authorship but allows private use. socket.dev/blog/rust-mo...

socket.devRust Moves to Restrict LLM Use in Contributions After Months...The Rust project is moving toward formal rules on LLM use in contributions after months of internal debate over maintainer burden, code quality, and c...

Vincent reposted

Replying to @sxzz.dev

Credit where it's due. Huge thanks to the @pnpm.io, @npmx.dev, and broader tooling communities (@e18e.dev) You're the reason working with JS packages still feels okay day to day. You filled the vacuum npm left behind. The registry is still a single point of failure, but the tools around it aren't.

It should be more common to show a video of a demo as a fallback when sharing new browser capabilities (e.g. HTML-in-Canvas), rather than a “your browser is not supported”. I see it far too often and it’s simply lazy.

Vincent reposted

Catalogs just landed in evlog Centralize your error & audit management in one place. No more magic strings scattered everywhere. Start small with a single file, scale to multi-package monorepos with full TypeScript autocomplete. You define it once, use it everywhere. evlog.dev/learn/catalogs

Everyone wants to call the environmentally friendly sendBeacon() method these days, but give sendBacon() a chance it is delicious 🥓

Non tech people often make a strange assumption that humans can somehow have the entirety of a codebase perfectly in memory. Even worse when folks in tech make this assumption, even about themselves

A friend of mine, not in tech, is getting bullied by his boss on a Saturday for not using Grammarly. I am afraid to ask how many of us, in tech, are going through the same thing but with LLMs instead.

Someone on my team just said they always tell Claude to “review pull requests like you are Vinny”. New complement unlocked

Vincent reposted

In the next version of Vitest you can track leaking asynchronous resources via `--detect-async-leaks` option! Available in v4.1.0-beta.4 release. 🔍 (notice missing await in the example)

When you spend half an hour trying to find a file, and an LLM can’t find the file, is it a good time to start crying?

Emails that tell you to respond directly to the email, and then respond by telling you the inbox isn’t monitored and to go down other rabbit holes are the worst

Everyone is excited to discuss how well LLMs can program, but I just want to know when they’re gonna clean and climb my stairs

The English language is missing a term for “generic you”, so as to avoid confusion. Gyou are doing it wrong

What many Staff Eng fail to realize is that the amount of ambiguity you must deal with greatly varies depending on who you work for. Find the people that see eye to eye with you, and you’ll be set free.

Vincent reposted

Big news in this year's GitHub Octoverse report: TypeScript is now the most-used language on GitHub! We are thrilled and grateful to see the TypeScript and JavaScript community continue to grow and thrive. 🚀 Read up more at github.blog/news-insight...

github.blogOctoverse: A new developer joins GitHub every second as AI leads TypeScript to #1In this year’s Octoverse, we uncover how AI, agents, and typed languages are driving the biggest shifts in software development in more than a decade.

Vincent reposted

you can sponsor @e18e.dev through GitHub Sponsors or OpenCollective these funds will primarily be used for two things: - distributed to projects/individuals in the wider JS community - development of community projects/tools thanks so much to those of you who already sponsor us 💙

opencollective.come18e - Ecosystem Performance - Open CollectiveThe e18e community has the aim of improving performance of tooling and packages in the JavaScript ecosystem.

Ever wanted to defeat your nemesis? Send them handcrafted Etsy items for made up partners and anniversaries at random throughout the year

To all the junior engineers out there that need to hear this, you still need to learn the fundamentals, and then some. Using assistive technologies is not an excuse to avoid honing your craft.

If this is you, try using AI for menial things that may require much less review time. If you find highly complex code and think it would be difficult to review / change, prompt to write a test suite where one may be missing.

Dynamically loaded scripts were a mistake. So were iframes. Everything after ready should have been static content, even content being rendered from other pages.

I just merged a pull request on GitHub and the pull request stayed open, while the commit landed on the default branch. I guess the Microsoft acquisition has infected them after all.