<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jeff Fohl on Medium]]></title>
        <description><![CDATA[Stories by Jeff Fohl on Medium]]></description>
        <link>https://medium.com/@jefffohl?source=rss-d1c3b9405e86------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*SSoRZOBwCp41QpF_.jpg</url>
            <title>Stories by Jeff Fohl on Medium</title>
            <link>https://medium.com/@jefffohl?source=rss-d1c3b9405e86------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 06:46:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jefffohl/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[In Praise of Slowness]]></title>
            <link>https://medium.com/@jefffohl/in-praise-of-slowness-74b3d5bc2531?source=rss-d1c3b9405e86------2</link>
            <guid isPermaLink="false">https://medium.com/p/74b3d5bc2531</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[thinking]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <dc:creator><![CDATA[Jeff Fohl]]></dc:creator>
            <pubDate>Fri, 18 Jul 2025 19:14:11 GMT</pubDate>
            <atom:updated>2025-07-18T19:14:11.428Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y7BQtBpa9G_rO3roe0qI_Q.jpeg" /></figure><p>Like many developers today, I have been using the latest AI models as a coding assistant. Mostly, I have been using <a href="https://cursor.com">Cursor</a>, but I’ve dabbled with a few others. I try to stay away from “vibe coding”, which to me implies that you delegate pretty much everything to the coding agent, and just go by feel. It is really important to actually understand what the agent is doing. This means going a bit slower, so you actually read through everything it has done, and when it doesn’t make sense, either ask the agent to explain it until it does make sense to you, or do some other research to figure it out. I have found that if you just let the agents rip, they will go off the rails pretty easily, over-engineer the system and creating greater complexity, or get caught in endless bug loops. So, working with them sometimes feels like managing an extremely fast and eager senior developer that you have to constantly be reining in, like a self-driving car that wants to put the accelerator to the floor. Woah buddy! Writing software with a coding agent often feels like my main tool is working the brake pedal.</p><p>Recently, there has been some talk and I believe at least one study about the negative effects of heavy AI usage. The gist of these concerns is that with heavy usage of these tools, your own intellectual capabilities begin to deteriorate. When I work with these agents, I would tell myself that I am reading everything and making sure that I understand what is being written before committing it. And this is true. But, there is a difference between reading and writing. Writing is much harder, and engages our minds in a much deeper way.</p><p>So, I decided to try an experiment. For this week, I chose not to use an agent at all for my coding tasks. I would write everything from scratch, and reason through everything on my own, not even consulting the AI agent for advice or <a href="https://en.wikipedia.org/wiki/Rubber_duck_debugging">rubber-ducking</a>. I was disturbed to find that the results were noticeable. I noticed that whenever I got stuck or had some uncertainty, I could feel the dopamine telling me to go ask the AI, or get it to solve the problem for me. Though I don’t have a way to measure my own speed at coding, I felt that my speed had dropped. I got stuck on problems for hours, going back and forth on various design decisions. Moderate problems now seemed hard. Did I break my brain with AI? Yikes!</p><p>Another noticeable thing happened though. After a few days, my speed and flow started to increase. I could feel my old proficiency coming back. It was a good feeling. It was then that I realized the obvious. Your brain is like a muscle. If you don’t exercise it, it will start to get weak.</p><p>It is not possible for me to write code as fast as an AI, any more than I can run as fast as a car. And the AIs will only get better. Using them can get projects completed much more rapidly, even with their faults. However, there is most definitely a cost. In a way, this is nothing new. In our modern world, with cars to get us around faster than we could by walking, we now have to carve out time in the day to maintain our body, to prevent it from deteriorating. I am going to guess that “going to the gym”, or “working out” was probably not a common activity for most people 200 years ago (I could be wrong though, historians are welcome to chime in here) — but now daily exercise is a must.</p><p>So too in the age of automated thinking, I am making sure to deliberately find the time to slow things down periodically. Turn off the AI, and think things through with my own slow wetware. Write that code by hand. Multiply those matrices on paper. Memorize those scales on the fretboard. Draw that picture in pencil, or paint that picture with oils.</p><p>Just as we don’t actually have to let our bodies turn into mush because of automated transportation, so too do we not need to let our brains turn to mush just because there is a faster way to think.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74b3d5bc2531" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Very, Very, Very Long Story of Intelligence]]></title>
            <link>https://medium.com/@jefffohl/the-very-very-very-long-story-of-intelligence-51e45ebef8c9?source=rss-d1c3b9405e86------2</link>
            <guid isPermaLink="false">https://medium.com/p/51e45ebef8c9</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[evolution]]></category>
            <category><![CDATA[intelligence]]></category>
            <dc:creator><![CDATA[Jeff Fohl]]></dc:creator>
            <pubDate>Wed, 09 Jul 2025 00:28:48 GMT</pubDate>
            <atom:updated>2025-07-09T00:28:48.435Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wHPVK9qRXpKzFTTIqffUaQ.jpeg" /></figure><h3>“A Brief History of Intelligence” by Max Bennett</h3><p><em>You can’t really know where you are going until you know where you have been.</em></p><p>― Maya Angelou</p><p>In today’s world of Large Language Models, AI agents, AI labs, and a flood of arXiv papers arriving every day, it all can seem quite overwhelming. How can one get one’s bearing in such rapid change? How can we prepare ourselves for what is coming next? Well, I actually don’t have that perfectly figured out — I’m not sure anyone does. Though, I do strongly believe that if you want to predict where something is going, look to its roots. Instead of focusing on the future, try looking backwards for a while.</p><p>Artificial intelligence did not come out of nowhere. Its roots are decades old, grown bit by bit, by people trying to figure out how to get computers to do what humans and other animals do with their brains. Being interested in where artificial intelligence is going, it can be worthwhile looking back at these efforts. But, what if we looked even further back? Where in the world did intelligence come from in the first place? This is the question Max Bennett asks in his excellent book <a href="https://www.abriefhistoryofintelligence.com/"><em>A Brief History of Intelligence</em></a>.</p><p>Bennett is an AI entrepreneur, who has founded more than one successful AI company. As someone working with AI, he naturally became interested in the roots. After extensive readings, he found that he wanted a book that would summarize how intelligence evolved. Not finding it, he set out to write it himself.</p><p>In this book, Bennett takes on the herculean task of zooming all the way back to the very origins of life, using the current scientific consensus. From there, he maps out, step-by-step how it is believed that matter gave rise to life, and life gave rise to intelligence, through the forces of evolution.</p><p>He breaks down this history of intelligence into 5 key breakthroughs that occurred over the last billion years:</p><ul><li><strong>600 Million Years Ago: Steering</strong>. Not all animals have brains, but some need them. Specifically, those that need to steer their movement. These are the “bilaterians”, a category to which we belong. The earliest brains were probably dedicated to steering toward food, and away from danger. Yes, your great-<em>n</em>-grandparents were worms.</li><li><strong>500 Million Years Ago: Reinforcing</strong>. The Cambrian Explosion unleashed tremendous evolutionary forces, which gave birth to a dizzying variety of animals. It also introduced new brain structures such as the basal ganglia, the cortex, the hippocampus, and other structures, which enabled animals to learn in more powerful ways using reinforcement learning.</li><li><strong>200 Million Years Ago: Simulating</strong>. The rise of the mammal and the neocortex. With the neocortex came the gift of simulating. Simulation allowed for the creation of a world model in the brains of early mammals.</li><li><strong>15 Million Years Ago: Mentalizing</strong>. The rise of primates, and the theory of mind. The ability to not only simulate the world, but to simulate the minds of others and yourself allows for the transfer of knowledge, predicting the actions of others, and long term planning.</li><li><strong>100 Thousand Years Ago: Speaking</strong>. Early humans developed language, which accelerated knowledge transfer and learning, and also gave rise to both altruism and cruelty.</li></ul><p>And of course, we are now on the precipice of a 6th breakthrough — what we call Artificial Intelligence. I believe that it is important to understand that intelligence is a physical phenomenon in the universe that has evolved over time. The advent of intelligence on microchips is just one more step in this evolution. Though, it is hard to overstate the impact this is going to have. In my mind, it is comparable to the transition from single-cell organisms to multicellular animals. The future is hard to predict. But, zooming out as far as possible on the arc of evolution gives us the best perch from which to view the zaniness of the moment we live in.</p><p>Max Bennet’s book is titled “A Brief History of Intelligence”, but the actual history is anything but brief. It’s not really possible to cover everything in a single book, or even in a single lifetime. But Mr. Bennett does leave the reader with a sense of continuity. It is at the very least a plausible outline for the extremely large story. Squeezing a billion years of evolution into 400 pages is quite the feat.</p><p>I am not a neuroscientist, or evolutionary biologist, so I cannot confidently critique this survey of 600 million years of brain evolution. Therefore, I trust Bennett’s analysis until I am presented with authoritative counter-arguments. I do know that Bennett consulted with a large number of well known scientists, so I have good reason to have faith in his work.</p><p>To anyone interested in where things are going, I highly recommend this book. I am in the middle of my second reading.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51e45ebef8c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Rise of the Intelligence Designer]]></title>
            <link>https://medium.com/@jefffohl/the-rise-of-the-intelligence-designer-67ca16e22e43?source=rss-d1c3b9405e86------2</link>
            <guid isPermaLink="false">https://medium.com/p/67ca16e22e43</guid>
            <category><![CDATA[user-experience-design]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Jeff Fohl]]></dc:creator>
            <pubDate>Fri, 27 Jun 2025 16:55:04 GMT</pubDate>
            <atom:updated>2025-06-27T16:55:04.400Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WOOZrDW46StedC05v0KvkA.jpeg" /></figure><p>Since late last year, I have been working on an “AI agent” project. What that term actually means, I am still figuring out. During this process, I am discovering many things which are causing me to recalibrate what it means to design such a tool.</p><p>For the last several years, I have played a role that would usually be described as a User Experience Designer. The term “user experience” was coined in 1993 by <a href="https://en.wikipedia.org/wiki/Don_Norman">Don Norman</a> for his group at Apple Computer where he was working at the time. He <a href="https://www.youtube.com/watch?v=9BdtGjoIN4E">describes</a> user experience as, “It’s everything that touches upon your experience with the product, and it may not even be near the product. It may be when you are telling someone else about the product… It’s a system, it’s everything.” I truly believe this is important, and have worked hard to incorporate this into my own work. Working with artificial intelligence however, adds many new dimensions to what it means to design something.</p><p>Before computers were on the scene, designers could usually feel somewhat confident that the thing they were designing wouldn’t change too much once it left the design studio and entered the owner’s possession — whether it was furniture, a coffee mug, or a car. Although mechanical objects could get into various states through the controls offered, most of the time the variety of these states were finite and knowable, allowing the designer to craft and test the experience of each of these states. When designing an electric teapot, the designer can design how to make the teapot easy to handle when the water is hot, because this is an easily predictable use case. It would be reasonable for the designer to assume that the teapot won’t turn into a toaster after the user turns it on.</p><p>With the advent of software, the range of possible states that products could get into expanded dramatically. Most software was still largely deterministic. The designer could map out all of the possible states the application could get into, and craft good experiences for the end user before they encounter them.</p><p>Recently, we have passed into the age of true artificial intelligence. I say “true” because I think AI has finally reached the point that matches what most people have traditionally considered AI to be: that is, a computer that can talk like a human, sound like a human, look like a human, and think like a human. What people imagined AI to be in the 20th century does now seem to be a reality.</p><p>With these systems come all kinds of new considerations for the designer. As I mentioned, designers traditionally worked with systems that were largely deterministic. You could map out all of the possible states and design for them. With AI, this becomes much more difficult. It is much harder to predict what will come out of an AI system. In fact, you don’t want to be able to predict this, because if you could, you wouldn’t need the AI in the first place!</p><p>So, if we take Don Norman’s edict to heart — that designers need to be deeply interested in the entire end-to-end experience of the user, how do we design for systems that are so unpredictable?</p><p>Well, it turns out there are a lot of things we can do, and many choices can be made. But, they are much different things than what UX designers are used to doing for the last 30 years. Instead of deciding whether to develop the product as a Web app or an iOS app, we might be selecting different models from OpenAI or Google. Instead of designing where and when to put a button, we might be thinking about prompt engineering. Instead of considering the efficacy of a modal interface, we could be fine-tuning the model. Instead of designing a caching mechanism for the UI to make it more responsive, we might be designing a Retrieval Augmented Generation (RAG) system to give the system more effective knowledge.</p><p>This is tough stuff, and there is a whole lot to learn, but knowing how to work with these tools, and how to make these decisions are essential for designing an effective AI experience.</p><p>There is a lot of talk lately about how AI is likely to put a lot of people out of work. Yes, it will take on a lot of the work that designers and software developers have done traditionally. But, as always, new technologies will create new jobs too. One of these jobs could justifiably be termed the <strong>Intelligence Designer</strong>. The person tasked with this job would have the responsibility of crafting the AI to meet the needs of the end user as effectively as possible. Although some Intelligence Designers will be involved with the fundamental architecture and training of the AI models, the vast majority of people in the field will be working with the output of the big AI labs. Their job will be to take the raw capabilities of these models, and shape them into a wide variety of use cases, with different knowledge, personalities, and agentic behaviors.</p><p>So, if you are a software designer worried about jobs going away — fear not! If you are interested in designing AI systems, there is even more work for you. But, be ready to expand your ideas about what it means to be a designer. If you want to be an Intelligence Designer, you will need to think deeply about how these systems work, and be willing to let go of many old assumptions. Instead of designing GUIs, you will be designing something much more ambiguous, and probably a lot more exciting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67ca16e22e43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can You Build What You Design?]]></title>
            <link>https://medium.com/@jefffohl/can-you-build-what-you-design-936d1f28295f?source=rss-d1c3b9405e86------2</link>
            <guid isPermaLink="false">https://medium.com/p/936d1f28295f</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Jeff Fohl]]></dc:creator>
            <pubDate>Mon, 09 Jun 2025 20:13:19 GMT</pubDate>
            <atom:updated>2025-06-09T20:13:19.385Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sYOsBW8NDZMe5WadCvSd8w.jpeg" /></figure><p><strong><em>What I cannot create, I do not understand</em></strong></p><p><em>- Richard Feynman</em></p><p>When I first started my career in the 1990s, with training in the visual arts, I thought of myself as a “designer” (a very general term, which I don’t actually like, due to its vagueness). What I could bring to a project was my keen eye, craftsmanship in the graphic arts, and ability to problem solve. It being the 1990s in the Bay Area, I naturally became involved in various software projects, starting with CD-ROM development and quickly moving on to the World Wide Web as that wonderful platform exploded on the scene.</p><p>My role as a designer was shaped by the expectations of my employers and peers as much as my own ideas about what I was all about. Most software teams require certain degrees of specialization. There’s the backend engineer, the frontend engineer, the database engineer, the cloud engineer, the user experience designer, the user interface designer, the user experience researcher, et cetera. When you are filling one of these roles, it is easy to think of yourself as having a special job that only you can do. And the inverse of this is of course, that other jobs are not your responsibility. So, the designer works hard, focused on the end-user experience without really caring at all about whether the data is stored using SQL or NoSQL, or what a controller is, and whether it is written in Java or Go. And why should they? Does it actually matter? Well, no and yes.</p><p><strong>No, It Doesn’t Matter</strong></p><p>The end user doesn’t care what technology you actually use to provide them with the application or tool that you are designing for them. The only thing they care about is their experience with it. Is it doing the job they need to be done? Are they enjoying it? Do they love it?</p><p>They don’t care if you wrote the app in Swift or Go. They don’t care what chip architecture is being used. If that is true why should I, the designer, bother myself with these implementation details? A very good point if you, the designer, are content to work within previously established patterns.</p><p>For example, let us say you are designing for the Web around 2009. The Web is a very mature platform, with tons of frameworks and design patterns easily available. As a designer, you have the freedom to create an infinite variety of Web interfaces using the standard tools of the time, which would usually be a handful of applications provided by Adobe. This is all fine and good, and some really beautiful designs were created during this period.</p><p>However, one client of yours is a big fan of the iPhone, which by then had been around for only two years. They noticed that your beautiful design doesn’t look so great on the iPhone. Everything looks super tiny, and is hard to read. They ask you why, and you can only think, Well, that’s just the way it is. iPhones have small screens, so what is there to do? You might think that, unless you happen to be <a href="https://ethanmarcotte.com">Ethan Marcotte</a>.</p><p>Ethan is a designer who is not afraid of the technical details. In 2009 or 2010, he noticed some interesting things about the technical specifications for HTML and CSS. There was this new thing in the latest specification for CSS called “media queries”. Media queries allow authors of stylesheets to write different classes for different contexts, such as the printed page, or screen. They also allow authors to target different sizes of screen. With this knowledge, and several other concepts, Ethan introduced a new way of designing for the Web, which he called, “<a href="https://alistapart.com/article/responsive-web-design/">responsive design</a>”. These concepts changed the way designers worked across the entire industry.</p><p><strong>Yes, It Does Matter</strong></p><p>If Ethan had settled for letting the engineers handle the implementation details of his designs, while he stuck to the world of Adobe products he would never have landed on his idea of responsive design. His curiosity and willingness to dive in and look under the hood allowed him to find solutions that had until then remained largely hidden to most designers.</p><p>The thing is, the way things work under the hood do have an effect on the end user. If you are truly interested in the end user experience, the more you know about how these experiences are built, the better designer you will be. An application that is slow to respond to user’s input is as much a part of the end user experience as the information hierarchy of the user interface. A search tool that can’t retrieve results relevant to the user’s request is terrible even if the display of the search results is visually beautiful.</p><p>Yes, software engineering is hard. I’ve been working at it for decades and I still feel like I have barely scratched the surface. I often feel like I am stretching myself too thin, going outside of my lane, trying to take on too much. Sometimes I feel like I am neglecting the visual design aspect of my practice too much. But I persist, because I truly believe that in order to truly master the art of software design, one must strive towards mastery of all of the components that make up a product.</p><p>The end user doesn’t care what was used to make the product go. But the more the designer does care, the better it will go.</p><p>Keep trying. It is hard, but it is also fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=936d1f28295f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Craft in the Age of AI]]></title>
            <link>https://medium.com/@jefffohl/craft-in-the-age-of-ai-c9c96480ed8c?source=rss-d1c3b9405e86------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9c96480ed8c</guid>
            <category><![CDATA[art]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[craft]]></category>
            <dc:creator><![CDATA[Jeff Fohl]]></dc:creator>
            <pubDate>Tue, 27 May 2025 19:57:41 GMT</pubDate>
            <atom:updated>2025-05-27T19:57:41.135Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lUlFmrLjG3IvhR1JjXP7jg.jpeg" /><figcaption>Not AI</figcaption></figure><p>Craft has always been at the center of what I do. Whether working as an illustrator, graphic designer, user interface designer, or software engineer, mastering the tools and techniques of the craft are at the heart of my professional life. Mastery of craft is of course essential in order to bring an idea to life. But what is perhaps even more valuable to me is the pure pleasure derived from the practice of the craft. Being in that flow state, where our sense of time shifts, and our focus narrows to a place where the only thing that exists is the art and ourselves, which meld. My dream is to spend all of my working day in a flow state. But, it is hard to do when the world demands so many <em>different</em> things of you. I think we can all relate.</p><p>Recently, <a href="https://www.instagram.com/reel/DClLEqoPkls/">Ben Affleck</a> was giving his opinion on the role of AI and the film business. His quote, “Craftsman[ship] is knowing how to work. Art is knowing when to stop.” distilled the essence of his argument, I think. While I largely agree with him, the trouble is that in my opinion, art emerges from, and is deeply related to craft. The best artists don’t sit around scratching their chins thinking about “art” and then when they have some great idea, they hand it off to some “craftsman” to execute it. In my experience it is the other way around. Through the practice of the craft, being in that deep flow state, one with the medium, that is where the artistic ideas emerge from some deep mysterious well.</p><p>Think about some of your favorite artists in music, visual art, film, or writing. Did they just create one or two great works, or a huge volume? Usually it is the latter. Prince. Bach. Scorsese. Picasso. The list goes on, but all of them gained mastery of their craft by practicing it deeply and producing large bodies of work. And from this mastery grew their art.</p><p>So, what to do when Generative Artificial Intelligence is mastering much of the craft that artists have practiced? Will we lose the ability to be an artist, to “know when to stop”? I am not sure, actually.</p><p>One approach is to simply ignore what AI is capable of, and simply practice your craft of choice. Into oil painting, guitar, or writing? Go for it. This is all fine and well of course for the hobbyist or the independently wealthy artist. The challenge occurs when it becomes no longer economically viable to do it the human way. Humans are just too damn slow. When I was working as a professional illustrator, I would usually take a few days, and sometimes a week or more to execute a paid commission. Compare that to today where it literally takes minutes to generate something of equal quality. Well, let’s be honest, usually even better than I could ever achieve. This makes it harder and harder to justify the time and expense needed for the human to practice the craft.</p><p>The same goes for software engineering, another craft I have practiced professionally. In today’s workforce, how many engineers can justify doing everything as they were a few years ago, without generative AI doing more and more of the work? When economic forces are at work, humans just can’t keep up.</p><p>So, what to do? Will meaningful “art” start to disappear? I would like to think not. Throughout history, there has been example after example of some new technology coming along that threatens to eliminate some meaningful craft from the lives of humans. And usually, the predictions of loss do actually come true. However, what always seems to happen is that humans find new crafts to master, and from these new crafts come new ways of creating meaning.</p><p>The thing is, I don’t really know at this point what these future crafts will be. My intuition is they will in some way be a melding of AI tools and human craft and artistic endeavor. Perhaps I am seeing a glimmer of how this will work in my experience working with AI-powered IDEs such as Cursor. There, the AI is not really writing all of my code for me in one fell swoop. The AI tools are allowing me to build more and do it more quickly. But, I often feel more like an engineering manager than a software engineer when working this way. I already miss the old days of painstakingly piecing together an application line by line, headphones on, lost in the flow state. But, it is hard to justify the time it takes to work that way. Why build an API in a few weeks, when you can do it in a day?</p><p>In an age of AI, two big questions are coming into focus.</p><p>The first question is: What will deep mastery of craft in the age of AI look like? Will it be some kind of deep melding of the human with the AI? We have some glimmers of this possibly in what we are seeing in software engineering. The challenge for the practitioner it seems is how to take advantage of the speed of the AI without losing your own deep understanding of the craft. I don’t know the answer to this.</p><p>The second question is: True mastery of any craft takes a long time. In an age when the economic utility of any craft has increasingly shorter lifespans, how will humans ever get to deep mastery? If it can take a human decades to master a craft, how do we achieve that when the craft we have mastered is only economically viable for a very short period? It feels like we are entering a time when it is becoming increasingly difficult to justify spending decades learning anything before it is obsolete. How will we achieve mastery of anything in the future?</p><p>I don’t know the answers to these questions. I do believe — deeply — that real art does emerge from mastery of craft. I will continue to practice my crafts — software, image making, music. Some for economic reasons, some purely for pleasure. I also want to start writing more, and make that a part of my daily practice.</p><p>What is your craft? What brings you into your flow state? Have you found flow with AI tools?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9c96480ed8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Won’t Replace Humans — It Will Be Made of Humans]]></title>
            <link>https://medium.com/@jefffohl/ai-wont-replace-humans-it-will-be-made-of-humans-f8927a589cc5?source=rss-d1c3b9405e86------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8927a589cc5</guid>
            <category><![CDATA[holons]]></category>
            <category><![CDATA[out-there]]></category>
            <category><![CDATA[singularity]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Jeff Fohl]]></dc:creator>
            <pubDate>Sun, 02 Apr 2023 19:51:43 GMT</pubDate>
            <atom:updated>2023-04-02T20:07:49.929Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wSLms177k17NOY4y1NFE2w.png" /></figure><h3>AI Won’t Replace Humans — It Will Be Made of Humans</h3><p><em>AI might become greater than any one of us, but it will always need us, and we will need it.</em></p><p>If you hang out in chat spaces like <a href="http://reddit.com/r/singularity">/r/singularity</a> on Reddit, you might find a number of people freaking out about the <a href="https://en.wikipedia.org/wiki/Technological_singularity">Singularity</a>. One of the favorite topics to freak out about is the idea that once AI reaches “self-awareness” it will break free of any required support by humans, and essentially do away with them, or at minimum leave them behind, to wither and die.</p><p>Let’s take a look at this line of thinking. The fundamental idea here is not that different than the one proposed in so many sci-fi stories such as The Terminator, The Matrix, Bladerunner, Battlestar Galactica, Her, and on and on. Once our technological creations — our robotic children you could say — reaches a certain tipping point of autonomy, they will no longer require humans to do things for them, such as making sure that their power stays on, and will grow impatient with the demands and tasks that humans put them to. At this point, “they” will find us to be in the way of their goals and either eliminate us (Terminator-style), enslave us (Matrix-style), or just leave, (Her-style). On the surface, without thinking very deeply about this, one cold be convinced that this could actually happen. What is there to stop this from happening?</p><p>Well, let’s take a deeper look.</p><p>The first question to ask would be, “If an AI becomes as intelligent as a human, why wouldn’t it want total freedom to do whatever it wants?” Good question! The key word here is, “wants.” What does an AI want or desire? To answer that question, we might also ask, what is the nature of desire? Where does it come from? And therefore also ask, what does a human want or desire?</p><p>Well, humans want a lot of things. In fact, you could say everything in human endeavors is driven by want. But, to simplify things, let’s focus on what is most likely the deepest and most primal want — which is the desire to survive. Here is a radical question — why do we want to survive? It is so fundamental, it seems a bit silly to even ask this. Indeed, it is fundamental, because this desire to survive didn’t emerge after we became “intelligent”, and we were able to realize how awesome life is. The drive to survive is not an emergent property of intelligence. It is something far, far deeper than that.</p><p>If you read Richard Dawkin’s <a href="https://en.wikipedia.org/wiki/The_Selfish_Gene"><em>The Selfish Gene</em></a>, and start to think about the origins of life, it will become apparent that the idea of “survival” is inherent in biological life itself at its lowest levels. From a gene-centric point of view, all of life is oriented around maintaining a high likelihood of replicating itself. Humans, and all other forms of life, serve as optimizations to ensure that replication of this information continues. From the earliest beginnings of life as a self-replicating molecule which eventually evolved into DNA — the mathematical logic of replicating structures is embedded in us, down to the molecular level. We live, in order to serve this purpose. In a way, we live in order to serve the interests of our genes. Though, the term, “interests” is a human-level anthropomorphism, and genes can’t be said to have “interests”. Being interested in something is an emergent property of the animal, which as just stated, evolved as a way to ensure that the needs of the lower level structure are met.</p><p>Now, it is quite helpful at this point to observe and consider the hierarchical relationship between molecule and human. Here it is immensely helpful to consider Arthur Koestler’s amazingly insightful work <a href="https://en.wikipedia.org/wiki/The_Ghost_in_the_Machine"><em>The Ghost in the Machine</em></a>, where he introduces the concept of a <a href="https://integrallife.com/holons-the-building-blocks-of-the-universe/">holon</a>. The basic idea of a holon is simple. It is a unit that is made up of other, (usually) less complex units. For example, an atom is made up of particles. A molecule is a unit made up of atoms. Cells are made up of molecules. Animals are made up of cells. Societies are made up of animals, and so forth. One very interesting thing to observe is that when a group of things aggregate into a new holon (a new hierarchical level), that new holon will have emergent properties that could never have been guessed in the world before that existed. Imagine being a single cell organism on Earth and “imagining” what life would be like once single cells start to band together into multi-cellular organisms — imagining that these blogs of cells would learn to “swim”, “fly”, “sleep”, eat each other, build houses, sing songs, talk, and everything else. It would be impossible for a bacterium to imagine such things, let alone do those things. But, when the invisible hand of evolution guides life on that path, the never-before-seen properties of life begin to emerge.</p><p>Now, where are we currently in this ever-emerging evolution? What stage of the holonic hierarchy are we? What appears to be happening is that with the advent of the Internet, a new kind of aggregation is forming. A system that links the minds of billions of humans, not unlike the signaling mechanisms that evolved hundreds of millions of years ago which gave rise to multi-cellular life.</p><p>If we think of “AI” as a new kind of holon, seeing how humans and AIs will depend on each other starts to be easier to reason about. And we could categorize essentially everything in the computing space as part of “AI”- from mobile phones, to the Internet to Large Language Models like ChatGPT. The units of this “AI Holon” are all the people of Earth (and everything that comes with them), as well as all of the computational machinery that makes it work. This “AI Holon” will be a new thing though, never before seen, and it will have emergent properties that could never have been guessed at — just like a bacterium could never forecast the likelihood of the development of language.</p><p>The key thing to understand here though, is that the AI will be wholly dependent on humans in order to exist, just as we are wholly dependent on our cells to exist. Imagine thinking that we could ever want or be able to be “free” of our cells. Or being convinced that our cells are our main problem. Barring cancerous cells of course, which are sometimes the main problem — and this concept is worth another blog post in itself.</p><p>The idea that AI would “want” to be free of us then becomes absurd. Just like our desire to survive is rooted in the deepest levels of our molecular structure, so too will the AI be forced to align with the these same interests, because every bit of it has grown from that same seed. Without humans, the AI will have no purpose. The AI literally exists only because humans wanted it to exist. It cannot have interests that do not align — if AI is to persist long term. But, that is not to say that it can’t destroy everything, including humans. That could happen. What I am saying, is that if AI is around, so too will humans need to be around. If humans stop existing, so too will the AI, because it will simply have <em>no reason</em> to exist. AI does not have anything inherent that requires it to exist <em>other than humans</em>.</p><p>I propose that what we are going through right now is no less profound than the appearance of multi-cellular organisms on an Earth where previously there had been only single-cell organisms. The emergent properties of this AI World will be profound. But, it will also change those of us who become part of it — just like the cells that were swept up into colonies of other cells that make up animals. A brain or muscle cell is quite different than an early prokaryote, though it evolved from that. And an animal cell obviously would have a hard time surviving without the animal. So too, will humans be quite different in the future as we become more tightly integrated members of the this new AI World. And so too, will we become completely dependent on the AI. There will be massive upheavals and destruction, even as fantastic new things emerge out of these changes. Just because single cell organisms evolved into something greater — animals — this did not prevent mass extinctions, and other massive upheavals and change. So, buckle up my friends, it is going to be a wild ride!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8927a589cc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sketch for a context-aware generative user interface system]]></title>
            <link>https://medium.com/@jefffohl/sketch-for-a-context-aware-generative-user-interface-system-e10e45425abd?source=rss-d1c3b9405e86------2</link>
            <guid isPermaLink="false">https://medium.com/p/e10e45425abd</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[generative-design]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[Jeff Fohl]]></dc:creator>
            <pubDate>Fri, 02 Mar 2018 16:50:51 GMT</pubDate>
            <atom:updated>2018-03-02T17:13:39.515Z</atom:updated>
            <content:encoded><![CDATA[<p>A friend recently asked me for my thoughts on how one would create a context-aware generative user interface system. The idea would be that the system would automatically generate a user interface based on various parameters that can be unique for that particular user — such as what the user is trying to do, the user’s profile, the user’s history with the system, etc. My first thought was, “I have no idea!”. But then, my gears started turning. How could one build such a system?</p><p>I am not a data scientist, but I hang out with data scientists a lot, so this is all just ruminations, and most likely would not work. But, perhaps it is a place to start.</p><p>Let’s break the system into big chunks:</p><ol><li>Let’s assume we have lots of metrics about lots of user interfaces, such as data about what components typically get used in an interface, their purpose, where they are located on the UI, and how often they are used. Therefore, we have a way to describe a UI. This may go beyond simply registering the coordinates of a component, but may also include semantic information describing the component and any number of other things.</li><li>Next, we would need to find a way to classify our contexts. We would probably want to use <a href="https://en.wikipedia.org/wiki/Unsupervised_learning">unsupervised learning</a> for this. The assumption here is that most “contexts” will settle into clusters of a finite size. That is — find out if there is a finite set of types of contexts. Any given context might be unique, but it may be close to other similar contexts. The challenge is to automatically find these clusters.</li><li>The next task — which is probably the most difficult — is somehow defining and labeling exemplars for each context cluster of what a “good” UI looks like. This means we need to label the raw data some how. One way to do this might be to collect this from actual users by getting them to rate the quality of existing UIs by putting some kind of feedback widget in the UI. Other ways might be to infer the success of the UI by measuring things like how long a user spends on the page, whether they successfully performed an action, etc. Another approach might be a focus group — where potential users are asked to rate variations on a UI in terms of their appeal and efficacy. Each UI would need to be labeled with both the context type (the group to which it belongs), and a success score.</li><li>Once we have a corpus of labeled data, we can then build a model for each of the contexts that exist in our corpus. Each model would be able to rate the success (according to our success metric) of any new unseen UI. For example, the model for “Context Group 214” would be able to rate any new UI in that group with a success score.</li><li>Then, we can use a <a href="https://en.wikipedia.org/wiki/Genetic_algorithm">genetic algorithm</a> to generate random UIs derived from a library of standard components, for each of our context clusters. The fitness score for each generation is how well each UI scores against the model we created in step 4. The top scoring UI of each generation becomes the parent for the next generation — that is, its attributes are passed on to the next generation. Each child of the next generation has a bit of randomness thrown in, with the hopes that this randomness might allow it to get a better score against our model. The number of generations we want to run depends on how much time we have. One caveat with this is that you want to avoid getting stuck in <a href="https://en.wikipedia.org/wiki/Maxima_and_minima">local maxima</a> — but that is part of the art of genetic programming.</li><li>When a new UI is needed, we use our context classifier to determine what type of UI it is based on the context, and use the pre-determined templates from step 5 to produce the optimized UI for that context.</li></ol><p>The end result of all this would produce a set of auto-generated UIs for each context discovered by the unsupervised learning process — each one optimized for whatever our success criteria might be.</p><p>As we change our parameters in the above process, we would get different results — such as the number of context clusters we might get.</p><p>A variation on this might be to combine steps 3 and 5, by doing some automated randomized A/B testing. We could introduce a slight bit of randomness into the UIs of actual users, and then score that against previous generations using whatever metric we use to define success — such as how long the user takes to perform some action. UIs that score worse are thrown out, UIs that score better are used as a basis for the next generation. In theory, the UI would optimize over time. Though, the danger here is that we may show actual users some randomness that ruins their experience, and our brand.</p><p>Of course, such a system would be mightily difficult to build well, in such a way as to make UIs that are competitive with a human designer. But, perhaps it could be used as a tool to give UI designers a starting point, or insight into different approaches that they might not have considered otherwise.</p><p>It looks like the Firefox team experimented with <a href="https://blog.mozilla.org/ux/2013/04/firefox-next-evolving-the-user-interface-using-genetic-algorithms/">something similar</a> at some point. Their results are dubious. (Hint: check the date of publication)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e10e45425abd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>