Hello!

Today, I'd like to share my perspective on formal project management for small to medium-sized projects, using Secutils.dev as an example. When starting a new project, it's often driven by a spark of inspiration or a strong desire to solve a specific issue for yourself or a group of people. At this early stage, formality can be a distraction and drain motivation quickly. You have a clear vision of what needs to be done, and adding unnecessary formalities can hinder progress.

Initially, things may go smoothly without a formal project management process. You create functional prototypes, launch an MVP with a catchy domain name, and receive positive feedback from early users. However, over time, the excitement from these achievements can diminish, and internal motivation alone may not be enough to drive the project forward. This is a natural human tendency, and it's important to recognize it. If you're satisfied with your project in its current state, or if it was originally intended as a short-term fun project and you're ready to move on to something new, that's perfectly fine. You should absolutely embrace the joy of building and exploring new ideas.

However, if you want to advance a more complex project and still maintain sufficient motivation, I believe it's essential to adopt a different strategy. The strategy I'm going to discuss next involves incorporating a bit of formal project management to keep yourself on track, sustain progress, and avoid the disappointment of yet another unfinished project.

Hello!

In my previous posts, I mostly focused on the technical aspects related to Secutils.dev, such as the technological stack, deployment process, and tools for monitoring and usage analytics.

Today, I'd like to discuss the costs associated with running Secutils.dev in production. As developers, we understand the importance of being resourceful, frugal, and efficient when building and maintaining products. Therefore, minimizing costs is a crucial and ongoing topic. Let's dive into how I optimize costs for Secutils.dev.

Hello!

In my previous posts, I covered the technological stack behind Secutils.dev and how I deploy its components to the Kubernetes cluster.

Today, I want to showcase the tools I use to monitor my Secutils.dev deployment and collect usage analytics.

Hello!

In my previous post, I discussed the technological stack behind Secutils.dev and introduced its four separate components: a backend server written in Rust, a React-based Web UI client, a documentation website powered by Docusaurus, and a lightweight static promotional home page.

Today, I'll provide a brief overview of how and where I deploy these components to ensure the complete functionality of Secutils.dev.

Hello!

Today, I'd like to provide an overview of the technology stack powering Secutils.dev. Sharing this information might prove helpful to other individuals working on similar projects. So, without further ado, let's dive into the stack!

Hello!

My name is Aleh Zasypkin, and I am a software engineer with a passion for application security. Today, I am delighted to announce that the beta release of Secutils.dev is now publicly available!