Blog · 26 September 2026 · 9 min read

The Mother Seed: My 24-Month Blueprint to Become an Artist-Engineer

Code is getting cheap; taste and story are not. My 24-month blueprint to become a web designer who is equal parts artist and engineer.

Code got cheap. Taste didn't.

Every month, AI writes more of the code I used to type by hand. For a while that felt like a threat to my craft. Then I saw what it really means: when code gets cheap, everything a machine cannot supply gets expensive.

That means taste, a point of view, and the ability to turn a story into an experience that runs smoothly on a cheap phone. The websites people remember are built from exactly those three things. So are the studios that clients seek out by name.

I build websites for a living. Now I want to become the kind of designer-developer who is equally artist and engineer, someone who can take an idea from a blank page to a launched, award-level experience alone. So I wrote myself a plan.

I call it the Mother Seed, because everything that comes later (style, studio, reputation) grows from what gets planted first. It runs for 24 months in four phases, and each phase ends at a gate that opens only with public proof. I'm publishing it for two reasons: so you can hold me to it, and so you can steal it.

What "elite" actually means

Elite is not a job title or a follower count. In this plan it means three assets, and one test that proves them.

• Taste: judging what is good and being able to say why. It grows from volume: looking, copying, being critiqued.
• Authorship: a signature strong enough that people recognize your work before they see your name.
• Integration: story, design, motion, code, speed and accessibility fused into one experience, not stacked as separate layers.

The test is sovereignty: taking any project from blank page to launched, paid and published without depending on anyone. Self-respect follows from it. You price on value, hold your quality floor, and turn down work that would break it.

The seven laws

1. Taste before tools. Tools change every quarter. A trained eye compounds for life.
2. Hand before delegation. Do every core skill by hand until you can judge it, then hand it to AI. You cannot direct what you cannot evaluate.
3. Ship monthly. Every month ends with a finished, public piece. Unshipped work does not count.
4. Copy, combine, create. Rebuild the masters privately to learn. Publish only your own synthesis.
5. Constraints make signature. Limit the palette, type and technique of each project until your choices harden into a style.
6. Measure the craft. Every build reports load speed, accessibility and frame rate. Beauty that stutters is not elite.
7. Publish the process. The work gets you hired. The visible process gets you found.

Seven layers, one rule

The skills in this plan stack in seven layers. Each rests on the ones beneath it, and all seven train at once, at weights that shift over the two years.

0. Operator: how you learn. Focus, habits, a learning log, recovery. The layer that keeps you going for 24 months.
1. Eye: composition, typography, color, grids, image, drawing and design history.
2. Hand: HTML, CSS, JavaScript and TypeScript, with accessibility and performance built in.
3. Craft: research, interface design, design systems, frameworks, content management, testing and deployment.
4. Voice: motion, story, generative art, 3D, shaders and sound. This is where the work starts to feel like yours.
5. Multiplier: AI-assisted development, agents, AI features and automation.
6. Sovereign: positioning, brand, offers, sales, audience and studio operations.

One rule governs them: when two layers compete for the same hour, the lower layer wins until its gate is passed. Most developers invert this. They chase shaders before they can set a paragraph of type well.

So the first six months give about three-quarters of all hours to Eye and Hand. By the final phase, a third of the time goes to Sovereign work, while Voice keeps a quarter so the craft never goes cold.

The toolkit, ranked

• Master: CSS (the brush), JavaScript (the physics), HTML (the meaning).
• Fluent: TypeScript, GLSL shaders, the math of motion, the terminal, and copywriting in German and English.
• Working knowledge: Python for automation and SQL for data.

Around them sits a deliberately small stack: Vite, Astro, React with Next.js, GSAP, Lenis, Three.js, Figma, Blender and Rive. GSAP, including every former paid plugin, has been free for commercial use since April 2025 (GSAP). Everything outside this list is replaceable.

The map: four phases, four gates

Before Month 1 comes Week 0: seven placement tests that show which early modules I can compress. After that, every gate is a hard stop, and the next phase starts only when its proof is live and public.

Phase I · Foundation (months 1–6): the Eye and the Hand

No frameworks, and no AI-generated code. Each month ships one proof: ten typographic posters in pure HTML and CSS, a variable-font specimen, an accessible color engine, twelve hand-coded interaction toys. The gate is a one-page Manifesto site that must score 100 in Lighthouse and pass a WCAG 2.2 AA audit.

Phase II · Craft (months 7–12): interface, motion, story

Here the work turns professional. I research and redesign a real business site, build a design system of 20 accessible components, and give it a motion language grounded in the classic principles of animation.

Then comes story. Every narrative starts as a written script, becomes a storyboard and an animatic, and only then turns into code. The gate is a client-grade story site that is fast, accessible, editable by its owner and submitted for an award.

Phase III · Expression (months 13–18): worlds, shaders, signature

This is where the artist appears: generative art, real-time 3D under a 3 MB budget, a signature shader effect, a small explorable world with sound, and an AI feature with a real test suite. I learn WebGPU as the forward path, since it now ships in Chrome, Edge, Firefox and Safari (ICS Media), while WebGL stays the production fallback.

The phase ends by distilling every instinct into a Style Bible. Then comes a self-initiated flagship experience, built to the standard of the major award sites.

Phase IV · Sovereignty (months 19–24): studio and market

Skill becomes a business that respects itself: a clear position, productized offers priced on value, an audience engine, and a studio that runs on documented systems. Month 23 is the best client project of my life. Month 24 is the Final Trial: one brief, seven days, alone, from concept to launched site and case study.

The system behind the plan

Proof over feelings

Plans fail when progress is a feeling. Every gate in the Mother Seed is a fact anyone can check.

• Speed: Core Web Vitals in the good range for real visitors: LCP under 2.5 seconds, INP under 200 ms, CLS under 0.1.
• Motion: every animation holds 60 frames per second on a mid-range Android phone and has a reduced-motion version.
• Access: every build passes a WCAG 2.2 AA audit, including keyboard and screen-reader testing.
• Story: five people can retell the story of a site the day after they see it.

The 20-hour week

Alongside client work, I have about 20 focused hours a week. That is roughly 2,000 hours over two years, spent in a fixed rhythm.

• Weekdays, 2 hours: 20 minutes of drawing or type study, 75 minutes of deep building, 10 minutes on one master designer, 10 minutes of logging and sharing, 5 minutes of flash-card recall.
• Weekends, 10 hours: a 4-hour build, a 2-hour teardown of an award-winning site, 2 hours of study, 1 hour of publishing, 1 hour of weekly review.
• Every month: week one learn, week two drill, week three build, week four ship and take the gate.

With fewer hours, stretch the timeline. Never cut the modules.

How I use AI without letting it hollow me out

AI is in the plan from day one, but its role grows only as fast as my judgment.

1. Tutor (months 1–6): it explains, quizzes and reviews. It never writes the code for the skill I am learning.
2. Pair (months 7–12): I write the spec and the first draft. It suggests, and I accept changes line by line.
3. Team (months 13–24): agents such as Claude Code implement from my specs, while I architect, direct and review.

One rule never changes: I don't ship code I cannot explain. The AI skills that last are precise specs, rules files that encode my standards, and judging output fast.

The finish line

At month 24, the plan counts as complete only when every line below is provable with a link.

• Portfolio: three flagship case studies and a signature studio site, plus 24 monthly proofs and 60+ experiments.
• Recognition: an Awwwards Honorable Mention or equivalent as the floor, Site of the Day as the aim.
• Art: 500+ sketches and a written Style Bible for my type, color, motion and sound language.
• Speed of craft: a story site from concept to launch in five working days; any award-winning hero section rebuilt within 48 hours.
• AI: one AI feature in production, with its own test suite.
• Sovereignty: 100+ published process posts, an audience I own, and three income streams from craft: projects, retainers and a product.

Awards depend partly on jury taste and timing. They are a signal worth aiming at, never the only measure of the work.

What I refuse to learn

Elite is defined as much by what you refuse. Until month 24, these stay at awareness level at most.

• jQuery, Bootstrap and heavy page builders: the platform now does their job natively.
• Framework hopping: React, Next.js and Astro in depth beat six frameworks at the surface.
• Native mobile, Rust, Go and Kubernetes: a different career.
• Interview puzzles: I am building a studio, not preparing for interviews.
• Training my own AI models: API models are stronger and cheaper for this kind of work.
• Course collecting: an unfinished course is not a skill.

What this means if you work with me

Clients should not have to wait two years to benefit. The plan's standards apply to every project I take on, starting now.

• Story first: your narrative is written before anyone opens a design tool.
• Fast on real phones: measured with Core Web Vitals, not guessed.
• Accessible by default: tested against WCAG 2.2 AA. Since 28 June 2025, Germany's BFSG requires this of many online shops that sell to consumers (IHK Aachen).
• Motion that respects people: smooth and purposeful, and switched off for visitors whose devices ask for reduced motion.

Follow along

I will publish every monthly proof here, with the code and the thinking behind it. Month 1 is ten typographic posters built from nothing but HTML and CSS.

If you are on a similar path, take the blueprint and make it yours. If your brand has a story that deserves better than a template, let's talk.

Code got cheap. Let's make something that isn't.