a live coding session about a framework Go that autogenerates open api spec

Learning in public is gonna be a new series of blog posts in order to share some cool stuff I’ve been up to! I’ve been up to some stuff lately! So when it comes to courses and learning stuff, I’m back at Linuxtip’s ansible training that I have stopped for a while. Mainly to take some ideas for my Go course that I’ll be launching there, and also to get more formal training on ansible, my experience was always been driven by problems at work!

Hello folks! While working at Red Hat I had the awesome opportunity to brush up my Go skills on a daily basis again, and I stumbled across a lot of interesting technical problems. One of these problems struck my attention so much that I started playing with it on my free time and I came up with ez. This is a pet project, but I wanted to let people know I’m on it in case its going to be useful for someone else and/or if you wanna get involved and contribute!

Configuration management is such a fun problem to solve! You can use libraries like dynaconf (Python) or viper (Go) and they’re super fancy and will probably provide everything you want (and a bit more). Today I wanted to code, though. For a pet project, I wanted something as simple as: well, try to get this configuration from env vars, and try to look in a secret manager for those you can’t find.

DISCLAIMER: This has nothing to do with a certain famous book that also speaks about Clean Code. Nothing. I’m talking from the experience of writing lots of bad code throughout the years, of lots of research on how to do it better while writing Go code and these examples do not necessarily apply to any other programming language. This is the third post of a series that started here based on a talk I gave about Go and Clean Code(slides here, in Portuguese).