alecigne

I think there should be a compromise. Use your own config but be ready to switch quickly to a more "common" config and know how to use it (whatever common means in your context, just adapt to your team).

For example I use i3, and I switch ctrl and caps lock. During my first pair programming experience my colleague was struggling with all that and I was feeling quite guilty ("maybe this need to fine-tune everything is just immature after all"). After this I made sure to be able to switch quickly to a "vanilla" Gnome setup.

Although coming back to Gnome after using i3 is quite easy since the Gnome paradigm is quite universal, there are some alternative "configs" that I am afraid to adopt, such as exotic keyboard layouts ("bepo" in french instead of "azerty"). Losing the ability to type on this de facto standard layout would be quite problematic.

I listen to SomaFM's Drone Zone channel on noise-cancelling headphones when I program. It broadcasts "drone" music – no lyrics, very little rhythm, melody or harmony – the music concentrates mainly on sound texture. And of course, no ads. Can't recommend it enough.

It is not that slow. On my machine Vanilla Emacs starts in 0.1 second. With my 12 years-old config, it starts in 0.4 second. Emacs 27 pre-init system made it even faster.

And if your machine is slow you can use a daemon.

I use Emacs Org mode in a git repository hosted on my Raspberry Pi. On my phone, I use Orgzly to edit the files, along with Termux to manage the git repo. I also use Termux to launch Emacs from time to time when I need an advanced operation not yet supported by Orgzly.

I keep sensitive files encrypted using GnuPG and my private key lives on a Nitrokey Pro (a GnuPG token).

I usually export to various formats with Org mode built-in exporters (mainly ascii, markdown, html and pdf) but I sometimes use Pandoc, especially to export to docx.

I have even started blogging with that system. I can edit an Org file on my phone using Orgzly or Emacs, and then use Termux to automatically 1. push the change to my Git repo 2. publish the files to html using Emacs in batch mode 3. send the html/css files to my website using a bash script and sftp.

I don't think I will ever look back :)

I used StumpWM for a while, but switched back to i3, although I miss controlling my WM with Common Lisp. If StumpWM could implement i3-like window management, I'd be in heaven.

Although I am far for being a good Lisp programmer, I wouldn't recommend introducing Let Over Lambda (or anything about advanced macro programming) too early in anyone's learning curve.

For a comparable price (at least, when I bought them), Common Lisp Recipes might be a far better companion to PCL for an intermediate Common Lisp programmer.

Thank you!

I am interested in designs/technologies that could be viewed as alternatives to the usual tech stack for SPAs, even if these technologies are outdated but exhibit interesting properties compared to what we are used to today. That would include Smalltalk and Delphi yes. Sorry if I misunderstood your initial comment.

Could you provide some links/keywords about these alternative solutions? This sounds very interesting but I don't know were to start.

I use EXWM and it's basically EmacsOS.

Or give Emacs Org mode a try :)

> Slightly related: Almost all my "work music" is wordless, instrumental.

Slightly related to your already slightly related comment: SomaFM's Drone Zone radio channel has really helped me focus in our open space.