One of the best things about programming is that as you learn more, the possibilities increase dramatically. Each new thing you learn can be combined with so many other things for even more awesomeness. I'm getting ready for my idea-of-the-month experiment, and I'm thinking about the kinds of building blocks I'd like to learn more about and use.
Android development - I can build small apps for myself
Data visualization library like D3 - web-based graphs
Evernote API, so that I can improve my workflow
AutoHotkey - finely-tuned timesavers
Rails 4 - prototyping
WordPress backend - building things
WordPress theming - design
Twitter API, for analysis
Meetup API, for analysis
Google Contacts, Google Calendar, IMAP headers - for analysis
OCR, speech recognition - so I can convert, even at 80% accuracy
Arduino, sensors, and motors - for interfacing with the physical world
Emacs LISP - for personal productivity
PhoneGap - cross-platform mobile apps?
Dropbox API - tools, analysis
Twilio or some other text API - communication
For March, I'd love to dig into Emacs, D3, and maybe Evernote. That way, I can prepare for the Emacs conference, visualize my Quantified Self stuff, and dig into my new brain backup system. :)
Helping people learn is so much fun. I loved teaching introductory computer science. Even though sometimes it was frustrating, it was such a thrill getting people to those "aha!" moments. I speed-read, so it's easier for me to skim through Google results and documentation to spot just the right function. I've made lots of mistakes, so it's easier for me to debug things than it is for people who are starting out. Sometimes all people need is a nudge in the right direction, a snippet of sample code, and then they're off. I get such a kick out of it. It's high-leverage - a little help can go a long way.
Problem decomposition is a key skill: breaking a challenge down into small, motivating steps, identifying the things you need to figure out first so that you can build on top of them. It’s hard when you’re new, and easier when you’ve solved lots of similar problems. I want to get super-good at this, which probably means doing this with more breadth and depth so that we have more building blocks to play with.
I'm figuring out what I like. I like one-on-one sessions and co-working chats more than group tutoring or teaching a class. I don't mind looking at someone's screen using Skype. I'm not an expert, but we can learn together, and I've been told that my enthusiasm is infectious.
What could this look like, if I folded this into my experimental life? Maybe it starts with informal coworking in a shared space, helping people while hanging out and doing my own work. (I might have a "Do Not Disturb" / "Open for Helping with ..." sort of sign on my laptop.) I'm planning to join HackLab.to in March, after my current consulting gig winds up. (I hope the weather will be nicer by then!) More formally, people might book hour-long sessions in a cafe, coworking space, or library, like the way tutors meet with students. I'd get paid in cash (pay-what-you-can) and/or barter. I could offer virtual help, too - e-mail? Skype?
So there’s this idea of code coaching, for those questions that you can't ask on Stack Overflow or on mailing lists, and for learning not just a specific thing but also the process of learning it. Shall we give it a try? I'm open to inquiries about Emacs Lisp, PHP, Ruby, Rails, JQuery, Excel functions and reporting tools, AutoHotkey, Bash scripting, and other things people might want to learn.
I'm a little anxious about the impostor syndrome, but I should just get over that. I confess up front: I'm not an expert in any of these frameworks, especially since most of them move faster than I can learn. <laugh> (You won't believe the kinds of things people are building with Emacs Lisp these days!) I'm always going to be looking things up, because I switch between languages and don't have all the syntax in my brain. I sometimes have to look up how to do basic control structures like a for loop. And I'll tell you if I don't have the foggiest idea how to solve something, but at least I can show you how I'd look for it.
This sort of mentoring is an expected part of teamwork. Who's done this as an independent? Are there things I should watch out for? Will it hopelessly fragment my brain?
Who's interested in exploring this with me? How would you value it, and how do we test whether it's worth it for you and me? Jan/Feb's busy with consulting, but maybe we'll see what this looks like in March, or we'll do low-key coaching for starters...
“Why is your window transparent?” a coworker asked me when she noticed my screen. I told her about how I do my CSS theming, and she pulled another coworker over and made me repeat the explanation. Since that seems like something other people might find handy, here it is.
Sass: Syntactically Awesome Sytlesheets
I rarely do CSS/front-end theming work, but when I do, I try to make it as fun and easy as back-end development. I use Sass (Syntactically Awesome Stylesheets) so that I can use nested selectors, variables, and mixins. This makes my code cleaner and easier to write. You’ll need Ruby in order to install Sass, but the tool will give you CSS that you can use on any web platform.
I prefer doing the initial tweaking in Google Chrome, because I like the way that the developer tools make it easy to modify the stylesheet. The Chrome CSS Reloader extension is handy, too. Most of the time, I make my CSS changes in the text editor, then use the CSS Reloader to reload the stylesheet without refreshing the page. This makes it easy to manually toggle the display of some elements while allowing me to refresh style rules. If I want to figure out the values for a few simple changes, I’ll sometimes make the changes directly in Chrome (you can use arrow keys to adjust values), then copy the values to my Sass source file.
Colors, sizes, and spaces
A second monitor is totally awesome and well worth it.
Designs rarely specify all the colours, sizes, and spacing needed. To quickly get the color of a pixel, I use WhatColor. This shows the hex code for colors, and allows me to quickly copy the code with the F12 shortcut key. If you want to change the shortcut key, the source is available as an AutoHotkey script.
To make it easier to match sizes and spaces, I use WinWarden to make my browser window 20% translucent. Then I carefully position it over my design reference until the important features match. Magnifixer makes it easier to line things up because it can magnify a fixed portion of the screen. By focusing Magnifixer on the part I’m working on, I can tweak CSS without straining my eyes.
When I know I’m going to be making a lot of changes, I use AutoHotkey to map a shortcut so that I can refresh the CSS with one keystroke instead of several. When I happen to have my USB foot pedal handy, I rig it up to refresh my stylesheet.
Sometimes my CSS changes modify other rules. Instead of laboriously checking each page after changes, I’ve figured out how to use Selenium WebDriver to write a Java program that loads the pages in Mozilla Firefox and Internet Explorer, capturing screenshots and numbering them according to the pages in my design reference. This means that I can run the program in the background or start it before taking a break, and then flip through all the screenshots when I get back.
What’s CSS theming without the requirement of browser compatibility? Someday, when I need to deal with more browsers, I might look into Selenium RC. In the meantime, I develop in Chrome, my Selenium-based program makes it easier to test in Firefox and IE, and it’s easy enough to try the URLs in Safari as well. Virtual machines handle the rest of the requirements.
So that’s how I’ve been doing CSS theming on this project. What are your favourite tips?