Github is fantastic, but their pricing makes it so adding private repos gets expensive rather quickly. I was paying $12/month for 10 private repos and still running low - the thought of upgrading to $22/month wasn’t too appealing. Luckily, Bitbucket offers unlimited private repos for individuals.
There are a bunch of existing guides on migrating git repos to Bitbucket, but they’re all about changing git remote settings. And that’s fine, but I prefer a more foolproof approach that can be done quickly even when you want to migrate a lot of private repos.
Note: this approach involves deleting and re-cloning your repos, so don’t do it if there are dependencies on your local repos.
First, make sure all the repos you want to transfer are completely synced with Github, because we’ll be deleting them later. In each one, do:
git push --all origin
Now, sign up for a Bitbucket account and go to Repositories -> Import repository
Bitbucket knows the score and has a Github import feature. Click on it and authorize access (make sure you’re comfortable with the privileges granted). Once you do that, you’ll get a nice list of all your Github repos:
Now you can just click import on the ones you want. Don’t worry, private repos will remain private after importing.
Finally, delete the local copies of the repo and re-clone them with the Bitbucket URL, which you can find on the Bitbucket repo page. Note that to clone with SSH, you’ll need to copy your public key to Bitbucket, which you can find in your account settings.
Example with a repo named “configs”:
rm -rf configs
git clone firstname.lastname@example.org:iqnivek/configs.git
I personally prefer this approach over changing the git remote settings on each repo - there’s less likelihood for error. And if you use Bitbucket’s handy Github import, you can migrate a lot of repos quite quickly.
Flat design is popular and, as a whole, there’s not much to complain about. It’s easier to implement and harder to screw up, and its tendency towards clean, simple interfaces is great. But the lack of visual detail becomes a disadvantage when using certain components.
Here’s an example of Windows 7 native radio buttons:
And here’s an example of flat radio buttons, from the popular Flat UI:
Flat design, by eliminating gradients and textures, by nature means fewer affordances - you don’t have as many visually distinctive characteristics. With the Windows radio buttons, you don’t need to even look at the buttons directly to know what they do - the slight “scooped-in” effect clues you in subconsciously. Whereas with the flat buttons, it requires a moment’s thought (is that a button? or just a pretty icon?). You’ll still figure it out, but designers want users to have to think less, not more.
Here’s another comparison - native Windows buttons:
And flat UI buttons:
Again, with the flat version, it can be hard to tell exactly what you’re looking at, whereas with the former you don’t even need to think about it.
Adding small visual details like this give elements depth, but to make them look as simple and elegant as a “flat” counterpart takes more work - which I think is part of the reason flat design has taken off so much. But for interactive components like buttons and inputs, having clear and easily identifiable visual characteristics works better, and you can’t really do that with flat design.
There are a few ways you could experience wind speeds faster than 500 mph. One is to stand on top of a volcano when it erupts. When Mount St. Helens exploded in 1980, the column of ash was blasted outward at 700 mph, which is close to the speed of sound. Another way to experience 500 mph winds is to trigger a hypercane.
You are going to make every moment count. I mean, you better make every moment count. Live your life now; start in the morning. You mustn’t sit around waiting to die. When it happens you should come into the cemetery on a motorbike, skid to a halt by the side of the coffin, jump in and say: “Great I just made it.”
I think it’s important that you really like whatever you’re doing. If you don’t like it, life is too short.
Episode 1: what is going on
Episode 2-3: hrm.
Episode 4: eh. dropped.
keep seeing good reviews about it
Episode 5: okay, I’ll pick it up again
Episode 6: what is going on
Episode 7-9: huh, this is more interesting than I remember
Episode 10: everything makes sense now
Episode 11: this is the best thing ever