If I had a band to name, I'd name it Feiera, because feiera.band is still available and costs only 2,50 a month.
The Three Bad Reasons Why I Don't Use Git
Entry created on 2021-09-01
author:steeph (374)
cat:Computer (78)
cat:Git (1)
cat:Personal (12)
cat:Software (53)
cat:Version Control (1)
lang:en (253)
1. Github or other public Git repositories: Wouldn't be complete
Haven't published everything always, don't want to publish everything, would want to include everything but couldn't. So using public Git repositories would always be accompanied by a feeling of imperfection.
2. I've never used Git for anything really.
Apart from cloning and occasionally updating others' repositories I've never used them. I'm not used to using Git and I don't struggle with not using it. So starting to do so now would require me to hurdle quite some hurdle. I never used it. Why would I start now?
3. It's too late to start now.
I've noticed that the point where it would have been a good idea and would have made a lot of sense to get accustomed to using Git has long passed. So by starting now or in the future I would admit that I didn't take the hurdle when it would have been the right thing to do - when the best time to do so was near the present. I would admit to doing some things not the right way in the past if I would start to do them right from now on. It's easier to pretend that the way it always has been is the right way - the way I'm used to doing things.
That all makes no logical sense. It would be an improvement to start using Git for some things, be it coding projects, any category of texts that I have on my computers, any collection of files, ... The costs of these improvements would be hard disk space, which isn't all that rare for me nowadays and getting used to using Git, which isn't complicated.
So why don't I even try to use it in some cases? Well, I've just honestly told you my three reasons.
SBWG 0.9.6
Entry created on 2021-08-29
author:steeph (374)
cat:Bash (31)
cat:Code (31)
cat:Computer (78)
cat:Linux (36)
cat:Projects (41)
cat:SBWG (18)
cat:Scripts (28)
cat:Software (53)
lang:en (253)
top:Projects:Code:Bash Scripts:SBWG (16)
As foreseen I've made slow progress in development of SBWG, the script that generates this web site, because I want to test and improve it with the current feature set before I start to implement new features. The former is necessary. The latter is more fun. But today I've reached a point where I can say that the only thing left to do before I call it v1.0.0 is testing edge cases and things that I didn't think of testing before, as well as fixing potential bugs discovered from this testing.
So, version 0.9.6 is out, everything is working, The README file, other documentation included in the package, the example website, the included style sets and partly even the code quality has been deemed satisfactory, and I hope I'll find the time to test all sorts of weird stuff and discover and fix some bugs next month, at which point version 1.0.0 will be published and I'll finally be able to allow myself to start working on new features, some of which are awaited by both regular users of the script.
Hope Dies Last
Entry created on 2021-08-09
author:steeph (374)
cat:Hope (1)
cat:Thoughts (71)
lang:en (253)
I will never forgive her for doing that to meeveverybody!
Backmatch - A Simple Dual-N-Back-Inspired Performance Task Trainer For Bash
Entry created on 2021-07-31
author:steeph (374)
cat:Bash (31)
cat:Brain Training (1)
cat:Code (31)
cat:Computer (78)
cat:Scripts (28)
cat:Software (53)
lang:en (253)
top:Projects:Code:Bash Scripts (23)
Here is a script that I wrote as a short side project because I wanted my own n-back trainer. I'm aware that the practical memory improments of n-back training, even when using a proper audiovisual dual n-back trainer, is not as great as it's often said to be. I just wanted to try it and see whether I like the training.
Usage
Execute the script and pass it a number that resembles the difficulty level. For example bash backmatch 3 starts the script with a 3-back task. On
your keyboard press the key of the letter that was displayed n letters ago (in this example 3 letters ago). When you press a key the next letter is presented
immedietly. If you don't press a key for 3 seconds (the time value can be changed by changing the variable sec) the next letter is presented and you
don't get a point for this letter. When you exit the script by pressing ctrl+c your keypresses get compared to what was presented and you get your score.
#!/bin/bash
if [[ ${#} -ge 1 ]] && [[ ${1} =~ ^[0-9]*$ ]]
then
n=${1}
else
echo "'${@}' is not a number, is it?"
exit 1
fi
echo "Ctrl+C pressing is for quitters."
npo=$((n+1))
sec=3
end() {
echo -en " \n"
if [[ ${#str} -ge ${npo} ]] # If enough characters had been generated
then
for i in $(seq $n); do echo -n "-"; done # offset by $n dashes
echo ${str}
echo ${you}
got=0
for i in $(seq ${#str})
do
[[ ${str:$i:1} == ${you:$((i+n)):1} ]] && got=$((got+1))
done
echo -e "\n${got} out of $((${#str}-npo)) correct"
else
echo "Not enough data to judge you."
fi
}
trap end EXIT
while true
do
str+=$(cat /dev/urandom | tr -dc 'A-Z' | head -c 1) # Get a random new letter.
echo -en "\r \r${str: -1}" # Print the last character in the string (the new letter).
read -n 1 -t ${sec} key # Get a single character input, timeout $sec seconds.
[[ -n ${key} ]] && you+=${key^^} || you+="-"
[[ ${key^^} == ${str: -$npo:1} ]] \
&& echo -en "\r good" \
|| echo -en "\r bad" # Check if uppercase input char is the same as the nth char from the back.
done
end
exit 1