941 karma · joined February 7, 2008
[ my public key: https://keybase.io/bencollins; my proof: https://keybase.io/bencollins/sigs/hGAUM3Q3RKADa9EOm1RLFk7arseXNo5EiDH6U1f9qzE ]
I think that's a pretty narrow view. There are other possible alternatives, like: new businesses opening; completely new industry forming that doesn't require high skill levels from its workers. Given an individual situation, I don't think it would be too difficult to imagine additional scenarios.
I'm not trying to trivialize the difficulty the long-term unemployed are facing, but I don't think it's constructive to throw up your hands and despair, either.
Thanks for that.
Looking to build a new one soon, without making all the mistakes I made building this one :-)
Having said that, I tend to think that building a mobile version of a web app should go first because it's cheaper. Once you can show that there are customers using mobile, then you build native apps.
My preference goes something like this: chat (IM, something custom, whatever), video call (hangout, skype, etc.), email, text, phone call, in-person. Of course the order may vary depending on circumstances - obviously you don't have casual conversation via SMS when out to lunch with someone, or if you work in the same room - but this is generally how I view the value of communications. Phone calls are productivity killers.
"Questions asking us to recommend or find a tool, library or favorite off-site resource
are off-topic for Stack Overflow as they tend to attract
opinionated answers and spam. Instead, describe the problem
and what has been done so far to solve it." – George Stocker
The question is still there and is still helpful to anyone who happens to land on it from some search; it just cant' be contributed to anymore unless the question is edited to raise its quality and the community reopens it (it doesn't take a diamond-mod to reopen). I can't tell that it was ever deleted, although it could be that a status change was backfilled after the flags updates.In the strictest sense, I suppose this is correct. However, the funny thing about language is that it's designed to be perceived in the same way by as many people as possible. That's the entire point of language. We elect moderators to exercise their judgement with regards to how a question will be perceived by most people, and I'd say they aren't usually wrong.
The OP is correct, though: Google has an army of lawyers and should have caught this.
Yes. Yes you do. How many clothing lines exist solely because of some celebrity? Examples here: http://fashion.about.com/cs/celebritystyle/a/celebritylines.....
The difference is that the vapid celebrity culture is even more imitated than sports stars, but for even less apparent reasons. At least sports starts have accomplished something, even if it is ultimately not terribly meaningful.
# distance from home country to hosting country
# similarity of hosting country's culture to home country
I'd also like to know how many medals were won by NCAA or American professional league athletes representing other countries (Usain Bolt, for example).
git push origin master my-tag ...
That might also work with --all. If it does, you could get away with: git push --all origin my-tag
As for the rest...I'm not sure what your best way forward is. One way might be simply to don't delete branches. They'll clutter the list of branches, but so what? Just ignore them if you don't use them.The 'git remote prune' way is probably best. Run that, and then check for local branches that aren't tracking a remote. That's scriptable.
I don't think there's a simple and elegant answer here, because what you're doing basically turns Git into subversion. That's pretty much unavoidable when one is doing what you're doing.
You could be more "distributed" if you only worked on specific features or modules (or whatever) at specific locations. Then you could just merge when necessary instead of always having to keep your branches in sync :-)
git push --all --tags
From location1, if you just want to be able to make your working copy look like origin/<branchname>, you don't have to create a new branch. You can checkout on a tracking branch. You just can't do all your normal work there (i.e., when you want to commit, you'd need to checkout a branch to commit on). If you want to create local branches that track all the remote branches, the command you're currently using (minus the --track option) is what you need.As for deleting a branch, the simplest way is to not push branches that you're not going to keep. I understand what your context is, so you'll likely be stuck with maintaining branches in your central repository.
There's not a dramatic simplification I can see in your workflow, but here's where Git's strong-suit really kicks in: it's very, very scriptable. It would be nearly trivial to write simple bash scripts to do most of this in one command (you might even be able to get there with aliases).
But that's just the technical stuff that he rapidly dismissed in his update/addendum. Fine. I still think he doesn't get it. I think he's right that patterns are largely about vocabulary, but he's wrong to say that the GoF book (or patterns in general) turn people into macro processor systems. I have yet to read the GoF book, but my basic understanding of patterns is that it indeed creates vocabulary - which gives you abstractions with which to glue your thoughts together so you can have new thoughts. That's what vocabulary does. That's exactly how I think of design patterns in software.
And re: 45-year-olds - there are less of them in combat for very practical reasons: a) they've already retired (45-20 is 25, and most people join younger than 25) b) they're promoted into ranks that don't get into direct combat.
I think the notion that a 45-year old would have a lower survival rate is just silly, unless you've got some particular set of facts to back it up.
Go the route of a two-tier system, where users who listen to ad-supported music get to listen to music whose label doesn't demand more than $X, and to listen to music whose label demands too much you have to pay $Y per month, where Y must be calculated to cover the costs of the royalties. Pandora needs to realize that it's the future, and be confident about that. Relegate the music owned by extorting labels to the digital ghetto and be done with it. Eventually the great artists that are under a label will go independent, so you won't necessarily be killing off the best artists, in the long run. The important thing is that Pandora and it's investors have some balls.
This would work great for me, because the majority of the time, I don't really care all that much who I'm listening to, really; I'm after particular styles and sounds. Our current "system" of fan-dom is really just a way to keep track of what you like. If the Genome project is capable of keeping track of what I like for me,then I don't have to worry about who it is. This won't kill "fandom" either, because there will still be a handful of artists that I'll really like, and best of all, I'll discover them through the Genome's recommendations instead of ridiculous label promotions.
(a) oil is fungible. Fungible, FUNGIBLE.
(b) offshore drilling, will help, and nobody is proposing that it is a solution. Nuclear and solar electricity and better batteries are the solution. Drilling our own oil resources will help us while we get there.
#osdev used to be good, but trolls have made it a very inactive channel.