Effect is verbose is an argument that makes no sense, it is verbose compared to code that only cares about the happy path, that is not testable and doesn’t integrate telemetry. Compared to production grade code Effect is terse.
Take a look at your favourite skill.
Go on, take a look.
Check for lines like:
- "Make the commit message very detailed"
- "Be thorough"
- "Make the implementation easy to read"
What do these lines have in common?
They're no-ops. They do nothing to change the agent's behavior.
Agents always write good commit messages. They always try to be thorough. They always try to create easy-to-read implementations.
Try removing them. Does the output change? No? Then the line was a no-op.
Agent-authored skills are LITTERED with no-ops. Entire paragraphs and sections of text that does nothing to change the agents' behavior.
No-ops make skills harder to evaluate, harder to maintain, and burn tokens uselessly.
Learn to spot them, test them, and remove them. Your skills will thank you.
SkillKit is finally live on the Mac App Store 🎉
A simple macOS app for developers using agentic programming skills.
Built for agentic coding workflows and anyone who prefers coding over setup.
https://t.co/htSbzfzWei
#macOS#Codex#Claude#Gemini#Copilot#AgenticProgramming
I'm Boris and I created Claude Code. Lots of people have asked how I use Claude Code, so I wanted to show off my setup a bit.
My setup might be surprisingly vanilla! Claude Code works great out of the box, so I personally don't customize it much. There is no one correct way to use Claude Code: we intentionally build it in a way that you can use it, customize it, and hack it however you like. Each person on the Claude Code team uses it very differently.
So, here goes.
I watched the whole segment about error handling in @theo 's recent stream https://t.co/vynC72p3oW you should probably wait for the edited version but I wanted to share a few things while I am still fresh from watching. So a thread:
On parle de cette Masterclass ? Ça faisait longtemps que je n’avais pas vu une vidéo qui pousse autant à la réflexion. Et qui nous concerne tous.
A-must see.
Lien: https://t.co/kJmrfh5ZDr
Cc @ego_v1
Effect has been nominated for The Most Exciting Use of Technology in the JavaScript Open Source Awards, part of JS Nation @thejsnation.
Use the link below to vote for Effect! ✅ The winners will be announced at the JS Nation Conference on June 13.
https://t.co/9WObPfAU97
@KingRomstar Once you’re dealing with non-happy-path scenarios such as error handling, observability, concurrency, interruption, retry behavior or similar you’ll find Effect to come in handy.
What do you need to build a performant application?
1) observability
2) ability to refactor
3) concurrency
With @EffectTS_ you get it all, even though it has overhead compared to non effect code it is much easier to write performant code so you actually do it
"Why Effect Is More Important Than ZIO"
My latest talk, just published on YouTube, talks about effect systems and growing new OSS technologies & communities.
What I say may surprise you. Don't miss it! 👇
https://t.co/bOB0FInhnl
Effect:
Effect replaces most one-off libraries with a unified standard library and gives you new superpowers when building apps with TypeScript including:
◆ Type-safe error handling
◆ Better composability & code reuse
◆ Built-in observability (e.g. via Open Telemetry)
Effect gives me confidence to make (large) changes to my code without breaking my app while providing the best DX I've ever experienced in TypeScript.
It takes a bit to get used to it but it's well worth it to learn (similar to how React was a bit different initially).
This video is a good starting point:
https://t.co/m1lb2l5KPM
Website: https://t.co/tDWz0obRZ0