I read so many docs when I was trying to implement OAuth and got more and more confused. This video was a huge help though for explaining all of the concepts:
We use poetry just for development, but run Docker containers in prod. When the image gets built we just create a requirements.txt (poetry export --format requirements.txt --output requirements.txt), copy that into the image, and pip install. Because this is built using the poetry lock file, it'll always be exactly the same unless we specifically update something with poetry.
I used to work at a place that was just using requirements.txt files that only included our direct dependencies. There was a project that needed updating after not being touched for a couple of years. The requirements.txt didn't change, but when we built the project again, some of the transitive dependencies used a newer version, and a bug was introduced from one of those updates. A bunch of time was wasted tracking down the issue, pinning the old version of the transitive dependency, and figuring out the damage caused by the bug.
As a result, the requirements.txt was changed to also include transitive dependencies. We had vulnerability scanning on our code, and it found a severe issue with one of the transitive dependencies, but there wasn't a version of that library with the issue fixed yet. Time was spent looking into this to see how we could be impacted. As it turns out, it was a transitive dependency for a library that we no longer used and removed from the project months ago. When you create your requirements.txt by running pip freeze > requirements.txt, you don't have an easy way of knowing which library requires which transitive dependency.
There's ways you can fix this using multiple requirements.txt files, but at that point it's a lot easier to use poetry, especially if you want to keep your development dependencies separate.
Oh, this segues nicely from my DST, my favorite bikeshedding topic into my second favorite one!
Base 12 is better than decimal in every way. It divides cleanly by 1, 2, 3, 4, 6, and 12. Compare that to decimal, where you have 1, 2, 5, 10. It's much better for scheduling. With decimal you couldn't have a nice, clean schedule for a factory with 3 shifts per day for example. 60 minutes (which is a multiple of 12) gives you a lot of ways to break up an hour, vs 100 minutes.
I had a friend once rant about how we should switch everything to base 12. It's obviously crazy given the effort vs reward, but I think we would have been better off to have done so way back when.
Yup, I'm a big believer in applying the rule of three ( https://en.wikipedia.org/wiki/Rule_of_three_(computer_progra... ) for moving code into a library as well. I find if I create an API with just one or two examples in mind, it often doesn't turn out to be as general as I thought it would be. By the time I've done something three times, I have a much better idea of what the different use cases will be.
Me too! I spent Christmas there many years ago, and every person I talked to asked:
1. Are you going back home for Christmas?
2. No? Oh are you going to get a Christmas cake from KFC?
I was like, Christmas cake? And why KFC specifically? My confusion confused them just as much. Maybe they later thought it was because I was Canadian so it must just be an American thing.
I wish more companies had this, it's really useful.
I looked into applying at Gitlab, but was able to easily find out their location adjustment and avoided wasting my time or theirs. Unfortunately they pay less in a high cost of living Canadian city than for someone living in Alabama.
Just wanted to thank you for this. When I was a lost and confused junior, I had no one more experienced around to ask for advice. I stumbled across this and it answered so many questions that I had, and it still very much applies many years later.
Magnetic tape is still used in recording, but for the distortion it adds rather than concern about quantization. In fact, the audio is simply routed through the tape machine, then into a computer for storage.
Distortion here means both extreme distortion (e.g. clipping) which is what people often think of when they hear the word "distortion", or the more technical definition of any alteration of the input signal. The pre-amps, compressors, and so on will all add their own distortion to the signal. However this is desired distortion. Tape offers some of this, although I'm not familiar with what its exact characteristics are.
Clipping (when the input signal amplitude exceeds the limits of the storage medium or output device) is a type of distortion that can sound great or absolutely awful.
Digital clipping sound awful. The max amplitude is all 1's in the digital storage medium. When a signal exceeds this, for the duration of it exceeding every sample will have that same value of all 1's. The waveform will basically have the top lopped off. There will be sharp "corners" where it starts to clip, and where it stops clipping. Those corners create "pops". It makes that part of the recording unusable.
Analog clipping can be a very sought after sound though. The max amplitude on tape is when all of the poles of the magnetic material are aligned. This isn't perfect though and it's not instant, so you get a slower compression of the signal and some variation. The waveform will look like its top has been squeezed downward. This can sound amazing.
The quality on youtube is pretty bad (spotify or elsewhere is better), but this song has a great example. You can hear his voice distort in many places, but it sounds wonderful (particularly starting around 2:20 - 2:40 and 3:10). https://www.youtube.com/watch?v=wAGS8UL9b6A
From what I understand, shipping containers are sent out from Asia stuffed with goods, but there isn't nearly as much going in the other direction. The containers need to go back whether they're full or not, which is why it ends up being so cheap to ship plastic. And the CO2 caused doesn't really change as a result.
To the rest of your point though, I agree. My wife is a hardline recycler. I generally am too, but I have a hard time seeing the benefit in recycling soft plastics.
You "make" a loop but "take" a bight, as unhelpful as that may be. A loop is a step in making a knot, where as a bight is just a handful of rope somewhere in the middle of it.
You can tie a regular bowline, or a bowline on a bight. The same knot will need a different technique for tying on a bight, since you can't pass the ends through. When you tie a bowline on a bight, first you take a bight, then you make a loop.
Named after a region where the company's founder adventured down to in a Econoline van and made a first ascent up Cerro Fitzroy, which is part of the mountain range shown in the company's logo. It would be worth taking a read on his history https://en.wikipedia.org/wiki/Yvon_Chouinard, the man is an absolute giant in rock climbing and alpinism.