Many default or custom content types in Drupal will have the Title listed first on the "Add content" page, then the Body. The edit form is set up this way by default.
However, don't forget to take the needs of your content administrators into account. I recently was creating a "Testimonials" content type. It made the most sense to use the title field as the "Testimonial By" field, and the Body as the "Testimonial" field. However, the reading and editing order for this content type should be "Testimonial," then "Testimonial By."
I ran into an issue today. I rethemed a site in my development queue and declared my main content region as "regions[main_content]." This change introduced a problem that wasn't immediately apparent since the theme was already enabled on my development site.
However, when a colleague tried to rebuild this site minus the database, the Appearance page said "This version is not compatible with Drupal 7.x and should be replaced." Turns out that "regions[content]" is a required field for the theme .info file. Good to know.
Drush is certainly a tool that makes Drupal development faster. Even with that speed, I found myself typing the same commands over and over again every morning just to get started, and I wanted to cut down on that time. We use two repositories at Princeton, one for core and sites/all, and one for the sites/sitename folder. So, I had to update two repos (git pull), update the database just in case (drush updatedb), clear cache (drush cc all), and switch between directories to do so.
Included by default in Drupal Core is a .gitignore file. This file lives in the root folder. So why is it worth noting?
If you are using Git for version control, then this .gitignore file sets up recommended directories and files that should NOT be under version control. When we take a look at this file, we see the following: