Virtualization Authors: Elizabeth White, Carmen Gonzalez, Victoria Livschitz, Pat Romanski, Lori MacVittie

Related Topics: Java, AJAX & REA

Java: Article

How to Go from Geek to Manager

You've got the job now what do you do?

You're six-feet, 190 pounds and can type System.out.println faster than most people can say AJAX. You're a person who dreams about the Milwaukee Brewers winning the World Series and the correct data structure to be used when talking about a baseball player. You've spent five years of your life writing Java code and leading Java development teams. You consider yourself an expert in Swing, Struts, XML, and XSL-FO and feel comfortable talking about any other buzzword in the Java world such as JSF, Portal, and AJAX. You've had experience as development lead on a team with anywhere from three to seven people where Java applications were rolled into production well within the scheduled deadline. Now you have received a management position on an internal Java development team. Where do you start? What things do you look at from day one? What's your role going to be as a manager? What would you like to see happen within your team? Do you want to keep your technical skills? How do you rate your employees at the end of the year?

These are just some of the question's that you'll have to answer.

Fortunately, I'm the Brewers fan who just got a new first-line management position. The team that I'm managing consists of 18 employees with skillsets ranging from Java Swing development to J2EE Web development. The main point of our existence is to create, support, fix and build tools inside IBM for a number of platforms. A number of small tools have already been developed that use Swing technology for the front-end. The small tools end up communicating with DB2 systems on the back-end and start a number of native back-end processes depending on the back-end servers' platform. The team has also created a Web application that lets internal developers create a fix pack of a particular product. These are examples of just a couple of the many Java tools that my department is responsible for.

Now back to the questions at hand. Where does a manager start when taking over a Java development team? These are just a couple of the things that concerned me when coming in as manager of a Java development team.

Who's Doing What?
Every manager has to understand what the main responsibility of the team is. Once that's understood then the next question to answer is, who is working on achieving that goal. What positions have been defined in the department to carry out the team's primary responsibility? For instance, do you have developers working on a single application from the beginning to end or do you have each software development process task broken down among different employees. Once you understand the tasks that everyone is working on, does it matter how they're done? For example, the team that I'm managing has application owners who are responsible for the entire development process lifecycle for a particular application. An application owner would have to gather the new requirements that come in, create a design that fits into the existing application design, develop, unit test, and do the production test. And if an external customer discovers a problem with the tool it's their responsibility to fix it.

Some things I've heard from the group is that testing all our small tools is quite expensive. Every small tool is dependent on each other. New functionality added to one of them may have an impact on another, thus causing all application owners to test their code before it's released.

From a resource perspective this really scares me. You wouldn't like your most experienced developers spending a lot of time on testing. Some would disagree with me on this and say that this person has the application domain experience and should be involved in production testing. However, I feel that testing something like this should be documented in a test plan and tested by a separate group. Test cases could be written by this separate group cross-referencing the requirements. That way a different set of eyes could manually test the application outside of the application owners who should only do unit testing.

Is There a Development Process?
As the manager of any software department I would hope so. Hardcore software developers hate processes. I know this from past experience. When I was given an assignment, I wanted to complete it as fast as I could by writing code. If you wanted to know my progress all you had to do was ask. I felt the information in my head was sufficient. However, this kind of thinking makes things very hard when working on a team that's larger than one person. Information has to be communicated from one person to another. The memory of what someone said lasts only so long. Having documentation helps remind an employee of what's required. It helps for reviews and lets an employee hand his work off if something happens and he's pulled from the project.

Without a development process it's even harder to rate employee performance. Who is your best designer? Who is your best coder? By defining a development process, the strengths and weaknesses of each employee can be measured at particular stages of the development process. Running a tool suite that does metrics throughout a development process can be used to measure performance. Tracking and monitoring this kind of information will also help you understand the task force needed for a particular project. For instance, if a manager knows how long it took for an application to be finished with a particular number of employees, it makes it easier to estimate how long it will take those employees on the next project.

The team that I've inherited has an ad hoc development process. There's no standardized format of what's required in each development phase. For instance, Team A could have a requirements document that looks different from Team B's requirements document. Does something like this need to be standardized throughout the development process? Some would argue that as long as there's documentation for each development stage it shouldn't matter. They'd also argue that the format of each document should be up to the project lead. However, if you have employees switching from one team to another, this may become an issue. It may take an employee some time to understand a format that's different from what they used in a prior project. From a management perspective it's always nice to standardize the format in a tool that can run some kind of metrics. For example, if a requirements document is submitted with a tool, metrics could be run on how good the document actually is. When a review is held for the requirements document, the number of problems found in the requirements document could be traced and analyzed by a manager. This could be a perfect way to isolate the employees who have strong requirements-gathering skills. As a manager, I feel it's a priority to make sure our development team has a standardized format for all development process milestones.

Are Swing Applications Old?
First of all why would a manager even care about Swing applications? As long as the development lead knows when to change from Swing to a more Web-centric application, why should a manager even care? The reason I ask this is that you have to remember I come from a technical background. I feel that if a strategic decision has to be made on which technology we should use, I'd like to be part of it. If I were the type of manager who thought Swing was something for my two-year-old son then of course you wouldn't want me in the discussion at all.

We have a number of Swing-based applications that are used by our internal customers and by administration. The Swing-based applications follow a fix process required by every internal developer who wants to create a fix. This fix process is very complicated and requires an internal developer to run a number of the Swing applications so a fix can be created, tested and deployed to external customers. There have been a number of developers who have implemented additional functionality within the Swing applications. Over time, this has made some of the code hard to read. There is logic that is duplicated because a developer was not aware of particular methods that already existed. There are also a number of classes that were implemented that do not fit within the old design because of the changing functionality. Instead of enhancing the old design, now a new design and old design exist within the application. This, of course, has nothing to do with the debate over whether Swing-based applications are old but does create additional work if you were to migrate the applications from Swing to a Web-based tool. Time would have to be spent to understand the differences between the old design and new design. Eventually, a design bringing both of them together would have to be created.

More Stories By Benjamin Garbers

Ben Garbers is currently a 1st line manager at IBM where the department he
manages creates and maintains Java standalone applications and dynamic Java
web applications run on Websphere. Before his management position he was
the lead developer on a number of teams that developed standalone Java

Comments (4)

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.

@ThingsExpo Stories
The 3rd International Internet of @ThingsExpo, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that its Call for Papers is now open. The Internet of Things (IoT) is the biggest idea since the creation of the Worldwide Web more than 20 years ago.
Cultural, regulatory, environmental, political and economic (CREPE) conditions over the past decade are creating cross-industry solution spaces that require processes and technologies from both the Internet of Things (IoT), and Data Management and Analytics (DMA). These solution spaces are evolving into Sensor Analytics Ecosystems (SAE) that represent significant new opportunities for organizations of all types. Public Utilities throughout the world, providing electricity, natural gas and water, are pursuing SmartGrid initiatives that represent one of the more mature examples of SAE. We have s...
The security devil is always in the details of the attack: the ones you've endured, the ones you prepare yourself to fend off, and the ones that, you fear, will catch you completely unaware and defenseless. The Internet of Things (IoT) is nothing if not an endless proliferation of details. It's the vision of a world in which continuous Internet connectivity and addressability is embedded into a growing range of human artifacts, into the natural world, and even into our smartphones, appliances, and physical persons. In the IoT vision, every new "thing" - sensor, actuator, data source, data con...
The Internet of Things is tied together with a thin strand that is known as time. Coincidentally, at the core of nearly all data analytics is a timestamp. When working with time series data there are a few core principles that everyone should consider, especially across datasets where time is the common boundary. In his session at Internet of @ThingsExpo, Jim Scott, Director of Enterprise Strategy & Architecture at MapR Technologies, discussed single-value, geo-spatial, and log time series data. By focusing on enterprise applications and the data center, he will use OpenTSDB as an example t...
How do APIs and IoT relate? The answer is not as simple as merely adding an API on top of a dumb device, but rather about understanding the architectural patterns for implementing an IoT fabric. There are typically two or three trends: Exposing the device to a management framework Exposing that management framework to a business centric logic Exposing that business layer and data to end users. This last trend is the IoT stack, which involves a new shift in the separation of what stuff happens, where data lives and where the interface lies. For instance, it's a mix of architectural styles ...
An entirely new security model is needed for the Internet of Things, or is it? Can we save some old and tested controls for this new and different environment? In his session at @ThingsExpo, New York's at the Javits Center, Davi Ottenheimer, EMC Senior Director of Trust, reviewed hands-on lessons with IoT devices and reveal a new risk balance you might not expect. Davi Ottenheimer, EMC Senior Director of Trust, has more than nineteen years' experience managing global security operations and assessments, including a decade of leading incident response and digital forensics. He is co-author of t...
The Internet of Things will greatly expand the opportunities for data collection and new business models driven off of that data. In her session at @ThingsExpo, Esmeralda Swartz, CMO of MetraTech, discussed how for this to be effective you not only need to have infrastructure and operational models capable of utilizing this new phenomenon, but increasingly service providers will need to convince a skeptical public to participate. Get ready to show them the money!
The Internet of Things will put IT to its ultimate test by creating infinite new opportunities to digitize products and services, generate and analyze new data to improve customer satisfaction, and discover new ways to gain a competitive advantage across nearly every industry. In order to help corporate business units to capitalize on the rapidly evolving IoT opportunities, IT must stand up to a new set of challenges. In his session at @ThingsExpo, Jeff Kaplan, Managing Director of THINKstrategies, will examine why IT must finally fulfill its role in support of its SBUs or face a new round of...
One of the biggest challenges when developing connected devices is identifying user value and delivering it through successful user experiences. In his session at Internet of @ThingsExpo, Mike Kuniavsky, Principal Scientist, Innovation Services at PARC, described an IoT-specific approach to user experience design that combines approaches from interaction design, industrial design and service design to create experiences that go beyond simple connected gadgets to create lasting, multi-device experiences grounded in people's real needs and desires.
Enthusiasm for the Internet of Things has reached an all-time high. In 2013 alone, venture capitalists spent more than $1 billion dollars investing in the IoT space. With "smart" appliances and devices, IoT covers wearable smart devices, cloud services to hardware companies. Nest, a Google company, detects temperatures inside homes and automatically adjusts it by tracking its user's habit. These technologies are quickly developing and with it come challenges such as bridging infrastructure gaps, abiding by privacy concerns and making the concept a reality. These challenges can't be addressed w...
The Domain Name Service (DNS) is one of the most important components in networking infrastructure, enabling users and services to access applications by translating URLs (names) into IP addresses (numbers). Because every icon and URL and all embedded content on a website requires a DNS lookup loading complex sites necessitates hundreds of DNS queries. In addition, as more internet-enabled ‘Things' get connected, people will rely on DNS to name and find their fridges, toasters and toilets. According to a recent IDG Research Services Survey this rate of traffic will only grow. What's driving t...
Scott Jenson leads a project called The Physical Web within the Chrome team at Google. Project members are working to take the scalability and openness of the web and use it to talk to the exponentially exploding range of smart devices. Nearly every company today working on the IoT comes up with the same basic solution: use my server and you'll be fine. But if we really believe there will be trillions of these devices, that just can't scale. We need a system that is open a scalable and by using the URL as a basic building block, we open this up and get the same resilience that the web enjoys.
Connected devices and the Internet of Things are getting significant momentum in 2014. In his session at Internet of @ThingsExpo, Jim Hunter, Chief Scientist & Technology Evangelist at Greenwave Systems, examined three key elements that together will drive mass adoption of the IoT before the end of 2015. The first element is the recent advent of robust open source protocols (like AllJoyn and WebRTC) that facilitate M2M communication. The second is broad availability of flexible, cost-effective storage designed to handle the massive surge in back-end data in a world where timely analytics is e...
We are reaching the end of the beginning with WebRTC, and real systems using this technology have begun to appear. One challenge that faces every WebRTC deployment (in some form or another) is identity management. For example, if you have an existing service – possibly built on a variety of different PaaS/SaaS offerings – and you want to add real-time communications you are faced with a challenge relating to user management, authentication, authorization, and validation. Service providers will want to use their existing identities, but these will have credentials already that are (hopefully) i...
"Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this SYS-CON.tv interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
P2P RTC will impact the landscape of communications, shifting from traditional telephony style communications models to OTT (Over-The-Top) cloud assisted & PaaS (Platform as a Service) communication services. The P2P shift will impact many areas of our lives, from mobile communication, human interactive web services, RTC and telephony infrastructure, user federation, security and privacy implications, business costs, and scalability. In his session at @ThingsExpo, Robin Raymond, Chief Architect at Hookflash, will walk through the shifting landscape of traditional telephone and voice services ...
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at Internet of @ThingsExpo, James Kirkland, Chief Architect for the Internet of Things and Intelligent Systems at Red Hat, described how to revolutioniz...
Bit6 today issued a challenge to the technology community implementing Web Real Time Communication (WebRTC). To leap beyond WebRTC’s significant limitations and fully leverage its underlying value to accelerate innovation, application developers need to consider the entire communications ecosystem.
The definition of IoT is not new, in fact it’s been around for over a decade. What has changed is the public's awareness that the technology we use on a daily basis has caught up on the vision of an always on, always connected world. If you look into the details of what comprises the IoT, you’ll see that it includes everything from cloud computing, Big Data analytics, “Things,” Web communication, applications, network, storage, etc. It is essentially including everything connected online from hardware to software, or as we like to say, it’s an Internet of many different things. The difference ...
Cloud Expo 2014 TV commercials will feature @ThingsExpo, which was launched in June, 2014 at New York City's Javits Center as the largest 'Internet of Things' event in the world.