358 karma · joined July 24, 2014
However, that is a personal choice, I understand :-)
What about latency concerns for people who are not based in EU? I saw on that website that the servers are hosted in EU, and say I need to use it in Asia will have service have usable latency?
Moreover, my statement was more of a speculation rather than an advice :-D
Over time, I have started to think in terms of innovation tokens [1]. You cannot choose all the new technologies all the time and you have to measure how many innovation tokens would you like to spend on what.
Conceptually, I know why I should do a task at hand and complete it. I also know the priorities which task is more important and which are less.
The part which pulls me down each time is how to convince my brain at the instant where it is telling me to watch that netflix trailer, mindless scroll fb, etc. instead of the work that was needed to be done. What is the framework/trick/technique that people use to not give at that weak moment?
Thanks to @tutbhuf for mention of kafdrop. Will check it out as well.
I find this tool very very useful when you have lots of integration job. If you have an enterprise version, then you can do stuff like compare and merge files across two servers, compare PDFs, ZIPs, JAR, and obviously plain text files. This is a tool for which I definitely ask for an Enterprise Version license whenever I join a new organization.
find . -name *.gradle | blah blah
Instead of finding the root cause, I by-passed it by find . | grep "\.gradle" | blah blah
It just feels great to now connect the dot and know the real reason for the issue.So with this style one can follow the style :-
Jot down the requirement/problem ==> Think of all solutions for the problem ==> Evaluate solutions ==> Choose best one ==> Jot down commit messages before hand ==> Implement solution ==> Use "git add -p" to separate logical units of your commit as per your commit messages already prepared ==> Tada !!