<oembed><type>rich</type><version>1.0</version><title>jeffg wrote</title><author_name>jeffg (npub1zu…6c2uc)</author_name><author_url>https://nostr.now/npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>gm. software engineering in the classic sense is dead. &#xA;&#xA;before you dismiss that as obvious, consider the following:&#xA;&#xA;1. agents have reached a critical level where they&#39;re better than almost all human programmers. even when it comes to planning complex architectures.&#xA;2. we don&#39;t need to drive things on machines we have with us any more. in fact, sitting in front of a screen all day is now an anti-pattern. a powerful laptop can&#39;t beat a good desktop (and is less upgradable). you can also leave your iOS, Android, browser, and other hardware attached to your desktop for agents to use.&#xA;3. the judgement of what to build (vision) and how to build it (the values that drive decisions while pursuing that vision) has become THE critical skill.&#xA;&#xA;a lot of engineers and builders (myself included) are still holding on to vestiges of a bygone era, mostly because we enjoy the process, but if we&#39;re serious about building something impactful, we have to learn to get out of the way.&#xA;&#xA;The Way™&#xA;1. Define the problem to solve (vision)&#xA;2. Define the constraints (values)&#xA;3. Deliver feedback (your own to start, from users as soon as possible)</html></oembed>