Andrew Fecheyr (@andruby) header
Andrew Fecheyr (@andruby) profile picture

šŸ‡§šŸ‡Ŗ&šŸ‡æšŸ‡¦. Scaling Startups. Engineering Director. Now: Head of Product Design @getsilverfin.

Lier, BE
Joined April 2009
Photo by Andrew Fecheyr (@andruby)Photo by Andrew Fecheyr (@andruby)Photo by Andrew Fecheyr (@andruby)Photo by Andrew Fecheyr (@andruby)Photo by Andrew Fecheyr (@andruby)Photo by Andrew Fecheyr (@andruby)Photo by Andrew Fecheyr (@andruby)
Andrew Fecheyr retweeted
Just so we are all on the same page: * The Rust version has hundreds of commits, with multiple optimizations rounds, over several days. The others have 1 or 2 commits from an initial agentic rewrite * Based on the available documentation, different things were asked from each attempt. The agents.md from Go mentions the Rust version was the canonical example. The Elixir one mentions it was the Rails one * While we don’t have the full prompts, it seems they were vague, allowing the agents to make non-language architectural decisions that impact results (such as how closely it should replicate Rails’ drawbacks) It is actually amazing how quickly we can have full-blown rewrites up and running. But if we want to take conclusions from the data presented, it is important to understand the process behind it.
The agents finished porting Campfire to Laravel and Django too. I'm sure there are optimizations that could be found there too, but the whole point is to get a sense of how frontier agents do with different environments out the box. github.com/basecamp/once-cam…
39
86
18
1,110
52,669
Andrew Fecheyr retweeted
The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage. I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care. But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently. For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios. But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.
249
1,175
225
10,648
565,059
Andrew Fecheyr retweeted
Most software engineers are facing an identity crisis bordering on depression. As CTOs aggressively evangelize tokenmaxxing, a class divide ensues. The lazy. The lazy push code. They don't write it. They don't manually test it. They don't even read it. They're on autopilot. See Jira ticket, prompt for task, submit code. Many of them are barely on their computer the whole day. A comment on the PR asking why they did this? The lazy ask AI. A Slack message? The lazy ask AI. Need to prepare for standup? The lazy ask AI. As long as it sounds enough like them and isn't detected. Some of the lazy are even overemployed, and work multiple jobs. The lazy smart ones get away with this, and even rewarded. After all, software engineering for the lazy is just a dance to convince your colleagues you're smart and hard working. The craftsmen. The craftsmen are tired. Very tired. 15 PRs in queue. Slack blowing up. The entire burden of review falls on the craftsman. The burden of understanding. They try. They work their way through the code, thoughtfully commenting to improve what ships. The response? A lazy: "That's a clever idea! You're absolutely right." with an incorrect change. It's fine, the craftsman says. I can fix them. They write a doc urging his colleagues to be better. The next day? 20,000 line PR to review. Day after day, their workload grows. Bugs seep into production. No one seems to care. Another round of AI is thrown at it. Their animosity to their colleagues rises. Eventually, they give up. It's just not what it used to be. The craft they loved is dead. They eventually wake up, a lazy. This isn't all companies. Many companies are genuinely more productive, adopt the right set of principles and practices around AI development and have highly talented teams that trust each other. It tends to happen in bigger companies that are 10+yrs old with a higher talent variance. But it happens. A lot.
333
482
115
5,098
1,014,967
Andrew Fecheyr retweeted
We're dealing with a major malicious attack on @rubygems right now. Signups are paused for the time being. Hundreds of packages involved - mostly targeting us, but some carrying exploits. The team has been on this for hours. More details to follow once we're through it. #ruby
38
294
68
1,616
689,814
Andrew Fecheyr retweeted
The web was amazing prior to the reactification of everything šŸ˜„. Hotwire's Turbo framework is based on Chris Wanstrath's original Pjax concept (that powered GitHub in those early years). This kind of speed is still possible!
GitHub's performance in 2013. The web used to be so fast.
78
73
16
1,425
358,052
Andrew Fecheyr retweeted
Seems like Ruby is pretty well positioned as a language that is token-efficient when used with LLMs. Source "Which programming languages are most token-efficient?" by Martin Alderson martinalderson.com/posts/whi…
47
89
50
407
231,650
Andrew Fecheyr retweeted
It is finally here: Tidewave now supports Claude Code and OpenAI Codex. Tidewave unlocks the full-stack potential of your favorite coding agent by tightly integrating it with your web app and web framework at every layer, from UI to database. More info šŸ‘‡
14
49
12
346
101,944
Andrew Fecheyr retweeted
Not unity. Not unreal. Kitten space agency. Custom engine. Dust storm on Mars. Releasing for free, powered by contributions. Will have some tech firsts. See for yourself.
63
133
14
1,967
92,469
Andrew Fecheyr retweeted
What is a Wave but a Thousand Drops? I started my journey into video game development more than 25 years ago, back before there were any books or courses, back before there were engines to license, back before it even felt like a viable career. My high school friends and I spent our summers in Burlington, Vermont not working for others, but working to try to create a video game. Every summer we tried and every summer we failed. Failed to have anything even remotely playable before the leaves developed their autumn colors and threatened to fall. But we kept trying, until the final summer after my college graduation in 1996, when just two of us worked through the fall and got our first game playable: an underwater (!) Star Control II clone called Aquarium Fighter. When I played it against my friend for the first time, and I evaluated the fun, controls and balance, I instantly became hooked. Hooked on making games. Hooked on making not-fun-things (but with potential), fun. That game helped me land my first professional game programming job which I used to pay off my credit cards, and I started iterating through the now-familiar cycle of making money to make games. Now we’re halfway to 2026 and the world is a very different place. Anyone can learn how to make a game on YouTube using free engines. But making money off of making a game has become truly brutal. Like the world’s wealth distribution, it’s feast or famine. Game development is a career now, and it can be a very profitable one. And the artistic heights that games have reached is jaw-dropping: Starcraft. Braid. Limbo. Minecraft. League of Legends. Hades. Inscryption. I dreamed, but never thought, that the design, technology, art and business models of these games would one day be possible. Nor would I ever have believed that games could overtake Hollywood, even if they ā€œweren’t artā€. Without realizing it, I started Unknown Worlds in 2001 by making the Half-Life mod Natural Selection. I worked with a distributed team back before a health crisis mandated it and we released not half-baked games, but documents describing level design and textures for making those levels, with the hope that the community would make maps. Lo and behold, they did. And we eventually hired some of those people, giving them careers at Unknown Worlds, however shaky the long-term prospects might be. I asked the community to send me $20 bills in the mail so I could keep working on the game, and you did. $18k was a tough salary to live off of, but I made it work and loved every moment of it. Like a design hook, but I was hooked on design. So hooked that I spent 10 years making the sequel. There’s no way that could’ve happened without Max McGuire and his belief that the game was something special. With that, we made just enough money to get Subnautica into a stripped-down early access, which allowed us to find the fun. It didn’t have submarines, base-building, story or survival. But through the early access process, the community helped guide us forward until we found something we all loved. Something we loved to make and something that millions loved to play. There's no way it would've been as successful if we had waited until v1.0 before releasing it to the public. I tell you all this because I want to tell you that game development is in my blood. So is iteration and early access. Our games have thrived because of it, and one of our games failed because we thought we knew better. I was most passionate about that game, and it fell flat. We worked on it 5 years before our early access, thinking that this time we were experts and we knew better. But fewer people played that game than even that humble Half-Life mod. Even though our studio had financial success in that period, and even though many fans fell in love with the game, it really wounded me and I needed time to heal. Sometimes it feels like I’ll never get over that one. So with all this as background, I hope you can see why we were so excited to release Subnautica 2 into early access. Many of the folks that started the journey with us nearly 20 years ago have worked hard on Subnautica 2, and they're joined by some incredible new talent who were drawn to the studio by their love of the games and their passion for the way we've made them. We know (and love) that the expectations for this sequel are high. But the team has poured their hearts into the game and their dedication really shows. We helped pioneer early access and our community seems to love it just as much as we do. It’s the best way to develop a game like this. So you can see why for Max, Ted, myself, the Unknown Worlds team, and for our community, the events of this week have been quite a shock. We know that the game is ready for early access release and we know you’re ready to play it. And while we thought this was going to be our decision to make, at least for now, that decision is in Krafton’s hands. And after all these years, to find that I’m no longer able to work at the company I started stings. I want you to know that whatever happens to the founders, to the team and to the game, our priority is, and has always been, to make the best damned game we can for the best community in the world. With your Gorge plushies and your hand-drawn fish fan-art, and yes, your hard-earned dollars, you’ve supported us in every way, in every season, cold and warm, since Half-Life modding was even a thing. And I also want you to know that this is not where the story ends. -Charlie (ā€œFlayraā€)
124
27
986
81,747
Andrew Fecheyr retweeted
Everywhere I’ve worked, the GraphQL API was slower than what it replaced.
that’s him. he said graphql was a good idea.
129
135
26
3,692
448,737
Andrew Fecheyr retweeted
Special #RailsWorld announcement: @yukihiro_matz and @dhh will share the stage for the very first time for a fireside chat about #Ruby, #Rails and all things #opensource. This special conversation will be moderated and hosted by @Shopify founder and early Rails Core member @tobi. We are beyond excited that Matz has found time in his epic conference schedule to join us for this chat. This is a session that you don’t want to miss! rubyonrails.org/2024/8/7/mat…
17
96
31
570
180,913
Andrew Fecheyr retweeted
When Ruby on Rails was launched over twenty years ago, I was a twenty-some young programmer convinced that anyone who gave my stack a try would accept its universal superiority for solving The Web Problem. So I pursued the path of the crusade, attempting to convert the unenlightened masses by the edge of a pointed argument. And for a long time, I thought that's what had worked. That this was why Ruby on Rails took off, became one of the most popular full-stack web frameworks of all time, inspired countless clones, and created hundreds of billions in enterprise value for companies built on it. But I was wrong. It wasn't the crusade that did it. Since those early days, I've talked to thousands of programmers who adopted Ruby on Rails back then, and do you know what virtually every one of them cite? That original 15-minute blog video. Which didn't contain a single comparison to other named solutions or specifically pointed arguments against alternatives. It just showed what you could do with Ruby on Rails, and the A/B comparison automatically ran inside the mind of every programmer who was exposed to that. That's what did it. Showing something great, and letting those who weren't happy with their current situation become inspired to check it out. Because those are the only people who is able to convert to your cause anyway. I've never seen someone who was head'over'heels in love with, say, functional programming be won over by arguments for objected-oriented programming. You simply can't dunk someone into submission, and it's usually counterproductive if you try. But you can absolutely attract people who aren't happy with their current circumstances to give an alternative a chance, if you simply show them how it works, and allow them to conclude by themselves how it would make their programming life better. What I've also come to realize is that programmers come in many different intellectual shapes and sizes. Some of those shapes will click with functional programming, and that'll be their path to passion. Others will click with vanilla JavaScript, and be relieved to give up the build pipelines. Others still will find their spirit in Go. This is great. Seriously. The fact that working for the web allows for such diverse ecosystem choices is an incredible feature, not a bug. I found my life's work and passion in Ruby. I have friends who've found theirs in Python or Elixir or PHP or Go or even JavaScript. That's wonderful! And that's really all I want for you. I want you to be happy. I want you to find just that right language that opens your mind to the beautiful game of coding in your most compatible mode of conception, as Ruby did for me. This is not the same as just saying "everything has trade-offs, use what works best". That to me is a bit of a cop out. There is no universal set of trade-offs that'll make something objectively "work best". Half the programming conundrum lies in connecting to an enduring source of motivation. I wouldn't be a happy camper if I had to spend my days programming Rust (but I LOVE so many of the tools coming out of that community by people who DO enjoy just that). It also doesn't mean we should give up on technical discussions of advantages or disadvantages, but I think those are generally more effective when performed in the style of "here's what I like, why I like it, so look at my code, my outcomes, and see if it tickles your fancy too". Programming is a beautiful game. I would give up all the fancy cars I have in a heartbeat, if I was made to choose between them and programming. The intellectual stimulation, the occasional high from hitting The Zone, is such a concrete illustration of Coco Chanel's "the best things in life are free, the second best things are very expensive". Programming is one of those "best things" that is virtually free to everyone in the Western world (and increasingly so everywhere else too). So let's play that beautiful game to the best of our ability, in the position that flatters our conceptual capacities the most, and create some wonderful code.
100
419
115
3,163
708,330
Starship liftoff filmed at 2400fps! Our Road to Mars episode featuring footage filmed with @freeflysystems Ember cams is live. youtu.be/cjgBsZyPnBQ Huge thanks to our supporters & @Erdayastronaut
217
889
188
4,617
591,624
Andrew Fecheyr retweeted
What are the odds? šŸ˜‚
10,343
18,753
1,394
204,435
48,409,564
Andrew Fecheyr retweeted
Reading the classic ā€˜Getting Real’ by @jasonfried and @dhh and I can’t believe how relevant this stuff still is, or maybe even more relevant today. This book was written before my professional career and I’m considered old already 🤣 This is part of the chapter ā€˜Alone Time’. ā€œGetting in the zone takes time. Like REM sleep. It is where the real magic happens.ā€
9
12
3
103
57,891
Andrew Fecheyr retweeted
Ready for take off šŸš€šŸš€šŸš€ cc @maartengm @BeeckmanEvert @itpocket @lemaire
Showpad-oprichter Pieterjan Bouten richt start-upstudio Entourage op tijd.be/ondernemen/durfkapit…
2
3
1
33
3,021
Andrew Fecheyr retweeted
We're selling ONCE/Campfire through @shopify. It's a great platform for selling digital products as well. And it's fun to see all these visualizations of live sales as they roll in. You did alright, @tobi šŸ˜„āœŒļøā¤ļø
21
20
5
675
139,510
Andrew Fecheyr retweeted
šŸŽ§ New Hackers Incorporated! I've always wondered how @37signals builds new products, where there's no way the work will fit into a six-week cycle. So I went deep with @jasonfried about the entire year-long process of building the new HEY Calendar šŸ—“ļø share.transistor.fm/s/5e7f58…
10
16
5
262
99,087