This is your weekly reminder to buy flowers.
You know, buy yourself flowers. Put them in your bathroom so every day, when you wake up, you can see how lovely they are and have a reminder that you care about yourself.
Remind yourself that you can find appreciation and beauty in useless things.
- Drafted a blog post
- Used an LLM to meticulously improve the argument over 4 hours.
- Wow, feeling great, it’s so convincing!
- Fun idea let’s ask it to argue the opposite.
- LLM demolishes the entire argument and convinces me that the opposite is in fact true.
- lol
The LLMs may elicit an opinion when asked but are extremely competent in arguing almost any direction. This is actually super useful as a tool for forming your own opinions, just make sure to ask different directions and be careful with the sycophancy.
A lot of people quote tweeted this as 1 year anniversary of vibe coding. Some retrospective -
I've had a Twitter account for 17 years now (omg) and I still can't predict my tweet engagement basically at all. This was a shower of thoughts throwaway tweet that I just fired off without thinking but somehow it minted a fitting name at the right moment for something that a lot of people were feeling at the same time, so here we are: vibe coding is now mentioned on my Wikipedia as a major memetic "contribution" and even its article is longer. lol
The one thing I'd add is that at the time, LLM capability was low enough that you'd mostly use vibe coding for fun throwaway projects, demos and explorations. It was good fun and it almost worked. Today (1 year later), programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny. The goal is to claim the leverage from the use of agents but without any compromise on the quality of the software. Many people have tried to come up with a better name for this to differentiate it from vibe coding, personally my current favorite "agentic engineering":
- "agentic" because the new default is that you are not writing the code directly 99% of the time, you are orchestrating agents who do and acting as oversight.
- "engineering" to emphasize that there is an art & science and expertise to it. It's something you can learn and become better at, with its own depth of a different kind.
In 2026, we're likely to see continued improvements on both the model layer and the new agent layer. I feel excited about the product of the two and another year of progress.
🚀 Just released my first Obsidian plugin — Agent Client Plugin!
Bring AI coding agents (Claude Code, Codex, Gemini CLI, etc.) directly into your vault.
🧩Organize notes, search the web, and automate workflows with MCP tools.
Built on Agent Client Protocol (ACP) by Zed.
@_MathAcademy_ Thanks for the reply. I've just resent the email to [email protected] and DM'd you my email address so you can locate it easily. Please let me know once you receive it.
Thank you @code_scribendi for writing this helpful article.
Fetch API vs. Axios vs. Alova: Which HTTP Client Should You Use in 2025?
https://t.co/GVUmsSLbZd
Thank you @DoableDanny for writing this helpful article and making this video.
How to Use React's Context API – Tutorial with Examples
https://t.co/IzBXL8a2e6