Abenezer ♛

"Man suffers only because he takes seriously what the gods made for fun." -Alan Watts

[Bun @bunjavascript]

Bun 1.4

- Fixes over 2,900 GitHub issues
- +1,517 tests from the Node.js test suite
- Reduces idle CPU by 5x
- Reduces memory usage by up to 35%
- Starts up to 50% faster on Linux
- Rewrites Bun in Rust

Thank you everyone who contributed since Bun 1.3!

https://t.co/3YjnuhjE8s

[Lee Robinson @leerob]

Code is actually the right abstraction.

Too often I see the future of software engineering diminished down to, effectively, writing and reviewing markdown files.

Yes, it will be hard to review thousands of lines of agent code. But maybe the takeaway is that you want less code?

Rather than just giving up ("well I guess we won't read the code, or we'll read this lossy markdown summary") this should be a signal forcing you to think about better systems.

- How can we make our codebase more verifiable? For example, fast/robust/stable tests, or moving to a typed language.

- How can we deslop or improve the architecture/abstractions of the code generated by agents? For example, spending more time up front on the codebase architecture/types before yolo generating all of the code.

- How are we going to maintain and evolve this codebase over time? The slop compounds. One great solution here is... you guessed it, learning from the past decades of software engineering! For example, you might just have the wrong abstraction entirely, leading to a ton of duplicated code.

I think the markdown folks *are* right in some ways. If you are using skills every day, for many different prompts and workflows, isn't that effectively "coding with markdown"? Kinda.

There's been plenty of ink spilled on the merits and benefits of skills. To me, skills make your style of working legible for agents. They don't replace code and that's not really the point.

In reality, there's this messy and constantly re-evolving future in which both of these things are true:

1. Skills (and markdown) are important for how you give input to the agents and ensure high-quality code & systems are created
2. Looking at the actual code will not be replaced by markdown summaries or a collection of spec documents that ignore the lower level details of the code

In summary: reality has a surprising amount of detail (and nuance)!

[Abenezer ♛ @abenezer_x]

@better_auth An idea scenario would be adding a {region} or {area} to the user list so it would help us distringuish if the user(email) exists in the region.

[Abenezer ♛ @abenezer_x]

@better_auth we currently have a multi-area plugin but its a whole mess and as we are using both next and expo its a whole mess trying to use the authclient so we manual ffetch some apis

[Abenezer ♛ @abenezer_x]

@aidenybai Maybe an extra keybind, when pressed auto-opens that part of the code in your editor.

[Abenezer ♛ @abenezer_x]

@leerob Can I get the name of the cursor theme and browser. Please and Thank you

[Zeno Rocha @zenorocha]

Today, we're launching a new React Email website.

It shows how to build email beautiful templates using Tailwind + React + TypeScript.

Check it out → https://t.co/72VI5p3RVE

[Visual Studio Code @code]

Today, we're announcing plans to make VS Code an open source AI editor.

We believe AI development should stay true to VS Code's core principles: open, collaborative, and community-driven. Let's build the future of software development together.

https://t.co/C3ffio6X88

[Abenezer ♛ @abenezer_x]

@is_abenezer On your laptop?

[Peter Yang @petergyang]

"You can have a great strategy for the next billion-dollar developer product, but the battle is won in the trenches of daily iterations."

I love this clip from Lee Robinson (VP Product, Vercel). @leeerob helped scale Vercel to 1M+ developers and has some of the clearest thinking of developer marketing that I've read.

We talked about:

- Getting into the developer's mindset
- 3 pillars of a great developer experience
- Why developers don't trust your marketing

A few quotes from Lee:

"Most developers don't adopt a tool the first time they hear about it. It's probably the 10th time."

"Great documentation is great writing. The tech industry is plagued with jargon and fluff. It would be much cleaner if people wrote more like how they talk."

"The battle is won in the trenches. It could be a two-paragraph docs change or a small UX improvement. For every developer that complains, 100 more won't say anything."

📌 Watch now: https://t.co/IENokWJEUw

[Abenezer ♛ @abenezer_x]

@marclou 1200$

[vaxry @vaxryy]

sounds like a dream

[Abenezer ♛ @abenezer_x]

@animecoin @arbitrum @Azuki Lets go!🌍