<?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 Daniel Lauding on Medium]]></title>
        <description><![CDATA[Stories by Daniel Lauding on Medium]]></description>
        <link>https://medium.com/@daniellauding?source=rss-ce2d6b59b861------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Dk8pMR3c_iD-VIlXy4oSMA.png</url>
            <title>Stories by Daniel Lauding on Medium</title>
            <link>https://medium.com/@daniellauding?source=rss-ce2d6b59b861------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:03:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daniellauding/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[Still building — just with different tools]]></title>
            <link>https://medium.com/@daniellauding/still-building-just-with-different-tools-615a076e82f9?source=rss-ce2d6b59b861------2</link>
            <guid isPermaLink="false">https://medium.com/p/615a076e82f9</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Daniel Lauding]]></dc:creator>
            <pubDate>Fri, 27 Mar 2026 13:54:19 GMT</pubDate>
            <atom:updated>2026-03-27T14:07:12.375Z</atom:updated>
            <content:encoded><![CDATA[<p>A reflection after completing a JavaScript program — and what it means for how I build going forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fIiUjOzBFv14wQ0UIks9uA.png" /></figure><p>If I look at where I am right now, it doesn’t feel like a new chapter.</p><p>It feels like a continuation.</p><p>Just with a slightly different set of tools.</p><p>I’ve written before about how things started – LEGO on the floor, early websites, experimenting without really knowing what I was doing. Taking things apart, putting them back together, trying again.</p><p>That <a href="http://www.instinctly.se/">instinct</a> hasn’t really changed.</p><p>But the context has.</p><h3>Coming back to code</h3><p>Recently, I went through a JavaScript program at <a href="https://www.technigo.io/">Technigo</a>.</p><p>Not because I wanted to switch careers.</p><p>Not because I had to.</p><p>But because something felt… incomplete.</p><p>Over the years, I’ve been working deeply in product design — UX, UI, systems, flows and strategy. Building things that make sense for users, teams, and businesses.</p><p>At the same time, the tools around us have changed.</p><p>AI is everywhere now.</p><p>And suddenly, the distance between an idea and something real has become much shorter.</p><p>You can go from a thought → to a flow → to a prototype → to actual working code faster than ever.</p><p>And I realised that I didn’t just want to design those ideas.</p><p>I wanted to build them. <em>Not just to see if they worked — but to understand why they worked.</em></p><h3>Putting myself back in a beginner mindset</h3><p>Going back to coding after years in design is… interesting.</p><p>You’re used to knowing what you’re doing.</p><p>Then suddenly you don’t.</p><p>Things break.</p><p>Nothing compiles.</p><p>You Google things you feel like you “should” know.</p><p>And that’s exactly the point.</p><p>Because growth mindset isn’t really about motivation or positivity.</p><p>It’s about putting yourself in situations where you don’t have full control — and staying there long enough to learn something new.</p><h4>During the course, that meant:</h4><ul><li>writing code again instead of just sketching ideas</li><li>debugging instead of polishing UI</li><li>finishing things even when they weren’t perfect</li><li>asking questions instead of assuming answers</li></ul><blockquote><em>One of the projects I built during this time was </em><a href="https://www.pejla.io/"><em>Pejla</em></a><em> — a simple way to compare ideas, get feedback, and explore different directions through voting and remixes.</em></blockquote><p>Read my interview <a href="https://www.technigo.io/stories/daniel-on-web-development-and-pejla">here</a></p><p>It started as an idea, but quickly became something I could test, iterate on, and actually use — which is where things start to get interesting.</p><p>In projects like Pejla, AI became part of that loop — helping me explore variations, structure ideas, and move faster from concept to something real.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-LwPbUFq6dfG9fB1D2wVA.png" /></figure><p>And honestly, it felt familiar.</p><p>Like going back to how it all started.</p><h3>The space between design and development</h3><p>One thing became very clear during this process.</p><p>The line between design and development is fading.</p><p>You design something in Figma.</p><p>You test flows.</p><p>You generate variations with AI.</p><p>You jump into code.</p><p>You deploy.</p><p>You iterate.</p><p>It’s all part of the same loop now.</p><p>And somewhere in that loop, there’s a role that isn’t fully defined yet.</p><p>Not just designer.</p><p>Not just developer.</p><p>But someone who understands both — and can move between them.</p><p>Understanding how things are built.</p><p>How data flows.</p><p>How decisions affect implementation.</p><p>How to go from idea to something people can actually use.</p><p>That’s the space I want to keep exploring.</p><h3>Working with AI, not around it</h3><p>AI has been part of my workflow for a while now.</p><p>Not as a shortcut — but as a way to explore more ideas, faster.</p><p>To test things.</p><p>To remove friction.</p><p>To push concepts further.</p><p>But working with AI also makes your gaps more visible.</p><p>You can generate things quickly — but if you don’t understand what’s happening underneath, you’re limited.</p><p>That’s another reason I wanted to get closer to code again.</p><p>To not just rely on tools — but to actually understand how to use them properly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YeWqeTBIVMCDiAj1gCdW4g.png" /></figure><h3>Applying this going forward</h3><p>Finishing the course isn’t really the milestone.</p><p>Applying it is.</p><h4>For me, that means:</h4><ul><li>building more real prototypes instead of static concepts</li><li>moving faster between design and implementation</li><li>exploring ideas directly in code when it makes sense</li><li>understanding technical constraints earlier in the process</li><li>continuing to experiment with AI in practical ways</li></ul><p>And maybe most importantly:</p><p>not overthinking <strong>where something “belongs”.</strong></p><ul><li>Design or development.</li><li>Strategy or execution.</li></ul><p>It’s all part of the same thing.</p><h3>Still the same foundation</h3><p>Even if the tools keep changing, the foundation hasn’t.</p><p>Stay curious.</p><p>Try things.</p><p>Break things.</p><p>Fix them.</p><p>Build again.</p><p>That’s been the pattern from the beginning.</p><p>And going through this course didn’t change that — it just reminded me of it.</p><p>So this isn’t really about becoming something new.</p><p>It’s about expanding what’s already there.</p><blockquote><em>Still building.</em></blockquote><blockquote><em>Just with different tools — and a slightly different perspective.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KBPTUV4JrS0ZH9y3S_ICqA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=615a076e82f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My path wasn’t linear – but it makes sense now]]></title>
            <link>https://medium.com/@daniellauding/my-path-wasnt-linear-but-it-makes-sense-now-408dc1aeb47e?source=rss-ce2d6b59b861------2</link>
            <guid isPermaLink="false">https://medium.com/p/408dc1aeb47e</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Daniel Lauding]]></dc:creator>
            <pubDate>Sat, 29 Nov 2025 11:53:39 GMT</pubDate>
            <atom:updated>2025-12-01T09:33:28.354Z</atom:updated>
            <content:encoded><![CDATA[<p>If I look at my journey so far, none of it feels linear — but all of it makes sense when I connect the dots backwards.</p><p>It started long before design tools, AI workflows or job titles.</p><p>More like LEGO on the floor, an Amiga 500 humming in the living room, and stacks of floppy/CD disks from my dad that I opened just because I was curious.</p><h3>Growing up, that curiosity kept evolving.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*2MR7hLluI4jMmmMvmJ-lKQ.jpeg" /></figure><p>LANs in Hökåsen with my brother and his friends.</p><p>Custom Red Alert maps, custom HUDS/Sprites in FPS games.</p><p>DivX/Xvid and MP3s.</p><p>Improvised networks that broke constantly — and somehow got fixed again.</p><p>Nothing about it looked like a future career.</p><p>But it taught me how to experiment, explore, and build without overthinking.</p><p>My first real step onto the web was at <a href="https://www.loopia.se/"><strong>Loopia</strong></a>, helping people with hosting and domains — the first time I realised that the random things I had done for fun were actual jobs.</p><p>Then came my first front-end role at <a href="https://web.archive.org/web/20091124222733/http://www.drumedar.se/"><strong>drumedar</strong></a><strong> </strong>in Västerås 2008.</p><h3>The IE6 era.</h3><p>Floats, clears, PNG hacks, pixel-perfect matching of Photoshop files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/0*304ewcQswoHKsJ0d.png" /><figcaption>Screenshot of a previous big CSS only project i was working on (date released 2008)</figcaption></figure><p>You learned by building, breaking, rebuilding — and if you wanted to be seen, you made a website.</p><p>Then you redesigned it.<br>Then you rebuilt it again.</p><p>Submitting to CSS galleries, validating HTML (WCAG), tweaking tiny details no one else noticed.</p><p>Not for likes — just to express something.</p><p>And then the <strong>financial crisis</strong> hit.</p><p>Everything froze.</p><p>I ended up sending fifty job applications across Sweden and Norway, logging every follow-up and every silence.</p><p>Strangely enough, that period taught me resilience more than anything else I’ve studied.</p><p>It eventually led me to <a href="https://www.futurniture.se/"><strong>Futurniture</strong></a> in Stockholm 2009 — where the industry opened up properly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/0*jTVMyWAtiuHBCxrP" /><figcaption>Wordpress campaign sites for ikea back in 2009</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/0*qaXrMQ1LX3NuwT8E" /><figcaption>Wordpress campaign sites for ikea back in 2009</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uLl6z7F0GLwmobtk.png" /><figcaption>Freelance front end developer at a casino portal</figcaption></figure><p>Inspiring colleagues.</p><p>Real clients.</p><p>Developer and design meetups, afterworks, and freelancing around the city.</p><p>Those years shaped how I work in teams, how I design, and how I build things.</p><p>But the biggest shift came right after: <a href="http://www.hyperisland.se/"><strong>Hyper Island</strong></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*ipVMZuSW0q85mAP9Ew2bow.jpeg" /></figure><p>My first international flight.</p><p>My first intentional leap.</p><h3>Where “learning by doing” wasn’t a slogan — it was culture.</h3><p>It rewired how I think about collaboration, creativity, feedback and speed.</p><p>Since then, I’ve worked with startups, agencies and product teams across different cities and time zones. I’ve built tools, systems, and experiences that actually help people. And in the last few years, AI has reshaped my process — not as a shortcut, but as a multiplier for craft.</p><p>And now I’m here again — taking stock, looking forward, and exploring what’s next.</p><p>The market is tougher now.</p><p>More competition.</p><p>More noise.</p><p>But I’m also not the person who once sent fifty job applications hoping for a lucky break.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*fHeL6OYag26_yqXVZ8ezqQ.jpeg" /><figcaption>Trend spottin’</figcaption></figure><p>Back then I was trying to prove I could do the work.</p><p>And now I’m in a familiar but different place — not looking back for nostalgia, but for direction.</p><p>The market is louder than ever, competition is sharper, and the expectations on designers have shifted completely. But that shift doesn’t intimidate me. It actually feels aligned with how I’ve always worked: hybrid, curious, hands-on, mixing design, code and systems thinking.</p><p>What I’ve learned across all these years — from early web hacks to global teams to AI-driven workflows — is that the tools will keep changing, but the foundation stays the same:</p><p><strong>Stay curious.</strong></p><p><strong>Keep learning.</strong></p><p><strong>Build things that matter.</strong></p><p><strong>Make ideas real.</strong></p><p>And that’s the mindset I’m carrying with me into the next chapter — whatever shape it takes.</p><p>Not chasing titles, not chasing trends, but following the same instinct that’s been there since the beginning: explore, understand, create, and push things one step further.</p><p>Still curious.</p><p>Still building.</p><p>And excited for whatever comes next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=408dc1aeb47e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From LEGO Bricks to Digital Products: My Journey as a Builder]]></title>
            <link>https://medium.com/@daniellauding/from-lego-bricks-to-digital-products-my-journey-as-a-builder-51a07ac6624e?source=rss-ce2d6b59b861------2</link>
            <guid isPermaLink="false">https://medium.com/p/51a07ac6624e</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Daniel Lauding]]></dc:creator>
            <pubDate>Sun, 16 Nov 2025 16:35:46 GMT</pubDate>
            <atom:updated>2025-11-16T16:39:18.723Z</atom:updated>
            <content:encoded><![CDATA[<p>When I think about where everything started, it wasn’t with a school or a job title.</p><h3>It started with LEGO.</h3><p>As a kid, I could sit for hours building things, taking them apart, and trying again. I didn’t think about “logic” or “systems.” I just liked creating something from small pieces and watching it take shape.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*vQIwBzZ_3qBcHkyVR4RhIw.jpeg" /></figure><p>When I got my first PC, my LEGO worlds simply moved online.</p><p>I started making small websites and graphics I learned from random tutorials. I spent hours experimenting, breaking things, rebuilding them, and constantly updating my own little corner of the internet with whatever new idea I had.</p><p>At the same time, I was deep into Counter-Strike — playing in clans, hanging out on mIRC, and trying to climb in the Swedish scene. And that world pushed my creativity even more. I made websites for my teams, redesigned them over and over, created logos, and tried to keep up with what the “cooler” clans were doing. Seeing someone else’s site always made me want to build the next version, the next idea, the next upgrade.</p><p>Sometimes I also played around with CS maps, HUDs, and sprites — anything I could tweak or customize, I would.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/0*ZCpJlEpe4JJ2dmzd.jpg" /></figure><p>It was all the same feeling:</p><p>take something apart, learn how it works, make your own version, and push it one step further.</p><p>In 2007, I got a job helping people with their domains and hosting at <a href="https://loopia.se/">Loopia</a> in Västerås. That was the first time I realized that the things I had been doing for fun — websites, experimenting, fixing things — were the same things people actually worked with. That gave me the push to try it more seriously.</p><p>Not long after, I got my first front-end job. This was the IE6 era — endless layout bugs, browser hacks, and trying to make Photoshop designs match perfectly in every browser. In the teams I worked with back then, frontend was mostly HTML and CSS, so I focused on building, fixing, and learning by doing.</p><p>Then <a href="https://hyperisland.com/en/">Hyper Island</a> came into my life and changed everything.</p><p>“Learning by doing” wasn’t a slogan — it was a way of working.</p><p>Make things fast.</p><p>Work in teams.</p><p>Solve problems.</p><p>Try things even when you’re not sure how.</p><p>It shaped how I think about design, people, and building products.</p><p>From there, I worked with startups, agencies, and remote teams all over the world. I’ve spent years designing tools, systems, and digital experiences that help people in their everyday lives. What I enjoy most isn’t the industry or the size of the project — it’s the process of making something real.</p><p>Travel and remote work also became part of my life. Different countries, different people, different ways of solving problems — all of it shaped how I build things today.</p><p>In the last few years, AI became a big part of my work. Not as a shortcut, but as a tool that helps me explore ideas faster, test more things, and remove friction in design and prototyping. With <a href="https://vromm.se/">Vromm</a> — the driving-license helper app I’m building — AI has been part of everything from research to design to early concepts and final coded app.</p><p>But working with AI also made me want to sharpen some old skills again — especially JavaScript.</p><p>Not to change careers, but to build smarter prototypes, understand more, and close the gap between design and development.</p><p>Going through <a href="https://www.technigo.io/">Technigo’s</a> JavaScript bootcamp brought back that early spark — the same energy I had when I first started making websites and experimenting with ideas online.</p><p>After everything — LEGO, early web experiments, Counter-Strike clans on mIRC, IE6, Hyper Island, remote work, building products, and now AI — I’m still the same person:</p><p>I like making things.</p><p>I like solving problems.</p><p>And I like seeing ideas go live and help people.</p><p>With everything I’ve learned — and everything I’m still learning — I’m excited to see where AI takes our industry. It moves fast, and that keeps me curious, motivated, and involved. That’s the design engineer in me — always exploring tools, mixing design and code, and building whatever comes next.</p><p>And if someone out there needs a hand — with design, frontend, or figuring out how to use AI in a simple, practical way — I’m always happy to share what I know. I’m open for freelance and contract work too.</p><p>I’m surrounded by digital building blocks these days: components, systems, AI prompts.</p><p>But maybe it wouldn’t hurt to pick up some actual LEGO again — just to unplug from the <strong><em>generated blocks</em></strong> every now and then.</p><p>Visit my <a href="http://www.daniellauding.se/">digital space</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51a07ac6624e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>