I just posted the third update of the second edition of “The Yii Book“. This update brings this edition of the book to 365 pages, with two more revised chapters, getting to a total of 14, and completing Part II of the book. (I’m a little bit farther along than that, but thought Part II a logical place to do this release.)
Continue Reading...Archives For Web Development
On Monday, November 2, 2015, I posted the second update of the second edition of “The Yii Book”. (I was hoping to blog about it here on Tuesday but…) This update brings the book to 307 pages, with four more revised chapters, bringing the total to 12. Specific release notes are…
Continue Reading...
I just posted the first update for the second edition of “The Yii Book”, covering version 2 of the Yii framework. The release notes are lengthy, but a couple of quick “I’m aware” thoughts up front…
Continue Reading...
Hey, ho! Just a quick check-in to let you know where things stand on the second edition of “The Yii Book”, for version 2 of the Yii framework. Over the past month I’ve started sequentially going through the book to update it for the new Yii version. I’ve also set targets in my mind, with my own target deadline (not sharing, because then it’s just embarrassing when the deadline sails past).
Continue Reading...
I was fairly slow to adopt Git (having been raised on other version control tools), but, needless to say and like most of us, it’s now a daily component of my work flow. And certainly using Git myself is a much different beast than using Git in a massive organization with hundreds of engineers all working from the same code base. Which is to say: there’s still plenty of room for my Git skills to grow.
Recently, though, I’ve come to appreciate another value of Git, which hadn’t previously crossed my mind or been written about elsewhere (such that I’ve seen):
Git is a valuable tool for technical writers.
One interpretation of that sentence is that you can use Git to manage revisions to a document. Sure. That’s completely logical and not surprising. But I’ve found something more nuanced in my Git usage as a technical writer.
