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

Writing your own code or copying others' code? It's always the mix and match of these two methods Developers use! Well, it's not a crime to copy the code from StackOverflow or other forums and trying to implement an idea in your project. To get the best out of it, it's always best to understand the code that you see and try to implement it by understanding your requirements rather than blindly following it. Not always you will have the time and resources to start the code from scratch, and obviously, your first attempt to code logic will be the most effective. Accepting these facts, copying code is not such a bad idea, or at least getting inspiration from code. Cheatsheets are often helping hands for developers, and as the name says it's not "for cheating" but a one-stop for the commonly used commands and methodologies. One such cheatsheet repo that I found in GitHub is Cheatsheets  which is an awesome collection of tons for sheets.