Skip to main content


Showing posts from December, 2013

Deals You Can't Miss

1 Year Subscription

Talk Kata - Repeating Conference Talks

In the hard business of engaging the audience.. There are many kind of katas in the software world that I've been trying and practicing over the last 4 and odd years. Towards the end of last year, 2012,  I've started applying the concept of Katas in Public Speaking domain and I call it "Talk Katas". Talk Kata is all about sharing your thoughts by way of talks to different set of groups, again and again and learn the art of public speaking in the process. It is with deliberate practise of public speaking can one hone the art of communication. Attendees enjoying the talk "When Agile becomes Fragile" is a topic I've been talking about in all of the recent conferences. It only gets better and better with every talk based on personal conversations, feedback etc. I've with the attendees after my talk. Come year 2014, I'll again be talking about this in PMI Chennai edition as part of their invited talk series. For the curious minds,

Recursive chmod settings based on file or directory

I recently had to do this and below are the commands that I ran to get things done. $ find ./my-folder -type d -exec chmod 755 {} \; $ find ./my-folder -type f -exec chmod 644 {} \; where the pattern is: $ find [search-path] -type [d | f] -exec chmod [access-rights] {} \; Explanation: -type d => files of type directory -type f => file of type "file", a non-directory {} => replaces every file path found at the find command \; => is to escape the semi-colon. And semi-colon is required to denote the end of command.  If not escaped, the shell interprets it instead of find command. 755 => make a file readable/executable by everyone and writable by the owner only. 644 => make a file readable by anyone and writable by the owner only. And as I was doing this, I tried reading a discussion in stack-overflow on this and found an even simpler command: $ chmod -R a+rX ./my-folder where the pattern is: $ chmod -R a+rX [directory-name] Expla

Work around to file protocol in browsers

There are times when you're dabbling with Front-end technology like EmberJS, AngularJS, etc. You'd wish to load the just crafted web-pages of yours in a browser to see the work in progress state. What do you do? First attempt is to load the page in the browser with the hardcoded local-disk location. It would be something like file://usr/kartz/frontend_apps/fake_app/test.html This attempt might most likely fail in many modern browsers, especially if you have included any local javascript, css and similar assets. Are you here and wondering why? This is due to browser security constraints. The work around to this is to serve this/these kind of files from web server so that the protocol becomes http. But you don't want to get into the overhead of starting/managing a web server for this. You don't want to copy your file into the web-server  or work in the web-server's app directory. You want your project source in your own chosen location and wish for some l