"Entonces, ¿por qué tener una relación?
Sencillamente, porque vas a envejecer. Tu cuerpo va a fallar con el tiempo. Todos los placeres materiales irán perdiendo relevancia poco a poco. Ya no te importarán una mierda la comida, las posesiones, las vacaciones, los videojuegos...
@ElGaboncio "Women will say shit like this and then wonder why the entire planet and every major religion has imposed strict social restrictions on their sovereignty since the dawn of time in every place humans have ever lived"
@ElGaboncio Jajajajaj le lanzo "mira las mujeres son unas narcisistas que solo para alimentar su ego y destruir el de tu novia van a tartar de seducirte, tu solo das asco" unos seres de luz
@tebayoso El problema es Argentina el 50% del congreso son una manada de monos que cada vez que puede le gritan al mundo que van defaultear, gran parte de la población piensa que la solución a todo es devaluar y ganar 100 usd mensuales es un milagro que el riesgo pais no este en 5000
El problema de trabajar con IA no es que te quite el trabajo.
Es que ahora puedes terminar haciendo el trabajo de 3 personas, cobrando lo mismo.
Y la empresa todavía te va a preguntar por qué no terminaste más rápido.
Si mis horas trabajas se correlacionaran directamente con mi ingreso, trabajará 15 horas al dia feliz pero en la mayoria de los casos no es es asi por eso se suele hacer lo mínimo necesario
Vercel CEO Guillermo Rauch (@rauchg) says the old work week is officially dead:
“You would think, ‘AI has arrived, & we're all working 2 hours a week.’”
“The opposite is happening. I get text messages at midnight from the CEOs and CTOs of these companies.”
“It’s more like 7/7/7: 7 days a week from 7 AM to 7 PM.”
Abismal la distancia entre claude code usado para programar y claude code usado para analizar datos.
Mi conversacion viene siendo algo tipo
Yo: Pará, estás suponiendo X? De donde lo sacaste?
Claude: de mis dos huevos
J’ai entendu dire que la France était finie, qu’il était trop tard pour la sauver.
Mais la France est toujours aussi belle, enviable même. Sa grandeur n’a pas disparu, elle ne demande qu’à renaître.
Nous avons surmonté en un an un problème cent fois plus grave, sans avoir les moyens dont dispose la France.
La France pourrait y arriver en une semaine.
When I was writing Unreal Engine 1, my time was divided as follows:
- Around 30% went to seriously deep coding on hard problems: assembly language texture mappers, C++ BSP trees, data persistence, object oriented systems design, and networking.
- Around 70% was just typing and refactoring large bodies of code needed for a complete engine feature set. This was not hard, and while I was doing it my mind was mostly on the deeper coding topics, thinking and planning for what's next. It didn't feel much different from vibe coding today, except that it was just me typing code on an IBM Model M keyboard rather than prompting it and reviewing the results.
So, it has always seemed perfectly logical that we would rely on AI for that 70%, once the AI could do it with a similar quality standard as we could, which has never been perfection. It came as no surprise that, after a few years of AI model evolution, it was able to take the reigns on that 70% and free up programmers' time for more valuable tasks.
What's more of a surprise is the emergence of AI as a sort of insta-Carmack able to solve hard technical problems quite cleverly and often cleanly, and that it's able to reason about and work in complex 3D scenes both by operating the tools and by directly understanding the raw data files.
I abandoned assembly language in 1998 when out-of-order CPUs made much simpler C/C++ code faster, and never I missed it. If prompting through architectural documents, concept art, and design plans can transcend typing code and tweaking vertices, that will enable developers to spend their time on higher-level, higher value technical and creative tasks.
What matters is the end product, whether it's a game or an engine. Anything developers can do to try out more ideas and make better software and games faster is a win for everyone.
Primero escribieron TypeScript en TypeScript.
Después lo reescribieron en Go “para que fuera más rápido”.
Luego alguien lo portó a Rust con IA (porque había tokens de sobra).
Y ahora lo volvieron a escribir en TypeScript… y dicen que es más rápido que el de Go.
Están dando vueltas en círculos. Ya los desarrolladores no saben qué hacer con sus tokens.