Welcome!

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

Related Topics: Java IoT, Microsoft Cloud

Java IoT: Article

Standardized Tooling: Building Bridges, Not Walls

It’s time to reassess long-cherished practices

Some walls are necessary. We use brick-and-mortar walls to support buildings and firewalls to protect our computers from attack. But not all walls are good. Consider the Berlin Wall, a wall of segregation. It divided a country and its citizens, but has subsequently been brought down by people working together because upon re-evaluation the Wall did more harm than good. These thoughts led me to think about the walls that developers, QA managers, and database professionals have erected over the years to segregate themselves. Is it time to re-evaluate our own walls?

Most organizations, from the small mom-and-pops to the large enterprises, have established all kinds of walls. An example of a good wall is one that is intended to stop or prevent unwarranted access to mission-critical systems. An example of a bad wall would be one that stifles communication or understanding of the data being manipulated. Originally all walls were put in place to save time and rework, but over time it's a good idea to review long-held practices and reassess what's still effective and what isn't.

I've had a varied career; I have been a lone developer, a member of a team, a project manager, and I've run R&D for organizations. It was always been a practice to keep the database in the database professional's hands and away from others, such as application developers and QA staff. Why did I (and as far as I know, the rest of the IT industry) do this?

The answer is simple: the database is always a key fixture in any organization. Since the beginning, companies understood that they needed to have superior applications to collect information; the result was an explosion of invaluable data and information. And the industry learned quickly how bad things could get if that data was corrupted or lost. Based on this fear we established artificial walls that would isolate access, establish access rights, and limit communications between various departments in an organization.

But that was then. Is the same fear-based paradigm still valid in today's IT environment?

Various studies over the years have found that developers with correct requirements and the right tools are more productive and deliver better solutions. This makes sense, and it's been proven to be true across professions such as construction or automobile repair. Over the years, one of the areas that has been lacking in development are tools that cross boundaries to help developers write better SQL and database-related code. In many instances, the initial database interaction created by the developer is little more than a placeholder for the DBA or database professional to review later. This approach is inherently flawed primarily because it enables early mistakes to make it through the entire process to production.

We have all entered mistyped data, which has a cascading effect on the capture and storage of information. Developers who do not understand the database structures will inadvertently create new tables that are sometimes redundant, and don't always write the most effective SQL code. Somewhere in the chain the review process breaks, and mistakes that shouldn't happen do. This leads to DBAs missing or breaking SLA(s), mistrust between developers and DBAs and the application not working as it should.

So doesn't it make sense to put things in place that, at a minimum, help ensure the application developer doesn't just put in some "holder" code, but instead has a fairly good chance of creating a database manipulation layer that if the review breaks down, the code created will work as expected and that most errors or inefficiencies are caught and fixed upfront?

Current Practices: Barricades to Effectiveness
Developers don't want to write code that's incorrect, not up to the best standards, or performs poorly. So having the tools to help developers write solid code is essential. There are next to no developers in the world who think debuggers are bad or believe they shouldn't be used to isolate problems in code. Some problems are easily found using a debugger rather than applying other bug-hunting techniques. The same is true when it comes to optimizing an application.

A long-standing debate exists about the best approach to optimize for speed. Some in the developer community believe that optimization should only happen after the initial QA process has certified the application. Others have learned that making changes for speed and efficiency that late in the process can be dangerous and that it often takes another full QA cycle to ensure that the optimization process didn't break anything. (All developers have been bitten by the "one-line" change that fixes a problem but causes 50 other issues.)

Others in the community believe that initial testing of the software should be optimized before reaching QA. This can be effective, but also means code needs be reworked since QA hasn't certified it as correct. Then there's a school that believes optimization should only happen when the application is in maintenance, since that's the only time the software is usually considered correct.

Most likely an "all of these" approach is warranted. Consider Wall Street: if it didn't build performance and QA into every step its ability to process huge numbers of transactions would be almost impossible, and disastrous code could make it into production. Optimization needs to occur when things can be isolated, so using profiling tools throughout the development lifecycle is important for the developer. For example, how would a developer test the performance of an ‘x' algorithm versus a ‘y' algorithm if he doesn't have the tools to profile it in the first place?

It's been an established best practice that finding bugs early in the development process is a good thing. It saves time, and eliminates rework, retest, and redeploy cycles. It also reduces the possibility of bad code, embarrassing the company and delaying delivery.

Standardized Tooling: Building Bridges, Not Walls
Giving developers advanced tools to help write cleaner, better-performing code is essential in today's fast-paced marketplace. Plus, many organizations have put extra pressure on developers and DBAs, combining roles and making them wear both hats. But, there's a wall we've erected that's causing problems; the tools are not consistent between the two worlds.

But there are new tools on the market that help developers and DBAs visualize rather than read what they are building, and more importantly, reverse-engineer what they've already built. Products that let complex concepts be modeled and discussed from both an application developer, Q/A, DBA, and data center perspective have become critical to organizations. Existing tools will help find nightmares in applications, but the new tools are adding suggestions, best practices, and help in fixing code on the spot, even considering the context of who is making the change. Insights that may not be useful or understood from a developer standpoint may be incredibly important to a DBA and thus solve problems in less time. These new tools have capabilities we only dreamed about a few years ago, such as profiling the entire lifecycle so no one area is left out of the information chain, as well as automatically generating documentation, portals, and Wiki support to expose information to key players.

The walls that have been put up over the years are at least getting fitted with a few doors and windows; and in some cases they are even being taken down brick by brick, allowing for clean and nimble development. Will these changes eliminate all the problems facing developers and database professionals? Of course not, but hopefully standardized tooling will, at a minimum, increase the "vernacular" and reduce the bad code making it to production.

More Stories By Mike Rozlog

Mike Rozlog is with Embarcadero Technologies. In this role, he is focused on ensuring the family of Delphi developer products being created by Embarcadero meets the expectations of developers around the world. Much of his time is dedicated to discussing and explaining the technical and business aspects of Embarcadero’s products and services to analysts and other audiences worldwide. Mike was formerly with CodeGear, a developer tools group that was acquired by Embarcadero in 2008. Previously, he spent more than eight years working for Borland in a number of positions, including a primary role as Chief Technical Architect. A reputed author, Mike has been published numerous times. His latest collaboration is Mastering JBuilder from John Wiley & Sons, Inc.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


IoT & Smart Cities Stories
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.
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...
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...