I have a similar problem, and I’m terrible about deleting them. If they’re obvious garbage (blurry, total duplicate, bad lighting) I delete them right away, but I end up keeping the four extra versions of a good shot if they’re marginally different. The general cheapness of disk space these days has its drawbacks. I’d say the boundary is space more than anything else.
I organize things in a pretty simple fashion. My catalog is a series of collection sets—one for each year, one generic larger set for everything related to LA—with sub-collections for events or important groupings like our kids’ milestones:
When I import new photos, the first thing I do is drag stuff into appropriate collections. There might be crossover in the case of a photo of Oliver, for instance, where it will be in “Oliver, Year 2” and also “LA Apartment”. Once I drop everything into collections, I also flag photos I might want to edit and upload.
I have a few smart collections, the most important of which is the “flagged” collection. That’s where I do all my editing and posting from. If a photo is flagged, it either gets edited and posted or un-flagged if I decide I don’t want it to be public.
I could be much better about deleting photos I know I don’t need (like blurry shots, duplicates, alternates that didn’t work, etc), but I often don’t bother because hard drive space is cheap. If it’s an obviously bad shot, I try to kill it right after import. My entire Lightroom library is on Dropbox, so it’s backed up there. I also have a Backblaze backup as well as a physical backup here in the office.
Flickr (and 500px and Facebook) are my showcases, not my backups. I consider any of those temporary since Yahoo! could make the crazy decision to kill Flickr tomorrow (which would be horrible, but). I take backups very seriously because this data is the most precious thing in my digital life.
It might also be worth noting I have two Lightroom catalogs: This one, which is on my Mac Pro and contains nearly every shot from the past 6 years, and a separate mobile catalog which I use when I need to edit a photo from my MacBook Pro on the go (on vacation, from home, that sort of thing). Since I keep my collection on Dropbox and I don’t want the entire giant data set to be on my laptop, I selectively sync only the mobile catalog on my MBP.
I have children. Because I have children, it does not give you license to let your children run around me acting like assholes. You’ll notice I keep my children under control. You’ll notice they don’t walk up to your children and take their toys, they don’t walk up to people trying to enjoy a meal and start screaming in their faces. Because I have children, it does not mean I want to interact with your children without expressly choosing to do so. I certainly don’t want your unattended children randomly walking up to me and my attended child and acting like little assholes while you browse on your iPhone or chit-chat with your bonehead husband 40 feet away. When I chose to have children, I did not give up my basic rights to not be bothered by you and your children.
Further, because I have children, this does not give you any rights to infringe on my space or basic social rules with your children. Therefore, do not bring your toddler over to my infant and tell them it’s okay to touch him. Do not pick your child up and hold it over my infant. That’s not acceptable in any situation. You do not have special rights because you also procreated. These are my children and they deserve as much personal space as I do. You’re confusing our mutual parental status as a license to act like a fucking asshole.
I think it may actually be fine to learn Swift as your first programming language.
But you're going to need to also know how to at least read ObjC for the next several years at least.
Which means that for a while, all iOS/OSX programmers will have to know how to think in two modes: Dynamically typed message-passing OO, and statically typed vtable-style OO.
So maybe that makes it a harder platform to learn, but with smarter people mastering it? Dunno.
Maybe it makes us all better programmers.
First of all, I'm a brogrammer.
Let's get that straight, dude.
*chugs beer for 40 seconds straight, smashes can on face, picks up iPhone 5S and tests that new build super hard*
I opened a new Swift playground a while back and I've just been yelling LET'S DO THIS ever since.