> Some also have dealt with logic or projects at a much younger age or in college (like college is supposed to do)
As said, the experience learned under the pressure of a workplace is quite different from the experience learned at a lazy school- or hobby-project. School and hobby only teaches the basics and is more acceptable to failures. But companys are seeking the masters, for which experience is neccessary. Of course there are always exceptions, but those exceptions usually can present some kind of experience, so they kind of automatically fall out of the scope of the question. Someone working x years activly on a bigger project should put it into his vita, so that he can sell this experience.
Absolutely: if a place is looking for 10 years of experience in software development, and you have 6-7 but apply, you have a chance of being considered. If you never apply, you have no chance of being considered.
In some ways it's like the truism that lottery vendors bandy about, "you can't win if you don't play".
That's the undefined - and, most often, unencompassable - aspect of informal experience.
Personal example: I was doing pretty intense C++ programming starting when I was about 13 as first an apprentice, and then a "real" developer on a finite element analysis program. I wrote the 1-D, 2-D, and 3-D mesh generators. I learned a couple DOS graphics packages for visualizing the mesh, the analysis, and the results.
None of that was especially documentable: it took going through school and blowing most of my programming courses out of the water to get the formal experience.
And, because I was doing this as a hobby/side-project with a friend, I was also missing a lot of what most people would think are core aspects of programming (didn't learn recursion, for example, until my second year in college - a solid 5+ years after it would have made our project far more manageable and expandable).