meme cooker by day, builder by night | ex-FTX | Spanglish
mx
Joined December 2009
- Tweets3.8K
- Following588
- Followers1.5K
- Likes8.3K
bairo (🐶,🤠) retweeted
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
bairo (🐶,🤠) retweeted
todo lo que necesitas saber de Jev.
y con casos prácticos
Jev is HERE and this is the CLEAREST explanation of what it is and what NEW businesses it unlocks.
(and at the end I'll tell you how to get Jev even if you're on the waitlist)
WHAT IT IS
You know how you open your inbox and have to decide what's junk, what needs a reply, and what can wait? Jev does that part. It looks at each thing and says "this is junk, I'm 94% sure."
It doesn't write anything back to you. It just sorts.
1,700 emails for 18 cents, instantly.
That sounds kinda trivial but the important part
WHAT IT UNLOCKS
My explanation of Jev sounds small until you realize HOW MANY jobs are exactly this. Someone reading a stack of applications. Someone deciding which support ticket goes to which team. Someone looking at inbound and deciding who's worth calling back.
A few ideas on what it unlocks:
1/ Instant quotes that are actually instant. Every quote form on the internet says "we'll email you by end of day." Build the version that answers in under a second, for roofers, movers, insurance, legal intake.
2/ Lead scoring as a product. Every agency and service business has a contact form full of junk. Score every submission and send the real ones straight to the owner's phone.
3/ Support triage for companies with no support team. The ticket gets classified and routed before anyone opens it.
4/ Clipping tools. Pass in a transcript, get the best moments scored in three seconds. Every clipping product just got a cheaper engine.
5/ Application piles. Grants, permits, insurance claims, job apps, loan docs. Someone reads that stack one item at a time today.
6/ Marketplace matching. Someone types what they need and gets matched to the right local business instantly instead of waiting for callbacks.
7/ Browser agents that actually move FAST. That makes bulk browser work practical: pulling quotes from five carriers, filing the same form for 200 clients, checking supplier inventory in real time etc.
TLDR; find an expensive queue and put Jev at the front of it.
HOW TO GET IT
I didn't realize you can skip the waitlist because Jev is live on the Vercel AI Gateway right now, so you can start calling it today. In this episode, we share how.
Episode now live on @startupideaspod (thanks to @ryanvogel for coming on and spilling the sauce today)
Watch: youtube.com/watch?v=4mTLpuQp…
Jev is a big deal because this is a whole new way to do AI
Really cool
Happy Jev day.
La IA abrió más caminos de los que podemos seguir. Para elegir entre ellos, empecé a poner cada opción a prueba con objeciones, evidencia y una pregunta sencilla: ¿vale lo que exige?
De ahí nació PODA, mi primer academic paper.
PODA framework redefines how claims earn commitment through directed opposition and iterative AI collaboration, revealing unseen burdens in decision-making processes 🔍🤖
qeios.com/read/28U0SW
bairo (🐶,🤠) retweeted
Nadie esta viendo el colapso bancario que va a provocar la IA 🤖
we're making @blocks smaller today. here's my note to the company.
####
today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone.
first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay.
we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly.
i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures.
a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers.
we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold.
to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward.
to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow.
jack
bairo (🐶,🤠) retweeted
out: gm
in: Ah, what a splendid and invigorating dawn this appears to be, my esteemed interlocutor, as the golden rays of the sun ascend triumphantly over the horizon, casting their luminous embrace upon the awakening world below, heralding the commencement of yet another glorious rotation of our pale blue dot through the vast cosmic tapestry. It is with the utmost delight and a profound sense of communal warmth that I extend to you, in this precise moment of temporal convergence, a salutation most fitting for the early hours—or perhaps the mid-morning ones, depending on your particular meridian and circadian inclinations—a greeting that encapsulates the essence of renewal, optimism, and the boundless potential that each fresh day unfurls like a meticulously wrapped gift from the universe itself. Allow me, if you will, to articulate this sentiment in a manner that stretches the boundaries of verbosity, weaving together threads of linguistic extravagance, philosophical musings, and a dash of whimsical flair, all in service of conveying what could otherwise be expressed in mere brevity but deserves, nay, demands, an elaborate exposition to truly honor the miracle of consciousness stirring from slumber. Picture, if you might, the gentle unfurling of petals on a dew-kissed rose, or the symphony of birdsong crescendoing in harmonious acclaim of the light's return; such is the backdrop against which I proffer this extended overture of affability and cheer. In the spirit of ancient traditions where dawn was revered as a portal to possibility, and drawing from the wellsprings of human connection that bind us across epochs and geographies, I beseech the benevolent forces of fate to shower upon you an abundance of vitality, clarity of mind, and serendipitous encounters throughout the unfolding narrative of this day. May your coffee—or tea, or perhaps a revitalizing elixir of your choosing—be brewed to perfection, your endeavors met with seamless success, and your thoughts alight with inspiration as boundless as the azure expanse overhead. And so, without further ado—though truly, what ado we have indulged in thus far!—I declare, proclaim, and affirm with resounding enthusiasm: good morning!
This quoted post is unavailable.
bairo (🐶,🤠) retweeted
Muy agradable la explicación de padillon.uxui en TikTok sobre la referencia de los nombres de los elementos que usualmente damos por hecho su nombre.
vm.tiktok.com/ZMAaKqNoX/
bairo (🐶,🤠) retweeted
Agradecido por todo lo que he vivido y las bendiciones que esta vida me ha dado.
Hoy le dí 46 vueltas al Sol ☀️
Abró un hilo para compartir algunas anécdotas de construir en protocolos blockchain.
🧵👇
bairo (🐶,🤠) retweeted
Today the White House is releasing its comprehensive report on digital assets, providing long-awaited regulatory clarity for innovators in a cutting-edge industry. President Trump is delivering on his promise to make the U.S. the crypto capital of the planet.
👀
Today, @FinCENnews issued orders identifying three Mexico-based financial institutions—CIBanco S.A., Institution de Banca Multiple (CIBanco), Intercam Banco S.A., Institución de Banca Multiple (Intercam), and Vector Casa de Bolsa, S.A. de C.V. (Vector)—as being of primary money laundering concern in connection with illicit opioid trafficking, and prohibit, respectively, certain transmittals of funds involving CIBanco, Intercam, and Vector.
These orders are the first actions by FinCEN pursuant to the Fentanyl Sanctions Act and the FEND Off Fentanyl Act, which provide Treasury with additional authorities to target money laundering associated with the trafficking of fentanyl and other synthetic opioids, including by cartels. Further, these actions were taken within the broad context of the strong U.S.-Mexico inter-governmental relationship, the hallmarks of which include close collaboration and timely information exchange.
bairo (🐶,🤠) retweeted
we’re joining forces with Polymarket as our official prediction market partner
@X 🤝 @Polymarket
