@orslimy חצי מסכים, אני חושב שהתפקיד יעשה תזוזה שמאלה וגם כמו המפתחים שלא יעלמו רק בגלל שיש agent כותב קוד- יש המון ערך להבנה של הארכיטקטורה, טרייד אוף, הסתכלות על הלקוח והריסקים. אני חושב שמנהל המוצר ימשיך להיות אבל ישקיע יותר במקומות שלא היה לו מספיק זמן להשקיע לפני כי עשה עוד המון
Very interesting moves, seen many partnerships/investments lately between hyperscalers and AI leaders.. each partnering for different purposes but mostly around chips, compute and offering expand
https://t.co/uvfBmDkoqQ
@testestear המפתח עדיין owner קצה לקצה, גם אם הקומפוננטה עובדת ויש coverage, צריך עדיין שהקוד יהיה maintainable ויאפשר לאנשים לקרוא אותו, כראש צוות אתה צריך להסביר מה עומד מאחורי ואת החשיבות זו בדיוק הפרדיגמה שמטעה היום הרבה מפתחים,פרודקשן זה מעבר רק לכתיבת קוד שנשפך מהפרומפט
https://t.co/sdVmyqGzqu thought about this lately while writing my post, what will happen with growing engineers seniority and talents, they ref to a US market data evidence paper: “Investing in early-in-career developers ensures today’s expertise becomes tomorrow’s intuition”
The web is full of apocalypse posts about how many engineers AI will replace, I think this is not the right question to ask, we should ask: If AI increases the leverage of engineers, so what is the right shape of an engineering org? https://t.co/CeKlELtafk
Its funny to read the posts around SaaS apocalypse, yes its true SaaS will need a moat to survive but when people say they replaced @mondaydotcom in a weekend project, they dont understand where the real difficulty in software lies - integrations, maintenance, security, data, etc
RIP Heroku, used them alot in the past, thank you for bringing https://t.co/hsCkw97JIA - Heroku were one of the foundational pillars of services as we see them today.
Heroku is transitioning to a sustaining engineering model focused on stability, security, reliability, and support. Heroku remains an actively supported, production-ready platform, with an emphasis on maintaining quality and operational excellence rather than introducing new features. We know changes like this can raise questions, and we want to be clear about what this means for customers.
There is no change for customers using Heroku today. Customers who pay via credit card in the Heroku dashboard—both existing and new—can continue to use Heroku with no changes to pricing, billing, service, or day-to-day usage. Core platform functionality, including applications, pipelines, teams, and add-ons, is unaffected, and customers can continue to rely on Heroku for their production, business-critical workloads.
Enterprise Account contracts will no longer be offered to new customers. Existing Enterprise subscriptions and support contracts will continue to be fully honored and may renew as usual.
Why this change
We’re focusing our product and engineering investments on areas where we can deliver the greatest long-term customer value, including helping organizations build and deploy enterprise-grade AI in a secure and trusted way.
Just came across this blog post and this is something I keep repeating:
Impact comes from engineers who think product, not just ship code. Creating impact is by asking "why", understand your users, challenge the assumptions and own the outcome
https://t.co/854RtAEc4X
People usually mix moving fast with building irresponsibly “Move fast does not mean: get low-quality buggy garbage out the door faster”
@allenholub
https://t.co/fG93XIg78T
“…we have a choice. We can chase complexity for its own sake, or we can build cultures that celebrate clarity, delivery, and impact. In the end, customers won’t remember whether you used Kafka…They’ll remember whether your product solved their problem.” https://t.co/kS6wBZsWUk
“The goal isn't to build a product that does everything for everyone. That's how you end up with bloated software that frustrates more users than it delights…” https://t.co/DZweBpbxJ7
Didnt think about this, but now after reading this post, this is one one if the key strengths of small models- less hallucinations https://t.co/yEnxjB2WMJ