software engineer | YC W22
Joined March 2009
- Tweets5.4K
- Following412
- Followers7.2K
- Likes57.1K
Bruno Lemos retweeted
This is it.
Everyone is excited about AI.
I'm not.
AI is the biggest commoditizer of human capability we have ever built. Doctors earn more than cleaners because expertise takes a decade to acquire and judgment to apply. AI is going to make most of that expertise available to anyone, at marginal cost.
The gap doesn't go to zero. But it shrinks. And the same thing happens in almost every knowledge profession. Programmers. Lawyers. Analysts. Traders. Designers. The taxi driver replaced by a robotaxi is the easy case. The harder ones are people who spent twenty years training to do something a model can now do in a second.
The one corner of human life I don't see this hitting is sport. Nobody pays to watch a robot beat a human. The whole appeal is humans competing against each other. That's why nobody watches Deep Blue play chess anymore.
From an investing perspective, the next decade plays out in three phases.
Phase 1 is the buildout. Hundreds of billions in capex on chips, data centers, and energy. This is what's driving today's market.
Phase 2 is the deployment. Productivity rises sharply, then deflation sets in as the cost of knowledge work collapses. Jobs disappear faster than the economy can replace them.
Phase 3 is the social adjustment. Capital becomes more powerful than labor. The biggest winners are likely to sit where AI cannot reach. Real assets. Energy. Commodities. Precious metals. Scarce land.
And there's something deeper than the economics. The Japanese have a word for it: ikigai. The reason you get up in the morning. Your vocation. Your purpose. The work that makes you feel needed. AI is coming for that too. Nobody has yet figured out what a healthy society does when most of its members no longer feel needed by anything.
I might be wrong. I hope I am.
If I'm not, the world is about to change faster than most people are ready for.
it’s interesting how claude models are the best at creating beautiful designs, yet their own apps are among the least visually appealing
i've been using AI to generate explanation videos to learn and understand things, even tweets and blog posts.
not sure if lazy or genius
They don't need to know anymore. The AI will take care of all this automatically.
Who's gonna tell vibe coders about...
1. SQL Injection
2. XSS
3. CSRF
4. CORS
5. SSRF
6. IDOR
7. Path Traversal
8. Mass Assignment
9. Clickjacking
10. Content Security Policy
11. Security Headers
12. Input Validation
13. Server-Side Authorization
14. Row-Level Security
15. Least Privilege
16. RBAC
17. Secrets Management
18. .env in .gitignore
19. API Key Rotation
20. Secret Scanning
21. Hashing vs Encryption
22. Password Salting
23. bcrypt & Argon2
24. JWT Expiry
25. Refresh Tokens
26. OAuth 2.0
27. OpenID Connect
28. Session Fixation
29. MFA
30. Brute Force Protection
31. Account Enumeration
32. Timing Attacks
33. File Upload Validation
34. Webhook Signature Verification
35. TLS Certificate Expiry
36. HSTS
37. Encryption at Rest
38. Dependency Vulnerabilities
39. Supply Chain Attacks
40. Threat Modeling
41. Indexes
42. EXPLAIN ANALYZE
43. N+1 Queries
44. Full Table Scans
45. Connection Pooling
46. Database Migrations
47. Down Migrations
48. Transactions
49. ACID
50. Isolation Levels
51. Deadlocks
52. Optimistic Locking
53. Pessimistic Locking
54. Normalization
55. Denormalization
56. Foreign Keys
57. Unique Constraints
58. Cascading Deletes
59. Soft Deletes
60. UUIDs vs Auto-Increment
61. Cursor-Based Pagination
62. Full-Text Search
63. Read Replicas
64. Replication Lag
65. Sharding
66. Partitioning
67. Hot Partitions
68. Postgres VACUUM
69. Materialized Views
70. Backups
71. Testing Your Restores
72. Point-in-Time Recovery
73. Change Data Capture
74. Outbox Pattern
75. ORM Lazy Loading
76. CAP Theorem
77. Eventual Consistency
78. Strong Consistency
79. Raft Consensus
80. Leader Election
81. Split Brain
82. Quorums
83. Clock Skew
84. Distributed Locks
85. Consistent Hashing
86. Bloom Filters
87. Two-Phase Commit
88. CQRS
89. Event Sourcing
90. Race Conditions
91. Backpressure
92. Load Shedding
93. Bulkheads
94. Jitter
95. Retry Storms
96. Cascading Failures
97. Thundering Herd
98. Cache Invalidation
99. Cache Hit Ratio
100. TTLs
101. Cache Warming
102. Write-Through vs Write-Back
103. Redis Eviction Policies
104. CDNs
105. Cache-Control Headers
106. ETags
107. Dead Letter Queues
108. Poison Messages
109. At-Least-Once Delivery
110. Exactly-Once Semantics
111. Message Ordering
112. Kafka Consumer Groups
113. Partition Keys
114. Background Jobs
115. Webhook Retries
116. DNS
117. DNS Propagation
118. HTTP Status Codes
119. HTTP Method Semantics
120. Keep-Alive
121. HTTP/2
122. WebSockets
123. Server-Sent Events
124. Long Polling
125. gRPC
126. Protocol Buffers
127. API Versioning
128. OpenAPI Specs
129. Backward Compatibility
130. Request Size Limits
131. Compression
132. Latency vs Throughput
133. Egress Fees
134. VPCs
135. Subnets
136. NAT Gateways
137. Firewalls
138. Security Groups
139. Service Mesh
140. Ingress Controllers
141. Health Checks
142. Liveness vs Readiness Probes
143. Graceful Shutdown
144. Connection Draining
145. Stateless Services
146. Failover
147. Multi-Region
148. Availability Zones
149. Single Points of Failure
150. Disaster Recovery
151. RTO & RPO
152. SLAs
153. SLOs
154. Error Budgets
155. Incident Response
156. On-Call
157. Runbooks
158. Postmortems
159. Chaos Engineering
160. Graceful Degradation
161. Autoscaling
162. Horizontal vs Vertical Scaling
163. Cold Starts
164. Capacity Planning
165. Load Testing
166. Memory Leaks
167. OOM Killer
168. Structured Logging
169. Log Levels
170. Log Rotation
171. Distributed Tracing
172. OpenTelemetry
173. Correlation IDs
174. Metrics Cardinality
175. p99 Latency
176. Alert Fatigue
177. Error Tracking
178. Profiling
179. Flame Graphs
180. Infrastructure as Code
181. Terraform State
182. GitOps
183. Blue-Green Deployments
184. Canary Releases
185. Rollbacks
186. Feature Flags
187. Environment Parity
188. Staging Environments
189. 12-Factor Apps
190. Multi-Stage Builds
191. Non-Root Containers
192. Image Scanning
193. Resource Requests & Limits
194. Pod Disruption Budgets
195. Semantic Versioning
196. Lockfiles
197. Reproducible Builds
198. Branch Protection
Bruno Lemos retweeted
"Das Pferd wird es immer geben, aber das Automobil ist nur eine Modeerscheinung – ein Spielzeug für Reiche."
Michigan Savings Bank, 1903
"Ich denke, es gibt weltweit einen Markt für vielleicht fünf Computer."
Thomas Watson, 1943
"No chance that the iPhone is going to get any significant market share."
Steve Ballmer, 2007
"Das Internet hat für die Wirtschaft kaum wichtigere Auswirkungen als das Faxgerät."
Paul Krugman, 1998
"Flugmaschinen, die schwerer sind als Luft, sind physikalisch unmöglich."
Lord Kelvin, 1895
"Das Spam-Problem bei E-Mails wird in spätestens zwei Jahren gelöst sein"
Bill Gates, 2004
"Der Fernseher wird sich auf dem Markt nicht halten. Die Menschen werden es bald leid sein, jeden Abend auf eine Sperrholzkiste zu starren."
Darryl F. Zanuck, 1946
"Es gibt keinen Grund, warum jemand einen Computer in seinem Haus haben wollte."
Ken Olson, 1977
"Wenn die Pariser Weltausstellung schließt, wird das elektrische Licht ausgehen und man wird nie wieder davon hören."
Erasmus Wilson, 1878
"Die Amerikaner brauchen das Telefon vielleicht, wir aber nicht. Wir haben genug Laufburschen."
William Preece, 1876
"Egal wie die Wissenschaft in Zukunft fortschreitet, der Mensch wird den Mond niemals erreichen."
Lee De Forest, 1957
"Reisen mit hoher Geschwindigkeit ist nicht möglich, weil die Passagiere keine Luft mehr bekommen und an Erstickung sterben würden."
Dionysius Lardner, 1830
"Mit Wechselstrom herumzuspielen ist reine Zeitverschwendung. Niemand wird ihn jemals nutzen."
Thomas Edison, 1889
"Mobiltelefone werden die Drahttelefone absolut nicht ersetzen."
Marty Cooper, 1981
#TeslaRoadster
#Tesla
elon said in the livestream, before the unveiling: "this car really sucks"
he was talking about the suction mechanism
i just got the joke now 👍
the next step is so obvious @elonmusk
ALT spacex rocket -> tesla roadster -> iron man suit
mano, muito barato.
US$250k com o propulsor
US$50k sem o propulsor
pra um carro futurístico desse 🔥
Configurations
– Performance: road ready, seats 2
Active aerodynamics & multi-mode suction system for next-level performance on & off the track
– Thrust: race ready, seats 2
Multi-mode suction system paired w/ rear-mounted cold-gas thrusters that enable 0–60 in <1 second
– Rocket: air ready, seats 1
Multi-mode suction system plus perimeter-mounted cold-gas thrusters supporting forward & upward acceleration plus lateral rotational movement. So...yes, it can fly
Range >300 miles
Top speed up to >230mph (Rocket)
0-60
Performance (<1.6)
Thrust (<0.9)
Rocket (<0.59)
Reserve now –
Tesla.com/Roadster
Bruno Lemos retweeted
Roadster event livestream xitter.cf/i/broadcasts/1yKAPwNgg…
Opus 5.5 one shotted this explainer video for their blog post
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
