You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basic docker-compose with a volume, and bash entrypoint
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
“It does not fully describe the subjective and complicated process of human color vision, it's not without edge cases, but” >>> “color vision, and it’s not without edge cases, but”
I think it would be helpful to number the sections
For the spinach graph, I think having the color spectrum underneath the x-axis could make it easier to see how it comes out as green
“Inside the eye there are three types of cone photoreceptors called L, M and S” could point out that these stand for “long”, “medium”, and “short” since that makes it easier to remember it goes with blue/purple <——> red
Luminosity function graph: label the axes.
“The original V(λ) was eventually shown to under represent our sensitivity at the blue end of the spectrum but that's not too important right now.” YOU CAN’T TELL ME WHAT’S IMPORTANT Maybe change this to just “out
Whoo, more things on GitHub! It’s definitely a step forward, and thorough notes are good. However this immediately comes across as something that would be a pain to get running.
programs must be written for people to read, and only incidentally for machines to execute
— Preface of Structure and Interpretation of Computer Programs textbook
Basically, whatever you put up, you should aim to make it have as much utility to other people as possible. Either they should learn something from the results/non-results, or be able to use the program themselves. Especially for projects you are making within the context of making yourself employable, you have to demonstrate that you will add value to a company, through some combination of competent programming and providing insightful analyses.
Kind of a stream of consciousness thing. Updated at the end of each day starting with Day 1. It's not really edited though perhaps at the end I will make a more focused post about what I thought and got out of PyCon.
Day 0
Seattle
Flew to Seattle from SFO to visit Greg and Diane (and accidentally Alex Anderson). First time flying by myself, and it was pleasingly anti-climactic.
Did the whole touristy thing at the Space Needle and Chihuly glass gallery and Pike Place and the Folklife festival and got loads of grease stains on my shirt at this neat Vietnamese restaurant that gave off a speakeasy vibe because I'm terrible at eating noodle soup. Was kind of woozy from Benadryl the whole time to ward off cat allergies but it was still quite nice.