- A Unicode book that is both concise and useful
- A protocol with "Simple" in its title that has remained simple - SNMP, SMTP, SDLIP are just a few that have not.
- Revision control merges with absolutely no conflicts
Tuesday, September 28, 2010
Friday, September 24, 2010
Monday, September 20, 2010
99% of everything written about statistics is wrong, including this. So when people really do understand how to set up proper clinical trials or fit their data to useful distributions, I'm impressed. What most of us learned in school and university really wasn't enough to understand the traps for the unwary and naive in this area.
Statisticians also get to use some great words like homoscedasticity and kurtosis.
Thursday, September 16, 2010
If you develop or maintain Atlassian products (JIRA, Confluence, etc), this event is a great place to be (October 11th - 13th, California, $200).
I'm looking forward to it again with a relish I rarely find for many group events.
Wednesday, September 15, 2010
Wednesday, September 1, 2010
Everyone wants a good technical environment for developing their software, and Practical Development Environments contains helpful guidelines for how to create and maintain a great development environment. It discusses some of the current tools that are available, covering different areas...
Good advice, tools sections dated now
Pros: Concise, Well-written, Accurate
Cons: Partly outdated
Best Uses: Intermediate, Toolsmith, Novice
Describe Yourself: Consultant, Sys Admin, Developer, Author, Toolsmith
I'm the author and the book still works as intended. Each chapter has a section on using software development tools (version control, builds, bug trackers etc). The second half of each chapter refers to tools in each area that were current five years ago, so these parts have aged correctly.
I've run a consulting business for the past four years based around many of the ideas in this book and find that, for the most part, they are working well for my clients.
Posted by Matt Doar at 11:27 AM
I remember writing some parts of Practical Development Environments vividly, despite the sleep deprivation that writing a book and having a new child will produce. One such section summarizes what goes into a good bug report:
The three key points to bear in mind when creating a bug report should be:
- How to reproduce the bug, as precisely as possible, and how often this will make the bug appear
- What should have happened, at least in your opinion
- What actually happened, or at least as much information as you have recorded
I still like what I wrote. And now I think it's good advice for other situations. For example,
- Action: I was taking my brother's toy from him. It was his new toy.
- Expectation: He should have let me take it because he wasn't using it anymore
- Observation: He hit me!
Maybe I'll get it printed on my next batch of business cards:
Action, Expectation, Observation.