This is a presentation I gave with Brie Hoblin for the BTV Testers meetup. These slides may be useful for anybody working with eCommerce or online credit card transactions.
Many dungeon masters fall victim to the trap of over-preparation.
Spending a lot of time preparing a specific plan for a game can make it difficult to let go of that plan (as I wrote in Part II). One might conclude that planning is a waste of time. As an absolute, this could not be more wrong.
“Planning is essential. Plans are useless.”
Rather than preparing for one story, a good dungeon master prepares for any story.
There are a lot of ways to use git to collaborate with other developers. I’ve found the following principles to be useful for keeping my sanity when working with git. My experience has mostly been with small teams of two to six developers, but these principles may apply to any size team.
Of course, “best practices” are elusive, and the following is just my established method.
- Do not commit vendor code.
- Do not commit compiled code.
- Do not commit commented-out code — just delete it.
- Make small commits.
- Explain the why, not the what, in your commit message.
- Create a new branch for every task / small feature / bug fix.
- Rebase instead of merge to resolve conflicts.
- Use pull requests. Get reviews.
- Do not commit or push directly to the master branch.
- Deploy from the master branch to staging.
Recently I received some questions from a student who is just starting out on their freelance web development journey. For those new to client work (and even those with experience), managing client expectations, contract terms, and payment schedules can be incredibly daunting. Here I’ve provided my tips to help you in your own freelancing.
Last week Fred Meyer from WP Shout published the first draft of an “Honor Code” for small business web developers. I don’t know of any website owner or website developer who hasn’t had at least one client relationship sour. In an industry with as wide as a knowledge gap between vendors and customers as software development, trust is more than paramount. I highly recommend this article for anybody who works with clients or vendors in the technology and software space.