JKirchartz

Web Monkey n'at

VIM quick-start, cheat-sheet, and links

If you've been following me for a while, you might know my editor of choice is VIM, it's very clean. There's nothing there to get in your way, except your own limitations, and those limitations can be destroyed through practice. Havn't tried vim yet? What are you waiting for?

Vim is a text editor written by Bram Moolenaar and first released publicly in 1991. It is commonly found on unix-based operating systems. VIM is based off an older text editor, vi, and it's name is an acronym for Vi-Improved. With vim Your fingers never have to leave the keyboard to command great power. The learning curve is a little steep but you can very quickly pick up new skills as you need them. The basic premise is that there is an Input mode and a Command mode. By default you start in command mode, here you can move around the document, search, and do a fair bit of editing quickly. Insert mode is designed for adding (and removing) text, it's just like a normal text editor.

Quick Start/Cheat Sheet

From the Command Line

Working in VIM

VIM Commands

VIM tips

Going Further

Vim is highly customizable, you can set shortcuts and preferences in the .vimrc file, usually located in your home directory. There are a ton of plugins (aka scripts) available too. They're easy to manage with other scripts like Pathogen or Vundle.

If you want to get a headstart, my dotfiles are available on github, but there are a lot of people doing that lately, for example there's a very nice VIM Distribution named Janus that's worth a look.

Links

RIP Google Reader

Google unceremoniously killed Reader. It was fun while it lasted, but you knew it was going to happen. I've been using Reader to keep up with my feeds for a long time; sometimes ignore them for weeks, but still skimiming for the best. The closure was hardly the hardest part. That respect does to when Google originally decided to start damaging Reader with a redesign in late 2011. This redesign brought in the new Google black bar, and partially replaced the social aspect with Google Plus. Up until then you could share articles with your friends, if they actually wanted to see them. It was great for discovering things from new perspectives, and for trading the best feeds to follow But G+ never really filled the gap. It was a separate entity and integration into Reader went out the window with this announcement. Google Plus won't be filling in any other gaps either.

The major losses here are in China & Iran where it was being used to circumvent oppressive regime's policies, so I can hardly compare my plight.

So now to fill this new hole in my life, there were a few solutions offered as replacements that I tried.

I think I've found my man here with Feedly, I'm really enjoying it and the learning curve from Reader is nearly non-existent.

Why I Stopped Designing in Photoshop

When I was learning design I was glued to photoshop. Touching every filter and tool, researching customisation and automation. Working hard to improve my skills, and learning all the tricks and etiquette, but it was hogging my time. It was all fluff, web browsers don't care about your layer-naming scheme or how well you use smart objects. The web is open, free, and unpredictable; Photoshop is none of those things. It's a monolith of photo manipulation and drawing tools, it exists purely for creating and improving stunning images. It's not a web devlopment tool, it's a graphics tool, and you should always use the right tool for the task at hand.

PX

Everything you do in Photoshop has to be pixel-perfect, snapping to the pixel grid ensures jpegs are crisp and don't have any jagged edges or odd artifacts. Only one small problem: on the web, there is no such thing as pixel perfect. There's just no telling what a pixel will be on the end-user's screen. When using viewed at smaller resolutions set pixel values don't change, so if you have a combined total of 960px of margins, padding, and images on a 320px wide screen you're not giving the user the best experience. There's another bug when using IE6-8, if you set your font with a pixel height it won't resize like modern browsers and this hurts your site's accessability.

Mockups

Sometimes mockups are neccessary, but I don't use them often. It's much faster to prototype instead and it gives you a great head start to the final product. Clients love seeing progress, and if you let them play with the minimum viable product they feel much more involved in the process. This also allows them to give you feedback quicker, spot mistakes, and ask questions — all valuable time savers.

Don't take my word for it

A PSD/PNG should be nothing more than an idea of a website. It should give clues and a direction to the build, but ultimately should not be treated as a final design. Following PSDs to the pixel will lead to ill-considered code, and code is your final product, not an image. For example, if your PSD uses three shades of very similar blue, the build should pick and honour just one. There is no point repeating similar declarations in your CSS when a happy middle-ground is more efficient, easier and quicker. A PSD is a clue, not a contract.

Harry Roberts