Next: first steps, Up: (dir)

GOing bare: Learning GO by building a bare-metal provisioning system

I'm learning the GO language, using a bare-metal provisioner as the working example. It's a challenging exercise and a lot of work, so there's no particular timeline. I'm trying to spend at least an hour a day on it.

The new, "release early, release often" plan

I started out with a really aggressive, guesswork plan (see it below), but pivoted with mentoring to an approach more compatible with my "release early, release often" mindset:

First steps christian grabowski: "Well so when I start a Go project, I usually start with a main function, it has logging, sets up a Prometheus exporter and can gracefully handle a SIGINT or SIGTERM, and I go from there." Sounds like a plan.

The old plan, for reference

I'm keeping this around because there are a lot of good nuggets in there. It will probably be a decent checklist, at least:

Steps 1-20 . . . . . . .Laying the foundation (Basic types thru reflection).
Steps 21-40 . . . . . . Building the components (Pointers thru CI & dependencies).
Steps 41-60. . . . . . .Enhancing features (Concurrency thru database ops).
Steps 61-84 . . . . . . Expanding functionality (Rest API, Temporal, advanced techniques).
Steps 85-93. . . . . . .Project finishing & best practices.
Steps 95-103. . . . . . End-user documentation.

Copyright (C) 2020-2023 by stormrider; All Rights Reserved