I had an exercise bike that came with a heart-rate band monitor, but it only pairs with the stationary bike. I wanted to use it for running to show heart rate zones. So I wrote an android app that pairs with the band, gets reading and make some nicer display. I had no idea how to write flutter, or talk to bluetooth devices, but github and chatGPT helped a lot.
> Interestingly enough AWN had this DNS dashboard saved with a filter specifically looking at Facebook traffic. It's unclear why they would be particularly interested in who was going to Facebook.
One likely non-malicious explanation is that the telco is offering some plan with data caps based on social media such as instagram, facebook, etc. Searching around, I found the offering below for unlimited data on 9 social media apps http://www.ais.co.th/one-2-call/simcard/en/super_social.html...
I'm guessing one way the telco implements the selective cap is by tracking user's DNS, and is probably interested to know traffic to facebook
On the first book, see chapter 10 - 12 (on floorplanning, placement, and routing). End of chapter 11 points you to some literature survey as well. But the book itself is somewhat dated (published in 2009)
I haven't read the second book but it's much more recent (published in 2018), it also has chapters on placement, and routing.
>I think we need a ridiculously fast interpreter so that we can skip machine code generation and linking. To me, this should be the default way of running unittest blocks for faster feedback, with programmers only compiling their code for runtime performance and/or to ship binaries to final users. This would also enable a REPL.
I am most excited about this, where a language supports two modes 1) interpreter for development, and 2) compilation for performance. Never thought about this, but reading this, it makes perfect sense on large projects
Matyukevich page on GitHub has lessons with accompanying code to develop a Linux OS for raspberry Pi.
The author goes into kernel, processor initialization, interrupt handling, scheduler, implementing syscall, and virtual memory.
I like his approach for these reasons
1. Minimal workable code,
2. Points you to entry function in linux repo
3. Line commentary of those entry function
Note that it's also a somewhat short read as he focuses on the practical implementations instead of the theory.
I myself was hoping that the author continue developing the chapters on file system, drivers, and networking but seemed to have been on hiatus.
https://github.com/kernyan/HeartRateBandHacking