Last time, I did a controversial post about the benefits of IDEs over text editors. With IDEs, I argued that the tools available far outweigh any advantages you get from text editors. For example, IDEs provide built-in tools for refactoring, auto-completion, static analysis, and testing, just to name a few. But I must admit I’m a bit of a hypocrite. I do in fact use Vim. I use it mainly because it is just easier to open a file quickly. But that’s just me. I don’t do pure development currently, so I only need to
Read More »
“Take nothing for granted,” is the mantra of every software tester. Add localization to the mix and the level of vigilance goes into hyperdrive. 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. Part 2 was development discomfort and solutions. In this final installment, we explore the lessons learned by our testing department, who are known for being generous to a fault, as in “here’s a PR for you, and you, and you…” For this post,
Read More »
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 »
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 »
Everyone knows this chart, right? The later bugs are introduced, the more they cost. Of course, common sense. But it also happens to be true. As the chart shows, very little bug detection is happening before testing, while a developer is coding. So, if you find more bugs when the cost of repair is least expensive and risky, you’re obviously going to get a big payoff. Ok, so far you haven’t heard anything that every software development professional doesn’t already know. What everyone doesn’t know is that source code analysis can deliver this payoff. We
Read More »
As any static analysis or source code analysis vendor will tell you, false positives are a way of life. As any user will tell you, false positives suck! So what do you do about them? Make the tools better at finding the real issues and provide automated filtering capabilities. But I’m not here to talk about false positives where the tool is utterly wrong. What I want to talk about today is what I call “perceptual false positives”. I’ve had discussions with customers where they tell me 80% of all their defects are false. Odd,
Read More »
So it’s that time again, when our team finally gets to sleep for a day or two and get their lives back in order. What am I talking about? Answer: Klocwork Insight 9.5 releases today and boy are we ever happy to see it go live — we’re “out there Jerry” and yes, of course we’re loving every minute of it. This has been a long release, taking significant research and development to bring to fruition, all the while continuing to release more traditional shipments as we went, but finally culminating in a new, game-changing
Read More »
Klocwork Developer Network presents Klocwork University, which consolidates all our online learning resources onto a single page. Klocwork University is your one stop for self-paced online learning and how-tos about: Setting up and using our static analysis tools on your desktop or integration build The latest trends in software security Agile coding practices and how they intersect with static analysis Klocwork product overviews At Klocwork University you’ll see helpful descriptions of: In-house and partner-generated e-learning courses Video how-tos Webinars After you browse our offerings on the Klocwork University page, click your selection and access your
Read More »I often hear that closing resources properly is way too verbose in Java, especially considering that resource freeing methods such as ‘close()’ are often throwing some type of an exception. However, if you handle resources properly it might turn out to be less of a burden than one might think. Let’s start with the following snippet, where I use an SQL driver to retrieve the list of “codes” matching the given “id”: 09 List<String> requestCodes(String dbUrl, String id) { 10 List<String> result = new ArrayList<String>(); 11 try { 12 Connection conn = DriverManager.getConnection(dbUrl); 13 PreparedStatement
Read More »
I’m sure this topic has been discussed a million times, but hey, here we go again. A recent question came up on whether people liked their experience of Eclipse vs. Visual Studio. Of course this brought up the advantages of one versus the other. But is that really a fair comparison? It really depends. What type of application are you building — a native Windows application? Surely going with Visual Studio makes sense. But if the goal is cross-platform, then you might look at Eclipse. Glad to see people are thinking about IDEs, but what
Read More »
