I'm not saying you should all go out and set up aliases to enable your various typos and slip-ups, but I honestly don't know why I didn't do this 25 years ago.

alias cd..='cd ..'

#bash #UNIX #Shell #UnixShell #POSIX

#shell #cli

i wrote a little time log parser in posix shell. it collects from all the files in my todo directory, selects all the lines formated like this...

# start-time stop-time project: task description
- 20260301-085700 20260301-095640 code: add log.sh

code	05:10:44
home	00:22:00
kids	00:42:40
meta	00:40:22

#smallweb #indieweb #shell

i try to push shell as far as it reasonably goes. for most tasks, sh, find, grep, sed, and cut is more than enough. only when things become truly complex or painfully slow do i reach for another language.

i used to care a lot about strict portability, but in practice i only run my scripts on macos and #openbsd. that simplifies things: if shellcheck is happy, i'm happy. i'm 99% sure my scripts work on other unix-like systems, but i don't feel the need to check.

what really draws me to shell is that it's always there. it's part of the base system, requires no extra installation, and the runtime has been stable for decades. that stability translates directly into confidence: shell scripts feel future-proof.

i know i can run something like ssg.sh ten years from now and it will still work --- certainly on #openbsd, and hopefully on macos too. there's no dependency churn, no worrying about the "right" version of python or ruby, and no hoping the ecosystem hasn't moved on.

it just runs.

Alt...

built with /bin/sh