Do people actually get value out of conferences? Those always seem more like cash grabs and marketing events than actual training value-adds.
In terms of skill development? Yes, although it's value you could get for free if you read the right blogs, keep involved in the community, and are a self-motivated person.
In terms of networking? Yes, although perhaps you could get that for free too, if you go to enough hackerspaces and meetups etc.
Ironically, a lot of the people I meet at conferences are the kind of driven, motivated, outgoing people who are well suited to getting those benefits for free. But not all of them!
I certainly derive value from going to conferences.
Other than that, books and screencasts seem to be a good way to spend that training budget as well. But there's a ton of videos online available for free too.
Of course, they all require time. Which is money. :)
I suspect there's plenty of value in the well-known conferences.
1. This differs more from workplace to workplace than industry to industry. Many dev workplaces will give developers a week or two of official "training time." Many other industries have workplaces that don't do that.
2. The reality is, training on new technologies has more value to you than it does to your employer. If your employer uses J2EE, Subversion, and Oracle, there's little benefit to them sending you off to learn Node, git, and Mongo. But there's a big benefit to you in knowing that, potentially. If the benefits of learning flow more to you than to your employer, you shouldn't be surprised if the burden of learning falls onto you.
3. But mostly, if you're a person who finds software development genuinely interesting (the hobbyist-type), you'll keep up on stuff basically recreationally. When you read about the latest whatever, you'll be curious and want to try it out and learn how it works because you're interested in that. You don't need any formal training to learn new technologies, just a little motivation and time. An hour spent not watching TV can get you a long way in understanding a new technology.
At least I found myself falling into that the last time I was between jobs -- constantly watching beginner videos on new thing X, Y, Z instead of actually doing something useful in one of them.
Back in employed world of course it can be the opposite -- you become a master of whatever tech your company is using but get little exposure outside that. It is however often possible to guide the company into a new technology and get the best of both worlds.
Training should be seen as a part of compensation. While there's some alignment with the employers needs, giving employees a training budget shoulder be seen as a cheap way to provide more compensation and they should be able to use it to hone their skills in whatever area they want, regardless of its utility to employers.
Working 40 hrs without training or proper mentoring leads to skill stagnation. A $500 training budget will get you nowhere and you'll find yourself using long weekends (like I'm doing right now) learning new skills. Maybe that's expected in the industry and I've made my peace with it but in other industries you get sent to training courses even if they take away few days or even weeks of "productive" time.