Me está costando horrores conseguir lo que necesito y casi todos los bloqueos son burocráticos. Tampoco es tan difícil lo que pido.
Secuenciar mi tumor y desarrollar vacuna a partir de ahí.
Bueno pues tardamos tanto que ya tengo extendida la metástasis.
En hueso estaba más tranquila, no es órgano vital, pero en hígado la cosa cambia, y si salta a cerebro, que es el siguiente sitio ya estoy perdida y no hay vacuna que valga.
Tengo el dinero, tengo los medios, pero lo que no tengo es tiempo para malgastarlo en burocracias paradas porque es agosto
SOLID Principles Explained with Clear Examples:
𝐒 - 𝐒𝐢𝐧𝐠𝐥𝐞 𝐑𝐞𝐬𝐩𝐨𝐧𝐬𝐢𝐛𝐢𝐥𝐢𝐭𝐲 𝐏𝐫𝐢𝐧𝐜𝐢𝐩𝐥𝐞
A class should have only one reason to change.
- Example: Instead of one giant User class that handles authentication, profile updates, and sending emails, split it into UserAuth, UserProfile, and EmailService.
𝐎 - 𝐎𝐩𝐞𝐧/𝐂𝐥𝐨𝐬𝐞𝐝 𝐏𝐫𝐢𝐧𝐜𝐢𝐩𝐥𝐞
Classes should be open for extension but closed for modification.
- Example: Define a Shape interface with an area() method. When you need a new shape, just add a Circle or Triangle class that implements it.
𝐋 - 𝐋𝐢𝐬𝐤𝐨𝐯 𝐒𝐮𝐛𝐬𝐭𝐢𝐭𝐮𝐭𝐢𝐨𝐧 𝐏𝐫𝐢𝐧𝐜𝐢𝐩𝐥𝐞
Subtypes must be substitutable for their base types without breaking behavior.
- Example: If Bird has a fly() method, then Eagle and Sparrow should both work anywhere a Bird is expected.
𝐈 - 𝐈𝐧𝐭𝐞𝐫𝐟𝐚𝐜𝐞 𝐒𝐞𝐠𝐫𝐞𝐠𝐚𝐭𝐢𝐨𝐧 𝐏𝐫𝐢𝐧𝐜𝐢𝐩𝐥𝐞
Don't force classes to implement interfaces they don't use.
- Example: Instead of one fat Machine interface with print(), scan(), and fax(), break it into Printable, Scannable, and Faxable. A SimplePrinter only implements Printable.
𝐃 - 𝐃𝐞𝐩𝐞𝐧𝐝𝐞𝐧𝐜𝐲 𝐈𝐧𝐯𝐞𝐫𝐬𝐢𝐨𝐧 𝐏𝐫𝐢𝐧𝐜𝐢𝐩𝐥𝐞
High-level modules should not depend on low-level modules. Both should depend on abstractions.
- Example: Your OrderService should depend on a PaymentGateway interface, not directly on Stripe or PayPal.
The real power of SOLID is not in following each principle in isolation. It's in how they work together to make your code easier to change, test, and extend.
♻️ Repost to help others in your network
I'm pretty sure everyone at my company saw this article and now they all think we're in an AI crisis.
We're not in an AI crisis. We use Claude to summarize Slack threads.
But here's what's actually interesting: this whole panic reveals something nobody wants to admit.
Every company in America has been bullshitting about their "AI strategy" for two years.
We all saw the hype. We all knew we had to say something. So we rebranded our existing automation as "AI-powered" and called it a day.
My company isn't special. We're all doing the same thing.
The problem is now the executives actually believe their own bullshit. They think we have "significant AI exposure" because they've been telling investors we're "AI-first."
I just got pulled into an emergency meeting. Six executives asking me to explain our "AI dependency matrix."
There is no AI dependency matrix.
There's Claude for meeting summaries, there's some sentiment analysis in our support tickets that came free with Zendesk, and there's whatever Gmail is doing when it autocompletes my sentences.
But I can't say that in a room full of people who told their boards we're "transforming the business through AI."
So I said we have "distributed AI touchpoints across multiple vendors with no single point of failure."
Which is technically true. We use a bunch of different services that all have AI features we mostly ignore.
The CFO asked if we should "hedge our AI exposure."
I have no idea what that means. Neither does he.
What am I going to do: nothing. Because in three weeks, Anthropic will say something reassuring, the stocks will recover, and everyone will forget this happened.
But I'll have documentation showing I recommended a "risk assessment" that mysteriously never got prioritized.
The funniest part is that half these executives probably don't even know what Anthropic is. They just saw "AI" and "crash" in the same headline.
We're all pretending. The whole industry is pretending.
And articles like this just remind everyone how fragile the pretending is.
🔴 Una caída de los servidores informáticos de Adif paraliza la alta velocidad en Madrid
Debido a esta caída de los servidores, la información de llegadas y salidas de las dos principales estaciones madrileñas (Atocha y Chamartín) no está disponible 👇🏻
https://t.co/5YNi5lKrZc
I tested @lovable, @boltdotnew, and @v0 with the same product prompt.
Thought I knew which AI design tool would win
Let’s just say, I was very wrong.👇🧵
OpenAI acaba de lanzar cursos gratuitos sobre IA.
Cursos para principiantes e ingenieros.
Y son 100 % gratuitos.
Aquí tienes los 6 mejores cursos que no te puedes perder ↓
Desarrollé un #prompt para aprender lo que quieras usando los "Niveles de incompetencia".
Solo le pasas el tema y el tiempo que tienes disponible y vámonos.
Explicación en el video, prompt en el siguiente tweet.
❤️ Suelta RT para que tus compas también aprendan.
Clean Architecture con TypeScript.
Repositorio con un ejemplo de la famosa kata "users"
🔗 https://t.co/qCYNVaHuUG
- Monorepo con NPM Workspaces
- Husky para git hooks
- Biome para Linting y formato
- Github Actions para CI
Check your color contrast for accessibility natively in @figma—rolling out over the next week or so. Find it in a color picker near you!👏👏👏
• Auto adjusts for graphics / text size and weight
• Visualizes out of range options
• Click indicator to get accessible recommendation.