Posts Tagged ‘Developer Productivity’

  • Klocwork Developer Network Set to Go Live

    on Mar 22, 11 • by Alan Weekes • with No Comments

    Our dilemma: How do we remove the barriers to knowledge about Klocwork's toolset, and developer best practices for creating high-quality code? The answer: Klocwork Developer Network--a new online portal designed for learning, sharing and discussing all things source code analysis.

    Read More »
  • Death by a thousand cuts

    on Feb 11, 10 • by Helen Abbott • with No Comments

    Spend 80% of your time on One Thing.

    As a manager of a small tech writing team in an agile environment (are there any large tech writing teams left out there?), it’s easy to lose myself in how-the-heck-can-we-keep-up-with-myriad-coders-frantically-coding thinking. So when my manager scheduled a meeting to ask what innovations my team has planned for the next release or two, I thought of a few choice responses, such as “Um… how about documenting the new features in time for release? Is that innovative enough for ya?” and “Innovate THIS.” Eventually I calmed down, since he’s the boss, and I have a mortgage.

    Read More »
  • Limping through agile

    on Jan 21, 10 • by Patti Murphy • with 2 Comments

    The not-so-agile technical writer

    I’m a technical writer who’s a big picture kind of person and that means agile development is sheer torture for me. Going into my second agile project, I thought I would be able to go with the “flow” a bit more. I was wrong. But, it’s important to point out that our documentation team hit all of our deadlines for new features, while substantially rewriting our help set and moving it to a wiki. I’m pleased with the outcome, but the trip was not pleasant. This will be my first post in a series about

    Read More »
  • ESC Boston Day 1 Recap

    on Sep 22, 09 • by Brendan Harrison • with No Comments

    Good first day at ESC Boston2009. Gwyn and Alen presented a well attended talk on using source code analysis (SCA) to improve developer productivity. Key takeaways from the presentation: How SCA will impact your development velocity Quick history on SCA – talked about lint and the general evolution of the technology How the information generated by static code analysis can be used to solve a variety of development challenge Demo of where SCA fits from a code review, refactoring and bug detection standpoint Interesting change from past presentations where most people now understand the basics

    Read More »
  • You don’t need tools?

    on Aug 4, 09 • by Alen Zukich • with No Comments

    A recent article brings up some interesting discussion.   I definitely agree that high quality code can be created without tools or any automation. But in organizations where you have tight deadlines, fewer developers and more features than ever, something has to give.  To me, saying that you don’t need tools or automation is like saying you want to dig a hole for your pool with a spoon OR climb Mount Everest jumping on one foot OR you get the point…Sure you can write high quality code, but how productive will you be when you have

    Read More »
  • The Unspoken Agile Advantage

    on Jul 28, 09 • by Mike Laginski • with No Comments

    Agile board by pcalcado (flickr)

    I sat in on an iteration review this week and came away feeling great about the team, the process and the strategic direction we taking our products.  Reflecting on the meeting I asked myself what was the magic in the meeting? The strategic direction of the product had been hashed out months ago in a grueling multi day session,  almost all of the members of the development team that were present for the review have been with the company since it’s inception back in 2001  and the meeting covered what it was billed to cover

    Read More »
  • Developer productivity thrown out the door

    on Jun 2, 09 • by Alen Zukich • with 1 Comment

    I deal with many organizations that deploy the Klocwork software to the desktop so that developers can use our tools to help them find and fix bugs in their code.  The message is simple, fix your bugs before you check in your code.  Many of the organizations I deal with have a mismatch of environments and tools.  In the world of writing code it is not uncommon to find developers using Emacs, Vim, Visual Studio, Eclipse or any number of IDEs/text editors.  Nothing wrong with this, although it doesn’t offer a clean, repeatable environment but

    Read More »
Scroll to top