I have recently found myself writing this code and I wondered, should I be writing such code at all? Is it too obscure?

return (tokens!= null && tokens.length >=1 && tokens[0].compareToIgnoreCase("NIL") != 0) ? tokens[0] : null;

It is pretty straightforward but it will require some mental power to process this code.

It is a often advocated that the code should be self documenting and I think it indeed should. Some thinkg only hacks and edge cases have to be documented but I still think placing notes in the strategic places in the code saying in a few words (few here means literally 3 to 5 words) what this piece of code does/is supposed to do.

Developers often take pride in complex and obscure code. This is, I guess some sort of narcissism in a shape of saying “I am so smart” instead of “I am so pretty”. Let’s call this the “Narcissistic code complexity syndrome”

Many times I do prefer writing such code however because I like the conciseness of it. Maybe I am deluding myself and I actually am a victim of narcissistic code complexity syndrom?

Let me know in the comments.

Here’s the recipe to remove the lib folder. You can change the file/path matching and also limit the command for range of commits because what it actually does is basically overwriting the history and removing the unwanted files.

Step 1: filter-branch

git filter-branch --index-filter 'git rm --cached --ignore-unmatch lib/*' --tag-name-filter cat -- --all

Step 2: push –force

git push --force

This will clean the unwanted lib folder from the repository completely

It will not rewrite the log commits though and the commit messages will still be there.

[This is an update to post on how to remove Pods folder from iOS project]

TL;DR
add the css into your ~/.atom/style.less which you can open from Atom -> Open Your Stylesheet.

Yesterday following the fix of many major issues I had with Atom where one of the major ones being the save state issue which I missed so much from Sublime and this was a deal breaker for me. Up until tomorrow when I realized it has been finally implemented in Atom.

I completely switched to Atom now. So long sublime… Or so I hope :)

I have realized that the search highlighting in the dark themes (I use Dark Monokay pretty much everywhere) and I used a custom Monokai theme in Atom that I changed a little to match better the Sublime Text Monokai theme I have been using for a while.

Anyhow. I realized that there is no search highlighting for me going on. Ok, so I thought maybe it’s me and tried some other dark themes. Nada yada…

Fortunately it’s a pretty easy fix via the custom styles that will apply to any theme you load:

atom-text-editor::shadow .highlight.find-result .region {
  background: red;
}


atom-text-editor::shadow .highlight.current-result .region,
atom-text-editor::shadow .highlight.current-result ~ .highlight.selection .region {
  background: red; // the active search highlight - to distinguish from the other results
  border-color: yellow;
}

After playing a little with various options I decided to settle on these. You can of course change the background and the border to your liking.

The red used here is the default one and is rgb(255, 0, 0).

UPD (2015-11-01) As of October 2015, the colors are broken with the updated Atom. I still did not have the chance to fix it.

UPD (2015-12-10) I got some time to have a quick fix for the search highlight issue

KeyCDN is an awesome PAYG (pay-as-you-go) CDN service. I have been using them and I love them so far. I am planning on writing a more detailed post about why I like them and what makes them a great fit for us in hope to help someone to make a decision on which CDN service to use and just to give some props and praise to the guys behind keyCDN.

It is free to try and if you like it, you can get $5 off using this promo link

In this post I just wanted to show some code that interacts with their Node.js library.

I am using a prompt module to get input as to what needs to be done

The purgeZone(1) and listZones(0) are pretty much taken from the sample with some very minor enhancements to make the methods be more “output friendly”.

var secret = require('./secret.js');        //put your secret key here or you can use it directly passing to the keyCDN method.

var KeyCDN = require('keycdn');

var keycdn = new KeyCDN(secret.key);


function purgeZone(zoneID) {
    // purge zone cache
    keycdn.get('zones/purge/' + zoneID + '.json', function (err, res) {
        console.log('GET zones/purge/' + zoneID + '.json');
        if (err) {
            console.log('ERR:' + 'Could not purge-> ' + zoneID);
            console.trace(err);
        } else {
            console.log('ACK:' + 'Purge-> ' + zoneID);
            console.dir(res);
        }
    });
}


function listZones() {
    // get all zones
    keycdn.get('zones.json', function (err, results) {
        if (err) {
            console.trace(err);
            return;
        }
        console.dir(results);
        console.log(results.data.zones);

    });
}



console.log('-------------------------- START -------------------------------');

console.log("1. List Zones\n2. Purge Content Zones\n3. Purge All Zones\n\nChoose option: \n");

var ZONES1 = [
    {
        zone: 'name1',
        id: 1111
    },
    {
        zone: 'name2',
        id: 1112
    },
];


var ZONES2 = [
    {
        zone: 'name3',
        id: 1113
    }
];


var prompt = require('prompt');
prompt.start();
prompt.get(['insert'], function (err, result) {

    var s = result.insert;

    switch (s) {

    case '1':
        listZones();
        break;

    case '2':
        ZONES1.forEach(function (zoneObj) {
            purgeZone(zoneObj.id);
        });
        break;

    case '3':
        var allZones = ZONES1.concat(ZONES2);

        allZones.forEach(function (zoneObj) {
            purgeZone(zoneObj.id);
        });
        break;

    default:
    console.log("ERR: no action mathches the input");
    }
});

the secret.js is just one line

exports.key = '*****************************';

I could do a much nicer job I suppose using a commander package or the optimist but I just needed to throw something quick together to be able to basically purge all the zones or some types of zones quickly.

Here’s my new 404 page. What do you think? Click here to test it

I like being able to see the invisibles in my text editor. While the invisibles are enabled in Atom though, it shows all of the invisibles and it may be overwhelming.

To make it a little saner use:

showInvisibles: true
invisibles:
    eol: false

in your Atom config file.

To get to the config use Atom → Open Your Config

Enjoy.

Try the markdown writer plugin for the Atom. You would most likely be very pleasantly surprised at all the additional functionality that you get out of this great plugin for general markdown editing but with great features to make your static blogging ever so more pleasant!

Atom editor in general is taking pretty good shape. Hopefully I will soon be able to completely switch to Atom from Sublime Text.

Don’t forget the companion markdown preview package to preview your markdown files as you type if you want to.

Good design is obvious. Great design is transparent

––Joe Sparano

A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away

––Antoine de Saint Exupéry

Here’s an excellent plugin to preview any arbitrary file as a text file.

Very handy for previewing README or any other weird extension files that finder would not preview by default.

Once you unpack the archive, you need to move the plugin to ~/Library/QuickLook. To get there fast (or any folder for that matter) you can use a nifty Finder shortcut: ⌘ + ⇧ + G

To delete lines 2, 12-17 and line 57 from file data.txt using sed you could do something like this:

sed -e '2d;12,17d;57d' data.txt

[Source]