Welcome!

Containers Expo Blog Authors: Yeshim Deniz, Pat Romanski, Liz McMillan, Zakia Bouachraoui, Elizabeth White

Related Topics: Containers Expo Blog, Microservices Expo, Agile Computing, @CloudExpo, @DXWorldExpo, SDN Journal

Containers Expo Blog: Blog Feed Post

Design Docs, Code Comments, and . . .

We need to treat our projects more like research projects, and keep a “notebook” somewhere

When first you build a bookshelf from raw wood, on your own, you learn a lot. While the first may be the only one you ever want to build, by the time you’re done, you know you could have done X, Y, or Z better. This is true of so many crafts. You get better by doing, in large part because you learn new tricks, figure out how to make useful tools, get more efficient because you purchased more useful tools… I know that while I would never consider myself an artist, painting models and miniatures has made me progress to where some have called me one. (Picture is a battery of M7 “Priest” artillery I painted up – models by Brittania miniatures)

The thing is, when it’s a hobby, or you’re a one man shop, or the job is not particularly taxing, this knowledge is easy to keep around. You have that jig you built to make cool shelf angles hanging on the wall, or the box of perfect fasteners is still on the shelf. The glue or stain you settled on is what you kept when the last shelf was built, etc.

But when the job is complex, and the problems increasingly so, it is not so simple. When the tools used to achieve a solid solution – the things used to learn and used to improve your productivity – are on a disk somewhere in the org, things get a little more complex.

But not irretrievably. You just need to pay a little more attention.

When you’re developing an app or configuring a network, there is the design, showing what is to be done, the code comments describing what was done, and the finished product for use by the enterprise. You have accumulated knowledge, which is good for you and the organization, but you also did some other things that normally fall through the cracks. That tool you cobbled together to check the validity of file formats, or the browser plug-in that helped you resolve network issues, or the DNS tool you downloaded that helped you get redirection correct… These things are important. Just as important as the tool I discovered to make the mud up the side of that vehicle. More important, because in a hobby I have time to mess around and reinvent the wheel if I must. in the enterprise, I’ve never met the IT staffer that went “you know, I did this seven months ago, I think I’ll just go figure out how to do it all over again, I’ve got the free time”. Never.

So what you need to do is keep track of these things. Put them in version control, store them on a special share for just such tools under a heading/directory that associates the tool with the project it helped with. Even silly little things. And put them in a word document if they’re things like links to a web page. Sure the page may be gone when next the word doc is opened, but that’s true of bookmarks in your browser too, and your word doc is likely to have greater longevity. This is for you – because in many orgs if you created it, it’s your problem for eternity – but it is also for the organization, because eventually it will not be your problem, and it will save the next poor person from figuring out how to do the same things. I’m not talking about tools like lint, if you don’t have a corporate standard to use that type of thing though, you could include it. I’m talking about that library you found that does what you wanted, but was a nightmare to configure. So document it. While you’re celebrating that you got it going. Save someone else the headache. Or yourself, should something horrendous happen and you have to configure it from scratch again.

Devops has helped in this regard with networking, by stressing repeatable processes, but developers are asked to do something different almost every app. Patterns are great, but it’s rarely patterns that trip us up, it’s some weird exception case that only occurs in this language/environment/requirements document. Much more difficult to turn into repeatable, when if it was simply repeatable you’d have found source or used a library to achieve it quickly.

What we do is more science than art. We need to treat our projects more like research projects, and keep a “notebook”. somewhere. Those tools, random observations, difficult to discern but very profound solutions… All of that could be part of the intellectual property of the app/tool/network in question, making everyone more productive. But document it in English (or the tongue spoken by the bulk of your coworkers, for my international friends), not in your “from here I understand a ton, I’ll write about the bit I just learned”.

Sometime soon – hopefully next week – I will be writing up my solution (and recommended more generic solution) to the several issues found in Android SSL. By writing about it out here, I am documenting what I went through, and have to write about it in plain English. You need to do the same (but normally internally only, so you don’t have to explain the entire environment/problem-set), so that five years from now, the local Intern can figure out how to work on your app/network. Or you can remember what the heck you did to make it work. ;-)

You’ll thank yourself. Most good developers I know have forgotten more coding projects than they remember, and this might provide the clues to get back up to speed when it circles around and you have to work on the solution again. I assume network admins have the same problem. Your employer will thank you, because you (and potentially anyone else asked to work on it) will be more productive, just like using that jig over again is more productive. It’s not necessarily part of the solution, but it makes building the solution far easier.

Meanwhile, keep building the next generation of apps and networks, we’re expecting lots, and even though complaints are louder than compliments, no one can argue that developers and network admins as a whole haven’t responded in astounding ways over the last 30 years. Unless you prefer disconnected mainframes I suppose...

Read the original blog entry...

More Stories By Don MacVittie

Don MacVittie is founder of Ingrained Technology, A technical advocacy and software development consultancy. He has experience in application development, architecture, infrastructure, technical writing,DevOps, and IT management. MacVittie holds a B.S. in Computer Science from Northern Michigan University, and an M.S. in Computer Science from Nova Southeastern University.

IoT & Smart Cities Stories
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
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...
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 settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
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...
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...
Whenever a new technology hits the high points of hype, everyone starts talking about it like it will solve all their business problems. Blockchain is one of those technologies. According to Gartner's latest report on the hype cycle of emerging technologies, blockchain has just passed the peak of their hype cycle curve. If you read the news articles about it, one would think it has taken over the technology world. No disruptive technology is without its challenges and potential impediments t...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
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...