Angel Martz

@angelmartz_

๑๑๑ Trust Me, I'm an Engineer. ๑๑๑ #UNAM ♛♚♝♞♜♟ Amante de la Música ♫ ♪ ♬ Somos fuego andando en el viento, cenizas del recuerdo que revive en el momento

Joined February 2011

728 Following

222 Followers

3.5K Posts

Angel Martz @angelmartz_

17 days ago

@TELMEXSoluciona no tengo servicio ni internet ni telefonía

angelmartz_ retweeted

Leo

@leoxbtt

about 1 month ago

Un dev creó transferencia de archivos SIN INTERNET… solo con códigos QR y Claude Un desarrollador quería hacer un reproductor de MP3 web para escapar de los anuncios. Terminó inventando algo mucho más loco: Un sistema air-gapped que pasa archivos de un teléfono a otro sin WiFi, sin Bluetooth, sin estar en la misma red. ¿Cómo? Mostrando códigos QR que parpadean a toda velocidad en la pantalla. Usó Claude Code y en una sola noche tuvo la prueba de concepto 100% funcional. La IA está haciendo que un solo developer pueda inventar cosas que antes solo se veían en laboratorios.  El futuro se está construyendo más rápido de lo que creemos.

317

11K

angelmartz_ retweeted

Boris Cherny

@bcherny

about 2 months ago

Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually. These kinds of things were the highest leverage activities an engineer could do, because it multiplied their own output, which in turn meant they could build more things. I think many of these automations have become even more important now. This is true for a number of reasons. First, infra and DevX automation speeds you up. And if you are running an army of agents, each of those agents will be sped up also. More automation == more output per unit of time. Second, moving things to code improves efficiency. Your agent could fix an issue every time it sees that issue happen, but that uses tokens and might miss cases. If Claude instead writes a lint rule, CI step, or routine, that class of issue can be fully automated forever. This is really what people are talking about when they talk about loops -- it's about automating entire types of busywork rather than solving them one off. This isn't a new idea at all. Engineers have been doing this for a long time! Third and most importantly, automation makes it possible for others to contribute to the codebase more easily. Increasingly what I am seeing is engineers are contributing to codebases on day one because Claude can navigate the codebase for them, and that non-engineers are able to contribute to a codebase as effectively as engineers can. What gets in the way of both of these is domain knowledge that lives in peoples' heads rather than in automation -- the stuff you used to have to learn when ramping up. What has changed thanks to agents is the domain knowledge that can be encoded as infrastructure is no longer limited to what is expressible in lint rules and types and tests; it can now capture nearly all domain knowledge, encoded as code comments and skills and CLAUDE.md rules and memories. If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation. Every team should be writing the CLAUDE.md's, REVIEW.md's, skills, and docs that enable agents to productively work in their codebase with zero additional context from the prompter. This sounds crazy, and at the same time is a natural extension of the stuff engineers have always done: automate, and encode domain knowledge as infrastructure. As the model gets smarter and as the harness matures, this task becomes easier. In the meantime, it is on every team to look for ways to convert their domain knowledge to infra so that Claude can write code better, so that code review catches issues automatically, and so the next person working on your codebase can contribute more easily.

392

10K

902

10K

Angel Martz @angelmartz_

about 2 months ago

@Uber_MEX @Uber_Support ayer su app estuvo fallando y dejo de calcular la ruta, me cobraron un tarifa que no corresponde, mande soporte y me reembolsaron "un poco" pero tampoco corresponde al precio real

Who to follow

Jose Luis Alonso

@jlareguera

Director General en @Garantipro , Insurtech, Mobile Expert by #Google, dirijo equipos de Ventas y MK Online, Speaker, Profesor, Mentor, #SEO, #SEM #MK Online

Jose Adrian Aranda

@Jose_Aranda

La caída, Albert Camus

Angel Galindo

@doncocol

Angel Martz @angelmartz_

about 2 months ago

@maripydev Ya no andabas en redes D:

151

Angel Martz @angelmartz_

2 months ago

@CastaneHD @CFE_Contigo @CFE_Contigo 11:20 pm aun nada

Angel Martz @angelmartz_

2 months ago

@YuridiaPerezBa1 @24_morelos @CFE_Contigo alguna novedad?

angelmartz_ retweeted

Rahul

@sairahul1

3 months ago

https://t.co/kZFYtIdHAj

107

484

12K

angelmartz_ retweeted

Nico

@nicos_ai

2 months ago

ADOBE ACROBAT ESTÁ ACABADO. Alguien ha creado un editor de PDF gratis y open source que corre 100% en tu máquina y no sube ni un solo archivo. Se llama Stirling-PDF. Cada vez que editas un PDF online, tu archivo se sube al servidor de otro. Tu NDA. Tu extracto bancario. Tu pasaporte escaneado. Stirling-PDF lo procesa todo en local y lo borra en cuanto termina la tarea. → 50+ herramientas PDF en una sola interfaz → Unir, dividir, comprimir, convertir, rotar, reordenar → OCR integrado para hacer buscables los PDF escaneados → Contraseñas, marcas de agua, firmas y redacciones → API REST completa para automatizar → Corre en Docker en tu propio hardware Adobe cobra 239$/año por Acrobat Pro. Esto hace lo mismo por 0$. • 81k estrellas en GitHub. • 30M+ descargas. • La app de PDF #1 de la plataforma. 100% open source. Enlace abajo👇