patrck

6 ms·

31.
by patrck 4y ago
TeX, Calendar file, scratch wiki TeX for everything; it's basically `duck-talking` with snippets of code. One TeX doc per project. Calendar file with reminders to do stuff in the future, ie. delegate to your future self. Todos in a scr
32.
by patrck 4y ago
This needs a prefatory "Tools for a Culture of Reading". How many colleagues will do a literature review before starting something? How many will take notes and try to understand the history of how everything got to be the way thi
33.
by patrck 4y ago
Do you keep an engineering log for yourself? If not, then start one as that's the easiest way to review what the concerns of the day were back then, and to begin to see where having history starts paying dividends. Otherwise, something
34.
by patrck 4y ago
Every shell is a REPL Using your editor to drive a shell is a huge win because it: (a) flips the development bit in your brain, and (b) creates a shared history across all your machines. Combine that with literate programming and you have a
35.
by patrck 4y ago
All-nerds, Responsibility, and Systems Many tales of woe (see https://rachelbythebay.com/w/2022/02/09/nice/ for a good sysadm one, or the syndicated loan problem in the original DDD book) could have
36.
by patrck 4y ago
That said, not sure why `ps` isn't a better choice? ps -e -o size,user,comm | sort -n | tail
37.
by patrck 4y ago
Here's an attempt at the script. Let's golf it! N=10 find /sys/fs/cgroup/ -name memory.current | while read f; do test -e $f || continue echo `cat $f` $f done | sort -n | tail -n $N | awk '