Skip to content

Instantly share code, notes, and snippets.

@discoverlance-com

discoverlance-com/my-golang-progress.md

Last active February 4, 2026 08:11
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save discoverlance-com/1bca5f12e70b8a80815faca880ca45fa to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save discoverlance-com/1bca5f12e70b8a80815faca880ca45fa to your computer and use it in GitHub Desktop.
Download ZIP
My Golang Progress
Raw
my-golang-progress.md

This is where I document my progress and journey on Go - Systems Engineer - Cloud native tooling - OSS. The plan is to get familiar with golang and make useful projects like developer tooling and contribute meaningfully to Golang OSS.

Week 0

Success Indicators:

  • Restructured Github profile README emphasizing focus on Backend engineering with Golang and Cloud native tooling.
  • Setup a new github repo and a Golang environment setup for the System inspection CLI project for Week 1.
  • Created a technical direction document that dictates and guides my new direction and goal
  • Created a shortlist of OSS targets I intend to contribute to around week 3 of this journey.
  • Defined success criteria for Week 1

Open Source Contribution ShortList

https://github.com/charmbracelet/gum This project aligns with my primary target of Go CLI tooling and developer productivity.

One issue I can look at is #1003. Adding useful info command. I can comment with the proposed flag name, a sample output and a proposal about it on the issue and making sure it's not a breaking change.

https://github.com/spf13/cobra This project is a secondary target for documentation-focused contributions and deepening my understanding of CLI frameworks and OSS workflows.

One issue I can look at is #2319. This talks about a documentation update about a deprecated command. Also, issue #2322 is about incorrect links in documentation. It will help me to understand the CLI docs structure.

Week 1

Success Criteria

  • Problem Class: Make a repetitive dev/ops task faster
  • This tool is for me, Go / Cloud / Serverless engineer
  • The tool has a clearly defined input -> output contract (document)
  • It should use a standard Go CLI framework
  • It should handle flags + errors cleanly
  • It should have a usable README
  • The tool has meaningful exit codes (0, non-zero on failure)
  • The tool should have at least one core behavior validating test and a critical edge case handling
  • It can be installed and run by someone else
  • It will not include auth, databases, background process or any complex provisioning of resources

Project Idea

portdie - I want a fast, memorable CLI that shows me what ports are in use on my machine and lets me kill the associated process without remembering OS-specific commands.

Requirements/Capabilities

  • Windows only
  • List active TCP ports and associated PIDs
  • Support basic filtering by port or process name
  • Can kill a selected process by PID
  • Uses a standard Go CLI framework (cobra or similar)
  • Clean flag handling (--port, --pid, --force, etc)
  • Clear error messages (e.g. permission issues)
  • README with
    • What it does
    • Installation
    • Example usage
  • Installable via go install

Explicit non-goals: No interactive TUI (yet), No tagging, No config file, No background services, No cross-platform support (yet) to avoid scope creep.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment