<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Home on Walsen&#39;s blog</title>
    <link>https://blog.walsen.website/</link>
    <description>Recent content in Home on Walsen&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2020 23:00:00 +0000</lastBuildDate><atom:link href="https://blog.walsen.website/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DevSecOps Fundamentals Project</title>
      <link>https://blog.walsen.website/posts/devsecops-project-fundamentals/</link>
      <pubDate>Mon, 16 Feb 2026 21:13:54 -0400</pubDate>
      
      <guid>https://blog.walsen.website/posts/devsecops-project-fundamentals/</guid>
      <description>Introduction Every engineer has that one project — the one that starts as a simple idea and evolves into a full-blown learning laboratory. For me, that project is this Publisher Web App: a system designed to publish announcements across multiple social media channels simultaneously. The primary use case? The AWS Certification Announcer, a community tool where members submit their AWS certification achievements and the platform automatically publishes them to Facebook, Instagram, WhatsApp, LinkedIn, Email, etc.</description>
    </item>
    
    <item>
      <title>An Incredible Operations Platform - Rundeck</title>
      <link>https://blog.walsen.website/posts/an-incredible-operations-platform-rundeck/</link>
      <pubDate>Sat, 31 Jan 2026 19:30:20 -0400</pubDate>
      
      <guid>https://blog.walsen.website/posts/an-incredible-operations-platform-rundeck/</guid>
      <description>Introduction There&amp;rsquo;s a moment every operations engineer knows well: it&amp;rsquo;s 2 AM, something&amp;rsquo;s broken, and you&amp;rsquo;re frantically SSH-ing into servers trying to remember the exact sequence of commands to fix it. You&amp;rsquo;ve done this before, but was it systemctl restart first or the config update? And which servers exactly?
This is the problem Rundeck solves. It&amp;rsquo;s an open-source runbook automation platform that lets you define, schedule, and execute operational procedures across your entire infrastructure—with proper access control, audit trails, and the peace of mind that comes from knowing the procedure will run exactly the same way every time.</description>
    </item>
    
    <item>
      <title>GitHub Action to Publish Hugo Posts to Dev.to</title>
      <link>https://blog.walsen.website/posts/github-action-to-publish-hugo-posts-to-dev.to/</link>
      <pubDate>Sun, 25 Jan 2026 22:23:37 -0400</pubDate>
      
      <guid>https://blog.walsen.website/posts/github-action-to-publish-hugo-posts-to-dev.to/</guid>
      <description>Introduction As developers who maintain technical blogs, we often face a common dilemma: should we publish exclusively on our own site, or should we cross-post to platforms like Dev.to, Medium, or Hashnode to reach a wider audience?
The answer is usually &amp;ldquo;both,&amp;rdquo; but that creates a new problem: manual cross-posting is tedious, error-prone, and time-consuming. You write a post in Hugo, publish it to your site, then manually copy-paste the content to Dev.</description>
    </item>
    
    <item>
      <title>A Wild Ride Into Vibe Coding</title>
      <link>https://blog.walsen.website/posts/a-wild-ride-into-vibe-coding/</link>
      <pubDate>Sat, 22 Nov 2025 17:49:33 -0400</pubDate>
      
      <guid>https://blog.walsen.website/posts/a-wild-ride-into-vibe-coding/</guid>
      <description>Introduction Since I was a child, computers have held a magnetic fascination for me. I vividly remember the first time I saw one in my mother’s office at the age of eleven; in that exact moment, I knew precisely what I wanted to do with my life.
Although destiny led me down the path of infrastructure, I never truly abandoned the dream of developing applications. While I have a solid foundation in programming and can hold my own in the terminal, a lack of daily practice and the time required for a deep dive had—until now—prevented me from producing professional-grade software.</description>
    </item>
    
    <item>
      <title>The Future of Work</title>
      <link>https://blog.walsen.website/posts/the-future-of-work/</link>
      <pubDate>Sun, 09 Nov 2025 16:16:20 -0400</pubDate>
      
      <guid>https://blog.walsen.website/posts/the-future-of-work/</guid>
      <description>The Future of Work Current Landscape As I write this article, technology companies find themselves in a transitional phase. With the advent of artificial intelligence, the way software is produced will change, and so will the type of professionals required to build it—if this transformation hasn&amp;rsquo;t already begun.
In the IT field, the most common professional roles include: architects and developers, quality assurance (QA) specialists, infrastructure engineers, database analysts, and all related variants of these specialties.</description>
    </item>
    
    <item>
      <title>Devbox: Portable and Isolated Development Environments</title>
      <link>https://blog.walsen.website/posts/devbox-portable-and-isolated-development-environments/</link>
      <pubDate>Thu, 16 Jan 2025 23:34:01 -0400</pubDate>
      
      <guid>https://blog.walsen.website/posts/devbox-portable-and-isolated-development-environments/</guid>
      <description>Introduction I am one of those people who need to have everything in its place to be able to do something. This applies, of course, when I work with a local or remote repository. I need to have all the dependencies installed and configured; moreover, the environment must be prepared with all the tools and with signaling showing the current status of the environment.
By signaling, I mean the console &amp;ldquo;prompt,&amp;rdquo; which should be as friendly and aesthetic as possible.</description>
    </item>
    
  </channel>
</rss>
