@poteto I get it, but, productivity = lines of code written is not the product culture present in every company. Saying "No" to something that won't add value is also being productive
@barckcode Cada uno reaccionamos diferente a las situaciones, quizá tu dopamona se dispara al ver materializado algo que imaginaste. Para otra gente, la dopamina está en toparse con una pared y poder escalarla (no en el resultado en si)
@silvercorp@Infonavit Ya no es lo que era antes, pero, quizá la parte más usable es el Cofinavit, terminas con dos créditos, el de Infonavit y el del banco, pero, te ayuda a acceder a un monto más alto.
@leonpalafox Yo sí, una startup, la cultura de ingeniería era muy alta, enfocada mucho en la calidad de la plataforma. Pero, independiente de eso, no importa quien escriba el código, una buena arquitectura y atención al detalle es lo que te lleva a grandes cosas
@barckcode@borjaperfra También existe mucho el miedo de ser reemplazado, todo el hype y humo genera mucha carga cognitiva, por salud mental, mucha gente prefiere bloquear ese ruido y seguir con su rutina normal. Falta mucho trabajo para simplificar la historia
security and even data strategies. Granted, the code is simply the most visible outcome, but, it is only the tip of the iceberg. LLMs are incredible copilots, but we are a long way off from autopilot. Engineering remains a game of critical thinking and trade-offs.
Lately, my feed has been flooded with "AI killed the developer" hype. I see CEOs claiming no one writes code anymore and influencers promising you can build a unicorn in a weekend. It’s a lot of noise and some impressive marketing stunts. 🧵
The funny thing is: software engineers were never actually paid top dollar for writing code, engineers are paid handsomely to solve problems. Building a product isn't just about writing code, it’s about understanding the "why", architecting the solution, managing databases,
@LBacaj The programming language does not make a product to fail or to succeed, use whatever you feel more comfortable with, customers pay for products that solve problems, the tech stack is irrelevant
@AdamRackis@thdxr The opposite is true too though, you can increase retention by having customers love the way your product behaves. There is no "one size fits all" here