DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Code Inventory and Tracking Releases

Daniel Ackerson user avatar by
Daniel Ackerson
·
Oct. 14, 12 · Interview
Like (0)
Save
Tweet
Share
8.96K Views

Join the DZone community and get the full member experience.

Join For Free
you know by now that code inventory is something of an obsession with me. like it or not, most of us, whether developers or sysadmins, work in a service industry. it’s fast and furious, and we don’t have time to build features that nobody wants. with sufficient test coverage, there’s no code that can’t be released within a day of pushing to the repository.

lettuce seeds by photofarmer
creative commons license dwight sipler

a couple of years ago, i showed you how to visualize small batch sizes with git by plotting day-to-day the amount of changed source code lines that hadn’t yet been released to production. while this graph gave immediate feedback about the “drift” of development from operations (live), it’s not something easily digested by upper management. what do these guys really care about? it’s all about the releases silly!

commits are “units of work”

easily understood and very simple to calculate.

code inventory by release and git commits
tracking number of code lines changed can easily be misleading with a copy/pasting, package refactoring or adding a new javascript library.

what was in the release?

clicking on the release shows pivotal tracker stories worked on and the actual commit revision id in github.

contents of release
the pt story types also give a good indication what the main work type was – user features, chores or bugfixes.

cause and effect

now you’re able to show quite clearly to the organization how often you do releases (and even what your releasing). if tagging releases is ‘crawling’, then you are now at the ‘walking’ phase. what would it take to really stretch our legs out and get ‘running’?

showing the impact of a release is the next logical step. did you manage to grow traffic? has the response time of the site improved? see any more bugs after the release? these are all fairly easy to track, and plotting them as a backdrop to the releases demonstrates the real impact your team is having on the bottom-line.

what other metrics make sense here? what would you expect to see? and what would really be kick ass? share your thoughts on twitter using the #codeinventory hash tag!

Release (agency) Inventory (library)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • How To Check Docker Images for Vulnerabilities
  • Bye Bye, Regular Dev [Comic]
  • How to Create a Real-Time Scalable Streaming App Using Apache NiFi, Apache Pulsar, and Apache Flink SQL
  • How Observability Is Redefining Developer Roles

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: