More from Naz Hamid
Bridging the design-development gap as AI rises. There’s a frustrating gap in how development projects present themselves. What looks straightforward on GitHub — ‘just run this command!’ — quickly spirals into an odyssey of sudo permissions, package managers, and missing dependencies. As someone comfortable with design tools but less versed in development environments, I find myself mashing through terminal commands, hunting through Stack Overflow threads, and piecing together solutions without understanding the underlying context. What I’m missing isn’t the how, but the why. I get it: developers and engineers speak their language and rarely cater to non-developers. Robust beginner-friendly documentation isn’t what engineers want to be doing. Could these projects see greater adoption if they provided better context and more accessible instructions for newcomers or non-engineers? This includes guidance for people who’ve never worked with an API, or even know which directory they should be in to make package installs, let alone what packages are. The asymmetry between designer and developers is an interesting one. In my experience, designers build more of a bridge to developers because of wanting to communicate better with them. Designers start to code (sometimes as a forcing function) because they want to prototype and bring their designs to life quicker — no longer static and in turn opening their design and development possibilities. Developers might not return this in kind as they can build functional products without deep design knowledge or interfaces can be constructed using UI frameworks and libraries. Engineers are less pressured to become designers. They are paid more to specialize. Their bridge is to collaborate closely with design rather than to become a designer. Let’s talk about the new thing that is aiming to… supplant the above: AI. I can feed Claude or ChatGPT my entire codebase, give it files, have it sit inside my IDE, or even ask for code that does x, y, or z, and it’ll work with me to get these projects running. I’m comfortable with Claude, and it will give me cursory information on how and why. Of course, I don’t even know if the code is valid! And sometimes it’s not, but we work through it, and I come to a result that works. The knowledge transfer becomes even greater to non-existent. As I mentioned previously, vibecoding and generative codebases will likely increase as these LLMs serve solutions to ideas and concepts from the new generation of startups. Depth and understanding will be lost. When developers don’t understand the underlying principles of their code, debugging becomes a struggle; they can’t optimize for performance; and security flaws may abound. Technical debt will accrue in systems that become increasingly unknown and unpredictable. Broader innovation stutters because you’re stuck with what AI can give you. Homogeny ensues. For providers, the goal regarding LLM dependency, viewed from an investment perspective, is to mitigate or reduce cost and risk. In the end, entire software businesses are created around abstracting, simplifying, and making technology easier to use. What I lament is the focus on business opportunity, versus taking a more inclusive approach to bridging the gap between design and development or any other discipline with engineering. How do we get to better knowledge transfer? A tiered or tracked approach. One documentation track that exists for experts, and another that’s more verbose: context and explanation of the basics. Can open source projects and the like benefit from templates that encourage documenting the why along with the how? More collaboration is always good. I’ve benefitted hugely from working with engineering-centric product thinkers. I come at it from design with the knowledge of development, while my collaborators deal in code but find design a skillset to complement their coding skills. We meet in a middle ground that’s fruitful because we understand concepts. I am never shy about asking why something is done a certain way. And yes, AI. Can we use pattern recognition and matching to level up and progressively explain how and why things are built? There are many code-based helpers, but I’d love to look at how that a designer can utilize AI to pair program (something I do in trying to get to the why of it) — beyond working with an LLM. I’m imagining visual documentation or interactive tutorials that help guide you to various parts of a system. This knowledge gap has persisted for years, but AI is rapidly changing this landscape. While AI tools may bridge the divide between design and development by filling in missing context, I'm uncertain if this technological solution addresses the underlying communication problem — especially in an industry already stretched thin by time and resource constraints. This is an open dialogue for me at the moment, and I wanted to collect these thoughts at this time for later reflection. Visit this post on the web or Reply via email
Memories are an interesting beast. I have certain core memories that are embedded deep in my mind. The years I attended SXSW from 2007-2012 encompass some of those. In 2011, I shared a house with longtime partner-in-crime Scott Robbin, Jeff Skinner, and Sam Felder. We were off South Congress up at the top of the hill and tucked away close to Curra's Grill on Oltorf. We were in a neighborhood where all the streets were named after Robin Hood characters: Friar Tuck Lane, Little John Lane, Sherwood Lane, Long Bow Lane, and Nottingham Lane. Because we had this house, we ended up hosting two separate nights of hangs and invited a bunch of people we knew. I made a video of it using the Panasonic Lumix GF-1, the much-lauded camera that my friend Craig Mod made famous. The video isn't much — but watching it back now, some 14 years later, I'm so very glad I put it together. Many of these people are still friends to this day[1]. Perhaps, one of the most poignant memories I have is shown at the end of the video — when just us housemates went bowling during some downtime, and I put Spoon's “The Way We Get By” in the video because on the drive back from the bowling alley, that song came on the radio. I'd never heard it before, but Jeff, Sam, and Scott all sang along to it, belting out the lyrics, windows down, as we're cruising south on I-35. We lost Sam years later. Sam was a great guy, and he is missed by many. I'm very, very glad I made that video, and that I can look back on it. And remember everyone there, but especially recollect, see, and hear Sam in it. RIP Sam. SXSW brought many things, and in particular memories of some of the best people on the internet I got to know, and became friends with. Thank you, all. In order of appearance: Jeff Skinner, Scott Robbin, Dave Rupert, Nathan Peretic, Reagan Ray, Jay Fannelli, Luke Dorny, Trent Walton, Scott Boms, Sam Felder, Patrick DiMichele, Christopher Cashdollar, Kevin Hoffman, Jack Auses, Rob Weychert, Jonathan Bowden, Phil Coffman, Noah Stokes, Harold Emsheimer, Paul Armstrong, Wilson Miner, Andrew Huff. ↩︎ Visit this post on the web or Reply via email
The third culture difference. One of the hardest aspects of being a third culture kid and eventually adult is the difficulty in the journey of your identity. When you're young, the movement and culture- and context-switching are par for the course — it comes with the literal territory. As you get older, things happen: you transform into a chameleon and adaptation is one of your greatest assets. If you're me, you are seen as, sometimes advantageously, ethnically ambiguous. You somehow are part of the local fabric, depending on where you travel. And on the other hand, depending on where you reside over time, an assimilation or assimilations begin. It becomes part of your operating mode. As you get even older however, the mish-mash of identities and going with the flow start to untether any semblance of where you belong. Is it your birth country? Is it your citizenship? Is it the place you've lived the longest? Most are not like you. They may struggle with identity in completely valid and different ways. The third culture one is a big mash-up. I haven't completely met or known anyone quite like myself. Even a good friend who shared a similar path from college to the US, only overlaps with my experience to a point. My early years began elsewhere, which is a decisive difference. I have family, loved ones, and friends, but also my chosen or proximate family. They may not completely understand or ever understand, but I am thankful for their kinship, even if there's a part of me that will never feel completely whole. Visit this post on the web or Reply via email
A meditation on entering flow state. A snack beckons. I stand up and head a few feet away to the kitchen area. A hojicha latte is on my mind, and also a bite. My brain is at operational capacity, and I am in a flow state. The metabolic need feels high, and I need to keep my energy up. I make the latte, iced with almond milk. I devour an oat bar. It’s the time of year when projects are in full swing. The seasons also drive business. Today started with syncing on UK time, getting on a call with Simon and then Jeff joining. We reviewed work and made plans. I know what’s immediately ahead of me today, and I steel myself mentally. It’s funny how the pressure from a timeline and deadline can focus you. Because I am a shokunin, I have my design mise en place laid out both in the mind, and at the physical desk. The plan appears, as I percolated on it after the call. I am now executing it. Windows are open all over: a browser with a tab count I can't even see, a few design tools, two deck tools, communication tools, and note tools. I stop to consider that I'm working across multiple variants of the same core pieces of software but in different flavors and with different purposes or are inputs from others collaborating. The mise en place is multi-modal. I am traversing them, wielding a strange authority over them all. After all afternoon and as the evening beckons, I share the file, toggling on collaboration. A message goes out to all parties. Flow state will come for us all. This is just the beginning. Visit this post on the web or Reply via email
More in literature
A partner at the Houston law firm where my youngest son is working as an intern this summer has loaned him two nineteenth-century law books. Both were compiled by John G. Wells (1821-80) and were bestsellers in their day, long before the practice of law was fully professionalized: Every Man His Own Lawyer, and Business Form Book: A Complete Guide in All Matters of Law, and Business Negotiations, for Every State in the Union (H.H. Bancroft & Co. of San Francisco, 1867). Every Man His Own Lawyer; or, the Clerk and Magistrate’s Assistant. This is the “tenth edition, improved,” published by William Wilson of Poughkeepsie in 1844. Both are the size of mass-market paperbacks and bound in leather, which is scuffed and worn. Both are in delicate condition. The front cover of the former has detached from the spine and the pages in both are foxed but legible. Wells writes in his “Introductory” to the former: “This work, prepared some years ago, was received with great favor by the public, attaining a larger sale, it is believed, than any work of this kind ever published. Lapse of time has brought material changes in the statutes of many of the States; the war has not only altered the social conditions of some of them, but has introduced the Internal Revenue system, National Banks, modifications of the Tariff, [13th and 14th] amendments to the Constitution of the United States, emancipation of the slaves, and the General Bankrupt law.” The book is organized by occupation and social role, making it user-friendly. Chapters are devoted to farmers, mechanics, discharged soldiers and sailors (two years after the Civil War), immigrants, and married men and women. Wells includes templates for such documents as “Order of Commissioners to lay out a Highway” and “Deed by a Sheriff of an Equity of Redemption sold at Auction.” The emphasis is not on law in the abstract but on the minutiae of legal documentation. The books are eminently practical, as useful as dictionaries, and are aimed not just at lawyers but at average American citizens. They are early examples of a well-known category of books today: “Self-Help.” The autodidactic impulse among Americans was once very strong. People seemed to assume they could teach themselves almost anything – a trade or craft, science, engineering, medicine, the Western literary tradition. “Experts” were not automatically deferred to. One could, like Abraham Lincoln, attach himself as an apprentice to an experienced professional. Few Americans attended a college or university or even completed their secondary education. Lincoln practiced law for twenty-three years before he was elected president. He may have consulted Wells’ guides. He never attended law school – not unusual for the mid-nineteenth century -- and was entirely self-taught. He handled cases ranging from debt to murder at the justice of the peace, county, circuit, appellate and federal levels, and kept an office in Springfield, Ill. Consider that even in his own day, Lincoln was judged by some a hick, born in 1809 on the frontier in Hodgenville, Kentucky. Now we know he was educated and well-read by the standards of his day, and through strict application became one of the great American writers of prose. In 2007, Robert Bray published “What Abraham Lincoln Read—An Evaluative and Annotated List” in the Journal of the Abraham Lincoln Association. Bray’s research determined which books were read by Lincoln. Among others he confirmed were John Bunyan, Robert Burns, Lord Byron, William Cowper, Daniel Defoe, Euclid, Edward Gibbon, Thomas Gray, Edgar Allan Poe, Alexander Pope and much of Shakespeare. In 2010, Bray published Reading with Lincoln (Southern Illinois University Press), in which he writes: “From boyhood on, Lincoln’s habit of reading concentrated a naturally powerful mind; and reading provided models of voice and diction to one who had inborn talent as a storyteller and a near-flawless memory and therefore needed only the stimulus of literary greatness, and emulative practice, to emerge as a great writer himself.” Bray emphasizes that Lincoln as an adult read “deeply rather than broadly.” In his own words, he went to school “by littles” and his reading was full of holes, but he read deliberately and what he read he remembered. He read like a writer – learning, testing, gleaning, absorbing, assimilating. Serious writers, when they read, are always weighing and assessing: “This works. This I can use. Forget that.” Lincoln’s mind was deeply analytical, coupled with a gift for pithily articulating his thoughts – essential gifts for a successful lawyer and an embodiment of the democratic ideal. In his “Introductory,” Wells describes his guide as “a book that everybody can understand, and that will enable every man or woman to be his or her own lawyer.”
It must be encoded there, in the childhood memories of our synapses and our cells — how we came out of the ocean 35 trillion yesterdays ago, small and slippery, gills trembling with the shock of air, fins budding feet, limbs growing sinewy and furred, then unfurred, spine unfurling beneath the bone cave housing three pounds of pink flesh laced with one hundred trillion synapses that still sing with pleasure and awe when touched by the wildness of the world. Even as the merchants of silicon and code try to render us disembodied intellects caged behind screens, something in our… read article
I’ve learned with time that my mind has periods of attentiveness followed by drifts into passive, relaxed states of consciousness. I’m awake but almost empty. I might be taking a shower or staring out the window at nothing. That’s when I occasionally find myself in an old song or childhood memory or, more mysteriously, inhabiting a character from fiction, taking on his values. When I become conscious of this channeling, it disappears leaving a faint, lingering impression, like the afterimages left by bright lights. Recently I found myself in Austin King, the Illinois lawyer, father and put-upon husband at the center of William Maxwell’s 1948 novel, Time Will Darken It. It’s the opening scene. King is in his bedroom getting dressed for a party for relatives visiting from Mississippi. His wife, pregnant with their second child, is not speaking to him. She resents the party and the presence of outsiders. I wasn’t recalling the words but the setting, emotional and physical, which I had abstracted from the text. I’ve read Maxwell’s novel three or four times, starting in the late seventies. I know it well. Unintentionally, I had projected myself into King because his emotional state was familiar – conflicted, guilty, wanting to satisfy contradictory wishes and please everyone. I didn’t have to go looking for it. I carry it as a latent memory. There’s a semi-popular theory floating around out there that we read fiction to boost our empathy quotient. In short, we read to learn to be better human beings, to feel the pain of others. That’s silly but also kind of obnoxious. How self-centered. Willa Cather would have snorted. My flashing onto the bedroom of Austin and Martha King lasted seconds. I enjoyed the sensation but made no effort to hang on to it. It was a fairly primitive mental event, not freighted with philosophical baggage. A handful of other fiction writers have done this for me, all in my private pantheon – Chekhov, James, Proust, among others. Part of the reason I value them is that they leave these phantom scenes in my subconscious mind, through no effort of my own. Time Will Darken It, along with So Long, See You Tomorrow (1980), is Maxwell’s finest novel. In 1955, Maxwell delivered a speech at Smith College, “The Writer as Illusionist” (collected in the 2024 volume of the same title, published by Godine). He likens a novelist to a dog who dreams of chasing a rabbit. He writes: “The novelist’s rabbit is the truth—about life, about human character, about himself and therefore by extensionh, it is to be hoped, about other people. He is convinced that this is all knowable, can be described, can be recorded, by a person sufficiently dedicated to describing and recording, can be caught is a net of narration. . . . . But what, seriously, was accomplished by these writers [Maxwell has just mentioned Turgenev, Lawrence, Woolf and Forster] or can the abstract dummy novelist I have been describing hope to accomplish? Not life, of course; not the real thing; not children and roses; but only a facsimile that is called literature.” The finest writers of fiction, those we treasure most highly, work simultaneously in two mediums – words and human beings. William Maxwell died twenty-five years ago today, on July 31, 2ooo, at age ninety-one.
And create an interspecies future that benefits humans and ecologies alike.