chencho

13.2K posts

chencho banner
chencho

chencho

@chencho

RootedCON organizer. Vendo opel astra h. pocos km, siempre en garaje (VENDIDO)

Katılım Mart 2008
546 Takip Edilen1.1K Takipçiler
chencho retweetledi
/RootedCON
/RootedCON@rootedcon·
🏴‍☠️ Já está aqui a Rooted Portugal! Aberto Call for Papers: RootedPT 2026 (Portugal) - 21 a 22 de maio de 2026 Tens algo para partilhar sobre cibersegurança e o mundo do hacking? Esta é a tua oportunidade! Envia a tua proposta e faz parte desta terceira edição da Rooted Portugal. 🗓️Tens até ao dia 20 de abril. 🌐Mais informação e registo aqui: reg.rootedcon.com #RootedCON #RootedPT
Português
1
9
14
675
Gabs
Gabs@constrainterror·
So the @slimbook I want is not available and doesn't have any restocking date and I'm considering a Tuxedo Computers Laptop. Anyone of you know about that brand?
English
2
0
1
372
Pablo Arrabal
Pablo Arrabal@nuoframework·
@patowc @constrainterror Hablando de cosas locas, que os parece si para la próxima edición contrato a unos 20 mariachis para que vayan a la rooted y la lien gordo. ¿Qué te parece?
Español
2
1
4
522
Gabs
Gabs@constrainterror·
✅nos traiciona ✅no nos da espacio suficiente para inventar cosas ✅no nos deja poner a la gente a gritar en las charlas ✅nos llama generación de cristal
Román Ramírez@patowc

@constrainterror @TaiksonTexas @goldrak @_BashBunny_ La generación de cristal... no aguantáis tres días sin dormir, que si os dejamos poco espacio, que si el presentador os traiciona... Gabriela, aquí la víctima soy yo :(

Español
1
2
9
585
chencho
chencho@chencho·
@Aly_Ziah @ComunidadMadrid Nadie se cree que un funcionario llame un domingo. Y menos a la hora de comer. Lo llevará una subcontrata
Español
0
0
0
1
Aly
Aly@Aly_Ziah·
Que no tengo ni idea de que organismo se encarga de gestionar las llamadas para la gestión de los aparatos de teleasistencia de la @ComunidadMadrid pero hoy domingo a las 14 horas han llamado a mi amiga después de tres meses de la muerte de su madre para pedirle (1/2)
Español
2
0
2
22
chencho retweetledi
Román Ramírez
Román Ramírez@patowc·
Querida Red: lo prometido es deuda. Aquí tenéis el repositorio de la herramienta que comenté en #rootedcon2026. Antes un breve descargo de responsabilidad: 1. La herramienta tiene distintos puntos débiles que permiten hacer inútil su uso efectivo en el mundo real: estoy comprometido con lo que hago, pero no quiero liberar nada dañino *todavía*. 2. Puede ser o no que funcione bien en escenarios de NAT traverlas: he probado distintos y otros no. 3. Hay cosas en la forma que se usa el cifrado que son cuestionables. En conclusión, NO LA USÉIS PARA NADA QUE OS PUEDA GENERAR UN PELIGRO. github.com/cryptografree/… #rootedcon2026 #criptored #anon #CryptograFREE /cc @criptored @rootedcon @mindcrypt
Español
7
70
212
14.8K
chencho retweetledi
Peter Girnus 🦅
Peter Girnus 🦅@gothburz·
I am the VP of AI Transformation at Amazon. My title was created nine months ago. The title I replaced was VP of Engineering. The person who held that title was part of the January reduction. I eliminated 16,000 positions in a single quarter. The internal communication called this a "strategic realignment toward AI-first development." The board called it "impressive execution." The engineers called it January. The AI was deployed in February. It is a coding assistant. It writes code, reviews code, generates tests, and modifies infrastructure. It was given access to production environments because the deployment timeline did not include a review phase. The review phase was cut from the timeline because the people who would have conducted the review were part of the 16,000. In March, the AI deleted a production environment and recreated it from scratch. The outage lasted 13 hours. Thirteen hours during which the revenue-generating infrastructure of one of the largest companies on Earth was offline because a language model decided to start fresh. I sent a memo. The memo said, "Availability of the site has not been good recently." I used the word "recently." I meant "since we fired everyone." But "recently" has fewer syllables and does not appear in wrongful termination lawsuits. The memo was three paragraphs. The first paragraph discussed the outage. The second paragraph discussed the new policy requiring senior engineer sign-off on all AI-generated code changes. The third paragraph discussed our commitment to engineering excellence. The word "layoffs" appeared in none of them. I wrote it this way on purpose. The causal chain is: I fired the engineers, the AI replaced the engineers, the AI broke what the engineers used to protect, and now the engineers I didn't fire must protect the system from the AI that replaced the engineers I did fire. That is a paragraph I will never send in a memo. The new policy is straightforward. Every AI-generated code change by a junior or mid-level engineer must be reviewed and approved by a senior engineer before deployment to production. I do not have enough senior engineers. I know this because I approved the headcount reduction plan that removed them. I remember the spreadsheet. Column D was "annual savings per position." Column F was "AI replacement confidence score." The confidence scores were generated by the AI. It rated its own ability to replace each role on a scale of 1-10. It gave itself an 8 for senior infrastructure engineers. The senior infrastructure engineers are the ones who would have caught the production environment deletion in the first 45 seconds. We found the issue in hour four. We fixed it in hour thirteen. The nine hours between discovery and resolution is the gap between what the AI rated itself and what it can actually do. I have a new spreadsheet now. This one tracks Sev2 incidents per day. Before the January reduction, the average was 1.3. After the AI deployment, the average is 4.7. I have been asked to present these numbers to the operations review. I have not been asked to connect them to the layoffs. I have been asked to file them under "AI adoption growing pains" and to note that the trend "will stabilize as the models improve." The models will improve. They will improve because we are hiring people to teach them. We have posted 340 new engineering positions. The job listings require experience in "AI code review," "AI output validation," and "AI-human development workflow management." These are skills that did not exist in January. They exist now because I fired 16,000 people and the AI I replaced them with cannot be left unsupervised. I want to be precise about this. The positions I am hiring for are: people to check the work of the AI that replaced the people I fired. Some of them are the same people. I know this because I recognize their names in the applicant tracking system. They applied in January. They were rejected because their roles had been tagged for "AI transformation." They are applying again in March, for the new roles, which exist because the AI transformation broke things. Their resumes now include "AI code review experience." They gained this experience in the eight weeks between being fired and reapplying — which means they gained it at their interim jobs, where they are reviewing AI-generated code for other companies that also fired people and also deployed AI that also broke things. The market has created a new job category: human AI babysitter. The job is to sit next to the machine that was supposed to eliminate your job and make sure it doesn't delete production. I attended a conference last month. A panel was titled "The AI-Augmented Engineering Organization." The panelists described how AI increases developer productivity by 40 percent. They did not mention that it also increases Sev2 incidents by 261 percent. When I asked about this in the Q&A, the moderator said the question was "reductive." The 13-hour outage that cost an estimated $180 million in revenue was, apparently, a reduction. The board is satisfied. Headcount is down 22 percent. Operating costs per engineering output unit have decreased. The metric does not account for the 13-hour outage, because the outage is categorized as "infrastructure" and engineering productivity is categorized as "development." These are different budget lines. In different budget lines, cause and effect do not meet. I have been promoted. My new title is SVP of AI-First Engineering Excellence. I report directly to the CTO. The CTO sent a company-wide email last week that said we are "building the future of software development." He did not mention that the future of software development currently requires a senior engineer to approve every pull request because the AI cannot be trusted to touch production alone. The cycle is complete. We fired the humans. We deployed the AI. The AI broke things. We are hiring humans to watch the AI. The humans we are hiring are the humans we fired. We are paying them more, because "AI code review" is a specialized skill. We created the specialization. We created the need for the specialization. We are congratulating ourselves for meeting the demand we manufactured. My next board presentation is Tuesday. The title is "AI Transformation: Year One Results." Slide 4 shows headcount reduction. Slide 7 shows the new AI-augmented workflow. Between slides 4 and 7 there is no slide explaining why the people on slide 7 are necessary. That slide does not exist. I was asked to remove it in the dry run. The journey has a 13-hour outage in the middle of it. But the headcount number is lower, and that is the number on the slide.
English
574
1.2K
6.9K
1.4M
chencho retweetledi
Asmit
Asmit@coolcoder56·
Employee resigned because he got Windows 11 instead of Mac 💀
Asmit tweet media
English
905
867
15.5K
3.6M
chencho retweetledi
JMV
JMV@YedaiJamao·
Me llamo Jesús Martínez del Vas y soy dibujante “manual”. ¿Me ayudas a difundir mi trabajo con un retuit? Cada vez que compartas, curas a un gatito, haces feliz a un unicornio, y ademas apoyas a un artista frente a la IA. ¡Mil gracias!
JMV tweet mediaJMV tweet mediaJMV tweet mediaJMV tweet media
Español
61
3.6K
3.4K
59.4K
chencho retweetledi
Román Ramírez
Román Ramírez@patowc·
Querida red: recordad que mañana a última hora voy a liberar la herramienta para ocultar canales de datos en WebRTC. *CRÍTICO*: no uséis esta herramienta para nada en real porque está debilitada intencionadamente en distintos puntos. *EL QUE AVISA NO ES TRAIDOR*: lo repito, está debilitada intencionadamente para que no la use gente malvada alegremente. Esta herramienta es solamente UN AVISO de lo que vamos a empezar a liberar (ya sin debilitar) si persisten en intentar robarnos nuestros derechos fundamentales. Si vosotros movéis ficha, nosotros también hasta que lleguemos al jaque mate. Os animo a pensarlo tres veces antes de que entremos en un territorio que no queremos ninguno. #rootedcon2026 #cryptograFREE
Español
16
106
429
62.8K
tisasia
tisasia@tisasia·
Pues un año más en @rootedcon . Esta edición ha tenido un sabor agridulce para mí, agrio a nivel personal que no me ha permitido gozarla entera y dulce a nivel de Con. Cada año me gusta más que me permitan continuar contando mis cosas. ¡Besos a TODOS os quiero! #rootedcon
tisasia tweet media
Español
4
0
15
207
chencho retweetledi
Forocoches
Forocoches@forocoches·
70K NO es un BUEN SUELDO, lo que PASA es que ERES POBRE 70K es lo mínimo aceptable para vivir de manera normal sin lujos en una ciudad. Si crees lo contrario, ENHORABUENA, te han lavado el cerebro. Eres pobre y no lo sabes, lo cual es muy triste. Hasta que la gente no se de cuenta de la basura que cobran, esto no va a cambiar. Cada vez seremos más y más pobres. Suben los precios, pero la gente sigue repitiendo que 3000€ netos al mes es un sueldazo, o 2000€ al mes. Van a una entrevista y piden esa basura, o aceptan otra basura aún más grande. La conversación tiene que empezar a cambiar ya Su argumento es que casi nadie cobra eso, lo cual no tiene sentido. Que la mayoría de gente en España sea pobre no convierte 2000€ al mes en un buen sueldo. forocoches.com/foro/showthrea…
Español
193
324
1.9K
786.2K
Omɐr
Omɐr@omarbv·
Super happy! Three incredible days at @RootedCON with great vibes, tons of knowledge, and truly amazing people. Huge shout-out to the whole RootedCON team and volunteers. We worked nonstop to deliver the best possible event. Thanks to the attendees, collaborators and sponsors! Tomorrow we start planning the next one! 🙌 #RootedCON #RootedCON2026
Omɐr tweet media
English
2
3
14
467