I'm ok with that! I'm not planning to write an OS, just want to have a programmer's mental model of how an OS works.
1,277 karma · joined August 14, 2017
I'm ok with that! I'm not planning to write an OS, just want to have a programmer's mental model of how an OS works.
I spent a year with Baby Rudin in college, what would you recommend as a replacement fit for self study?
Right. Get that all the time. My solution is to try to condense the useful code built up across different cells into a reusable block, most often a function. Do that while the 'state' is still fresh in your mind and you remember the order of execution.
It also helps to break up a long notebook into sections using headings and markdown cells with comments. I often start by writing down a question/problem I am trying to solve in prose, that makes it easier to recover the context of the code cells that follow.
1. Interactive computation and plotting, run data through a pipeline.
2. Quick prototyping and testing. Once a function/class is ready, it goes into a module, together with some unit tests.
Nothing beats Jupyter for that second use case, 90% of the bugs are squashed through interaction and inspection in the notebook cells, not through unit tests.
If I need a file browser or I want to quickly view two notebooks side-by-side, Jupyter Lab is still more convenient than Spyder. Although it doesn't support all the features of the notebook, and you end up installing additional extensions managed through yarn and webpack (jeez).
What exactly is wrong with it? I use Jupyter daily and find no other Python environment more productive, be it scripts or IPython or IDEs. Granted, I work in scientific computing and use Python for data wrangling and stats. I find immense value in interactivity and iteration speed.
I know a common architecture is JS in the browser making requests to the server and receives JSON and then renders it somehow. Sometime the server renders stuff itself and sends it to the browser, right?
And then there's possibly a database attached to the server.
How does all that work?
1. Head over to physics.stackexchange.com.
2. Sort all answers by votes.
3. Start reading (read the corresponding questions first).
4. Emerge three days later slightly enlighted with a stubble on your face.
5. ???
6. PROFIT!!!
Why does this sound so familiar?