Skip to main content

Lost forever

One of the addiction that is tough to get over is love for a friend. Irrespective of how horrible the spilt up was, no matter what reasoning lead to the parting, a warm mind would naturally gravitate toward the beautiful memories of the long lost friend. There will be a feeble voice from inside that brings up the possibility of getting in touch with him or her, only to be silenced by the rational mind which takes us through the thought process that you once used to justify your action.

It is just plain painful but sweetly melancholic to remove the photo album tagged with that friend. You cant let it stay, cos there is too much pain at every time of remembrance, and there is remembrance at every time of sight. Some times, we scribble about the special new friend to those dear diaries with a hope that they stick around long enough and when it doesn't work out you can't tear away the page or strike off that scribbles of innocent happiness... It is a permanent stain on the Diary's memory lane and is not always pleasant. If only the diary had a mystic power to convey people what I write about them in it... If only my dear diary had told her what I felt... Or at least showed me what she wrote in her's...Things would have been much more interesting.

 

Comments

Popular posts from this blog

GraphQL

GraphQL



What is GraphQL

It is a specification laid out by Facebook which proposed an alternative way to query and modify data. Think of it is an as a complimentary of REST/RPC.

Now head here and read the original graphQL documentation. It will take 2-3 hours tops but is a worthy read. This will help you build some impressions on it and help contrast against mine below:


Why use GraphQL

Core advantage

Instead of defining custom backend rpc/rest endpoints for every data-shape, graphql allows you to build a more general endpoint which give frontend/mobile engineers freedom and query and play with the data. It might be less efficient, add a bit more complexity (need for things like data-loader), harder to standardize and control client-contracts for. What it looses in complexity and control, it gains in flexibility and freedom - provided your data model is worth of a graphql-ish query How to tell if my data-model graphql-ish?Are there complex relationships between your models? Is there a need …

About me

Hi,

I'm currently working as a software developer in the logistics industry in San Francisco. 
My aim is to impact billions of people's live for the better and make the world a better place.

Cheers,
Vignesh



Backend - Tech refresher 2019

Hello there

As a software engineer, it is important to keep updating your skillsets by learning the latest programming-elements (includes paradigms, patterns, languages, tools and frameworks). This becomes a bit easy if you already working on the cutting edge of something. Even then, it is possible to go too deep and loose breadth.

I've taken upon myself to do a tech refresher every year. The intent is to read, experiment and understand these elements by spending anywhere between 4 days to 4 weeks. The ultimate goal is: "do I know most that I need to know to build a planet-scale backend tech-stack ground up"

I'll write up my learnings in posts to help myself (and maybe others) refer it.

Here is the initial list I'm thinking about:


RedisMySQL, GraphQLAurora, Mesos, KubernetesCadence, SWSCassandra, MangoDB, NoSQL, MySQL, Spanner, S<, DynDBELKFlink, Storm, Samza, SparkHadoop HDFS, Yarn, MapReduceHive, HBaseKafka, ZookeeperNW: http, Tcp, thrift, grpc, yarpc, Terraform,…