I rarely see the classical three-tier architecture in the wild; I frequently see a different architecture.
I don't know this architecture's name. Do you?
The "three-tier architecture" has been the reference pattern for Internet services:
'()[]{}' | |
'(((]))' | |
'](' | |
processClosedBracket('()[]{}') | |
processOpenBracket('paren', ')[]{}') | |
const isOpening = (char) => { |
# <type>: <subject> (Max 50 char, Why is this change necessary?) | |
# |<---- Using a Maximum Of 50 Characters ---->| | |
# |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->| | |
# Explain how the commit addresses the issue | |
# IMPORTANT!! Describe any side effects of the change. | |
# Provide links or keys to any relevant tickets, articles or other resources | |
# Examples: "Jira issue [ABC-123]" or "Closes Github issue #123" |
This document describes methodology & tips for keeping our JS dependencies up-to-date. It assumes we are using classic yarn
over npm
.
Using an automated tool such as Dependabot or Renovatebot can help streamline updates, but there is no substitute for having a reasonable understanding of what our dependencies are, and why we have them.
First of all, it's useful to know the syntax of the package.json
1 and yarn.lock
files. Understanding how to read these can be extremely helpful when trying to determine what version of a dependency is being installed, and to debug potential issues.
### | |
### [2023-06-19] UPDATE: Just tried to use my instructions again on a fresh install and it failed in a number of places. | |
###. Not sure if I'll update this gist (though I realise it seems to still have some traffic), but here's a list of | |
###. things to watch out for: | |
### - Check out the `nix-darwin` instructions, as they have changed. | |
### - There's a home manager gotcha https://github.com/nix-community/home-manager/issues/4026 | |
### | |
# I found some good resources but they seem to do a bit too much (maybe from a time when there were more bugs). | |
# So here's a minimal Gist which worked for me as an install on a new M1 Pro. |
Someone asked in chat (paraphrased) "I am coming from synchronous online systems, and now am going to work on a queue-based system. What should I be aware of?" This is a (somewhat freely-associated) collection of thoughts, based on my experience at SoundCloud.
# When you SSH into a server for the first time it prompts you if you trust the remote server's host key | |
# To validate that they key you received is the same as the server you just logged into you can check | |
# the fingerprint of the host key on the remote server itself. | |
# Output fingerprint of system's host key | |
ssh-keygen -l -f /etc/ssh/ssh_host_ecdsa_key.pub | |
# You can fingerprint both the private and public key from a file | |
# They should both produce the same fingerprint value. | |
ssh-keygen -l -f ~/.ssh/id_ed25519.pub |