After years writing bash scripts I stumbled with this line...

set -e

Which forces the script to exit on first error.

This line be in the bible as Genesis 1:1

  if ! failing_cmd; then
    log "this fails!"
    return 1
  fi

  log "this won't log"

First, there was LiveJournal. Then there was MySpace. Then there was FaceBook. I was on FaceBook until .edu stopped being a requirement. Shortly after that change, my wall became a mix of soft porn and hightimes. Nothing wrong with that, but it isn’t what I want to see so I deleted my FaceBook account. I went over to Twitter. Over time, Twitter ceased to be interesting as it turned into people affirming their positions on things they usually didn’t understand very well. I deleted my Twitter account half a decade ago. All of it is actually useless, and it does nothing but eat time.

I'm very happy I dug into rust half a decade ago. The language has been fun to learn as it evolved futures and async/await, and the future continues to look promising. I've had the pleasure of working professionally in Rust twice in my life (once at Full story, now at Deno) and I can say it's by far my favourite language to work in.

I did some Rust training with Ferrous but by far the most useful way to learn was just picking up a project and building it.

It's alway pretty fascinating to me that people can actually be productive without an IDE.

I've tried several times Vim and I just don't get it how you can live without certain functionalities, I'm sure that with enough tinkering you can get pretty close but, for example, search seems to always be kind of a pain in the ass for the complex queries with regex through many files and stuff like that, specially the presenting of results has never been close in my opinion as to something like IntelliJ does it.

Things like "god damn, I've done goofed or I don't quite remember something" and having the internal file history with a diff readily available.

Some of the click and find implementation/usages never seems to quite there to me.

I could go on, if you're truly being productive and not missing out on feature, more power to you, but I honestly wonder if there's no element of fun/pride in using something like vim now-a-days, which of course is totally fine and way more important in my book (to an extent) to pure productivity.

There is also the point of being able to use vim bindings inside of the IDE.

Maybe I'm just an idiot that can't Vim, totally open to that idea, but I'm truly wondering how productive it actually is.

They could just take the old game engine as-is, give it a new plot and art, and I would beg them to take my money.

100% sane advice on the "should" front, but I don't always follow the shoulds..

Bash is just too damn fast to whip things up in (even at the risk of endless footguns). Build up a pipeline of commands, translate into script, done. It's powerful and can scale if common conventions and good practices are used.

For easier debugging I always add a simple flag along the lines of: if $1 = -v then set -x; shift

Obviously shellscripts are a terrible or highly suspect idea when production-grade transactional integrity is critical, but in many cases the swiftness of shell development outweighs the cons when the goal is to Get Things Done.

The shell is a pretty sweet interface.

You can!

https://gohugo.io/templates/output-formats/