A Postcard from Tools of Change

Think back to the summer of 2007. The first iPhones are just hitting the stores. Kindle is still a gleam in Jeff Bezos' eye. And in the words of Publishers Weekly, "a festival of practical geekery" is taking place in San Jose, CA.

That festival was the first Tools of Change for Publishing conference. We were there, of course. And while comparatively small, it was the largest gathering we'd found of people who cared as much as we did about the transition from print to digital books.

That's still true today, which is why I'm excited to be on the floor of ToC 2010 as I write this. The show's a lot bigger now, and has spread beyond its geeky roots to focus on seismic shifts we're all aware of…the explosion of handheld devices, social software and changes in the ways all of us find and use information.

If you're here, come see us. We'll be in booth 114 with our partners Digital Divide Data, and you can always reach us via our contact form. If you're not here, we'll be posting updates on Twitter:

http://twitter.com/tizra

We believe change is not only good, it's constant, and we're looking forward to what comes next.

Comments

Technical Podcasts

If there is something the web as surely changed, it was the way that software engineers need to work. It is now a crucial aspect of our work to be able draw from the huge internet knowledge base out there in an efficient way to get to the right answers. Part of that information extraction is related to the keeping-up-to-date effort that every developer is required to accomplish to continue to be productive. While previous a software engineer could rely mostly on print material, nowadays we need to rely as well on content available on the net. Podcasts are such a source that can bring an amazing amount of information to the mix of knowledge one needs these days. If you are a software engineer and have not jumped into the podcast wagon yet, I suggest you do so. Here is a list some technical podcasts that we hear at Tizra: The Java Posse : a fantastic podcast on Java development. Containing news info update, analysis of tools, overall software development discussions. Software as She Dev...

Using XML to Create a Better Online Reading Experience for the American Payroll Association

Congrats to the American Payroll Association on their recent launch of XML-based publications on Tizra! Thanks to this collaboration, APA's authoritative books for payroll professionals are now available in crisp, reflowable HTML, creating a user experience that feels like a truly digital native product, rather than a conversion from print. XML-based publishing also creates a better mobile reading experience, supports more precise search and navigation, and opens the door to better accessibility for users with low vision and other disabilities. Our partners at Scribe did a great job supporting APA through the process of producing the XML for loading into Tizra, and we’d definitely recommend them to anyone interested in such a transition. It’s hard to overstate what a big step forward this is for Tizra as a platform and a company. XML has long been planned for in the product's architecture, but now for the first time, we have a working example that demonstrates t...

The importance of continuous integration

Leading a team of developers in the effort of building a robust, quality software product should involve the establishment of some process and tools to assist the team effort and serve as a safety net for the errors of getting people to work together. Continuous integration is, I believe, a crucial element of that process. Introduced by Martin Fowler and Matt Foemmel (see article Continuous Integration ), continuous integration establishes the practice of frequent integration of work developed by the several team members verified by automated build and testing of integrated code within a clean sandbox. This practice is valuable for several reasons: It promotes the development of a clear process of building/deployment independent of any specificity of developer's platforms. Code that exists on a single platform only is bound to become dependent on specific aspects of that platform without anyone really noticing the dependencies until trying to port to other platforms. The existence ...

Tizra Blog

Search This Blog