Programming and reading.
Not quite correct. For html, that is to signal standard compliance, you can leave it away and the browser will still handle it. For the bash one, all (most) shell scripts use .sh, so you need to give a shebang to tell the loader which executable (sh, bash, zsh, csh, ...) to use
Also on Linux xdg does take file extensions into account, just executables do not
We do, for two 2-3 person projects, where no code reviews are done. This is mostly because (a) it's "just" a rewrite and (b) most new functionality is small and well-defined. For bigger features a local branch is checked out and then merged back later. Commits are always up-to-date, which makes it much easier to test integration of new featues.
With git. Every time we start work, we pull. After every commit, we push (and pull/merge/rebase) if necessary.
Can confirm, I'm using a dock (from Razor) daily without problems. Hot switching doesn't work though, you need to restart X/your display manager to connect or disconnect the eGPU. I'd recommend the gswitch utility to configure the graphics card to be used (on X11). Haven't tested much on Wayland, but I know that at least Gnome (Wayland only) has trouble mixing eGPU and the internal display if that is important.
I use it for everything, because I connected my external monitors through the eGPU. https://wiki.archlinux.org/title/PRIME has a few methods for running only selected applications via the eGPU, but I haven't tried them. Edit: See also https://wiki.archlinux.org/title/External_GPU#Xorg for eGPU specific setups.
streaming small commits straight into the trunk
The image even calls it like that
Some things don't have good CI/tests, so it doesn't make sense to include the build step, especially on a small team where we trust each other. But yes, it's not good practice, and we don't do this on every project, but sometimes it's necessary to adjust the flow to the specific project
It'sintended to be used when the cookies are actually required for the app to work. For example, to preserve your login, you need a cookie, no way around. Unfortunately, as mentioned by others, it's often abused
Usually we don't distinguish between many2one and one2many, since it's the same just viewed from the other entity.
There is one more class though, which is one2one. That is, the entities have a direct relationship. Sometimes this also includes the case where you have zero or one, i.e. the relation is optional on one side. This can be accomplished with an FK plus unique constraint or by merging the tables.