Sharing Tech Knowledge

Introduction Shipping your product just after you have committed your changes in code. Automatic Build, Running Test Scripts, Release to your artifactory. Ya  Continous Integration  is the exact thing I am talking about. Jenkins is the most popular CI-CD tool available out in the market nowadays. As always to kick-start a new tool the official documentation is good but not the ideal solution as it can be a bit high level. Jenkins has its official tutorial:  Jenkins Tutorial Recommendation Tutorial Articles:   Jenkins Tutorials Point Tutorial Overview Installation Download Jenkins from its official website: Jenkins Download . Download the corresponding installer for your operating system. Install the installer via the wizard and do the required steps on wizard-like setting the default port, admin username, and password. My personal suggestion is to go with Stable-LTS (Long Term Support) version. Installation is an easy task, after installation, the Jenkins server will start at localhost

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

Why Start Blogging about things we know or learned? Have you tried to learn a new topic, say a new language or a new framework, and then try writing about it? Yes, now you know the real pain of it. While teaching your colleagues or while blogging on a topic, one has to go in-depth to answer the WHYs. " Writing is an exploration. You start from nothing and learn as you go. " – E.L. Doctorow, American writer, novelist  Sharing helps you to find and fix the blind spots in your understanding, which in turn improves us. Hmm... so blogging is not just sharing your knowledge, it's also improving yours too. Maybe initially it's just as useful as documentation, but it will change. When we start blogging and share our knowledge, not always things get applaud, especially when they reach a greater audience or a community. And these will surely will be stepping stones. Blogging options are in many, now just Blogger by Google. Github can be a good or perhaps the best space for tech