Been quite happy with my Razer blade 15, it's not a ridiculously thick laptop, but thanks to extra tall rubber feet, beefy fans and a couple other tricks it's able to run a gtx 1060 and a hexacore cpu just fine under load.
I used to have one of those. Sure it can run all that hardware, but it sounds like a jet engine when it's running. Completely ridiculous design that would never be released by Apple.
The Microsoft Surface Books also have a 1060 inside, but they are whisper quiet.
Note: this isn't just a Bose thing. Bluetooth has separate profiles built in for phone calls/two way audio and one way audio. Because of bandwidth limitations, quality is essentially cut in half while using two way audio. While self-voice can add back some external noise, the bulk of the audio quality loss is built into the Bluetooth spec.
Check out the "better bibtex" extension to zotero for exporting to bib files, I find it helps with unicode/utf-8 characters and might fix that alphabetical problem.
I use this all the time, it's a great way to collect papers about different topics and easily add them to writeups. The option to keep a bibtex bibliography updated in real time is especially helpful. All it takes to add a new source is a single click on Firefox and then just cite in latex/docs/word.
I feel the same way about Fastai v1. Hard to use bits and pieces of it without rewriting everything. Apparently they heard this and addressed it with fastai V2 though so you can just pull in the critical bits you need.
As long as there are market regulations, and as long as people have some kind of morals the market will stay a long ways from being perfectly efficient. Any profit-making trade that you can't make because of legal or ethical reasons shows a crack in the efficient market. That may not be a bad thing, but it's so important that we recognize these imperfections and keep them patched so that they're not exploited.
Came here to post the same thing. Nbdev helps fill in the strengths that IDEs are traditionally good at. Even if you don't use the full nbdev library and templates, the work flow makes sense. Write code in Jupyter, export to a python library, and you can use it everywhere else after that.
One idea for a pain point not mentioned: better variable persistence. If I declare a variable, then delete the cell I declared it in, the variable persists. I've had this cause issues because if I use the deleted variable by accident, it will work fine right up until a kernel restart.
I make a "scratch pad" section of my notebook and work on ideas there. Then once I've pieced together a function line by line and tested it a bit I move it up to where it should be in the chronological order of the notebook. Kind of like your two notebook system but makes copying easier in Jupyter.
I do the same, though it feels dangerous because both the good-copy and scratch sections share the same kernel. JupyterLab works on .ipynb files, and makes it way easier to copy (or drag and drop) cells between different notebooks. One of these days, I plan to switch to JupyterLab to get a sense of what else it offers above Jupyter Notebook.
