The Probability of Spilling Tea

I just published a story on the Probability of Spilling Tea.
Hope you'll enjoy :)

Time to hit F5 on some OS concepts

A lot stuffs happened during this break. I'll scratch em down here later cz it isn't time for it.

It's Sunday 2:30 am and I'm not gonna lie, I couldn't sleep in peace for the past 2 days as my mind has been haunted by an issue.
One of my hobby app is firing a lot of requests to the Google Cloud Datastore. Technically speaking, my app has been well optimized for least requests - and it is doing it right. It turns out the issue is normal: the more people uses the app the more hits on the Datastore and each hit costs.
Even though Google offers an economic awesome pricing scheme on Datastore, I've to account for higher hit ratio. I'm not rich, I've to fix this.

I'm thinking of some kind of a caching mechanism. I've found some npm modules out their, unfortunately they don't have the right balls. So decided to give a try to make a pluggable solution that works just like how the OS manages hdd-ram-cache stack on a computer. But, my app is not buil…

A final note to my Voldmort.

Voldmort is the name I given to my computer when I joined Interland 6 months ago as UXD. But personally, I'm more a MEAN stack developer than UX developer. Recently I got an opertunity as MEAN developer in a company at Infopark. So, today I'm signing off from Voldmort forever.

I started writing this post from Voldmort.
6 months he served me awesome in Linux. Running node in it was a breeze. I always kept it up to date and bugfree. "Oh my zsh" beautified my terminal so that I never get tired by looking at it. My desktop was clean and stupidly simple. I never had more than 5 icons on my desktop even though I had a dual monitor setup. It always gave me fresh new feel whenever I turn it on.
And when I'm wired in 🎧, story begins. It keeps me focused and distraction free. Thanks to SoundCloud, Sublime Text, GitHub, Node and Google (and ofcourse, java - I'm not gonna miss you 😂).

The one single jerk was with Eclipse, but still forgivable.

Big thanks 💜 to Voldemo…

Validate JSON within Node.js with is-good-json npm package.

This is a simple npm package to determine if the given JSON is valid or invalid. Again, it parses the given file in the proper format if it is valid. So you don't have to parse it by your own.

Visit is-good-json npm package.
Just #published another #npm package 'is-good-json' to validate a #json file internally in an #app. 👨🏽‍💻 — Vajahath (@vajahath7) December 27, 2016

Building node.js applications on Google Cloud Platform.

found this as very inspiring and informative.

npm lme 1.2.0 is out !

I had published an npm package named lme, to console.log() better. (read the post)

v1.2.0 of the lme npm package is out now. This version covers some additional features for drawing lines and some support for node's default output methods such as trace and info. Thanks to @amandeepmittal for #2.

Visit the lme npm package.

Install / Update lme
npm install --save lme

#npm lme 1.2.0 is out #now with more features and bug fixes. — Vajahath (@vajahath7) November 23, 2016

lme: console.logging done right.

Visit the lme npm package.
I've been using Node.js for last 2 years. Till then, whenever I wanted to output just a "hi" it requires me to write the entire 13 char long console.log(). I'm lazy enough to write that hard.

It is even insane to find something that console-ed out to the terminal from a pool of texts. If you are using the morgan npm package, then it requires no time to fill up your terminals with loads of text. We need all. Morgan is a great tool for logging HTTP requests. How can we develop an app ignoring the outputs of Morgan!? At the same time, we also need out custom outputs.

Well, there is a great package called chalk. Yeah, it's wonderful with much color. So if you need to output something to console with colors, use chalk. But it takes even longer to construct your console.log() statements. You need to individually style each of your statements.

The lme package
To handle all these shortcomings, I just published a simple npm package named lme(sta…

Hello World in MongDB.

On 15th January 2016, Divin, one of my best friends sent me a message in Whatsapp.
Greetings from ICT Academy of Kerala,

We are pleased to invite your college to participate in the ICT Academy of Kerala’s Student Magazine to be released in 2016. Students may submit articles related to technology(all engineering disciplines), social innovation, individual and  group projects. The submitted articles which will be reviewed by ICT Academy of Kerala’s editorial board before incorporating it to Student’s Magazine . The ICTAK Students Magazine will be a unique blend of articles by students from your college and the industry. The best student article will be rewarded by ICT Academy of Kerala.
 Articles to be send to this email id: <divin's email>
 Please ensure the following steps to submit the articles.
 1)      Articles should be related to technology(all engineering discipline), social innovation, individual and group projects.
2)      Articles should not be more than 2-3 pages.

Dynamic Divs

Some days before I was asked to do something like this. That was terribly simple! Here is a snapshot from my wandering editor..

See the Pen dynamic divs by Vajahath Ahmed (@vajahath_ahmed) on CodePen.

Polymer element to make a success feel to user.

Some days ago our team lead told me they want something like this. I produced one and gave it back.
But I thought I could make a stand alone custom element so that it can be reused a hundred times without writing the entire bulky code.
I published an npm package here:
Here is the docs:

It's a special feeling when I code wired-in with this;

Lots of things during this break. And finally an npm package.

Well, lots of things happened during this break! Thank God, most of them were funny and good, except one can invoke curiousness ( I'll mention that in my later post).

I've been learning some UX principles these days as I got a job as UXD in a major company.
I'm gonna dive into Polymer. cz that's what's gonna save my time. Thus as the first step, I published an npm package which is a Polymer custom element. Good news is version 1.0.9 of the element is out today.

Even though the package is not intended to blow your mind, it helped me to understand the basic polymer principles. So I invite you guys to give a try there. The documentation is also provided with the package.

Save a lot by modularizing your CSS.

I recently published an article on facebook discussing a good practice in CSS that we should follow.

At my baby steps in designing (mm may be 3 yrs ago) I wrote a new class for each element and styled them. The funniest thing was most elements had the same style. First styled a class, then copy-pasted to a dozen times. Finally I used to look at them and think "God! I wrote this much!", in which most of them are repetitions which are ctrl+vd. Those days were the funniest..

When I learned Bootstrap, I really liked the way they modularized their CSS. Then I started doing that modularization my own.
Now here is a note for kids who are getting started.

Find what's goin on my editor

I think it's nice to make the coding more documented, or may be.. can I say simultaneous blogging? I don't know. Let it be whatever you call it. I'm gonna do that stuff here or on facebook.
"A live mad thought update from my wandering mind". Eh.! did i really said that?!

Piano is beautiful #Yiruma

Yiruma, (이루마) - Reminiscent