You will need to root it. It’s running a very custom android. There is a good documentation about it. Look for DPTTools.
But if you want a epaper tablet with the play store (and certified) look at the BOOX ones (note, air or Lumi). You can install the play store and download the official kindle app.
Some says that BOOX has questionable GPL practices and does some api call in China (might be just telemetry), check in this forum for opinions:).
Damn! I checked the reviews of the Quaderno Gen 2: I am strongly considering this one!
The build quality of the RP1/CP1 is so good (the texture of both the screen and the back is a delight), i hope it feels the same on the Fujitsu.
I’ve got the boox note 3 color for my partner.
It’s 7”, a bit small for me but it’s pretty good.
She loves it but after couple of months she used only the black ’color’ and doesn’t bother to switch to other colors.
I’ve been using a Sony Epaper notebook for almost 2 years now and considering buying a Boox Note 5 or Air 2 (the remarkable didn’t make my short list)
They are running almost stock android and the quality seems better than remarkable.
I’ve watched My Deep Guide (https://youtube.com/c/MyDeepGuide) where they test every single feature of all note taking devices.
This article says that you have root access on the remarkable, but doing so will void the warranty.
Disclaimer: Googler here.
There are many ways to land a job at Google:
1 - work somewhere else then after couple of years of xp in a field try to find a job opening that matches your xp (that’s how i got in).
2 - if you are in Uni, apply for internship. We always welcome interns.
3 - apprenticeship: there is a program so that you can start working after college. I know some people went this route and are now full time employees.
4 - other ways like PhD etc...
Bottom line is: you don’t need a fancy uni (I did a state uni in france). What’s important is that you are good at what you do and you do it for yourself, not just to work in a FAANG company.
Tips:
Skills that Google is looking for: critical thinking, collaboration, communication, analysis of trade offs and being a genuinely nice person.
Books that got me into Google:
The Algorithm Design Manual by Skienna
Grokking Algorithms by Aditya Bhargava
Full disclaimer: I am Mauritian and work in the UK. I am happy about the regognition in the UN and the ICJ’s decision even that it is quite late and a lot of Chagosians already suffered a lot. I would say the Mauritian Gov is interested in the fishing rights provided by the islands which is critical for us. I would like to see .io domain be given back to a Chagosian association and let them use the income from it. It could be used to develop transport to the island and resume coconut farming, fishing, tourism...
I would like to see more pressure being applied to UK, because to be honest i don’t see them doing anything and just do like they always did so far, ignore ans delay any actions to be done there.
Ps: the Gigaom acticle about it is great to understand the situation.
Pss: the US has no need for a base there, their base in Bahrain and Qatar are much closer to their illegitimate war interests.
All these comments are good. Also ALWAYS watch out for 'Quick Win': When you do something quick and dirty, mark it up for 'refactoring' (i.e. Tech Debt). When your list of quick and dirty builds up, go and clean it. Do not accumulate tech debt, try to keep it low otherwise you will pay full price later (examples up here).
Another great tip that saved me from tons of refactoring: "The wrong abstraction is worse code duplication". Meaning sometimes duplication of code is better than trying to create the wrong architecture (as long as you mark it in your quick and dirty list).
I tend to learn new things with the objc.io videos (paid subscription to all video. Worth every cent/penny)
I also subscribed to the iOS dev weekly email by Dave Verwer.
nshipster has great content. Also following the right people on twitter leads to great articles.
I tend to avoid medium article as there is a lot of noise about the “cool-new-thing-that-everybody-should-do”.
If you want to get into iOS programming, find an app that you like that seems easy enough and try to recreate it. Also don’t follow blindly random tutorial. Try to understand what you are trying to achieve and how other (more than one) people solved it.