An experience like that really affects one's coding habits and makes them structure things in a more future-proof way: things like having loggable errors, even basic usability sense cannot realistically come from anywhere but hearing real user reports, going through the most basic deployment process, finding an issue on a live system.
In addition, certain naive over-engineering impulses get tempered by real shipping experience - because YAGNI is honed as well.
It's been described that anyone creative/constructive plays both a "writer/implementer" role and an "editor" role (using a book analogy here). Writing code is what we learn in school - but editing and directing and culling that output is something that takes real exposure to user problems to get better at.
One other metric is letters per line...guidelines recommend roughly 70 to 80 characters, because as lines get wider, it's harder to track which line you were on when your eyes go from the end to the beginning of the next line. It looks like your site is at around 100 characters despite it not having an extremely wide article body size.
Anyway, just my rant...this post on typography I've found to be useful: http://www.vanseodesign.com/web-design/typographic-choices/
As for what kind of project makes a developer, well, that's definitely open for discussion. I have no idea, but was just looking for a litmus test beyond just learning or being interested in code.
As for the developer argument, the problem is that there is no hard line. How big of a project must one complete before they're a developer? You said even a small one, but Hello World is a small "project" and certainly isn't enough.
I completely agree that there is a difference between learning to code and calling yourself a developer. One problem here is that the industry uses developer, coder, and programmer interchangeably, although programmer seems to be currently falling out of favor. (I was once at a party where someone thought that I meant I was a "party programmer" or something.) Obviously they don't mean the same thing, but it's kind of like arguing over the difference between a geek and a nerd at this point.