Netbook development


I'm looking for a laptop for side-projects, mostly server-side.

I've been using a Web-based editor at work, which makes my Macbook feel like a glorified netbook.


The 15" Macbook is great, but $2500 is steep for my needs. I think an actual netbook would be sufficient, but I have little experience w them.

I like Chromebook's simplicity. The Pixelbook seems well-designed, but it's pricey. Looking around, $500 seems like a reasonable experiment.

At this point I'm looking for a Chromebook with:

The Acer Chromebook 14 is highly rated on Amazon, provides 4GB ram, 32GB storage, USB 3, Wi-FI AC, HD video, supports Android and costs ~$300, and I can pick it up immediately at a local BestBuy, which provides a surprisingly nice Instacart-like experience.


Acer is the genus of trees containing maples :) 🍁

The keyboard, esp the space bar, is flaky compared w a mac. (On the upside, it's improving my touch-typing :)

After using the chromebook for a few months, 4GB is just enough. It's great for having a few Chrome tabs open. But jumping between a dozen, esp email and slack, with a few different apps running, esp video conference, pushes the limits.

Android interop is great, but not all apps work well. For example, 1Password is fine, but Slack is crashy. Also, not all apps are compatible, ie just because I have an app on my phone doesn't mean it can be installed on my chromebook. I'd guess the same would be true with a tablet.

Dev machine

Now that I have a screen, keyboard and internet connection, I need a machine to develop on. Cloud9, which layers a Web-based IDE on EC2, is good, but lately I've just been using an Ubuntu instance on Google Cloud.

This whole plan of using a chromebook + cloud really shines wrt dynamic resource changes, ie as compared w upgrading hardware. I've been playing around with large data sets recently using Anaconda, and ran out of storage with the default Cloud9 configuration (8GB). Upgrading the EBS "volume" to 16GB was fast and easy (once I found it):

  1. open the EC2 console
  2. stop the EC2 instance created by Cloud9
  3. in the left column, find Elastic Block Store > Volumes
  4. ctrl click on the volume and select modify


Google Cloud Shell (or Cloud9's shell) makes it easy to create SSH keys I can use to access VMs via Secure Shell (with "open as window" enabled, so I can use ctrl-w and have more conventional alt-tab navigation).

Here's what worked for me:

  1. Use the shell to generate an SSH key pair:

     ssh-keygen -t rsa -b 2048 -v -C "erikeldridge@ubuntu.gcloud" -f admin
  2. Enable read permissions on the private key (so Secure Shell can read it):

     chmod 400 admin
  3. Download both keys (copy/paste to local files)
  4. Create a new VM, copying the public key created above into the settings, and start the VM
  5. Grab the external IP from the VM console. (Note this changes every time the instance stops.)
  6. In Secure Shell, specifying the user (eg "ec2-user" on EC2) and IP copied above, and import both the public and private key. (The identity field should change from "default" to the key name, eg "admin".)

It took me awhile to figure out how paste text into Secure Shell: two-finger tap.


EC2 distributes private keys (corresponding with public keys on VMs) via .pem files

Several people have documented the process of generating a public key from the private key.

Source control

Storage-backed VMs, like Google Cloud's and EBS-backed EC2, maintain state, so public keys are durable for use w source control hosts like Github, BitBucket, etc.

Create a new SSH key pair with the default "id_rsa" name for each VM that needs to connect to a host, and add the public key to the SSH settings in the host.

Remote desktop

For apps like Android Studio and VSCode, I need a desktop.

  1. Install Chrome Remote Desktop chromebook app.
  2. Follow the Google Cloud workstation notes to install enable CRD

Development HTTP

I like using JavaScript for prototyping ideas. Given we're just working in Ubuntu, running a server is standard. We just need to open a port to call the server

  1. Create a security group with a "Custom TCP Rule" exposing port 3000
  2. Add this security group to the VM
  3. Note instance's external IP
  4. In browser, load IP with scheme http and port 3000


Thoughts? Suggestions? Hit me up @erikeldridge


Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 International License, and code samples are licensed under the MIT license.