Over a million developers have joined DZone.

Translating Code Smells in Server Smells

DZone's Guide to

Translating Code Smells in Server Smells

· DevOps Zone
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

At xpdays Benelux 2009, I attended an interesting session called 'Developing a Sense of Smells' by Kevin RutherFord and Lindsay McEwan.

The exercise we did went as follows: suppose you are asked to do some work on code you never saw before. How would you assess this, go about estimating the effort and explaining that effort to justify the price/number of days. The first round resulted in terms like 'look for design patterns', 'readibility of the code', ...

Then they explained code smells patterns: f.i. a greedy function: one function that does way to much making it difficult to change, hidden secret: internal knowledge such as the real interpretations of a CSV file data format that can not be deduced by looking at the code. The code smells made it easier to express the problems.

The devops in me,thinks that this can be translated to the sysadmin world. Here are some of the 'smells' I've come up.


Private Playground

The sysadmin uses the system as his toy playground, doesn't clean up.

  • /tmp & /var/tmp full of old install files
  • / full of files

Gready Server

One server that does every function

  • combined mail and web and dns and fileshares
  • all users on the same system

Root is the cause of all evil

  • last show login all root
  • no sudo is activated
  • no sshd keys for logins
  • nfs share/root?
  • Chmod 777
  • most processes run as root

Cranky Crutches

Things that are needed to keep the system alive when failed

  • /etc/ start but no stop scripts
  • kill /stop/start in cron jobs

Nobody lives here anymore

Mainly indicate not much maintenance is done any more

  • Last update is a long time ago
  • Older kernel versions
  • last login was more then x days ago
  • olders reboot is a long time ago

Complexity Conspiracy

Loadbalancers, Cluster software, Dependencies

More is Less

  • All packages installed
  • All services running
  • All ports are open

This is just the beginning, so if you have your own ideas/names, just leave a comment.

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.


Published at DZone with permission of Patrick Debois, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}