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.
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.
Very rarely will you hear an attorney/lawyer so tongue and cheek refer to themselves as a such, more generally they will reference "I practice law". I know the term is used for Doctors as well, "practicing medicine". The idea is the medical and legal professions and their standards are constantly changing, but the professionals are constantly continuing their education of the profession as well as incorporating the latest advances/techniques. If a CS student described what they do as the "practice of coding" instead of describing themselves as a coder/hacker/developer I think it would be a clear and professional description.
However, I see your point unlike a "practicing" doctor or lawyer, whom you know is licensed from the very term, "there is virtually no concept of "licensing" for the fields of "developer" or "hacker" in the way lawyers and doctors have it". I do not know how practical this is, but perhaps there should be licensing for various programming languages like MS has certificates for MSCE, after all lawyers did not always have to go to law school to become members of state bars and in fact some of the best US Supreme Court Justices, and most well written, never went to law school - nevertheless bar requirements evolved to raise the standards of the profession.
http://en.wikipedia.org/wiki/Software_engineering_profession...
I'm not sure I agree with the OP on this: > So to all the girls learning how to code, and not sure where you stand: screw it, and just call yourself a developer already.
Replace "girls" with "people" for now (again, I'm not saying gender is irrelevant, I'm just focusing on a tangent for now)...I know there is virtually no concept of "licensing" for the fields of "developer" or "hacker" in the way lawyers and doctors have it (i.e. you can't call yourself a lawyer just because you're reading case law for fun)...and that's a good thing. But there's something in me that wants to say, "Well, you have to have built something, and watched it either succeed or fail". It doesn't have to be something big. It just has to be something you invested your time in and that you put out there because you thought the world might be interested...at that point, even with a small project, you know what it's like to "ship" and be invested.
To me, that's the difference between learning to code and calling yourself a developer.
If I were to try learning guitar, does that make me a musician? If I read the works of George Carlin and think of one-liners of my own during the day, does that make me a comedian? I would argue 'no'. But once you practice and refined yourself to the point that you book a gig, or even do an open mic, then the labels of "musician" and "comedian" seem more applicable.
---
OK, now for me to be really catty: Why does any modern blog (this is not the OP's fault, obviously), in this day and age, think it acceptable to use 13px as the body font for articles? Sorry, had to get that off my chest.