Forcing myself to do something different

This is usually not what I do, but it is now the reason I'm doing it. Writing posts about what I do, or about myself is just not my cup of tea, but I also don't want to be the same old same old either. Why not switch it up and see what happens? So, I will start writing about my re-learnings. I set myself a goal to build a DevOps toolkit of sorts. Nothing complicated, an app that will be deployed for consumption, with testing and and proper CI/CD setup, hosted on AWS, with all IaC on GitHub. No clue what I will use for the app, but it will have to be something that needs to be compiled and built, something that would provide a challenge for the automation setup. Should be pretty fun, I love doing stuff like this, and haven't had a chance to play around much lately. Management role will do that to you, just no time, and I feel like I'm getting more and more disconnected from the DevOps stuff I was involved in building with my previous team. For my own musing I will also generate a ChatGPT result of my post (if its just rambling and not some technical documentation) with a prompt of "Make this sound better". ---ChatGPT Says...--- This isn’t something I usually do, but that’s exactly why I’m doing it. Writing about myself or what I’m working on has never really been my thing. But I’m also not interested in doing the same old thing just because it’s comfortable. So—why not shake it up and see where it goes? I’ve decided to start writing about the things I’m re-learning. I’ve set myself a goal: build a kind of DevOps toolkit. Nothing too fancy—just an actual app that gets deployed, fully tested, with a solid CI/CD pipeline, hosted on AWS, and all infrastructure as code in GitHub. I haven’t decided what the app will be yet, but I know it’ll be something that needs to be compiled and built—something that’ll make the automation setup a fun challenge. Honestly, I’m really looking forward to it. I love this kind of work, and I haven’t had the chance to dive in for a while. That’s the tradeoff of stepping into a management role—less hands-on time, and I’ve been feeling more and more disconnected from the DevOps work I used to lead with my team. As a bit of a tradition (and self-check), I’ll probably run my posts through ChatGPT with the prompt: “Make this sound better.” Especially if it’s more of a ramble than proper documentation.

Apr 19, 2025 - 15:35

Forcing myself to do something different

This is usually not what I do, but it is now the reason I'm doing it. Writing posts about what I do, or about myself is just not my cup of tea, but I also don't want to be the same old same old either. Why not switch it up and see what happens?

So, I will start writing about my re-learnings. I set myself a goal to build a DevOps toolkit of sorts. Nothing complicated, an app that will be deployed for consumption, with testing and and proper CI/CD setup, hosted on AWS, with all IaC on GitHub. No clue what I will use for the app, but it will have to be something that needs to be compiled and built, something that would provide a challenge for the automation setup.

Should be pretty fun, I love doing stuff like this, and haven't had a chance to play around much lately. Management role will do that to you, just no time, and I feel like I'm getting more and more disconnected from the DevOps stuff I was involved in building with my previous team.

For my own musing I will also generate a ChatGPT result of my post (if its just rambling and not some technical documentation) with a prompt of "Make this sound better".

---ChatGPT Says...---

This isn’t something I usually do, but that’s exactly why I’m doing it.
Writing about myself or what I’m working on has never really been my thing. But I’m also not interested in doing the same old thing just because it’s comfortable. So—why not shake it up and see where it goes?
I’ve decided to start writing about the things I’m re-learning. I’ve set myself a goal: build a kind of DevOps toolkit. Nothing too fancy—just an actual app that gets deployed, fully tested, with a solid CI/CD pipeline, hosted on AWS, and all infrastructure as code in GitHub. I haven’t decided what the app will be yet, but I know it’ll be something that needs to be compiled and built—something that’ll make the automation setup a fun challenge.
Honestly, I’m really looking forward to it. I love this kind of work, and I haven’t had the chance to dive in for a while. That’s the tradeoff of stepping into a management role—less hands-on time, and I’ve been feeling more and more disconnected from the DevOps work I used to lead with my team.
As a bit of a tradition (and self-check), I’ll probably run my posts through ChatGPT with the prompt: “Make this sound better.” Especially if it’s more of a ramble than proper documentation.