Welcome!

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

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 deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by ...
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Poor data quality and analytics drive down business value. In fact, Gartner estimated that the average financial impact of poor data quality on organizations is $9.7 million per year. But bad data is much more than a cost center. By eroding trust in information, analytics and the business decisions based on these, it is a serious impediment to digital transformation.
Digital Transformation: Preparing Cloud & IoT Security for the Age of Artificial Intelligence. As automation and artificial intelligence (AI) power solution development and delivery, many businesses need to build backend cloud capabilities. Well-poised organizations, marketing smart devices with AI and BlockChain capabilities prepare to refine compliance and regulatory capabilities in 2018. Volumes of health, financial, technical and privacy data, along with tightening compliance requirements by...
Predicting the future has never been more challenging - not because of the lack of data but because of the flood of ungoverned and risk laden information. Microsoft states that 2.5 exabytes of data are created every day. Expectations and reliance on data are being pushed to the limits, as demands around hybrid options continue to grow.
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 ...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.
As IoT continues to increase momentum, so does the associated risk. Secure Device Lifecycle Management (DLM) is ranked as one of the most important technology areas of IoT. Driving this trend is the realization that secure support for IoT devices provides companies the ability to deliver high-quality, reliable, secure offerings faster, create new revenue streams, and reduce support costs, all while building a competitive advantage in their markets. In this session, we will use customer use cases...