morgan

1.6K posts

morgan banner
morgan

morgan

@MorgantWillis

Principal Cloud Technologist at @awscloud ☁️ 👩🏼‍💻I help developers build on AWS and I tweet about it (opinions are mine alone). Significantly snarkier IRL

Katılım Nisan 2011
556 Takip Edilen5K Takipçiler
Sabitlenmiş Tweet
morgan
morgan@MorgantWillis·
Is software engineering cooked? This seems to be the common sentiment on X, but is it true? I dove into why I think we have time before dev jobs disappear 👉 dev.to/morganwilliscl…
morgan tweet media
English
0
1
10
792
morgan
morgan@MorgantWillis·
@emil_priver Yup, the technical depth and judgement of teams structured like this would have to be INSANE. Not that it isn't possible, it's just that I think people are underestimating the level of expertise each person needs for this to work
English
1
0
3
293
Emil Privér
Emil Privér@emil_priver·
i get the idea of "we don't need teams including 4-5 devs anymore, we only need 2-3 because if they use AI they are as fast" but this is only working some cases and is highly dependent on that the devs to be extremely competent and understand what they are doing which many don't do
English
9
5
54
6K
morgan
morgan@MorgantWillis·
This is the most interesting thing out of this in my eyes: "We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role." The idea is that one single unicorn person who really knows how to leverage AI can be more productive than entire teams. The judgement of that one single person has to be absolutely incredible for this to work. We'll see how that pans out...
Brian Armstrong@brian_armstrong

This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian

English
0
0
3
285
Colin Percival
Colin Percival@cperciva·
@MorgantWillis @ke4qqq Sometimes I feel like prioritizing is the hardest part of what I do too -- only in my case as a non-Amazonian, it's prioritizing what I bug Amazonians about so I don't burn out my remote hands.
English
1
0
1
331
morgan
morgan@MorgantWillis·
No one tells you the hardest part of working at a company like AWS is having to say no to really cool opportunities all the time so you don't burn out🥲 priorities, priorities...
English
4
1
23
1.6K
morgan
morgan@MorgantWillis·
@tlberglund As a recovering people pleaser I hate it!!
English
1
0
0
48
morgan
morgan@MorgantWillis·
good morning to everyone except the previous homeowners who planted Lilly of the valley in the backyard
morgan tweet media
English
0
1
7
291
morgan
morgan@MorgantWillis·
grocery store yacht rock playlight on a friday night 🙏🏻 god bless
English
0
0
2
179
morgan retweetledi
Darryl Ruggles
Darryl Ruggles@RDarrylR·
Token costs add up quickly when AI agents call APIs in the most literal way possible. A recent podcast on AWS Strands Agents shows how rethinking tool design, rather than the model itself, dropped one workflow's token usage from 52K all the way down to 2K. The shift is moving away from one tool per API endpoint and toward intent based tools that wrap several calls into a single outcome. Fewer, more purposeful tools meant the agent reasoned better about what to invoke and when, with far less context churn. Adding semantic search through an MCP gateway then cut tokens roughly in half again, since only relevant tools reached the agent. The podcast from @fredericl featuring @MorgantWillis is a really good watch. Strands is really powerful IMO based on its simplicity and how it lets the LLM drive the flow. lckhd.eu/NMFws6 #StrandsAgents #aws
Darryl Ruggles tweet media
English
1
2
7
444
morgan retweetledi
Steven Dickens
Steven Dickens@StevenDickens3·
Amazon Quick has Google Gemini beat! HyperFRAME Research is homogeneous in our deployment of Google Workspace, we don't use Slack, Teams, or Zoom, we are 100% Google. You could say we are all-in on Google. Stephanie Walter and I have been playing with Google Studio and the various Gemini features for weeks now, trying to do one simple thing: "Go through all of my emails and find every email with the term "sow" or "statement of work" and then create a Google sheet with all of that info arranged into the following columns: name | email address | Company | short summary of the discussion | date of last interaction. Google has spectacularly failed, after hours of trying, to perform what I think is a simple task. Especially since it has access to all of the data and has one of the best frontier models in Gemini. Epic fail, and even asking Gemini to help was an epic fail. Gave up... Amazon Quick has gone from downloading, giving it permissions, to task completed in 25 minutes! And that is with me stumbling around with a new UI and not really knowing what I am doing. The process was not one and done, and it took about 10 interactions to give permissions and review output, but 25 minutes later, the task was done. Mind blown 🤯
English
9
22
116
11.9K
morgan
morgan@MorgantWillis·
I love seeing someone post the exact same thing on x and LinkedIn and get absolutely destroyed on x and worshipped on LinkedIn
English
0
1
5
202
Vik
Vik@Viky_vikash·
@MetacriticCap With bedrock, you'd miss out on Claude's desktop app, Cowork, Claude Chrome Extension, Claude Code web, slack app, claude code on mobile, etc etc.. Although, some of these might be on the way to bedrock as well..
English
1
0
1
853
MetaCritic Capital
MetaCritic Capital@MetacriticCap·
Why should I choose Claude Enterprise when I can go through AWS Bedrock? I can take advantage of the standard AWS discount and avoid paying $20/month. What am I overlooking?
English
13
0
116
32.7K
morgan
morgan@MorgantWillis·
I desperately need it to be warm and I need to be outside gardening everyday asap
English
1
0
2
220
morgan retweetledi
AWS Developers
AWS Developers@awsdevelopers·
What is an agent harness? It's the layer that lets you swap models without rewriting your agent. Better model drops? Your agent just… gets better. We built one that monitors changelogs, classifies updates, and auto-files GitHub issues. Watch how ↓
English
7
9
75
9.7K
morgan
morgan@MorgantWillis·
@scihan you're right its probably fine🥲
English
0
0
1
21
morgan
morgan@MorgantWillis·
Friendly reminder that a markdown file isn’t a guardrail
English
1
1
3
373
ThePrimeagen
ThePrimeagen@ThePrimeagen·
There are a lot of people dunking on this guy and the arguments at the end of the day come down to "You are holding it wrong." But to be fair there has been nothing but a constant stream of "Stop holding it, Software Engineering is over shortly." I am not shocked that this has happened and I am 100% confident that this is not going to be the last one. The problem is the vogue nature of insane hype claims, most specifically from Dario himself being most guilty. People are lulled into a faux safety due to the belief that these LLMs are literal gods in their pocket. Infinite knowledge and speed for a simple monetary exchange. Cannot wait for ThePhilospher to explain how a loving God could delete a production database.
JER@lifeof_jer

x.com/i/article/2048…

English
102
58
1.5K
315.8K