
Director of SW | Indie Developer | Tacos | Fly Fishing | Pickleball | Other Stuff | Not necessarily in that order || @ewarrin
Tucson, AZ
Joined January 2013
- Tweets2.6K
- Following1.3K
- Followers337
- Likes9.2K
Eric Arrington retweeted
every single productivity hack in the world added up together saves you less time than working on the right thing instead of the wrong thing
Eric Arrington retweeted
I realized peace is not achieved through lack of pain.
But through pain tolerance.
Huge shift in perspective.
Eric Arrington retweeted
Managers have been vibe coding forever by @thekitze :D
Eric Arrington retweeted
The deployment frequency downward spiral in 6 steps:
1. Team doesn’t write sufficient automated tests and doesn’t automate deploys.
2. Team spends significant time manually testing each release and getting it to prod.
3. Releases must be batched to make manual testing practical. Testing the entire app for each ticket would take too long, and getting code to prod is time-consuming and risky.
4. Production deploys are infrequent, late, and buggy because the release is big,and risky. Manual testing is too slow and insufficient to catch all issues.
5. Management loses trust in the dev team, so it creates even more non-prod environments and more mandatory manual checks and approvals.
6. Bugs still slip through and late releases become even later due to more environments and more manual validations. So management institutes a “Change advisory board” that must approve every change and every release. This further slows progress and makes releases even bigger and thus, higher risk.
Eric Arrington retweeted
just went 12 1st places in a row against my kids at Mario Kart, this is what it taught me about B2B sales
Eric Arrington retweeted
Yes if your job is “take well-specced ticket, write code”, that’s going away. It’s been going away for 30 years.
Replying to @Swizec
Thing is, many teams are organized in a way that one or two people know that, the rest are doing the role of the LLM, executing based on the task.
All those men on the video swinging axes weren't in the machinery business, they were swinging axes.
Eric Arrington retweeted
Replying to @dhh
"computer grifter" is finally the perfect way to explain my job to the kids.
Eric Arrington retweeted
United States Coast Guard Rescue Swimmer and Petty Officer Scott Ruskin, directly saved an astonishing 165 victims in the devastating flooding in central Texas.
This was the first rescue mission of his career and he was the only triage coordinator at the scene.
Scott Ruskin is an American hero.
His selfless courage embodies the spirit and mission of the @USCG.
Eric Arrington retweeted
Replying to @ryanflorence @mjackson
The pervasiveness of React. Things have grown so much since when people were willing to give different technology a chance. While the general web ecosystem is vast. The pool that is looking at this technology is dominated by React.
We've gotten to a point where almost all of that outside of React has actually reached consensus but it is smaller part even added up. If there wasn't this consensus I could write all of this off as being novel.
Larger projects will grow faster than smaller projects, and the web constantly grows so there is no signs of React slowing down. Nothing is pushing the needle here. I'd say there are even outside forces too like the desire for JavaScript to mature. The end of fatigue. We've created a culture afraid of challenging the status quo. No one ever got fired for choosing React is said unironically. React would have to stumble considerably worse than Angular 2 migration for anything to change in the way we may have seen historically.
It isn't about the technology at all really. Those within the React ecosystem just get a huge boost and it just self propagates. I'm not sure it is a battle that can be won. I keep pushing because it is right thing to do. Technology has to progress. I've seen so many interesting approaches in the web space that could benefit so many people. I don't even dislike React. I think React is actually quite innovative for an incumbent technology. There is just so much more out there.
Eric Arrington retweeted
My pops is up 102% from a trading bot I made for him 2 months ago.
Messaged him today to sell it to my x followers.
This is what he sent me back.
"This AI Investor Bot is next level. 102% return over the last 2 months. Identifying solid companies with growth potential in trending industries. Not only tech and FANGS can produce exceptional performance. Highly recommended."
Man's giving you a full sales pitch via text message.
The bot focuses on low-cap stocks for higher returns instead of chasing the same overpriced tech everyone's buying.
Here's what this n8n workflow actually does:
→ Scans both stocks and forex markets simultaneously
→ Identifies undervalued companies in trending sectors
→ Analyzes growth potential beyond just tech/FANGS
→ Provides buy/sell signals with risk assessment
→ Tracks portfolio performance obsessively
Updated it last month with some unreal community nodes that made it even more accurate at spotting opportunities others miss.
While everyone's fighting over Tesla and Apple scraps, this thing finds the hidden gems that actually move portfolios.
My dad went from "what's a webhook" to sending me testimonials about algorithmic trading.
Follow, RT + Comment "STONKS" and I'll drop the JSON file that turned my boomer dad into a low-cap stock hunting machine.
(Disclaimer: Past performance doesn't guarantee future results, but this bot has been printing for months)
Eric Arrington retweeted
Ever seen a codebase that makes you think "You don't need an engineer, you need an exorcist"?
Eric Arrington retweeted
my dad sat me down once and said:
“There are only two jobs in the world: building or selling. If you’re not doing one of those, you’re just an expense.”
still think about this.
Eric Arrington retweeted
"Developers are drawn to complexity like moths to a flame, frequently with the same result."
- Neal Ford
Eric Arrington retweeted
the biggest trick the devil ever played was convincing management that MBAs should determine how software planning works



















