Posts

One thing that often happens to me is I’ll start a project looking forward to seeing it’s completion, and then later in the project’s lifetime I’ll give up, scrap the project, and start a new one. This happens over and over again, and it’s honestly emotionally exhausting. This is partially due to being in a loop of “this code isn’t good enough”, which in result can cause things like imposter syndrome, lack of motivation, and similar, a great explaination of this is a xkcd comic named Good Code....

I came out as trans around June of last year I believe, near my birthday. It’s certainly experience, questioning your gender, and while I do certainly think of myself as female, I can imagine myself wearing dresses, wearing feminine undergarments and doing other things such as wearing makeup occassionally (which isn’t necessarily feminine!) there is those times where I just start to feel a sense of unease, a sense of uncertainty, a sense of worry and dread that either I’m lying to myself, or that I will never look like what I want to....

One thing that happens when you’re developing projects, no matter big or small, is burnout. You work on a project for hours, days, weeks, months, or even years and you hit those points (or point if you’ve given up) of just feeling like it’s not worth it, or that the project is too big or tedious for someone like you. Today we’re going to be talking about that feeling and how to escape it, and how to stay motivated through projects, as well as learn from people in other projects how they push through it....

There is a lot of programming languages in the world, why create another, or more relevantly, why learn another? Today we’re going to be discussing the programming language named Zig and why I have fallen in love with it. Let’s start from the beginning, Zig is meant to “fix” a lot of issues other programming languages have, a good video to watch is The Road to Zig 1.0 by Andew Kelley, which goes into a lot of the nitpicking on other languages such as C, Rust, D, and others....

One mistake I’ve seen people make, especially newcomers to devops or programming in general, is they try to learn to much. I don’t mean in a specific time frame either, I mean overall. They end up learning 50 different languages and/or tools, when in reality they’re going to only end up using using at most 5, especially in their career. I know this because it’s something I’ve personally done, I ended up learning so many languages, tools and more, that I have per-say “cluttered” my brain with information that probably won’t be used, and this is problematic, especially at scale....