---
title: "Discussion on \"diskdoc and dockit: same problem, two languages, different answers\" | Hashnode"
description: "Discussion on \"diskdoc and dockit: same problem, two languages, different answers\". diskdoc and dockit: same problem, two languages, different answers\nI built two tools that clean up disk space. Both are CLIs. Both deal with Docker. Both ship as a single binary. And if you put them side by side, they look like the same project in tw..."
url: "https://hashnode.com/posts/diskdoc-and-dockit-same-problem-two-languages-different-answers/69e85d1ecc3e85deeb10d826"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [diskdoc and dockit: same problem, two languages, different answers](https://vineethnk.hashnode.dev/diskdoc-and-dockit-same-problem-two-languages-different-answers?utm_source=hashnode&utm_medium=feed)

diskdoc and dockit: same problem, two languages, different answers I built two tools that clean up disk space. Both are CLIs. Both deal with Docker. Both ship as a single binary. And if you put them side by side, they look like the same project in tw...

Apr 22 · 11 min read · vineethnk.hashnode.dev  
Read the article

-   [#cli](https://hashnode.com/tag/cli)
-   [#docker](https://hashnode.com/tag/docker)
-   [#go](https://hashnode.com/tag/go)
-   [#rust](https://hashnode.com/tag/rust)
-   [#tui](https://hashnode.com/tag/tui)

## Written by

[Vineeth N K](https://hashnode.com/@vnknotes)

@vnknotes

  
[View profile](https://hashnode.com/@vnknotes)

What I learned the hard way. So you do not have to.

Hi, I am Vineeth (VNK). I am a software developer and DevOps engineer based in Kochi, India. I work across backend (Node.js, NestJS, PHP), infrastructure (Docker, MySQL, Linux), and frontend (Vue, React). I am currently building and operating products with BEO, where I do everything from architecture decisions to staging deployments to fixing the things that break at 9 PM on a Friday. I write about real problems from real work - the kind of things you do not find in tutorials. Production incidents, hard-won architecture lessons, team and process notes, and the occasional opinion piece. If something I shipped, broke, or learned might save someone else half a day, it goes here. No fluff. No ghostwritten thought leadership. Just notes from the terminal.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.