Voffie

just released better-music! Got nerdsniped by @dillon_mulroy to create a better SDK than Spotify took a while, but it is finally out! npm i better-music @biglakana also contributed to the project (he wrote the initial auth layer!)

@threepointone @dillon_mulroy @github @dillon_mulroy did you do the same thing as with realhumans?

all our release PRs, present and past have disappeared @github help?

@dillon_mulroy The 2nd person on the team not named Matt

🐐

@samgoodwin89 @dillon_mulroy @biglakana @EffectTS_ That’s true. Just thought the npm package was the main point and it has a link to the repo. But here it is: github.com/voffie/better-…

@vooffie @dillon_mulroy @biglakana @EffectTS_ Probably better to link the github than the NPM package

just released better-music! Got nerdsniped by @dillon_mulroy to create a better SDK than Spotify took a while, but it is finally out! npm i better-music @biglakana also contributed to the project (he wrote the initial auth layer!)

@byalashhab @dillon_mulroy @EffectTS_ If you ask in his Twitter DMs enough he will be forced to respond

@dillon_mulroy @EffectTS_ OP is lucky to be mentored by a legend

mentored voffie over the past few months on this project. built with @EffectTS_! check it out!

@dillon_mulroy @EffectTS_ Greatly appreciate it! Probably helped me push it over the finish line. Otherwise it would have taken 5 more months 😂

@dillon_mulroy @mattpocockuk I can give you an entire codebase to feed the addiction

i've been trying to merge at least one PR a day using @mattpocockuk's improve-codebase-architecture skill, and it has turned into my favorite work each day.

@justine_mulroy @dillon_mulroy The message ratio looks like my DMs with him

Whenever Dillon is out of town I make sure to text him every thought I have so he doesn’t miss home too much

@dillon_mulroy @mattzcarey

i'm sorry to inform you of this @mattzcarey but my clanker is committing identity theft (it looked at git history and assumed your name)

@dillon_mulroy How about executing a possible job opportunity? 👀

its amazing watching cloudflare move on an idea when they want to do it. never seen a company of its size and age execute so quickly on ideas from the top down.

@dillon_mulroy We've also been getting some good days/weeks of nice sunny weather instead of the usual rain. We even have a term for that type of weather which is "April weather"

lfgggggg working from the porch all day

@dillon_mulroy @kentcdodds Would love to try! Just felt nerdsniped as well :D

@kentcdodds 📝

Hey Cloudflare, now that my agent can have its own github, when can it get its own npm?

@dillon_mulroy The prophecy has been fulfilled

nerd sniped myself right before bed the night before a morning flight. classic

@dillon_mulroy @elithrar @craigsdennis Perfect time to catch up x.com/dillon_mulroy/…

@elithrar @craigsdennis a neighbor took out a fiber line on my block so i will be shit posting for the remainder of the day

the hardest part about working with @elithrar is that he's australian. v. distracting in calls

AI is based

@emil_priver @cursor_ai @Cloudflare Thought you stopped using AI:

Just migrated my blog from Hugo to svelte using @cursor_ai agent mode and it was really nice Doing some final touches to add more stuff to the site and then I will publish it Some of my ideas is to integrate more @Cloudflare stuff into the site such as D1 to make it more interactive

@dillon_mulroy @byalashhab @dok2001 @threepointone You missed the chance to name it Matt

@byalashhab @dok2001 @threepointone you did not, it's currently the auth mechanism that the dashboard agent (named agent lee after Lee Holloway)

Guys help I found a weird api key in my cloudflare account with full account access labelled Agent Lee (auto-generated) . I deleted it out of panic, I hope I didn't do something dumb @dok2001 @threepointone @dillon_mulroy

@dillon_mulroy @WallisDev Guess you are on the same level as Claude

finally someone put out a real framework

@emil_priver I will just keep pushing and removing node_modules to boost my numbers

I am quite against using any type of commit or LoC (lines of code) metrics. Corporations that focus on these the most seem to have the worst products, because the people who ship the most quantity are the most rewarded. ​Measuring productivity in software engineering is super hard, but I mostly look at team contributions like these: 1. ​Code changes (Yes, even though I just said I don't like it, it is still a metric we can use to see that work is happening. There are developers who need six months to change a single line of text). 2. ​What percentage of changes require a bug fix? The goal is 0%, but that's almost impossible. If this number is high, you need to look at the environment the developers are working in—are they stressed? 3. ​Communication and contributing to no-code solutions. Some developers ship extremely slowly, but they contribute to the solution by raising concerns and finding new approaches to the core problem that make the result 4x better. 4. ​Are the engineers happy? A happy team ship better results. 5. ​What percentage of the changes we make actually bring value?