|By Jesse Randall Warden||
|July 17, 2006 10:15 AM EDT||
Depending on the scope of your project, you may have the opportunity for code reuse. The reasons you might want to do so are two-fold. First, you reduce duplication of efforts. If you have already created a hyperlink enabled CellRenderer for your DataGrid once, why do it again? Second, you create, or build upon, an ever growing utility code base. While it may not be in the "utils" package per se, you'll soon end up with re-usable events, common GUI controls and widgets, and yes even utility classes. Whether by merely being in a different folder means the client doesn't own it is up to you or your sales team.
Duplication Killed on Sight
On the current project I'm on, we re-use a LOT. My eagle-eye boss the architect head-shots any duplication he sees. Thus, we the developers have been trained to quickly identify something we create for re-use if possible and either plan accordingly when building it, or go in search of "spare parts" from existing classes throughout the main code-base for re-use. Our main base consists of 3 company names, each containing at least 3 individual "products". The first question I ask my fellow developers, and they in return, when starting to build something new is, "Has this been done before?" Re-inventing the wheel has no place in a production cycle unless you can clearly point out how the original wheel design was flawed, can be done better, and done so in a reasonable time frame approved by the client.
This also helps ensure I don't code something similar to what has already been done. To the client's point of view, they already paid for a LoginForm...why should they have to pay for a new one when all they want is for it to be green instead of blue?
"Dan, the login form's blue by default, but the mockups I have here are green."
"That's because the View using it sets it to blue; it has a color property that is an inherited style; you can style it yourself, just do color='#yourcolor'."
Suddenly, I spend 10 minutes finding the file and including it, setting its color, registering for its login event, and building a test file to see it in action. This instead of 4 hours doing the same building a green one. Take how much you make per hour, multiply by 4, and then subtract what you make in 15 minutes. That difference is what you just saved the client by "asking a question." I've learned the hard way to ask a lot of questions to the point of being annoying and forcing people to repeat themselves.
The same goes for building more complex things that have to be unique to a point. The most common example which I already alluded to is the CellRenderer. This is a class commonly utilized in Flash and Flex development to customize what's showing in a DataGrid column; each row will render the custom class instead of the default and pass it an item to render. Since every DataGrid on a project is unique, you inevitably end up with a multitude of cellrenderer classes. These classes are, at least for me, notoriously hard to share so you attempt to make them as generic as possible so others can either use them as is, or do the most common thing and extend your base one to customize it to their needs.
This is an important point. The 30 or so lines of code that are required to setup a cellrenderer are suddenly already written for you, and the other developers on your team. This is a great place where inheritance really works and should be exploited. It doesn't stop there; some of the cellrenderers created could be used elsewhere as well. The only challenge is how they're designed from a visual standpoint. Styles can handle a lot, but most designers I have had the pleasure of working with have a knack of making something unique, and unique isn't always re-usable. You can either find a happy compromise with your designers, or respect their artistic integrity and recognize the fact that that they design is truly made specifically for a certain need and shouldn't be made re-usable.
Con of a Component Buffet
The first con to reusing already-built components hits the design side hardest. One of the biggest gripes people have had with any Flash/Flex component is styling and skinning. While CSS styling has come a long way in Flex 2, there are always those times where the artist (in you or beside you) goes, "It's just not right..." Sometimes extending the base component just for styling purposes is the best repose since the base component isn't muddied with application specific styling routines.
The second con which can really come to the forefront in teams is you just don't like the component. Any developer who isn't apprehensive about using a component they didn't write makes me nervous. You trust code you didn't write? Sometimes you don't have a choice or recognize the alternatives are unacceptable. We're all human, and have our coding styles, and even if notation and other rules are enforced on your team, you can still dislike the implementation of something. This should be in the back of your mind when creating code for reuse as well. How will my code be perceived? The base rules such as encapsulation should be followed, but obviously there are other esoteric and styles of implementation that can drastically impact your involvement to ensure others spend very little of theirs getting acclimated to how it works for example.
Sum Greater Than Its Parts
For components that are made up of other components via Composition, I'll ask my fellow developers if the pieces I need are already built. For example, if I'm creating a form, I'll re-use the extended TextInput's we have. For the above CellRenderer, if it has to display a Date, I'll set the labelFunction to utilize the DateUtils class we have which will take a regular Date object and make it look like, "Tue 5/23/2006". I didn't have to write the base class of the CellRenderer and I didn't have to write a class to format dates, I just had to use the class. I've been doing the same thing for a long time without really thinking about it. For example, I take for example I can just "use a DataGrid" and "extend it with a CellRenderer". Macromedia/Adobe spent a lot of time developing one that could be reusable. Naturally, there comes a point where something is coded to business rules or a certain design, and the pragmatist in me knows when to stop trying to overdo it.
Let's turn it up a notch, though. What if you've built a DataGrid that has custom cellrenders, text fields on the bottom to filter it, and is tied to a specific ValueObject it knows how to display, and display well? Can you re-use that? Absolutely! Just because you don't right now doesn't mean you won't later. You should typically design with the intention to do so, but not so much you don't ever actually complete anything beyond a pimped out skeleton. Adamantine ingots may have great potential, but are merely blocks of immobile metal until merged with, say, a regenerative Canadian supersoldier's skeleton. Put what you write to use sooner rather than later.
This is where code reuse really shines. You're near mini-application status component which does a lot is now re-used by your team. If the components within it follow normal styling rules and expose their innards to those who wish to extend it, your golden if certain custom styling needs to be applied. What could possibly be a con about this?
Package structure. Package structure, for those who don't know, is how code is organized into folders. Folders are called "packages" because they have code and other packages in them depending on how deeply you nest your code. Code is placed into class files (.as or .mxml) and placed into folders. The typical naming scheme goes deployment type, company, project, and then regular code. This can take the form of com.adobe.utils.DateUtils where you have a com folder that contains an adobe folder which in turn contains a utils folder which contains the DateUtils.as file. You then import the class or "package path" into your code and the class DateUtils, and your code will know what folder to look in from the import statement.
Some projects do get large enough where you do in fact have more than one project folder. Code re-use is typically thought of through Views of some sort client developers. There is however, no reason you cannot re-use Views across projects. You just reference the package path. The pros are, work effort utilized on a project can be re-used on other projects. Sometimes you can plan for this re-use, and sometimes it's a pleasant surprise.
I suppose, depending on the license, that you could use it for different companies as well, but each license has specific rules on how code is used. Creative Commons is pretty simple; just keep the author's name in the code unless she/he says otherwise. From that point forward, you can modify and re-modify to your heart's content with no license fee. Others are a lot weirder. Some companies require you supply them source code. Some don't even know what source code is. Still others own everything you write while in their presence, thus preventing you from using any of your own re-usable stuff. A common tactic I've seen is to have your company's name next to the client's company name. All common views and utility classes are put in yours, and the custom developed work is put in the client's package path.
That last point is another important point. Code by residing in your company's folder its very nature has a very special, and important place; it's created for re-use. On the current project, or projects, it's re-used in many places. While all uses of it are immediately improved upon once you improve the base component, thus improving the whole project, this can have unforeseen consequences as well.
For example, you build your own List control to render extremely unique rows that animate instead of simply refreshing. In practice, you see that it is extremely slow, especially when multiple instances of it are used. You go in and re-factor it, finding many places in the code you can speed up. Suddenly, the entire app speeds up where those components are used.
One of these changes was to expose a method for updating one specific item versus all of them when a piece of data changes. This is accomplished via a new method. That's a bad thing. Suddenly all the classes that use it now have to update themselves just to access one of the new optimizations.
Touching a point I brought up earlier, sharing views between projects - the problem with that is that, if you change a view in one project, you've just affected the other one. Code that was seemingly "working" you just broke, and you didn't know it because you were never compiling, nor even involved in the other project. The important point here is: if you are going to identify something as re-usable, make it so, and put it into a global package such as your company's folder, or another aptly named common folder. Developers who go into the code in those packages know full well the ramifications of what their changes could do, for good or ill.
When I got my first apartment, I had one screwdriver and one small Phillips head to my name. Now that I own a house, I have a small utility closet full of tools. I'm sure by the time I'm eighty, I'll need a tool shed to hold them all. The same can be said about your "common" code base: you'll find over time that it'll grow into an extremely useful and portable set of code. Remember, you don't have to write it all yourself, nor does your team. There's a lot of free code on the Net that you can test yourself, and then incorporate. This'll save you from having to create a hammer before you can use said hammer every project; going in, you'll be equipped to the teeth, and you'll come out with more ammo than you started with.
The greater the size of the project, and/or the more frequenct the projects,the more important reusing code becomes. Making the most of a developer's time spent coding is done this way, and allows many others to benefit from that work for months, even years to come. For example, I've been using the same preloader in Flash for 3 years, written in ActionScript 1 in Flash 5. I still customize the colors, though, every time.
With reuse comes great responsibility. If you are designating something as reusable, it can be quite frightening to realize that a lot of others are suddenly depending on this pinnacle piece of code. That is a risk worth taking, and a strength you should prey upon. As long as you recognize the dependencies, and reduce coupling, you'll start gaining a lot more efficiency from the time you and your team spend coding.
When I first learned about reuse, I could never get it to work in practice. I either ran out of time and copy-pasted or my original design was perceived to me as being "flawed" even though it worked perfectly fine. I was just being unreasonable. Keep it simple, and you'll do fine.
|SYS-CON India News Desk 07/17/06 10:44:08 AM EDT|
Depending on the scope of your project, you may have the opportunity for code reuse. The reasons you might want to do so are two-fold. First, you reduce duplication of efforts. If you have already created a hyperlink enabled CellRenderer for your DataGrid once, why do it again? Second, you create, or build upon, an ever growing utility code base. While it may not be in the 'utils' package per se, you'll soon end up with re-usable events, common GUI controls and widgets, and yes even utility classes. Whether by merely being in a different folder means the client doesn't own it is up to you or your sales team.
"ReadyTalk is an audio and web video conferencing provider. We've really come to embrace WebRTC as the platform for our future of technology," explained Dan Cunningham, CTO of ReadyTalk, in this SYS-CON.tv interview at WebRTC Summit at 19th Cloud Expo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Dec. 6, 2016 10:15 AM EST Reads: 520
Financial Technology has become a topic of intense interest throughout the cloud developer and enterprise IT communities. Accordingly, attendees at the upcoming 20th Cloud Expo at the Javits Center in New York, June 6-8, 2017, will find fresh new content in a new track called FinTech.
Dec. 6, 2016 09:15 AM EST Reads: 2,141
Whether your IoT service is connecting cars, homes, appliances, wearable, cameras or other devices, one question hangs in the balance – how do you actually make money from this service? The ability to turn your IoT service into profit requires the ability to create a monetization strategy that is flexible, scalable and working for you in real-time. It must be a transparent, smoothly implemented strategy that all stakeholders – from customers to the board – will be able to understand and comprehe...
Dec. 6, 2016 09:00 AM EST Reads: 3,963
In his keynote at 18th Cloud Expo, Andrew Keys, Co-Founder of ConsenSys Enterprise, provided an overview of the evolution of the Internet and the Database and the future of their combination – the Blockchain. Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life sett...
Dec. 6, 2016 08:45 AM EST Reads: 7,124
Successful digital transformation requires new organizational competencies and capabilities. Research tells us that the biggest impediment to successful transformation is human; consequently, the biggest enabler is a properly skilled and empowered workforce. In the digital age, new individual and collective competencies are required. In his session at 19th Cloud Expo, Bob Newhouse, CEO and founder of Agilitiv, drew together recent research and lessons learned from emerging and established compa...
Dec. 6, 2016 08:30 AM EST Reads: 879
The WebRTC Summit New York, to be held June 6-8, 2017, at the Javits Center in New York City, NY, announces that its Call for Papers is now open. Topics include all aspects of improving IT delivery by eliminating waste through automated business models leveraging cloud technologies. WebRTC Summit is co-located with 20th International Cloud Expo and @ThingsExpo. WebRTC is the future of browser-to-browser communications, and continues to make inroads into the traditional, difficult, plug-in web co...
Dec. 6, 2016 08:30 AM EST Reads: 1,335
WebRTC is the future of browser-to-browser communications, and continues to make inroads into the traditional, difficult, plug-in web communications world. The 6th WebRTC Summit continues our tradition of delivering the latest and greatest presentations within the world of WebRTC. Topics include voice calling, video chat, P2P file sharing, and use cases that have already leveraged the power and convenience of WebRTC.
Dec. 6, 2016 08:15 AM EST Reads: 1,671
20th Cloud Expo, taking place June 6-8, 2017, at the Javits Center in New York City, NY, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy.
Dec. 6, 2016 07:15 AM EST Reads: 1,837
Extracting business value from Internet of Things (IoT) data doesn’t happen overnight. There are several requirements that must be satisfied, including IoT device enablement, data analysis, real-time detection of complex events and automated orchestration of actions. Unfortunately, too many companies fall short in achieving their business goals by implementing incomplete solutions or not focusing on tangible use cases. In his general session at @ThingsExpo, Dave McCarthy, Director of Products...
Dec. 6, 2016 07:15 AM EST Reads: 740
Businesses and business units of all sizes can benefit from cloud computing, but many don't want the cost, performance and security concerns of public cloud nor the complexity of building their own private clouds. Today, some cloud vendors are using artificial intelligence (AI) to simplify cloud deployment and management. In his session at 20th Cloud Expo, Ajay Gulati, Co-founder and CEO of ZeroStack, will discuss how AI can simplify cloud operations. He will cover the following topics: why clou...
Dec. 6, 2016 07:00 AM EST Reads: 836
The Internet of Things (IoT) promises to simplify and streamline our lives by automating routine tasks that distract us from our goals. This promise is based on the ubiquitous deployment of smart, connected devices that link everything from industrial control systems to automobiles to refrigerators. Unfortunately, comparatively few of the devices currently deployed have been developed with an eye toward security, and as the DDoS attacks of late October 2016 have demonstrated, this oversight can ...
Dec. 6, 2016 06:30 AM EST Reads: 1,131
DevOps is being widely accepted (if not fully adopted) as essential in enterprise IT. But as Enterprise DevOps gains maturity, expands scope, and increases velocity, the need for data-driven decisions across teams becomes more acute. DevOps teams in any modern business must wrangle the ‘digital exhaust’ from the delivery toolchain, "pervasive" and "cognitive" computing, APIs and services, mobile devices and applications, the Internet of Things, and now even blockchain. In this power panel at @...
Dec. 6, 2016 06:00 AM EST Reads: 524
Internet-of-Things discussions can end up either going down the consumer gadget rabbit hole or focused on the sort of data logging that industrial manufacturers have been doing forever. However, in fact, companies today are already using IoT data both to optimize their operational technology and to improve the experience of customer interactions in novel ways. In his session at @ThingsExpo, Gordon Haff, Red Hat Technology Evangelist, will share examples from a wide range of industries – includin...
Dec. 6, 2016 05:00 AM EST Reads: 1,656
"We build IoT infrastructure products - when you have to integrate different devices, different systems and cloud you have to build an application to do that but we eliminate the need to build an application. Our products can integrate any device, any system, any cloud regardless of protocol," explained Peter Jung, Chief Product Officer at Pulzze Systems, in this SYS-CON.tv interview at @ThingsExpo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Dec. 6, 2016 04:45 AM EST Reads: 1,002
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place June 6-8, 2017, at the Javits Center in New York City, New York, is co-located with 20th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry p...
Dec. 6, 2016 04:30 AM EST Reads: 1,935
"We're a cybersecurity firm that specializes in engineering security solutions both at the software and hardware level. Security cannot be an after-the-fact afterthought, which is what it's become," stated Richard Blech, Chief Executive Officer at Secure Channels, in this SYS-CON.tv interview at @ThingsExpo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Dec. 6, 2016 12:45 AM EST Reads: 870
According to Forrester Research, every business will become either a digital predator or digital prey by 2020. To avoid demise, organizations must rapidly create new sources of value in their end-to-end customer experiences. True digital predators also must break down information and process silos and extend digital transformation initiatives to empower employees with the digital resources needed to win, serve, and retain customers.
Dec. 6, 2016 12:30 AM EST Reads: 1,201
The IoT is changing the way enterprises conduct business. In his session at @ThingsExpo, Eric Hoffman, Vice President at EastBanc Technologies, discussed how businesses can gain an edge over competitors by empowering consumers to take control through IoT. He cited examples such as a Washington, D.C.-based sports club that leveraged IoT and the cloud to develop a comprehensive booking system. He also highlighted how IoT can revitalize and restore outdated business models, making them profitable ...
Dec. 6, 2016 12:30 AM EST Reads: 4,593
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Dec. 6, 2016 12:00 AM EST Reads: 919
"Once customers get a year into their IoT deployments, they start to realize that they may have been shortsighted in the ways they built out their deployment and the key thing I see a lot of people looking at is - how can I take equipment data, pull it back in an IoT solution and show it in a dashboard," stated Dave McCarthy, Director of Products at Bsquare Corporation, in this SYS-CON.tv interview at @ThingsExpo, held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
Dec. 5, 2016 10:30 PM EST Reads: 1,072