EE/CS @ The Cooper Union
From prior experience, I'm not skilled with UI/UX. I'll leave it to the design gurus when possible.
This is also a design choice, because simplicity has its benefits:
While SPAs are great, I think they're starting to become an anti-pattern as they become the norm, even and especially for small academic projects that would do better with much less. Thus I regress.
See: Why are the default LaTeX margins so big?
See the Contact page.
For most others (mostly C-family languages): Linux Kernel style guide.
In general, it will most likely depend on the project or the language (gofmt is a good example of this). When in doubt: agree with your team on an IDE and use the auto-format feature. And when you have a project involving multiple languages: good luck.
80 characters is also a good convention for most code, but gets unreasonable with unstructured data (e.g., markup languages).
1) Golang. 2) Rust.
FreeBSD for experimenting with/learning about the OS.
Arch Linux for average screwing around and speed.
Debian for overall stability and support.
Desktop: Nvidia GT740. i7-2600. 8GB DDR3. Debian 10 w/ xfce4. 120GB SATA SSD. Some average Dell keyboard.
Laptop: Acer Aspire Spin 3 (~2017?). i7-7500U. 12GB DDR4. Arch Linux w/ xfce4. 256GB NVME SSD.
Server (NAS): FreeNAS (FreeBSD 11.3). 4GB DDR3-1600. 8GB DDR4. ZFS mirrored 2x3TB 7.2k SAS.
Server (for other shenanigans): FreeBSD 12.1. 4GB DDR3. 120GB SSD.
If the webpages look inconsistent (e.g., the navbar is different between pages), this is likely due to caching by the Fastly CDN. Sit tight for a few minutes or (for the impatient) add a query parameter. There shouldn't be any other errors except 404, since everything is static. (This is not true of the
files subdomains -- please contact me if you see errors on those sites.)
If in doubt, feel free to contact me.
© Copyright 2021 Jonathan Lam