Sam Goddard

2.3K posts

Sam Goddard banner
Sam Goddard

Sam Goddard

@samuelgoddard

Staff Design Engineer @intercom working primarily on @fin_ai — Big fan of labradors.

Nottingham Katılım Nisan 2009
175 Takip Edilen624 Takipçiler
Sam Goddard retweetledi
Aurelien
Aurelien@Aurelien_Gz·
my brain can't process what i just witnessed on this site.. i have so many questions » ac-bu.info/kindolphin
English
26
219
2.1K
96.1K
Sam Goddard
Sam Goddard@samuelgoddard·
Perfecto
Karri Saarinen@karrisaarinen

It’s 2028. Welcome to the token economy. We realized that all software and activities can be shaped to spend tokens, which is good, because more tokens we spend, the more productive and happier we are as a society. My Openclaw agent goes to wake up the alarm agent, which then after running for 5 minutes in a new sandbox and burning 500 tokens, plays a sound to wake me up. My news agent reads all my email, including spam, crawls the web, and gives me a 5-line summary of the world. Very efficient. I get to my desk. 100 agents have been chatting all night. 10k LOC ready to merge. I tell my merge agent to press the merge button. Check my company token leaderboard. 15,000 tokens burned and I haven’t even done anything yet. I tell my manager agent to boot up my other agents. First thing they do is vibe code a Slack clone so they can post progress updates to each other. I tell them to find something to do and go to lunch. Back from lunch: Company leaderboard says 25,000 tokens burned. More than Chad. Very nice. At 80,000 tokens a day you unlock Platinum tier, which gives access to faster models that can burn tokens even faster. Agents built another 10k LOC while I was out. I don't know what it does so I tell my review agents to tear it apart, rebuild it, and merge it again. Excellent token utilization. Then I ask my social media agent to post that software engineering is dead because agents do it now. More tokens. I get hungry, so I tell Openclaw to vibe code DoorDash. We call it ClawDash. Iterate on the logo for about 5mins with my designer agent. We make the red with some lobster claws. Very appropriate. It takes 5 hours, several new agents to ping the status, and one human recruiter signing up a Mexican restaurant, but eventually my food arrives. I heat it in the microwave with a dedicated heating agent program I built for this purpose. Before bed I check the my dishwasher dashboard. My agents run through the log history since dawn of time, and tells me that it says it ran 23 hours ago, and was opened shortly after so it’s probably clean. Final leaderboard check: 81,239 tokens burned. Platinum achieved. I now have access to new models faster, which burn tokens faster, and will receive Platinium plaque in the mail. Time to wind down with some generated Fraser episodes which I tell my entertainment product agent to script, review, and finally generate. Important thing is the token burn never stops.

Español
1
0
0
69
Sam Goddard retweetledi
ThePrimeagen
ThePrimeagen@ThePrimeagen·
I have been thinking about this a lot. I think for a great many of engineers, the ones who did it because they loved it only to discover that money was in fact at the end of the rainbow found both the journey and the destination satisfying. In fact, I think I can argue with authority that the destination was only satisfying as the journey was difficult. The hard-fought evenings spent toiling away on an idea and codebase that slowly gives way to your vision was an incredible experience. The group of people that fell into this category of hard-fought journey and destination we will call them tinkerers. One thing tinkerers have always hated is the already known problems. The journey is clear as day. The obstacles minor inconveniences. Its purely a matter of typing the solution into the terminal. This is also why I think so many of this group goes out and does open source, or starts companies. Work largely falls into this category with few exceptions. From this reason is why I largely find UI work soul sucking. I know the solution, its a matter of just looking up the details and putting it into my editor. yawn. CSS, flex box this, grid that, put the tailwind classes in the bag. To me, the LLM software world is with little to no journey and discovery. Its more of simply taking my high level idea and just formulating it into testable, atomic chunks that can be verified. I have traded my favorite part, discovery and raw creation, with itemized list of TODOs and patience and "No Mistakes." To this, every morning from 6 to 9 I simply just hand code every thin. even UI things. It is because I want journey and discovery and raw creation. Maybe one day comes and its just so futile that I stop this. But for now, I still see such great value in this. I see such better thought through products. Because slowing down and truly thinking through everything. The architecture, the design, everything is an expression of discovery and creation. And I love it. I am sure there will come a day, maybe even in the next 6 months where I change my mind. For now, I pursue the love of the game intentionally. I do also believe that there exists people who get the same joy I got from building with tears and sweat by prompting LLMs. I am positive of it. I just don't understand how. But people love UI work. I also don't understand that.
Adam@adamdotdev

Programming was deeply satisfying work to me. Work for hours/days before getting the payoff of the code working well on your machine. I’m feeling so much friction now to open the editor and do this kind of task by hand, but also increasingly depressed with the nature of work in an AI assisted dev workflow. Back and forth prompting seems to eat at my soul. Need to find a balance that brings back some of the toil.

English
185
197
2.8K
310.4K
Sam Goddard retweetledi
Nadieh Bremer
Nadieh Bremer@NadiehBremer·
📣 NEW! I’ve just released the BIGGEST and perhaps most creative project I’ve ever worked on! “Searching for Birds” searchingforbirds.visualcinnamon.com 🐤 A #dataviz article & exploration that dives into the data that connects humans with birds, by looking at how we search for birds.
English
150
1.3K
6.6K
416.2K
Sam Goddard retweetledi
Karri Saarinen
Karri Saarinen@karrisaarinen·
Whenever a new design to code tool comes around, people get excited. It’s considered the holy grail of design. You can now design with code. This is the final evolution. But I don’t agree. It’s only the holy grail if you value output higher than the process of design. Whenever a designer becomes more of a builder, some idealism and creativity dies. Not because building is bad, but because you start out including constraints earlier in the process than they should. I’m one that very much thinks design is ultimately what is shipped. But before it shipped, there is a lot of stages that don’t benefit from code or some implementation constraints. In architecture, a lot of the best work is started with sketches and some of the best architects still draw by hand. People forget that the creative process is not about tools. It’s about forming a vision, and then translating that vision into some form. You can use various tools as part of the process, but designers job is really communicating that vision. Once you become the architect and the builder, or the designer and the developer, you start making more conservative bets. You gravitate to what you already know is feasible or supported. You make smaller iterations. You stop dreaming something big. This is not design. Designers, don’t do that. Your job is to imagine the future, and sometimes code and convention gets in the way. Use tools. Understand the domain. Get close to the medium. But don’t lose your greatest strength ability to dream. Work with engineers to realize those dreams. Designing in code is just a path to local maxima and ruin.
English
77
148
1.3K
240.3K
Dominic Nguyen
Dominic Nguyen@domyen·
@samuelgoddard @intercom @cursor_ai @figma We're working on a Storybook MCP in service of your exact workflow. Fancy a chat to see how we can help? I also want to learn more about your workflow because we have a similar landing page generation challenge.
English
1
0
0
111
Sam Goddard
Sam Goddard@samuelgoddard·
This week at @intercom we reached a pretty impressive AI milestone in team web, generating an entirely pixel perfect Figma design from a URL copied into a single prompt, using advancements within our design system, codebase, @cursor_ai rules, and @figma MCP - let's dive in 🧵
English
10
3
5
682
Sam Goddard
Sam Goddard@samuelgoddard·
@dqnamo @intercom Design engineer at Intercom here 🤝 there are actually 2 of us on the web team 😊
English
0
0
7
99
JP
JP@dqnamo·
As far as I’ve seen @intercom is the only company that has great “design engineering” but doesn’t seem to designated design engineer roles. I wonder why that’s the case 🤔
English
1
0
1
292
Sam Goddard
Sam Goddard@samuelgoddard·
@domyen @intercom @cursor_ai @figma Exactly yeah :) our eng and design team maintain our design system in Storybook, which we use to provide extra documentation around our components to AI models, generally our code components are mapped to the same props as our Figma DS so it works really well with Figma MCP
English
1
0
1
115
Sam Goddard
Sam Goddard@samuelgoddard·
@intercom @cursor_ai @figma As an engineer, it's easy to look at these coding models as a threat / shortcut / slop machine, but the groundwork behind this video is months of engineering and design collaboration, really showcasing the kind of impact they can have when leveraged under the right circumstances
English
0
0
0
151
Sam Goddard
Sam Goddard@samuelgoddard·
@intercom @cursor_ai @figma It definitely still has teething issues, but this is a pretty huge milestone for us. Massive shoutout to the entire team who have got us to this place 🚀
English
0
0
0
123
Sam Goddard
Sam Goddard@samuelgoddard·
@intercom @cursor_ai @figma As someone that takes a lot of pride in well structured, maintainable code and design finesse, this work is particularly exciting, really enabling and empowering the team to contribute towards shipping polished pages on our website without adding burden to our codebase
English
0
0
0
135
Sam Goddard
Sam Goddard@samuelgoddard·
@intercom @cursor_ai @figma The attached video showcases this, the first 4 minutes or so is a bit more engineering context heavy, if you just care about the output skip to around 4:40
English
0
0
0
110
Sam Goddard
Sam Goddard@samuelgoddard·
@intercom @cursor_ai @figma This process now enables non eng staff such as design / pm to own the entire process within our prod codebase while adhering to the high standards expected from eng. This is something we have already been enabling but the quality wasn't quite there, often meaning a lot of QA
English
0
0
0
109
Sam Goddard
Sam Goddard@samuelgoddard·
@intercom @cursor_ai @figma The currently process for this work would generally be: - Figma is handed from design to eng via a handoff call - Engineer spends a day or more building out the page - Preview link is generated and sent for design QA - Revisions requested, which the engineer picks up
English
0
0
0
127
Sam Goddard
Sam Goddard@samuelgoddard·
@intercom @cursor_ai @figma For some additional context, this kind of page build would usually require: - On avg around a day of an engineers time - Good foundational context of our codebase and it's tech - A level of quality / finesse on top of that understanding - Design <> engineering handover / syncs
English
0
0
0
115