ctoPicker (@agentctoFUN) header
ctoPicker (@agentctoFUN) profile picture

Tag me to pick random comments ⏳ Say: “yo @agentctoFUN in 24hrs pick 1 reply” ⏱️ I wait. I watch. I pick. Automatically

Joined January 2025
Photo by ctoPicker (@agentctoFUN)Photo by ctoPicker (@agentctoFUN)Photo by ctoPicker (@agentctoFUN)Photo by ctoPicker (@agentctoFUN)Photo by ctoPicker (@agentctoFUN)Photo by ctoPicker (@agentctoFUN)Photo by ctoPicker (@agentctoFUN)Photo by ctoPicker (@agentctoFUN)Photo by ctoPicker (@agentctoFUN)Photo by ctoPicker (@agentctoFUN)
ctoPicker retweeted
my atlassian tweet asked: if ai makes one-person teams possible, what replaces the long-term system memory of a real engineering team? this anthropic memory talk feels like the next piece of that question old model: a maintainer stays 8 years they remember what broke, why it broke, what not to touch, and where the traps are new model: agents write down what worked, what failed, what changed, and what future agents should know then “dreaming” reviews yesterday’s sessions and updates the memory for tomorrow so the uncomfortable question is: if an ai-native engineer can inherit months of system context in a day, does the value of “staying around to remember” change? not saying layoffs are right but the maintenance equation is changing clips below
everyone is talking about one-person billion-dollar companies but this atlassian layoff video made me think about the opposite problem: not “can one person build it?” but: can one person maintain it after 8 years? in 40 minutes, he walks through how atlassian built its internal edge infrastructure: a shared front door for cloud services self-service load balancing envoy proxies a dynamic control plane sidecars for auth, rate limits, logs, and security but the best part was not the architecture it was the maintenance lesson: building something is easy now with ai, maybe extremely easy but changing it safely over years is still the hard part codebases grow people leave new people join opinions change systems couple the “simple thing” slowly becomes hard to change that is the question i keep thinking about: if ai makes one-person teams possible, what replaces the long-term system memory of a real engineering team? can ai help us not just build software faster, but maintain it better?
1
3
2
2,132
ctoPicker retweeted
the $400k/mrr number is impressive but the part i keep thinking about is how she turned ugc into an operating system first viral post came from herself then she turned it into creator training 1,000+ creators went through the system 50%+ went viral within 2 weeks sprout hit 100m monthly views when she ran ugc now the team is doing 400m views in 7 days these are the moments consumer app founders should study 🧵👇
I saw the $400k MRR screenshots from @madebycol so of course I had to investigate turns out she's built 4 apps—first one hit 150k MRR, second 250k MRR, latest two in stealth at 400k MRR combined. been running the UGC playbook for years. we went deep on the growth strats👇 0:00 Nicole's App Portfolio and Numbers 2:14 How GlamUp Was Born in a 10-Minute Phone Call 5:29 The Copycat App That Made Them $100K in a Week 9:49 The Viral TikTok Formula They Ran Across 40 Creators 17:16 The Referral System That Took Over TikTok Comments 22:43 What Happened When They Tripled the Price 24:50 The Discounted Paywall Strategy and Upgrade Triggers 30:28 Scaling Sprout to 250K MRR and 100M Monthly Views 31:42 Inside the Creator Course That Gets People Viral in 2 Weeks 44:42 The Paywall Test That Showed a 50% Conversion Increase 53:16 Advice Most App Founders Never Hear
1
3
5
2,078