Sharing Tech Knowledge

Well, I am a big fan of documentation and the reason for the same is not because I know a lot, the reason for the same is that I don't know a lot! Fact ! There are a lot of misconceptions that Agile Methodology is against Documentation. Working software over comprehensive documentation The above statement in Agile Manifesto states the importance of documentation in a project, but the real interception of the statement is often described incorrectly. It means you should create documentation that provides value and at the same time does not hinder the team’s progress. Agile document requirements are user stories, which are sufficient for a software developer to begin the task of building a new function. Major advanatages of documentations are: A single source of truth saves time and energy. Determine what others need to know about the product/services provided by us. The hiring and onboarding process can be easier. Enables Revision Control and provides a proper process for updates. S

This article is all about the tools that can help you to get more insight into your project when you are trying to explore the project on your own. These tools can help you to find the code flows even in times when the source code is not available, particularly focusing on Java Based applications. Wireshark Struggling to find the protocol used behind your application, then Wireshark will be the perfect tool to use, it's so useful that you can find the communication protocol on every single request your application sends even with the packet details. Ref: Wire Shark Offical Site . Java Decompiler Don't have the source but still want to explore the code behind the java application, Java Decompiler is there for your help. Say your code is deployed as war or jar, the compiled code can be viewed as readable code using this tool. Ref: JAD Offical Site . VisualVM Threads! A nightmare for Java Developers, VisualVM provides you a simpler view of your application and the details of each

"Debugger" Java Developer logger.info( " inside json parser " + json.toString()); System . out .println( "response " +gson.toJson(reponse)); . . . . Printing tons of sysout onto your console and checking the values of various attributes to resolve certain bugs ?! Sounds familiar!  Debugging is the perfect choice in those situations. Not always we can fix the issues and fixes by just checking the logs or by going through the conventional ways. That's where debugging can give you an extra hand. Choosing the right IDE which helps you to easily enable debugging and connect to your application is key. Different IDEs have different ways to enable debuggers.  For example: enabling debugging in Eclipse to debug an application that runs on Tomcat is quite different from an in-house application. Reference: here JPDA : Java Platform Debugger Architecture  Even when your target application is not hosted in your local or if the target application hosted system doe