Posts Tagged ‘Lessons Learned’

  • Lessons learned from localization Part 2: Development discomfort

    on Oct 5, 12 • by Patti Murphy • with 4 Comments


    Suffering is only suffering if you learn nothing. When you learn nothing and needlessly perpetuate suffering, that’s where misery comes in. We prefer to be misery-free around here. In the spirit of helping others avoid needless pain, I launched this Lessons learned from localization series. In Part 1, we explored documentation pain and coping strategies. For Part 2, I talked to Russ Sherk, a developer here at Klocwork, who works on our web tools and handles product licensing, to see if he was happy to share some of his survival strategies from our Japanese localization

    Read More »
  • Lessons learned in localization Part 1: Documentation pain

    on Sep 27, 12 • by Patti Murphy • with 7 Comments


    The big story for our Klocwork Insight 9.6 release was localization for our Japanese market. Prior to this effort, we provided a Japanese version that included a translation of a small portion of the documentation set. Since we’re magnanimous, we felt that others should benefit from our suffering lessons learned from this endeavor. Originally, I’d hoped to do a video for this entitled Crying While Localizing in homage to that fun meme Crying While Eating. But asking one’s colleagues to blubber on camera for minutes at a time while confiding their frustrations was a little too

    Read More »
  • Top 5 time wasters for developers

    on Dec 1, 10 • by Patti Murphy • with 6 Comments

    Klocwork developer Russ Sherk sporting his mo'stache. It's hair today, gone tomorrow.

    Time’s a precious resource, so the saying goes. Don’t waste it. That’s particularly true for developers, who live in the critical path lane. And if there’s someone who knows a lot about time management, it’s Russ Sherk, an intermediate developer here at Klocwork, and the father of three young ‘uns. Russ works on our Klocwork Review and Klocwork Inspect products and handles licensing. For Russ, these are lessons learned over his six-year tenure at Klocwork. “These are things you need to think about or you won’t progress as a developer,” he says. Here’s what to

    Read More »
Scroll to top