Tony Rost's Blog
The next decade will bring a society-changing transformation to smart, connected things throughout our personal, professional, and public lives. Everything about this change is big: the security risks are big, the improvements are big, and the scale is big. This change is a prime space to find new revenue opportunities for every product and service business.
The challenge of estimating software projects is that software is a creative act: you can paint a line, or you can paint a Monet. Every person involved has a different opinion about the amount of creativity needed for every miniscule feature.
Web design and development agencies are lacking in code review practices, and our collective clients are suffering as a result.
Views 3 now supports queries against Google Analytics. I've added this experimental module to the 7.x-3.x development release of Google Analytics Reports.
Most popular Google Analytics queries currently pass:
The slowest, most tedious way of finding a bad git commit is something we've all done before. You checkout some old commit, make sure the broken code isn't there, then checkout a slightly newer commit, check again, and repeat over and over until you find the flawed commit.
git bisect is a much better way. It's like a little wizard that walks you through recent commits, asks you if they are good or bad, and narrows down the broken commit. In this blog post, I encourage you to create a fresh git repository and walk through each step. Hopefully, you'll gain an intrinsic understanding of
git bisect by the end of the exercise.