Welcome!

Java IoT Authors: Zakia Bouachraoui, Pat Romanski, Elizabeth White, Liz McMillan, Yeshim Deniz

Related Topics: @DevOpsSummit, Java IoT, Agile Computing

@DevOpsSummit: Blog Feed Post

Who Is Responsible for “Good Code”? By @daedtech | @DevOpsSummit #DevOps

Typically, managers will rely at least in part on results and observable behaviors

Who Is Responsible for "Good Code"?
by Erik Dietrich

A few weeks back, I wrote a post about getting ready to address a coworker's bad code.  This sparked some conversation across various media, including the following interesting question:

...seems that there is a breakdown in managing the development process. Why is Bob allowed [to keep] writing bad code?

Measuring Developers
This feedback is interesting enough to merit a blog post in and of itself. I recognize a question that cuts to the heart of a software development conundrum when I see it.  The structure of most organizations that employ software developers is this: the developers responsible for code report up through a structure of people that don't.  To put it another way, the people responsible for personnel management usually don't understand how to evaluate the work of those reporting to them - at least not directly.

Even if people with titles such as "Director of Software Engineering" or "Development Manager" had been developers at some point, asking them to perform code reviews isn't a solid approach.  It wouldn't scale well.  Imagine asking someone to do detailed code reviews with seven or eight people while also doing all of the other things a manager is required to do, such as budgeting, dealing with other departments, worrying about software licensing, etc.  And that's even assuming they're technical. Most managers have to squint pretty hard into their rear view mirrors to see the last time they wrote a lot of code, if there ever was a time.

Typically, managers will rely at least in part on results and observable behaviors.  Does the developer keep long hours?  Does the developer take one for the team?  Did the developer heroically work 90 hours last week to get the code out on time?  Did the developer fix a lot of bugs, or better yet, write code in which not a lot of bugs were reported?

All of that sounds reasonable until you think of technical debt.  "Technical debt" is a term that describes a trade: when you take shortcuts in the code in order to ship today, it's at the cost of having a mess when you try to ship down the line. For a great visual of this, imagine a child tasked with cleaning his room who simply stuffs all of the clutter and food debris under the bed.  In this light, the very developers that managers view as effective may be writing awful code and making a mess.  Tired developers, working 90 hour weeks, are almost certainly thrashing in a tech debt cycle - making heroic efforts to overcome problems that they created in the first place by making a mess.

It's hard for a manager to make any form of direct evaluation, even when it seems as though there are easy ones to be made.

Metrics to the Rescue?
Okay, so they can't make direct evaluations.  What about indirect ones?  Well, those are tricky as well.  One of the most common traps for software management, particularly if it's not terribly mature, is the allure of metrics.  Perhaps you've heard calls for a team build that reports unit test coverage, method size, or cyclomatic complexity?  If a manager could get access to those statistics, the reasoning goes  he/she could know who on the team was writing good code and who wasn't.

Be careful what you measure.  It's possible to achieve a high degree of unit test coverage by writing test methods that don't assert anything.  You can keep method size under control by having classes with thousands of tiny methods.  Perhaps the most iconic example of unintended consequences for measuring developer productivity is the mountains of terrible code that resulted from managers, at one time, trying to measure developer productivity in lines of committed code.  Metrics are tempting for managers, but there be dragons.  Relying on metrics to measure developer effectiveness has not historically been a path to success.

Measurement via Human?
If the managers who make personnel decisions can't rely on themselves to evaluate developers and they can't rely on machines to do it, what choice is left?  Clearly, they're going to have to turn to other humans to do this.  Common patterns that you see are the appointment of a trusted advisor in the form of someone with a title like "Architect" or "Tech Lead." Or perhaps they take a more egalitarian approach, like having the developers perform peer reviews or pair program.  In this fashion, the manager delegates evaluation to people in a position to do it, and she uses the information they furnish to make decisions.

This is a familiar pattern, and I imagine that you might be nodding right now.  But, going back to the original question, what if Bob-the one checking in the bad code-is a senior team member or even the architect?  Think it's not possible?  It happens all the time.  Check out the popularity of this post, describing a phenomenon many people seem to identify with. A manager trusting an advisor will introduce one check and balance, but it's hardly foolproof.  It gets better when there is regular peer review and pairing.  More checks, more balances, more eyes, and more voices.

But guess what?  If we eliminate all evaluation options for managers with the exception of presiding over a team with extensive peer review, we're back to square one.  It's going to be up to a member of the team without any authority over Bob to let Bob know that he needs to improve his code.  It's going to take conversations, persuasion, and collaboration, as opposed to management cracking the whip and sizing people up.

In the end, there's only one reliable way for management to ensure that there aren't Bobs out there, writing bad code indefinitely without feedback.  They need to create a collaborative culture of positive feedback and trust so that the team of humans they're managing take care of one another and spur each other on toward improvement.  Bob's bad code is the team's bad code, not management's.  And the team, not management, needs to own the code.

Read the original blog entry...

More Stories By SmartBear Blog

As the leader in software quality tools for the connected world, SmartBear supports more than two million software professionals and over 25,000 organizations in 90 countries that use its products to build and deliver the world’s greatest applications. With today’s applications deploying on mobile, Web, desktop, Internet of Things (IoT) or even embedded computing platforms, the connected nature of these applications through public and private APIs presents a unique set of challenges for developers, testers and operations teams. SmartBear's software quality tools assist with code review, functional and load testing, API readiness as well as performance monitoring of these modern applications.

IoT & Smart Cities Stories
All in Mobile is a place where we continually maximize their impact by fostering understanding, empathy, insights, creativity and joy. They believe that a truly useful and desirable mobile app doesn't need the brightest idea or the most advanced technology. A great product begins with understanding people. It's easy to think that customers will love your app, but can you justify it? They make sure your final app is something that users truly want and need. The only way to do this is by ...
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
The challenges of aggregating data from consumer-oriented devices, such as wearable technologies and smart thermostats, are fairly well-understood. However, there are a new set of challenges for IoT devices that generate megabytes or gigabytes of data per second. Certainly, the infrastructure will have to change, as those volumes of data will likely overwhelm the available bandwidth for aggregating the data into a central repository. Ochandarena discusses a whole new way to think about your next...
CloudEXPO | DevOpsSUMMIT | DXWorldEXPO are the world's most influential, independent events where Cloud Computing was coined and where technology buyers and vendors meet to experience and discuss the big picture of Digital Transformation and all of the strategies, tactics, and tools they need to realize their goals. Sponsors of DXWorldEXPO | CloudEXPO benefit from unmatched branding, profile building and lead generation opportunities.
DXWorldEXPO LLC announced today that Big Data Federation to Exhibit at the 22nd International CloudEXPO, colocated with DevOpsSUMMIT and DXWorldEXPO, November 12-13, 2018 in New York City. Big Data Federation, Inc. develops and applies artificial intelligence to predict financial and economic events that matter. The company uncovers patterns and precise drivers of performance and outcomes with the aid of machine-learning algorithms, big data, and fundamental analysis. Their products are deployed...
Cell networks have the advantage of long-range communications, reaching an estimated 90% of the world. But cell networks such as 2G, 3G and LTE consume lots of power and were designed for connecting people. They are not optimized for low- or battery-powered devices or for IoT applications with infrequently transmitted data. Cell IoT modules that support narrow-band IoT and 4G cell networks will enable cell connectivity, device management, and app enablement for low-power wide-area network IoT. B...
The hierarchical architecture that distributes "compute" within the network specially at the edge can enable new services by harnessing emerging technologies. But Edge-Compute comes at increased cost that needs to be managed and potentially augmented by creative architecture solutions as there will always a catching-up with the capacity demands. Processing power in smartphones has enhanced YoY and there is increasingly spare compute capacity that can be potentially pooled. Uber has successfully ...
SYS-CON Events announced today that CrowdReviews.com has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5–7, 2018, at the Javits Center in New York City, NY. CrowdReviews.com is a transparent online platform for determining which products and services are the best based on the opinion of the crowd. The crowd consists of Internet users that have experienced products and services first-hand and have an interest in letting other potential buye...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...