Many times we get greeted by just Hi or Hey messages from our colleagues and friends in our various messaging systems. Be it Slack, Mattermost, Teams, Hangouts or whatever messaging systems that you use. This is one of the most irritating (sorry to use that word, couldn’t find a subtle one), messages that you can ever receive. Messaging systems are meant for asynchronous messages. Expecting that the person at the other end of the conversation is always available to answer the hi/hey messages is too much of an expectation. Remember messaging someone is NOT like making a phone call. You cannot expect an immediate response there. Follow these simple etiquettes next time you message your friend or colleague. Write the complete content that you are planning to ask the person in a single message (as much as possible) May be you can start with a Hi, but make sure it is a multi-line message with the actual content. There is nothing more irritating than receiving 10 notifications in the mobile ...

I am not the original author of this post’s contents. I recently found this email reply from John Mitchell while discussing the testing aspects of micro services in our project. It is so informative that I didn't want this to get lost in emails. Adding this here. (Names have been changed to keep the focus on the topic under discussion) Hi PersonA, I think our discussions about the Quality Criteria were pretty clear… And to be even more precise, they must be able to be automatically run as part of the appropriate phases in the pipeline. APIs Message / file formats, etc. UI’s which they provide Telemetry which they generate for business/application/operation/etc. monitoring/alerting/tracking/etc. Martin’s slide that you point ed is no excuse to get out of any of the above. He’s pointing out, as I did, that false metrics such as “code coverage” percentages are misleading and inefficient ways to measure actual quality of the software (as opposed to trying to force the team to spend t...

GCViewer developed by Tagtraum Industries is one of the free tools that you can use to visually analyse the garbage collection logs. Running GCViewer The latest version is now maintained by chewiebug and available for download at http://sourceforge.net/projects/gcviewer/files/ Download the gcviewer-x.xx.jar to your local system Launch the viewer by running java -jar path_to_gcviewer-x.xx.jar You need Java version >= 1.7 Using GCViewer Open the GC log file from the test run using GCViewer Adjust the zoom levels (dropdown at the top) so that the graph fits the window and there are no scroll bars (to get an overview) Check the trend of the 'Total Heap' usage of the VM. As long as it does not show an upward trend, VM is considered to be fine. Check the right side of the tool for the information related to the run - Summary, Memory and Pause. Summary 'Number of full gc pauses' are of concern and healthy VM should not generally be doing a full GC (which means it should i...

Day-0 For getting the calendar along with time. Download BetterSnapTool For those Windows users who is missing the maximize and automatic snapping of windows. It's worth it's price (Rs. 110). Download iTerm A much better terminal than the built-in one that comes with Mac Download Clipmenu Multiple clipboards to save you from losing your work. Download Skitch Much better screen snapping tool. Download

 

I would like to share an excellent write-up by the JIRA Agile Product Manager from Atlassian Shawn Clowes . This was written a while ago, but the depth and detail present in this reply from Shawn for one of the questions in the Answers site still amazes us. This was his explanation about time estimates and story points in the agile context. Here it goes: I'd like to provide a full explanation of why we we've offered 'Original Time Estimate' as an 'Estimate' value and not 'Remaining Estimate'. Some of my discussion refers to agile concepts that anyone reading probably knows well but I've included it because the context is important. Note that the discussion refers to the best practices we've implemented as the main path in GreenHopper, you can choose not to use this approach if you feel it's really not suitable. Estimation is separate from Tracking In Scrum there is a distinction between estimation and tracking. Estimation is typically perform...