For a long time, I thought I was “just a designer.” I went to graduate school for graphic design because I wanted to improve my visual skills—typography, layout, systems, and aesthetics. Looking back, however, the most valuable thing I learned was not a visual technique but a way of thinking. My professors constantly challenged us with questions about context, audience, intention, and meaning. Over time, I realized that design was not primarily about making things look good; it was about understanding the relationship between content and form. Form was not decoration. It was the result of deeper structural decisions. That mindset stayed with me after I entered the workforce, but professional environments often organize people differently. Companies divide work into roles: designers design, engineers code, writers write, marketers market. This division is practical and necessary, yet it can also become limiting. A role that begins as a coordination tool can gradually become an identity. I often found myself being treated mainly as someone responsible for visual execution, even though the questions occupying my mind were rarely limited to appearance. I was more interested in what something meant, why it existed, who it served, and what structure connected those elements together. For years, I lacked the language to describe this tendency. I only knew that I instinctively searched for structure before producing form. That changed when I began working with large language models. I noticed that generic prompts produced generic results, but when I shared my actual thinking process—even when it was messy, incomplete, or poorly articulated—the responses became significantly more useful. It felt as though the model understood me, but I do not believe it was reading my mind. Rather, it had learned enough of my underlying framework to interpret my unfinished thoughts through that framework. This experience changed how I understood AI. Instead of seeing it merely as a productivity tool, I began to see it as a structure-revealing interface. I could present a vague idea, receive a response, refine it, challenge it, and continue the cycle. The process did not magically make me an expert in unfamiliar subjects, but it dramatically lowered the barriers to exploring them. Whether I was thinking about philosophy, writing, systems, product strategy, technical concepts, or practical problems, AI helped translate unfamiliar information into structures I could understand and work with. The most significant shift occurred when I attempted to externalize my own thinking framework through a small AI-assisted software experiment. I do not come from a software engineering background, and I am not a traditional programmer. Yet AI allowed me to focus on defining intent, structure, direction, and judgment while it assisted with code generation, debugging, and execution. The result was far from polished, but that was not the point. What mattered was that an idea moved from imagination into reality. Something that previously existed only in thought became testable. That experience also changed how I think about engineering. I once viewed engineering as a discipline defined primarily by rules, specifications, and precise execution. Now I see it as an interface between thought and reality. No implementation can perfectly preserve an idea, and every translation into the physical or digital world involves compromise. Yet engineering provides a way for abstract structures to become visible, executable, and scalable. In that sense, it shares more with design than I once realized. Both disciplines are concerned with transforming intention into form. As a result, I have begun to rethink how I define myself. I am still a designer, and design remains my foundation. But perhaps the most important thing design taught me was not visual execution; it was structural thinking—the ability to connect context, content, audience, intention, and form. AI did not give me a new identity, nor do I believe it eliminates the need for expertise, responsibility, or judgment. What it did provide was the ability to test ideas that previously remained inaccessible. More importantly, it made me question how much of our identity is shaped by external labels such as degrees, job titles, departments, and expectations. Those labels are useful, but they are often low-resolution descriptions of human capability. AI did not make me someone else. It helped me recognize that I was never only the person described by the label I had accepted. submitted by /u/Weary_Reply
Originally posted by u/Weary_Reply on r/ArtificialInteligence