Javier Colimannn Reyesss retweeted
🚨 ESCÁNDALOSO
No le den RT ni FAV porque los van a poner en la lista de Sheinbaum.
Juzguen ustedes en manos de quién está el INE.
👇
Javier Colimannn Reyesss retweeted
🚨 #ULTIMAHORA | Una investigación del portal digital Xpectro revela que uno de los 5 detenidos por quemar el congreso de Jalisco es militante de Morena desde agosto de 2025.
Se trata de Chritopher Antonio, quien aparece en los registros del partido.
Javier Colimannn Reyesss retweeted
Make the false accuser famous.
A civil jury ruled in favor of ex-MIT scientist David Sabatini, who was accused by a younger colleague of inappropriate sexual conduct in his Cambridge research lab, and awarded him $6 million in damages. trib.al/s3v9VIX
Javier Colimannn Reyesss retweeted
Former MIT scientist wins $6M defamation verdict against colleague who accused him of sexual misconduct trib.al/q1cVlXE
Javier Colimannn Reyesss retweeted
🚨Identifican a cinco detenidos tras los ataques con bombas molotov contra el Congreso de Jalisco y el Poder Judicial, durante la manifestación para exigir agua limpia.
Los cinco hombres fueron detenidos en posesión de gasolina y una camioneta con reporte de robo.
📹🗞️Víctor Hugo Arteaga @arteaganoticias @XpectroFM
Javier Colimannn Reyesss retweeted
🚨 #LOCAL | Reportan la detención de 5 sujetos relacionados con la quema del Congreso de Jalisco.
Uno de ellos trabaja en un anexo ubicado en la zona de Las Conchas.
Javier Colimannn Reyesss retweeted
¡Cada vez hay más señalamientos contra Morena por los porros que reventaron la marcha en Guadalajara!
Ahora identifican a Pedro Ramírez, operador del senador de Morena Carlos Lomelí, y lo acusan de organizar a los grupos violentos que ocasionaron destrozos frente al Palacio de Gobierno de Jalisco.
¿Quién mandó a estos porros? Creo que hasta la pregunta ofende.
Javier Colimannn Reyesss retweeted
Yo viví en Guadalajara y en mi puta vida escuché a alguien decirle «metro» al Tren Ligero. Y para acabarla de chingar, también hablan del «Zócalo», como si estuvieran en la CDMX. Morena no puede negar que mandó porros a la marcha de Jalisco.
Javier Colimannn Reyesss retweeted
Elon Musk says a comedy book saved him from a teenage existential crisis..
he was searching for the meaning of life..
he read religious texts..
none convinced him..
then German philosophers..
he jokes that's a bad idea for a depressed teenager..
then he read The Hitchhiker's Guide to the Galaxy..
in it a supercomputer spends 7.5 million years on the meaning of life..
the answer..
42..
the joke is that nobody knew the right question..
Musk took that seriously..
the universe is the answer..
we just don't know the question yet..
so the goal is to expand consciousness..
more humans..
more minds..
more planets..
until we're smart enough to ask it
Javier Colimannn Reyesss retweeted
Elon Musk wrote a video game called Blastar when he was 12 years old. He coded it himself on a Commodore VIC 20. The game was a space shooter. He sold the source code to a computer magazine for approximately $500. He was 12. The year was 1984. The internet didn't exist. The personal computer was 7 years old. And a boy in Pretoria, South Africa wrote a working video game and sold it commercially.
The detail that matters is not the game. It is that he sold it. A 12 year old who makes a game is a hobbyist. A 12 year old who sells the game to a magazine for publication is an entrepreneur. The distinction is not talent. It is the instinct to convert creation into commerce. The instinct was present at 12. Before Zip2. Before PayPal. Before SpaceX. The operating system that would later build companies was running on a Commodore in a bedroom in South Africa.
He has described the childhood coding period as the only time he felt in control. The school was violent. The home was emotionally cold. The computer responded to input with output. It did what he told it. It did not hit him. It did not ignore him. It did not tell him he was wrong. The code either worked or it had a bug and the bug could be fixed. The certainty of cause and effect in a world that offered no certainty elsewhere was the first thing he fell in love with.
The boy who coded Blastar at 12 now runs a company (xAI) building one of the most advanced artificial intelligence systems on earth. The distance is 40 years and several hundred billion dollars. The fundamental activity is the same: telling a machine what to do and watching it do it. The machine got bigger. The boy didn't change.
The first thing Elon Musk ever sold was a video game about shooting things in space. The latest thing he is building is a rocket that goes to space. The 12 year old's fantasy became the 53 year old's company. The line between the two is straighter than anyone realizes.
Javier Colimannn Reyesss retweeted
Who’s going to tell the old school coders that there’s going to be nothing but vibe coding in like 6 months. All companies will need are people who can describe what they want properly, and someone to look it over. These tweets that make vibe coding seem stupid, are naive.
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
Asi se ve a alguién que ya padece el Sindrome del Prompt? @danieloso El Prompteado quiere despromptearse asumiendose un buen "No Prompteador.....
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
Javier Colimannn Reyesss retweeted
Fact: No one with a Gender Studies degree contributed to the making of this.
Javier Colimannn Reyesss retweeted
Así están el Luis XVI y la María Antonietta del siglo XXI mientras los musulmanes y africanos queman Francia.
De concierto de Celine Dion mientras arde todo el país.
Javier Colimannn Reyesss retweeted
On October 7, @EmmanuelMacron called Israel's 🇮🇱 Prime Minister @netanyahu and urged that Israel show restraint. Netanyahu responded: “if we don't dismantle Hamas in Gaza, you"ll meet them in Paris.”






































