Phil Shapiro was kind enough to post a very nice review of my book, Learn Linux in a Month of Lunches.
The review is here:
More of his greate reviews are here.
Desktop Linux for Everyone
Phil Shapiro was kind enough to post a very nice review of my book, Learn Linux in a Month of Lunches.
The review is here:
More of his greate reviews are here.
Manning has been offering DRM-free eBooks for nearly two decades. Starting in 2000, we were one of the first tech publishers to offer unprotected PDFs, and we’ve since added Kindle and ePub formats for all new MEAPs and eBooks.
Reading this entire statement reminded me I’m very proud Manning published my book.
My publisher created another slide deck from Learn Linux in a Month of Lunches. There’s also a discount code for the book. I’m not sure how they arrived at a 42% discount. Maybe double blackjack?
My publisher has a nice 42% discount on my book. It’s ssllinux over at manning.com.
My book is finally out in print! And I honestly think it makes a great gift for someone looking to take the leap into Linux.
An essay, by me, on why we need to spend more time thinking about how we use personal technology:
You can spend months choosing an outfit you might wear just a few times, and minutes choosing an interface you’ll use for hours a day for years. A lot of that is because technology isn’t considered changeable or personal. Free and open source software users know technology is both.
A post about using Linux to play with Tilde Clubs.
I don’t think anyone will be surprised to learn I’m a fan of the desktop environment concept…
I got this note a while back. It’s a great question and now I’m finally able to address it!
“It’s been about a year since your interview article about using Linux and Open Source for writing and publishing. Is there any chance you might consider a follow-on piece that talks about what has happened, what you have learned, and such during the past year? Also, much of the webliography that addresses Linux, Open Source and writing talks about “I have content. Let’s package it into the wild.” Talk about the front-end work flow: “I have facts. Let’s create content.” Notes, references, etc.“
As you can see, the answer to how I handle front-end workflow is paper. When I’m working on more scholarly work, I still print out articles and mark them up. In fact, I’ll often type an outline, print it, and then write on it as I work. There’s just something about the pen on a page that makes it easier for me to connect ideas. From the outline, I just type into a text editor. Any parts or pieces I feel I’m missing get flagged in the text as a note to myself. And any sections that need additional research get put into Remember the Milk for follow-up. I also use RTM to track ideas I want to integrate into an active piece. I use Google Keep to track ideas for pieces before I start writing, but once I’m writing, I don’t really use it. In fact, I usually just copy-and-paste my Google Keep notes into a text file and just work from the text file.
In terms of teaching Linux, this meant presenting options to the reader, but not always having a “right” way to accomplish a task. For instance, if you want to copy a bunch of files, you can do it via the command line or through the file manager. Both methods are valid. Both have advantages given the situation. But I’m trusting the reader to make sense of how to apply what they’re learning. They learn the skills and then reflect on how to deploy those skills.
I wrote this for Medium and I’m pretty proud of it.