Tag: google

Linux on the Desktop: Google Pixelbook Edition

Posted on by Scott
A friend of mine recently shared this post in our Slack group marking 2022 as the year of Linux on the Desktop.  While my own days of running Linux of self-built PCs are long gone, I’ve toyed with the Debian Linux distro occasionally since buying a Google Pixelbook back when the first came out in 2018.  I walked through post like this one explaining how to set up on Pixelbook for dev work.  I played a bit with some Go code.  But outside of those brief detours, I pretty much stuck to using it as intended.
I don’t recall why Google was selling them for $300 off back then, but $699 was an easier price point to rationalize than $999.  Though most of the mobile devices at home and some of the stationary ones are made by Apple (work and personal MacBook Pros, various sizes of iPad for myself and the twins, iPhones and watches for my wife and myself, and Apple TVs), I get a lot of use out of the Pixelbook.  The form factor makes it better than the iPad mini for watching streaming video (which came in handy numerous times when in-laws were in town and all the TVs in the house were occupied).  The keyboard and trackpad make it a capable device for web browsing, email, and social media.  It’s a great device for travel–pre-pandemic I took it on a work trip as a second device since I’m very strict about keeping work things and personal things separate.
Despite all these pluses, Google cancelled the Pixelbook earlier this year (not unlike many of its other projects).  It will get support through mid-2024 (it’s successor, the Pixelbook Go will get support through mid-2026) but that’s it.  Certain apps I used to be able to install and upgrade from the Google Play store (like Slack) have stopped releasing new versions for ChromeOS.  The aforementioned Linux distro came in handy when I got tired of using Slack in the browser.
I found this article with instructions for how to install the Debian Linux version of Slack.  Of course, the instructions didn’t work for me because it had been forever since I’d updated the Linux distro on my Pixelbook.  Following the fix problems with Linux device instructions took care of that.  But once I got Slack installed, signing into the browser didn’t redirect me to the app.  More searching yielded a Reddit thread, which said I needed to install the Chromium browser on Linux for the activation link to work properly.  So I followed these steps to install Chromium.  Now I’m back to running Slack as an app (instead of just another Chrome tab).

Can Google Find You?

Posted on by Scott

Recruiters use Google.  Whether you’re actively seeking a new job or not, it’s important to use this fact to your advantage.  My friend Sandro gave me this advice years ago, when he told me to put my resume online and make it “googleable”.  For me, the result was contacts from recruiters and companies I might never have heard of otherwise.  In addition to putting your resume online, I would recommend blogging about your job–within reason.  Definitely do not write about company secrets or co-workers.  Putting such things in your blog doesn’t help you.  Instead, write about what you do, problems you’ve solved, even your process of problem-solving.  At the very least, when you encounter similar challenges in the future, you’ll have a reference for how you solved them in the past.  Your blog post about how you fixed a particular issue might be helpful to someone else as well.

There are many options available for putting a resume and/or blog online.  Sandro hosts his, mine, and a few others on a server at his house.  But for those of you who don’t have a buddy to host theirs, here are a couple of readily-accessible free options:

There’s a ton of advice out there on what makes a great resume, so I won’t try to repeat it all here.  You can simply put a version of your 1 or 2-page Microsoft Word resume on the web, or you can put your entire career up there.  Having your own blog or website means you aren’t subject to any restrictions on length that a site like Monster or CareerBuilder might impose.  Consider linking your resume to the websites of previous employers, technologies you’ve worked with, schools you’ve attended, and work you’ve done that showcases your skills (especially if it’s web-related).  I don’t know if that makes it easier for Google to find you, but it does give recruiters easy access to details about you they might have to dig for otherwise.  Doing what you can to make this process easier for them certainly can’t hurt.

Figuring Out Google Wave

Posted on by Scott

I recently received an invite to Google Wave (thanks Rory).  From the few minutes I’ve played with it so far, it seems to be Google’s next offering in collaboration (Google Docs is probably their first).  I’ve still got some spare invites, so send me an e-mail if you’re interested in trying it out.

One of my bosses from a previous company came across a couple of links that explain Google Wave:

http://lifehacker.com/5272048/google-wave-is-what-email-would-look-like-if-it-were-invented-today

http://lifehacker.com/5395376/the-complete-guide-to-google-wave-is-a-comprehensive-book-on-wave

I’ll probably be checking these out when I have time (if I’m not distracted by other “oooo shiny” toys, or life in general).

Don’t forget to Google prospective hires

Posted on by Scott

One of my colleagues reminded me of that today.  The developer we’re interviewing tomorrow was the #1 result from Google when I searched on his name, thanks to his blog.  This works a lot better with uncommon names, of course.

My name (Scott Lawrence) is fairly common, so it’s only the #6 result on Google.  The result is probably that high because one of last month’s blog posts referred to Scott Hanselman.