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).
Hi. I spoke about Go and Clean Code in a couple of meetups and at the last Gophercon Brasil in 2019 (slides here, in Portuguese) and I am now breaking the presentation in a series of posts, starting with this one, to explain what kind code is considered clean in Go. The motivation behind this is to share a little after years of writing Go code on what kind of practices are considered good / bad.
Hello there! :) So, for those of you who want to write distributed systems easily in Python or are just curious about the subject, I was studying about Java RMI for my Distributed Systems class and I always get thrilledto know that I need to write Java code. Nothing against good ol’ Java, it’s just not my vibe these days but I’d happily do it if convinced. Since I was just studying and trying to learn a concept, I searched for a Python alternative.
This is the first of a series of posts that I will write to share some knowledge I gained on Python Web Frameworks plus a nice, public way to push me into learning more and more about them. I’ve decided to do the same project on all of them, starting with Django Rest Framework. This is will be a standalone analysis and then I will move forward to comparisons. My intention is to find a good framework to plug into a database and see how well it handles GET requests.
We code everyday. We produce code fast, following the rhythm of the rock and roll guitar playing in the background and every time we focus on writing code fast, we miss some important things that makes us lose time in the future. The next time you create a new file in your Python project, think about its name very carefully. Every Python file is a module. We import modules all the time.