I hack on @EffectTS_

Joined April 2008
43 Photos and videos
Is the X timeline rediscovering ralph loops all over again?
1
6
327
Tim Smart retweeted
We on the @EffectTS_ team we often recommend cloning the Effect repo into your project so your agent can explore the source directly. I finally wrote up why it works and how to set it up: effect.website/blog/the-one-…
20
37
404
30,346
GenServer meets effect: github.com/tim-smart/effect-… You can use them with effect cluster, rpc or effect atom.
13
14
168
11,457
Effect HttpClient is the correct choice
Mar 31
🚨 CRITICAL: Active supply chain attack on axios -- one of npm's most depended-on packages. The latest axios@1.14.1 now pulls in plain-crypto-js@4.2.1, a package that did not exist before today. This is a live compromise. This is textbook supply chain installer malware. axios has 100M weekly downloads. Every npm install pulling the latest version is potentially compromised right now. Socket AI analysis confirms this is malware. plain-crypto-js is an obfuscated dropper/loader that: • Deobfuscates embedded payloads and operational strings at runtime • Dynamically loads fs, os, and execSync to evade static analysis • Executes decoded shell commands • Stages and copies payload files into OS temp and Windows ProgramData directories • Deletes and renames artifacts post-execution to destroy forensic evidence If you use axios, pin your version immediately and audit your lockfiles. Do not upgrade.
4
3
129
15,395
Soon 👀 An Effect toolkit for building custom coding agents.
16
15
240
11,107
On a side quest 👀
3
4
49
4,870
Tim Smart retweeted
Last week we launched Effect v4 Beta 🚀 If you missed the announcement, here’s a recap of the initial overview -- what changed under the hood, what to expect during the beta phase, and how to approach migration: youtube.com/watch?v=j7U4Quue…
6
40
4,373
A year in the making! Excited to see people start playing with it. But how did we make Effect both smaller and faster? A thread 🧵
Effect v4 is in beta. 🚀 Rewritten runtime. Smaller bundles. Unified package system. The most ambitious release we've made so far. Here's what's new. 🧵
2
11
125
11,737
Also every other module has been given the same treatment. Instead of creating interpreters for everything (such as Stream or Schedule), modules now directly build upon Effect. Which improves both bundle size and performance. In some cases streams are 100x faster!
1
23
968
All of this work has resulted in a leaner, simpler library that feels nicer to use. There are many other improvements in Effect v4 I could talk about, but for now I encourage you to give it a try and tell us what you think!
29
919
Effect v4 Q&A! Feel free to hang and ask questions. twitch.tv/timmeeeeeeeeh
3
27
1,410
Assigning tasks to different models seems to be working quite well. Codex for the serious coding work, opus for things like frontend tasks or more "creative" work.
3
3
21
1,803
When it comes to interruption, just "killing a process" is not enough, especially when it is just a task within a larger process. Interruption should be another "code path" - if you interrupt a database query, the connection should be returned to the pool and so on.
Replying to @saltyAom
Also the “Effect fix this” is really annoying Yes but also no Effect is a nice abstraction but still it’s JavaScript AFAIK, Effect make your code split into small “tasks” that are connected together and check between each if it should continue I think I make it very clear that you can’t stop ongoing Promise and NOT check between each promises if it should the next promise should run Which is an entirely different thing Orchestrate multiple functions and check for stop between each is not equal to stop the process entirely similar to “kill the process”
1
3
37
5,609
There will need to be a fundamental shift to fix this. AI output quality is correlated to the context quality, and generally AI gets context from the current codebase. So, right now engineers are still responsible for fixing shit codebases.
A possible future: For the last 30 years, devs have made the sensible assumption that every time a human touches a codebase under time pressure, the codebase gets less maintainable. This is called software entropy. It's only possible to escape by continual monitoring and improvement. Or by employing ONLY 10x devs (impossible). The current generation of LLMs aren't currently good enough to escape software entropy. Without careful supervision, they make codebases worse. But soon, they will be good enough that they will make the codebase better each time they touch it. At that point, we won't need human review any more. Codebases will be better as a black box. We'll review inputs and outputs. Before Opus 4.5, models produced software entropy at an alarming rate. Opus 4.5 was the first time I felt like the entropy was manageable. Soon, there might not be any entropy at all.
2
1
12
1,008
Switching keyboard layouts is brutal
7
25
3,104