A Oneliner for grepping character-by-character differences between two files anywhere on filesystem

Long story short:

Install git.
Hit this at command-prompt from within any git repo(can create afreash using `git init`):

 git diff  --no-index --word-diff=color --word-diff-regex=. /path/to/file1 /path/to/file2

Sample Result:

Dear Cybernauts,

Many a times you might have wondered a way to compare 2 files not just word to word but character-by-character, nicely coloured, and easy to spot on minute changes!

Without finding anything easily on the Internet apart from purchasable solutions (such as desktop versions of diffchecker.com..) not worth the pennies, I dug up some manuals and found it worth the effort to document it for the lazyweb. There you go! ^^ 😉(HaCk tHe BuSy-NeSSeS build on top of it!??!!! Use the 'man' if needed!)


~Namaste
🙏

Guard clauses - avoid over dependence on "else"

I had gotten used to using guard clauses quite early on in my software engineering journey!

I saw this pattern in the code base of the GNOME project, Empathy, during my internship with them and was greatly impressed by this way of checking preconditions in every C function. From there on, I inculcated this strikingly clear way of stating assumptions and structuring functional code in my code style!

A few minutes ago, I received a notification of the following new medium blog post titled "Stop Using Else in Your Programs", in the "Better Programming" category and deemed it worth sharing:

https://link.medium.com/BNKA743hX0

Enjoy, and happy hacking!

Engineering wisdom from a Senior in Software Development and Engineering

I won't bore you by lecturing what has been often described before. This man, Neil Kakkar, did an amazing job at summarising (and kudos to keeping his mind open to learning these finer details) what he learnt from the craftsmanship of a Senior Software Engineer while working under his guidance:

https://neilkakkar.com/things-I-learnt-from-a-senior-dev.html

I would definitely have things to add on to this list, but I'll keep it for a future post. For beginners, this is definitely a read worth your time, though I agree- some things only come with experience and most young engineers don't realise the importance of such development disciplines until they have themselves faced the consequences of not having followed them!

Google Code Jam Qualification Round 2019 - My submissions and Post Contest Analysis

Hello World!

As promised in my last post, here are my submissions along with post contest analysis for GCJ Qualification Round 2019.

In all, I made 2 successful submissions (and one mis-formatted output submission that costed me some penalty) and with that I was able to score sufficient points for clearing the round and advancing to the next level! :) 👊
I also went through the third problem in the contest and came up with a solution but I couldn't push it in in time. I'll upsolve and share the remaining un-submitted problems here shortly.
So, without much ado, here are the problems that I did:

Problem 1: Forgone Solution
The solution I coded was written with all 3 and specially the largest hidden test set in mind. As N can be upto 10^100 digits long in the largest test set, it makes the problem obviously a string manipulation problem and thus the below solution is such.
Worst case run time complexity: O(n) where n is the number of digits in N.


Problem 2: You Can Go Your Own Way
This was a maze problem the solution for which was again written with the time constraints for the largest test set in mind. The solution you want should be no more than O(n^2) complex which was possible with a classic dynamic programming approach to it which I had used. All went well and visible tests got passed but the hit was the hidden test set which was executed post the end of contest where my solution couldn't satisfy the memory constraints. The verdict was Memory Limit Exceeded. It turns out that I have been spendthrift in the memory actually and some optimizations could be deployed to avoid that. I'll up-solve it with a more space-optimal solution for the problem and test it under the practice round but until then, the DP solution is as follows.
Worst case run time complexity: O(N^2) where N is the input - length of one side of the NxN maze.



Congratulations to all those who made it through to the next round! Hope to see you coming out with flying colors! See you at the score board of the hall of fame!!

As always, feel free to point out optimizations or share your suggestions to my approach to the problems shared here. Until then,

Love and Luck,
~glassrose

Google Code Jam 2019 Qualification Round Underway!

Google Code Jam 2019 Flyer

You don't need any more motivation!

[Stay tuned for my solutions to the Qualification Round on this blog post end of the contest ;) ]

Bidding Goodbye to 2018! *latepost*

"A man is known by the company he keeps!"

This is a memorable moment from most of the members from my company(pun intended) gathering together for 2018-year end celebrations! We happened to celebrate my birthday as well, that day. Here we see a ensemble of truly diverse and super-motivated folks - Rapyutians of Rapyuta Robotics - with a common mission of "hashtagEmpowering hashtaglives with hashtagconnected hashtagmachines" !!

Moved to Tokyo for Robotics Engineering experience

As a child, I used to watch this American sitcom called "Small Wonder" (https://en.m.wikipedia.org/wiki/Small_Wonder_(TV_series)) which made me go awestruck with the wonders that engineering could create! Coming from a doctors' family, this sitcom was my first hand exposure to what an engineer's life looked like.

Eventually, I ended up studying Computer Science and Engineering myself. But, it was not until now that I really got a chance to do something substantial on the robotics front.

Fast forwarding to about the last quarter this year, I bagged a job opportunity in a field that's an amalgamation of Software Engineering and Robotics! I graciously accepted the offer, changed countries and henceforth, will be working as a Software Development Engineer for Robotic Systems Software out of Tokyo, Japan for this Japanese company - Rapyuta Robotics, whose mission aligns so much with my vision.

I trust, it's all how it was destined to be and I wouldn't have been here without the experience that my previous gigs provided me. The knowledge of Linux systems software that I gained at IBM was definitely a pre-requisite for my current role and equipped with all these skills gained over years, I aim at creating and achieving many more milestones, with my team, for this new found love for empowering lives with connected machines.

That's all for now, and until next time, take care and happy hacking!