Posts Tagged ‘Code Review’

  • The Joy of… Code Review (part 2)

    on Jan 28, 10 • by Gwyn Fisher • with 1 Comment

    10-24-2012 2-16-09 PM

    Part II – Joy is the word… OK, so Grease is really the word, but it didn’t fit my theme, gimme a break… Anyway, back on topic, since Joy of code review – part one of this series was published last year we’ve seen our new code review product in action in a variety of customer and prospect situations, and much like the eponymous hair product in the musical mentioned above, what we thought of as an interesting twist on an existing paradigm has turned into a bit of a barn burner. I refer, in

    Read More »
  • Embedded Systems Engineering – German 2009 Edition

    on Dec 10, 09 • by Todd Landry • with 1 Comment

    IMG_0070

    Just wrapped up a successful 2 day Embedded System Engineering conference in Stuttgart, Germany. This “all-German” show had just shy of 600 attendees, as well as about 60 individuals (representing the 20 or so companies exhibiting), so this was considered very good by the show organizers (who by the way did a fantastic job… the food here, for example, was as good as I’ve ever seen for such an event). The Klocwork booth was shared with our good friends at Emenda, and we had a choice spot that allowed a good flow of people. We

    Read More »
  • The Joy of … Code Review?

    on Nov 24, 09 • by Gwyn Fisher • with 2 Comments

    sally-code-review

    Part I – Ode to Joy Since the launch of the seminal “Joy” work which hopefully doesn’t need mention here, we’ve seen everything from The Joy of Cooking to The Joy of Not Working (my personal favorite!), and so further to that deeply mined vein of authoritative works we bring you the necessarily over burdened… Joy of Code Review! Joy, you say? Let me count the ways… I implement a task, using what I consider to be best practice patterns and guidelines; I slave over this, my creation, and when it’s done, I stand back

    Read More »
  • Going Agile Part 2: Preparing for Iteration 1

    on Oct 20, 09 • by Todd Landry • with 1 Comment

    Scrum Board

    In part one of Going Agile,I talked about how we introduced Agile to our development team. This next post will look at the events that led to our first iteration planning meeting. During the weeks that led up to Iteration 1, there was much work that went on as a team, and much that each team member did individually. As the Product Owner, my biggest task was to create a backlog. Sure, I knew what the main new features were going to be, but I still needed to capture this, and add other oft-requested features

    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 »
  • Measuring Progress in Code Quality

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

    Succinctly communicating what Klocwork does and how it helps improve productivity during code reviews, integration builds, and of course for developers is always a challenge. We’ve tried to capture this visually with this simple SDLC image, and of course we always talk about the importance of finding bugs early. Then somebody else comes along and makes the point in a way you never thought of… here’s a funny that’s been going around for some time, but I figured it’s worth passing along to the Kloctalk readers

    Read More »
  • False positives in modern static analyzers

    on May 22, 09 • by Alen Zukich • with 1 Comment

    In response to Jason’s post about false positives.  First of all there is a general misconception of false positives.  Modern static source code analysis tools have changed the game.  It is not the Lint tool of the past, a focus with deep inter-procedural technology has placed the requirement that static tools today produce more real issues than false reports. With that said, Jason is right, large code bases never running static analysis will produce a large number of issues no matter how accurate it is.  Even though static analysis tools do provide a number of

    Read More »
  • Static analysis and code reviews

    on May 19, 09 • by Alen Zukich • with 1 Comment

    Jason certainly hits the nail on the head.  Automation, specifically using static analysis, is key and it should be tightly integrated with your code review. Although we need to be careful where we label source code analysis.  Static source code analysis certainly can find those low level issues such as labeling your local variables correctly, but it goes beyond simple code style issues. Where static source code analysis can really help is with the deep inter-procedural context that it can provide.  For example, during a code review you go through some code with a number

    Read More »
Scroll to top