My problem? There s no documentation, no roadmap, no guide. And even if there was one, I prefer experimenting.
So after 30 years away from coding, I decided to document my own path. Not to become a software engineer, but to bring my ideas to life. Cool apps, fun tools, things I imagine without going back to school for four years.
Every launch comes with new learnings. The platform is changing over time, but many things don t depend on the platform itself they depend on how you approach the launch: your pricing, customisation, or how early you show up, and more.
What did you learn from your launch, and what will you adjust for next time?
I'm a video game studio director managing 175+ developers. I watch code being written every day, but I haven't personally shipped anything in three decades.
Until two months ago.
The catalyst: My friend and I had an idea for an emotion tracker. I knew a bit about CSS, so I tried teaching him. But I quickly realized he needed to learn by experimenting and the traditional path was killing his momentum.
Setting up VS Code, understanding file structures, git commands, push/pull, local host servers... it was too much overhead just to see if changing padding: 10px to padding: 20px made a difference.
Free visual CSS editor and inspector for web developers and students. Upload HTML/CSS files or load websites by URL. Edit CSS properties in real-time with box model visualization. Learn CSS by exploring real websites.
