---
title: "Seung Joo Ahn (@seungjoo) | Hashnode"
description: "Backend Engineer. Read the latest articles by Seung Joo Ahn on Hashnode."
url: "https://hashnode.com/@seungjoo"
---

@seungjoo

# Seung Joo Ahn

@seungjoo · Seoul, South Korea · Joined January 2025

Backend Engineer

### [\[Day 11\] cron & Bash Scripting — Automating Tasks in Linux](https://frogsdevlog.hashnode.dev/day-11-cron-bash-scripting-automating-tasks-in-linux?utm_source=hashnode&utm_medium=feed)

Day 10 covered journalctl for analyzing logs. But repetitive tasks like "clean up old logs every day at 3 AM" shouldn't be done manually. That's what cron is for. 1. cron = An OS-Level Scheduler If y

5 min read · [frogsdevlog.hashnode.dev](https://frogsdevlog.hashnode.dev/day-11-cron-bash-scripting-automating-tasks-in-linux?utm_source=hashnode&utm_medium=feed)

[May 12](https://hashnode.com/posts/day-11-cron-bash-scripting-automating-tasks-in-linux/6a02fc08937b84f7795a5900)

### [\[Day 10\] journalctl — Finding Problems Through Logs](https://frogsdevlog.hashnode.dev/day-10-journalctl-finding-problems-through-logs?utm_source=hashnode&utm_medium=feed)

Day 9 covered systemd managing services. Unit files, service registration, auto-restart on failure. But when something breaks on a server running 50 services, you can't run systemctl status on each on

5 min read · [frogsdevlog.hashnode.dev](https://frogsdevlog.hashnode.dev/day-10-journalctl-finding-problems-through-logs?utm_source=hashnode&utm_medium=feed)

[May 7](https://hashnode.com/posts/day-10-journalctl-finding-problems-through-logs/69fc3e203d9a9c101979d539)

### [\[Day 9\] systemd — Who Wakes Up All These Processes?](https://frogsdevlog.hashnode.dev/day-9-systemd-who-wakes-up-all-these-processes?utm_source=hashnode&utm_medium=feed)

Day 8 was about pipelines. Chaining grep, awk, sort, and uniq -c together to aggregate socket states. Each tool is simple on its own, but piped together they become powerful. Today I took a step back.

6 min read · [frogsdevlog.hashnode.dev](https://frogsdevlog.hashnode.dev/day-9-systemd-who-wakes-up-all-these-processes?utm_source=hashnode&utm_medium=feed)

[May 7](https://hashnode.com/posts/day-9-systemd-who-wakes-up-all-these-processes/69fc26433d9a9c1019631c6a)

### [\[Day 8\] Linux Pipes Are Just Plumbing — And I Already Had the Wrenches](https://frogsdevlog.hashnode.dev/day-8-linux-pipes-are-just-plumbing-and-i-already-had-the-wrenches?utm_source=hashnode&utm_medium=feed)

Day 7 ended with a real shift in how I think about sockets. The kernel owns them. Processes just hold pickup tickets. accept() isn't accepting — it's picking up what the kernel already prepared. Today

8 min read · [frogsdevlog.hashnode.dev](https://frogsdevlog.hashnode.dev/day-8-linux-pipes-are-just-plumbing-and-i-already-had-the-wrenches?utm_source=hashnode&utm_medium=feed)

[Apr 23](https://hashnode.com/posts/day-8-linux-pipes-are-just-plumbing-and-i-already-had-the-wrenches/69e9ee4e16b084c068f8c09a)

### [\[Day 7\] The Process Went to Sleep — and the Kernel Kept Working](https://frogsdevlog.hashnode.dev/day-7-the-process-went-to-sleep-and-the-kernel-kept-working?utm_source=hashnode&utm_medium=feed)

In Day 6, I watched a single connection arrive at the server and saw two fds show up instead of one. The listening socket (fd 3) stayed at the door, and a new connected socket (fd 4) was created for t

12 min read · [frogsdevlog.hashnode.dev](https://frogsdevlog.hashnode.dev/day-7-the-process-went-to-sleep-and-the-kernel-kept-working?utm_source=hashnode&utm_medium=feed)

[Apr 22](https://hashnode.com/posts/day-7-the-process-went-to-sleep-and-the-kernel-kept-working/69e8cde55d1c1071054ec9b5)
