Tue, Dec
5 New Articles

TechTip: 7 Ways to Be a Better Programmer

  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Sure, you're good. But you could be better.


1. Understand the requirements. Users and business decision-makers don't talk (or think) the same way that programmers do. Before you start a new programming project, make sure you have defined, in a quantitative way, the hallmarks of success for the project—as determined by the users and decision-makers. What you're after here are solid metrics that can later be used to show that the program does what the users want it to do and provide the proof that the project is complete. In enterprise environments, they call these hallmarks a "statement of work." I'm not suggesting that for your internal, in-house work you craft a highly formal statement of work, but do get things written down and formally agreed upon. This saves a lot of downstream grief!

2. Review frequently. Back in the old days, we used to collect user requirements, disappear into a dark tunnel, and emerge when the program was done. We've since learned that this practice leads to incorrect or incomplete deliverables and unhappy users. At the very least, have regularly scheduled (short!) meetings where you show your progress and make sure that everything is on track. These meetings prove to all that you are on the right track—or, if you aren't, provide the chance to correct things before you've spent many weeks continuing to do the wrong thing. These meetings are also your chance to update delivery schedules and reset expectations. This transparency keeps everyone updated and happy. If your project is large enough, consider not only reviewing frequently, but also delivering frequently. The earlier you can get fingers pounding data into your app, the earlier you can get truly meaningful feedback.

3. Keep it truly simple. Writing code is easy. Reading code is hard. Think very carefully about your algorithms, your abstractions, your program composition, and even your naming conventions. The simpler you keep things, especially early in the project, the easier it's going to be to maintain and enhance later. In the effort to keep things simple, don't make the mistake of thinking that using tons of comments to explain obtuse code makes that code easy to understand. Tons of comments are a clear indication that the code isn't simple enough! Maybe your naming conventions aren't working; maybe you haven't decomposed the problem appropriately, or maybe your approach is just wrong! Don't try to comment your way to simplicity—rewrite and refactor convoluted code!

4. Code consistently. I think a strong argument can be made that while any one business needs many programs, perhaps hundreds or even thousands of them, that business only needs a fraction of that number in types of programs. Don't break new ground with every program you write. Categorize the types of programs you write and keep programs within any one category very consistent. Use the same routine and field naming—don't make the next coder need to start all over again each time he or she needs to read your code. Consistent naming and a similar approach to solving each type of problem substantially reduces the energy required to understand the program. The CL naming scheme of i5/OS (nee OS/400) is a superb example of great consistently. With about 80 verbs, IBM covers pretty much all the action any one programming task needs to do (and I'd bet you that of those 80 or so commands, 25% of them covers most tasks). Once you learn the CL naming scheme, you have to go out of your way to not be able to guess what a given command is doing. Don't reinvent verbs, nouns, and other naming conventions. Give something a name once and reuse it again and again!

5. Learn a new language. I recently acquired a hand-me-down Mac PowerBook Pro. It has rapidly become my latest hobby programming passion. I am learning PHP and UNIX—which is a pretty strange land for a long-time user of statically compiled Windows or IBM i-based languages. Over the years, I've learned, and used, many languages. Each time I learn a new language, the use of my core languages improved. Virtually every language has at least one core little piece (and sometimes major chunks!) that provides a new and better way to do something. Applying those new concepts and approaches in my everyday languages has made me a better programmer.

6. Get a second opinion. Did you ever write a chunk of code that you thought was the most amazing, greatest code ever? Then have other programmers glance at it and wince? And, even worse than that, when you look at the code through their eyes, you instantly see exactly what they are wincing at? That beautiful code just became, without changing a line, what-was-I-thinking code! In the old days, it was hard for one-person shops to share code. With today's social Internet, you can put your code in a blog entry or post it to a centralized code repository (https://github.com or https://bitbucket.org, for example) and ask others for critiques. The Internet has plenty of coders willing to do that!

7. Improve your fingertips. Having spent tons of classroom time with lots of students for the last 14 years or so, one of my general observations is that many programmers aren't as good at typing as they should be. I have had a surprising number of two-fingered hunt-and-peckers in my classes. If your typing skills aren't very good, there are tons of online typing tutor sites available (http://play.typeracer.com/ is especially addictive). Along with improving your typing skills, learn all that you can about your editor—and learn how to use it without a mouse! For many of us, that means learning the editor in Visual Studio. Take the time to learn its keyboard shortcuts and some of its easy-to-miss features. I've read about coding teams who have mouse-free Fridays. Everyone puts their mouse away all day on Friday—for the expressed purpose of learning how to navigate their tools with just their fingertips. I don't know that I could go mouseless for an entire day, but I often do make a conscious effort to minimize my mouse use. I'll get arguments here, but for my money, better typists make better programmers!


Roger Pence is ASNA's Product Evangelist. Roger has been in the IBM i midrange community for so long that Elvis was alive when he started. He has been with ASNA since 2000. Prior to joining ASNA, Roger was a technical editor for NEWS/400 and the author of the 400/Group's AS/400 and Windows newsletter.



Support MC Press Online

$0.00 Raised:

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: