HyruleMuse ▲✨ @_axtone

From Java to Golang | She builds | https://t.co/fgu6f5Cr0v | https://t.co/NpJG7fXnpm localhost Joined July 2025

Tweets

3K
Followers

12K
Following

1K
Likes

5K

HyruleMuse ▲✨ @_axtone

3 days ago

Que empiece el finde #mashle

2 1 48 1K 0

View Details

Angie | 안지 ❯❯❯❯ @AngieMatiz6

3 days ago

Inviten a chamba remota para una humilde dev y un devops 👉🏻👈🏻

18 8 264 11K 21

View Details

Agus Bellini | Always hiring @soyagusbellini

4 weeks ago

El mercado tech donde llovían ofertas por poner "React" o "Python" murió. Con los layoffs y tanta competencia, creé esta guía con lo que me sirvió a mí y mucha otra gente crack con exp para que puedan conseguir algo rápido y mejor. Espero les sirva :) x.com/i/article/2092…

17 36 465 60K 896

View Details

HyruleMuse ▲✨ @_axtone

3 days ago

@PrzmRaul Es un evento que vale mucho la pena, no para newbies

0 0 0 37 0

View Details

HyruleMuse ▲✨ @_axtone

3 days ago

Ya están a la venta los boletos para la #posadev2026 posadev.org Por allá nos vemos en Noviembre :)

3 4 35 2K 4

View Details

Simon Martinelli @simas_ch

4 days ago

Harness Engineering is not about writing bigger CLAUDE.md files. It is about designing the environment in which AI agents work. In my latest article, I explain why a minimal CLAUDE.md and a good Software Architecture Document belong together. The idea is simple: • CLAUDE.md is the map, not the knowledge base • The architecture document contains the actual architectural rules • Skills guide the agent before it starts coding • Tests and ArchUnit act as sensors that prevent violations from getting through The result is a shift from telling the agent what to do to designing a system in which the agent is guided and constrained by architecture. For me, this is where Harness Engineering and Spec-Driven Development really connect. Read the full article: Harness Engineering: Why a Minimal CLAUDE.md and a Good Architecture Document Belong Together martinelli.ch/harness-engine… #AI #HarnessEngineering #ClaudeCode #SoftwareArchitecture #SpecDrivenDevelopment #AIUnifiedProcess

6 13 58 3K 66

View Details

Agus Bellini | Always hiring @soyagusbellini

3 weeks ago

Si sufriste un despido o estás buscando cambiar de trabajo, no lo pongas ni lo grites a los 4 vientos en LinkedIn ni X. Mejor actualiza tus perfiles para dejar que te encuentren y ponerte a buscar en silencio. Acá te cuento cómo y lo que haría yo si me tocara (cosa qué ya me pasó en su momento)

Agus Bellini | Always hiring @soyagusbellini

4 weeks ago

17 36 465 60K 896

0 11 93 8K 96

View Details

HyruleMuse ▲✨ @_axtone

3 weeks ago

Feliz Viernes a todos :)

3 3 111 3K 1

View Details

Simon Martinelli @simas_ch

4 weeks ago

Spec-driven development is not one thing. There are three levels. Birgitta Böckeler from Thoughtworks describes them in her article: Spec-first: write a spec, generate the code, throw the spec away. Spec-anchored: the spec stays in the repository and evolves with the code. Spec-as-source: humans only edit the spec, the code is regenerated. Where are the tools? Kiro and spec-kit are spec-first. BMad is spec-first with good planning documents on top. OpenSpec is spec-anchored, with delta specs that merge into the main specs. And the AI Unified Process? Also spec-anchored. Requirements, use case specifications, and the entity model live next to the code for the whole life of the system. Tests are linked to use cases with @UseCase. Change the spec first, then the agent changes the code. I rarely type code myself anymore. So is this level 3? No, and on purpose. The code is not regenerated, the agent evolves it. That is the only way brownfield works. Nobody regenerates a 15-year-old ERP from a spec. You get most of the productivity of level 3 without depending on a non-deterministic compiler. And you keep a team that understands its own system. Full article: martinelli.ch/the-three-leve… #SpecDrivenDevelopment #AIUnifiedProcess #RequirementsEngineering #SoftwareArchitecture

4 21 175 13K 280

View Details

Enrique Almeida @ealmeida

4 weeks ago

1/4 Estoy leyendo un libro corto sobre Spec-Driven Development aplicado al desarrollo de software con IA. La propuesta es simple: describir el sistema mediante requerimientos, modelo de entidades y casos de uso. Y de ahi generar código, tests, documentación y verificaciones.

3 9 86 4K 62

View Details

HyruleMuse ▲✨ @_axtone

4 weeks ago

@gracegdays No sabía que ya eras mamá, muchas felicidades grace también por el añito de tu bby y aniversario de lactancia 🥹🥹❤️ te mando un fuerte abrazo y buenas vibras ojalá puedas descansar mejor pronto!

0 0 1 84 0

View Details

HyruleMuse ▲✨ @_axtone

4 weeks ago

@5eniorDeveloper Vaa, gracias por los tips colega 🫡🫡

0 0 0 136 0

View Details

HyruleMuse ▲✨ @_axtone

4 weeks ago

Compré el rompecabezas de Zelda Hyrule Map y estaba pensando en mandarlo enmarcar una vez terminado, lo han hecho ustedes? No quedan raros los cuadros?

5 1 73 5K 3

View Details

HyruleMuse ▲✨ @_axtone

4 weeks ago

Yo rumbo al fin de semana

1 8 126 2K 2

View Details

HyruleMuse ▲✨ @_axtone

4 weeks ago

@gracegdays sisisi ese mero :)

0 0 0 179 0

View Details

HyruleMuse ▲✨ @_axtone

4 weeks ago

@5eniorDeveloper No te pases están increíbles!!!! 😍

1 0 2 323 0

View Details

Lucas Biagetti @LucasBiagettiA

4 weeks ago

Paradójicamente aunque hace años que no codeo en Java estoy pensando mucho en este otro libro. Los patrones de diseño que expone pueden ser fácilmente trasladados al diseño de procesos útiles en la vida cotidiana. No es mala idea mirarlo.