Skip to main content

School and Chromebooks

 This year schools shifted to remote learning because of COVID-19. Before the semester started, our school district planned on a hybrid approach, where students attended schools physically a couple of days a week, and studied from home for the rest of the week. The thinking behind the plan was to balance the students’ exposure vs the benefits of in-person learning, however as the virus situation did not improve by the school start, the district abandoned the plan and opted for a full-time at home learning schedule.


Before the school started, my plan was to have the kids use their iPads to access their learning materials. They were comfortable with their iPads, knew how to use a web-browser, and switch between applications well. As school start neared, I started thinking that they would benefit from a bigger screen, and a decent physical keyboard, so I began to look for reasonably priced laptops that would do the job. As I started looking late, and I think a lot of parents had  similar ideas, almost all the laptops that I wanted to get were out of stock, with a month out expected delivery time. 

A friend recommended looking at Chromebooks instead. They are reasonably priced, and powerful enough for schoolwork. They have touchscreens, and good keyboards, and more importantly they are well integrated with the Android system and have good parental controls. I gave it a try and searched online for reasonably priced Chromebooks.


Again, most were out of stock, but I was lucky to stumble upon the Acer Chromebook 15. At $350, with reasonable memory and disk storage, a touch screen, and a keyboard, it was a good deal. And luckily it was in stock and shipped in 2-days, just in time for when the school started.


When it arrived, I was impressed with the build quality for the price, and the features the laptop had. Setting up Chrome-OS was a breeze, and when I used my son’s account for the laptop, Chrome-OS automatically enabled Parental Controls, tied them to my Google account, and Parental Link app. App purchase approvals were a breeze afterwards.


Next, I installed Microsoft Teams—the school uses that for classes, video conferences, and homework submission. I prefer having the application installed, instead of using the web-based application, however after a couple of tries, my son ended up using the web-based one. On the iPad, he became familiar with browsers, and switching between tabs felt more natural to him, and that carried over to the Chromebook.


It has been a couple of weeks now with the Chromebook, and everyone is happy. The battery life on the Acer is great—about 12 hours on a single charge, with good usage during the day for video conferencing, and educational games. The CPU is reasonably fast, and the thing is always on, so booting up is instantaneous. I forgot how satisfying that feeling is, when you want to do something, open the laptop lid, and you’re instantly ready to go. Perhaps I am justifying getting one for myself.


Comments

Popular posts from this blog

Kindle Paperwhite

I have always been allergic to buying specialized electronic devices that do only one thing, such as the Kindle, the iPod, and fitness trackers. Why buy these when technology evolves so fast that a multi-purpose device such as the phone or a smart watch can eventually do the same thing, but with the convenience of updates that fix bugs and add functionality? So, I was shocked when this weekend I made an impulse buy and got the newest Kindle Paperwhite—a special purpose device for reading eBooks. I was walking past the Amazon store in the mall and saw that the newest Kindle Paperwhites were marked down by $40 for the holidays. The device looked good in the display, so I went in to look at it closely. The Paperwhite is small and light, with a 6” screen that is backlit and waterproof.   The text was crisp and readable, and in the ambient light, it felt like I am reading a printed book. I was sold and bought it on the spot. At home I have struggled to put it down. The bo...

A paper a day keeps the doctor away: NoDB

In most database systems, the user defines the shape of the data that is stored and queried using concepts such as entities and relations. The database system takes care of translating that shape into physical storage, and managing its lifecycle. Most of the systems store data in the form of tuples, either in row format, or broken down into columns and stored in columnar format. The system also stores metadata associated with the data, that helps with speedy retrieval and processing. Defining the shape of the data a priori, and transforming it from the raw or ingestion format to the storage format is a cost that database systems incur to make queries faster. What if we can have fast queries without incurring that initial cost? In the paper " NoDB: Efficient Query Execution on Raw Data Files ", the authors examine that question, and advocate a system (NoDB) that answers it. The authors start with the motivation for such a system. With the recent explosion of data...

A paper a day keeps the doctor away: MillWheel: Fault-Tolerant Stream Processing at Internet Scale

The recent data explosion, and the increase in appetite for fast results spurred a lot of interest in low-latency data processing systems. One such system is MillWheel, presented in the paper " MillWheel: Fault-Tolerant Stream Processing at Internet Scale ", which is widely used at Google. In MillWheel, the users specify a directed computation graph that describe what they would like to do, and write application code that runs on each individual node in the graph. The system takes care of managing the flow of data within the graph, persisting the state of the computation, and handling any failures that occur, relieving the users from that burden. MillWheel exposes an API for record processing, that handles each record in an idempotent fashion, with an exactly once delivery semantics. The system checkpoints progress with a fine granularity, removing the need to buffer data between external senders. The authors describe the system using the Zeitgeist produ...