Thursday, August 13, 2015

Debugging Javascript

Just sharing a handy tip that saves a bit of time during javascript development. By using deb.js, it is possible to have stack trace in browser on errors (as javascript is not expressive while throwing errors). By using deb.js a lot of console.log statements and debugging sessions on chrome/firefox can be avoided.

Tuesday, August 11, 2015

Not just another bot

I receive a lot of mails from recruiters regarding job opportunities in some xyz technology. The trouble is that after five years of working in software development, I've picked up some mundane as well as niche skills and added them to my skillset.
However, when confronted with people who like to only concentrate on their requirements, I come up with something like this:
I guess, specialization matters, but real world requirements are different. If you happen to be a recruiter or a manager, you would have to take this fact into account that any person that knows about the tool that you are hiring is a unique individual who also happens to know other related and unrelated stuff.

Saturday, July 25, 2015

Going agile

I'll start this with a tool inspite of the title named after agile, a practice that cold shoulders it.
Sometimes, the tools that you desire are not available for customization and all the relevance of a given tool seems unrealistic. However, there are alternatives and when they are available, it becomes a pleasure to share.
Restyaboard is one such trello like tool which is opensource and you can setup and customize to your heart's content.
These days, as I am busy in an agile project (that is unfortunately not followed in an agile fashion), doing other things increasingly becomes difficult and same goes for my blogging also.
But one must not give up on good things in life and keep trying and exploring.

Wednesday, June 17, 2015

that frantic rush to jump the JS MVC brandwagon

I came across an advice on an online comment which is worth sharing:
Forget about it (at least for now). Simply stick to plain old jQuery, master it, be your friend.
If you suddenly find yourself getting swamped into a lot of jQuery spaguetti code, that means that your application is getting way too complex and your code needs some structure to make it maintainable.
This is where an MVC framework can help you, by giving some logical structure to your code, making it more modular and reusable, easier to read and to understand.

However, it's hard to learn a solution to a problem you never had...'
This is quite like the advice that veteran programmers give - if it isn't broke, don't fix it. There is a time and  place for sticking with MVC, but the traditional approach of keeping things simple is not a poor choice  - especially when the code is readable.

Sunday, April 26, 2015

My tryst with Hybris... continued

Rather than making a new post on my thoughts about development over hybris platform, I felt prudent to continue my older post about SAP Hybris and bring out some of the challenges felt and my take on this e-commerce platform.
Currently, I am still a newbie developer working on various features and parts of the platform.
My team is also in the young hybris phase as explained in detailed manner here ( ) and the knowledge sharing is limited and as frustrating as it seems, the development work is generally slow due to long list of assumptions that hybris platform assumes.
One example is in implementation of AdminCockpit - where all the fields in various editors are laid out in various xml files:

< editor >
    < group qualifier="General" visible="true" initially-opened="true" >
        < label >General< / label >
        < property qualifier="B2BRegistration.title" / >
        < property qualifier="" / >

These files are editable, but changing them yielded nothing - and no suitable help was found in hybris wiki or experts forum. Next , I tried doing ant all and searching for generated files but found nothing of importance. Finally, I tried doing an initialization of cockpit and admin cockpit which made the changes appear - the amount of efforts that I invested were shockingly huge as compared to the actual work needed.
If some hybris expert/creator reads this, I hope my plead for greater technical and functional documentation reaches - debugging without a knowledge of how the APIs function is like learning to swim inside a boat.
Development and trying to appear for hybris certification remain my top priority missions for the coming month and I hope to be a hybris certified developer after then and work on this platform for the near future.