Juan Pablo Ospina

🇨🇴 Software engineer 🧑‍💻 passionate about #architecture 🟢⚪ Soccer fan, ♟️ chess enthusiast, Rubik's solver, and 🤟 Rock. Advocate of software quality #tdd

[Juan Pablo Ospina @jpoh97]

"Learning how to learn is the greatest skill I learned in school. It's the skill of skills"

One of my new favorite phrases. Nice way of thinking 👏👏👏

[Vlad Mihalcea @vlad_mihalcea]

20 years later, I'm still learning a lot of things and still loving it.

Learning how to learn is the greatest skill I learned in school. It's the skill of skills.

[Javier Lopez @javisan81]

@iagolast Sobre waiters y changers, está charla de Kent beck es muy buena.
https://t.co/5yHelo6paD

[santi @santtiagom_]

Uno de los conceptos que más me gusta de Hermes es el learning loop.

La idea es que el agente no solo ejecute tareas, sino que pueda guardar aprendizajes para usarlos después.

Eso aparece muy claro con las Skills.

Una Skill puede ser una instrucción como:
→ “cuando revises un PR, mirá seguridad, tests, permisos y edge cases”.

Eso ya existe en varias herramientas.

Lo interesante de Hermes es que esa Skill puede mejorar con el uso.

Si encuentra una forma útil de hacer algo o le corregís algo, puede guardar ese aprendizaje como una nueva skill o mejorar una existente.

Ejemplo:
-> si revisando PRs aparecen seguido problemas de permisos, validaciones o rate limits, ese aprendizaje puede mejorar la skill de review o convertirse en algo más específico, como “review de endpoints públicos”.

Ese es el punto del learning loop:
convertir experiencia en capacidades que el agente puede volver a usar.

[Theo - t3.gg @theo]

My AI coding workflows have changed a lot over the last few months. 5.5 forced me to rethink everything, and I'm better for it.

[Vlad Mihalcea @vlad_mihalcea]

Reviewing code generated by AI offsets all the productivity gains you get by using AI. It takes a lot of effort to review and validate changes, and you cannot do that for 8 hours per day.

Unless you are vibe coding, the actual productivity gains are marginal in large projects where software mistakes cost a lot of money.

[Grady Booch @Grady_Booch]

The code is the truth, but it is not the whole truth.

A repository is the truth, but it is not the architecture: it represents only the development view of an architecture.

Therefore, by placing architectural description records as artifacts within a repository, you have a wonderful strange loop: the architecture is represented by multiple views, one of which contains a description of the entire architecture, including itself.

[Prof. Feynman @ProfFeynman]

In physics, as in life, the path of least resistance is often the least interesting.

[Dr Milan Milanović @milan_milanovic]

We are today No. 2 on Hacker News

Go and check our Laws of Software Engineering website: https://t.co/jgj81SHCLF

[Jason @mytechceoo]

CEO obsessed with token maxxing

[J.D. Nicholls is building in public @jdnichollsc]

Dejé de "hablar" de adopción de AI y Empecé a producirla en vivo. 🎬

Todos postean sobre AI. Casi nadie la vive (Talk is Cheap). Hoy armé una presentación completa sobre el tema — sin Keynote, sin Figma, sin slides a mano.

El stack que lo hizo posible 👇

🧠 NotebookLM como segundo cerebro sobre Adopción de AI — fuentes curadas, respuestas con citas reales
🔌 notebooklm-ai-plugin: conecto NotebookLM a Claude Code y chateo con mis fuentes desde la terminal
🎞 slides-ai-plugin: un agente toma el notebook y arma el deck mientras yo pienso en el mensaje
🎬 remotion-best-practices: la skill que convierte las ideas en video con animaciones
🚀 Todo open source, todo encadenable — adopción real no es usar UNA AI, es orquestar varias

Desliza hasta el final para llevarte los 4 assets 👇

📌 Guárdalo: es tu playbook cuando tu equipo por fin diga "ok, probemos AI en serio"

💬 ¿En qué parte de tu stack NO dejarías entrar a un agente todavía? Te leo abajo 👀

Construyamos esto juntos — PRs, forks y roasts bienvenidos.

Happy Vibe Coding! <3

#IA #VibeCoding #BuildInPublic #AgentSkills #AI #Claude #Tech #InteligenciaArtificial #AIAdoption

[Allen Holub. https://linkedIn.com/in/allenholub @allenholub]

In general, if you need to change a test because you changed the code, you didn't have a test at all. The whole _point_ of a test is that, when I make a change, I want to run the test to see if I've broken anything. A good test works both before and after the change. If I have to change the test, too, I've proven nothing. Any test that knows how the code works (as compared to what the code does) is fundamentally flawed.

I hear a lot about using an LLM not only to write code but also to write tests. I've rarely seen that work. IME, the LLM-generated tests are too fragile and test the wrong things (the implementation, not the intent).

People talk about spec-driven design, but the best spec you can have is a test—a test you write before you write the code. You don't write a test to see if the code adheres to a spec. The test IS the spec. Don't write specs. Write tests.

[Juan Pablo Ospina @jpoh97]

The Third Golden Age - Grady Booch https://t.co/lrETqurs4b via @YouTube

"The code is the truth, but the code is not the whole truth"

[Uncle Bob Martin @unclebobmartin]

@plainionist Learn the basics. Just as before. Learn them very well. Write assembler, C, Java, Ruby. Learn algorithms and data structures. Read the old classics.

And then start using agents.

Novices with power tools tend to lose fingers.

[Juan Pablo Ospina @jpoh97]

Software Craftsmanship en la era de la IA https://t.co/yxOMKh7421 #specialist expertise #metrics #automation #Technical Debt #silos

[Encapsulados teve | Tecnología @encapsulados_tv]

OJO ACÁ: ¿Cuántos programadores hacen sistemas y no saben cómo los usan? Hernán Wilkinson de @10pines dice que no ver al usuario no solo te complica el trabajo, también te roba una gran satisfacción. Dato para pensar.
🔗 https://t.co/yBWLZkyTDk

[Viv @Vtrivedy10]

https://t.co/Lb2gtM9SNs

[Bytebytego @bytebytego]

12 Claude Code Features Every Engineer Should Know

[PlanetScale @PlanetScale]

Postgres is using 80% of RAM, and that's a good thing.

But what's it actually doing with all that memory? At what point should you take action to mitigate usage?

Our latest blog breaks it down.

https://t.co/gZ5tYJB5nR

[Juan Pablo Ospina @jpoh97]

Distributed Systems 1.1: Introduction https://t.co/Ds1PMPCI1K via @YouTube

[Juan Pablo Ospina @jpoh97]

How to find your passion in life https://t.co/kJ7HVQJPpp

[Hernan Wilkinson @HernanWilkinson]

Tuve una charla distentida, amena y chistosa con @encapsulados_tv donde tocamos temas sobre Agile, AI y Desarrollo de Software

Se grabó hace de 6 meses, es muy interesante ver cómo cambió todo respecto de AI.

¡No se la pierdan! → https://t.co/srwcYtgSko

@10pines