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 List

Project Name

Project link here Why does project align with my direction here An example of an issue or contribution that will be a realistic contribution

I don't need to fully understand the codebase, announce anything publicly, or an accepted PR but just identifying what makes sense based on my progress

I should consider * CLIs like Github CLI, Infra helper tools and Task runners. * Cloud/GCP tooling, terraform providers/modules and GCP-adjacent Go tools. * CNCF/infra utilities, kubectl plugins, lightweight ops tools

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