I feel that dd is never the correct tool to write to SD cards. At least cp can figure out the block size itself. Or the more elaborated bmaptool can even skip empty blocks which are often found in disk images.
I live near a major university that has as many as 4 fablabs listed. All of them is reserved to students. If you are an outside "thinkerer", you need to pay something like 400€/month to show up and use a soldering iron. Sometimes there is only a "contact us" form where you can ask for a quote! These efforts are completly sterile. Students have free access, but nobody from the outside world of the university to learn from.
I had access to a local hackerspace during my studies that was 100% run by volonteers, without any university involvment. It was glorious. I sat next to software and hardware professional doing amazing projects on their free time.
I guess I still have to tinker on my own instead of sharing it with people eager to learn in a common space. I think that somehow big universities actually prevent such spaces from emerging by creating their own sterile initiatives.
Conversations [1] is the best Android XMPP client I know. IIRC they pushed the adoption of OMEMO and implemented it first, before the desktop clients could catch up.
The other counters on the page are updating after each refresh. I think only the ICMP counter is broken. The IP address points to a Norway provider. I do not think there is a CDN, elsewise the counters would be frozen.
Worse, stalebot makes it looks like the project has no issues nor known problems. Issues should be closed either with "wontfix" or let open if they detail a real bug that others may stumble upon. In the end, I agree that it takes time to do that, and who am I to dictate how people spend their time.
Maybe the best solution would be to completly disable issues and PRs on Github. Still better than having to deal with stalebot. At least you know what to expect: external solicitation is not welcomed.
> Data structures and algorithms: We used a dictionary instead of a list to go from O(S) to O(1) operations.
The list in TFA is so small that I wonder at what point creating a hashtable is more economical than going through a 9 items arrays. In C, accounting for allocations, etc. I would not be surprised that strcmp on an static array would be faster.
As always, measure with benchmarks (which does the article, but not on array vs. hashtable). In theory, O(1) is better than O(N). In pratice, with memory allocations and all, the order of magnitude of N plays a role.
Anyways, I would have used a hashtable also to convey the idea that I only want to check if the item is in the list. Python makes this easy. In C, I would have used an array unless N is "large enough".
Reddit is already aggressively pushing for users to go to their official app when browsing on mobile. I would not be suprised that custom-made apps will be more limited in the future, up to the point of being pointless. Twitter did it. Reddit may do it (only allow read-only as a first step?). They also may disable old.reddit.com at some point. Enjoy the ride while it lasts.
This also explains app size, IMO. Querying an API and displaying remote videos/images should not require 40+ MiB Android apps. I think most of the app size is the tracking code that analyze how much time you glare at ads.
> You may also look into Kernel Programming for a lucrative systems programming career.
This is the road I have taken since I started to work professionally, but I yet have to find a lucrative job. I know that I am paid more than microcontroller devs, but less than web devs. The market for kernel developers is not that big either.
Because Python pays more. Or Javascript. Or Ruby. More demand, more salary. Apart from finance, pay is lower than web languages. And finance is small. Embedded systems programming, that also uses the language, pays 30% less than web jobs from my last job hunting period.
Employees may be leaving the embedded space (and C++) for web tech because of this. This is the feeling I get from my local job market (western Europe). Maybe as the old timers retire, job offers will align? Who knows.
Initially, I learned it for fun and ham radio emitting. But I find it fascinating that you can use it with anything that can be turned on and off with a rythm.
I used a flashlight to say "hello" while waiting for a fireworks event, but the other person far away just blinked their flashlight randomly in response.
I guess it could be used for worst scenario speech, like blinking eyes for examples if I ever have a terrible accident somehow (has been used by tortured persons, see https://www.youtube.com/watch?v=WZ256UU8xJ0). When I saw Tuco’s grandpa in Breaking Bad taking so much time to write words with his bell, I just tought about using morse (but with something more elaborate than a bell, because you want to use long and short tones; same problem applies if you want to knock on walls or doors).
At $internship I developed a network router with something like 32 or 64 MiB of RAM. Basically configuring iptables, some routes, QoS, etc.. with a bunch of bash scripts, systemd units and custom drivers.
You do not need a lot of RAM for such applications. When running, the system was using 24 MiB of RAM. So, plenty left!
Edit: I am currently playing with NanoPi Neo that has 128 MiB of RAM and I never ran out of for small applications.
Having to program down to the bit (not byte) sparks a little something for me. I feel proudness in the craft, even if this is a bit (pun!) far frow nowadays’s constraints.
I just learned the hex decades (1, 16, 256, 4k, 64k, 1M, 16M, 256M, 4G…) and now if I need to generate a 1M empty file I know that `head /dev/zero -c $((0x100000)) > 1M.bin` would do without having to multiply 1024 three times. This kind of little things. :)
Nevertheless, it can still be useful if you write Linux device drivers or some other low-level tasks. Microcontroller programming, too, but without having to buy them in the first place (MCU shortage…).