Thanks for sharing this list, those sound like healthy activities.
Could you share how you're doing those online signing lessons? Is there a specific website, or did you find a personal teacher and get lessons via zoom/Skype? I'd be very interested in hearing about that.
Author here. I know I posted this a week ago, but I've since added more functionality (e.g. the ability to compare countries from the date when the disease reached 100 cases in each country) that should make it more useful, so I hope this is okay. I truly believe this could be a helpful resource for some people (on the Johns-Hopkins dashboard, Worldometers and lots of other sites you cannot easily select and compare countries). I also put some work into making this mobile-friendly. A friend of mine who runs clinical studies said "This is better than every other solution/dashboard out there!", and I'm glad if it helps more people to understand the infection numbers in different countries.
Feel free to provide feedback and improvement suggestions, I plan to add more functionality in the upcoming days.
Shoutout to Ben, py-spy is an amazing profiler. I believe cProfile has certain limitations and doesn't fully understand deep call stacks. py-spy does not have that limitation. It also offers multiple output formats (especially flamegraph and speedscope format, https://www.speedscope.app/) which make it so much nicer to identify bottlenecks.
At our company, py-spy has helped us a lot for our line-of-business application. I'm not affiliated with Ben in any way, but he deserves some praise for his work on py-spy.
I've tried out the Foxy Gestures add-on in the meantime. It turns out it has rocker gestures (called 'chord gestures' in the 'Other Gestures' setup tab) and besides the drawback you mentioned (doesn't work in system tabs) it works well so far.
Firefox used to have the amazing "Mouse Gestures Suite" add-on, which provides scroll-wheel-in-tabs and rocker navigation. Unfortunately with the new Firefox (since v57) it doesn't work anymore, since it uses the old extension approach.
That blog post mentions your featureFlag approach, the initial dogfooding and then the gradual rollout. I'd be very interested to hear on top of that:
1. How did you approach the rewrite on the coding side? What I mean is: Did you just say "Okay, let's start from scratch and use the lessons learned from v1?" Or did you use a specific approach along along the lines of: "Let's structure our code based on these principles and ...?"
2. When you started the rewrite, how did you know in advance and make sure that the rewrite would be faster and have a smaller code-size?
3. Was your focus during the rewrite on a cleaner code base (and the performance improvements followed automatically) or was your focus on speed right from the start?
4. Any other lessons learned during the rewrite? Patterns and approaches that helped/didn't help during the coding?
SEEKING FREELANCER - LOCATION: GERMANY, REMOTE ALSO OK
Kaptio (www.kaptio.com) is looking for a talented developer who's interested in working with Python 3, SQLAlchemy and TypeScript.
Kaptio provides a platform for travel businesses with emphasis on creating developer-friendly APIs and toolkits to extend the Kaptio Travel core application. Kaptio is headquartered in Iceland but development is led from Heidelberg, Germany. Some travel may be required, including at least one fun trip to Iceland!
We are generally looking for smart people who want to solve some complex problems related to travel pricing and inventory. Minimum project length: 6 months, with an option to extend if we like working with each other.
On the other hand, some of the mods' title changes significantly reduce the information content, as for example the title that was changed for that other thread today: https://news.ycombinator.com/item?id=12690853
Originally that title was something like "Microsoft SQL Server 2016 in Docker", which gave some helpful context. But they replaced that with: "Microsoft SQL Server 2016 Express", a change that was not helpful at all, since it sounds like a product announcement of SQL Server 2016 now.
That's one of the pros often mentioned about React. In practice, I haven't found it to be true so far. Once you start using React, you'll almost certainly have to use one the Flux implementations. So let's say you use Redux. Suddenly you also have Actions, Reducers and Stores that you have to learn. If you want to use Async Actions (which is very likely in a web application), you'll probably need Redux Thunk, so that's another concept to understand.
Then there's routing, which is not present in the React core, so you'll need a routing library as well. Again your API surface increases.
In the end, if you want to write a larger application with React, you'll often have a similar or even larger API surface than Angular. I can understand that some people prefer the conceptual model of React (with its focus on Components) over that of Angular. The claims about a smaller "API surface" have always felt wrong to me, though.