Made with 🧀 in Madison
Designers overlook it. Developers demand it. There’s always been a need for discernible web design in Photoshop. Nobody likes inheriting muddy PSDs, and Photoshop Etiquette’s purpose is to help you improve the clarity of yours.
I’m no astronomer, but I believe it’s also possible that the moon ends up being recaptured by Earth’s gravitational pull. Probably unlikely though.
http://youtu.be/B9Qny9cU1Ws
I really like being able to deploy my current theme to production from my local environment. I can test locally and then deploy to the live site when I’m ready.
Some people like to keep all of WordPress under version control. I don’t think that’s useful unless you’re a WordPress developer. You’re unnecessarily tracking changes to WordPress and your environment. I like to keep each theme and each plugin in it’s own repository. They’re separate projects so they should get separate repositories.
I constantly go back to this great tutorial when I have to set up a bare git repository on a production server.
As always, Merlin’s advice can be generalized to many different jobs. Whether you’re a freelance photographer, graphic designer, writer, speaker, etc., I think lots of people have a problem knowing their “price”.
As Merlin says:
This part sucks and is nearly impossible to get any good at for a year or five, but it’s something you simply must tackle with increasingly less fear and hesitation.
WordPress developers will be familiar with many of the problems described here.
I’ve been thinking about this quite a bit lately — writing open source software (where you have a whole variety of environments to support) will be entirely different from working at a company like Facebook (where you probably know more specifically what the servers will look like). Each is going to have his own challenges to think about. Once you get used to developing with certain challenges in mind, it’s probably not obvious what new challenges there will be in a different context.