Co-founder and Software Craftsperson at Incubyte
A tech evangelist and mentor, Sapan has been fuelled by two things in his 15+ year professional career; coffee and his love of designing self-motivated, high-performing and passionate software engineering teams. Being a software craftsperson at heart, he has created and coached teams of over 500 software developers spread across the US and India with the sole objective of forging exceptional software products with an unfettered focus on quality.
Choosing a direction when redefining your organization’s technical backbone is never easy. In this case study, we had the unique opportunity to observe the implementation of both - a Low-code/no-code CRM and tailored software solutions over two years.
Accelerate by Nicole Forsgren, Jez Humble, and Gene Kim was released in 2018, and it changed how I think about software delivery.
Clean Agile Summary Clean Agile is a book by Rober C. Martin that revisits the subject of agility in the world of software programming.
I recently came across Simple Sabotage Field Manual. What struck me was you do not need bombs and explosives to start sabotaging.
A technical deep dive Client: Monnai Reinventing global consumer insights for fintech The fintech market size stood at USD 112.
Are you a software developer? How can you be more effective on this journey of being a craftsperson?
The Checklist Manifesto by Atul Gawande, walks us through the benefits of the humble checklist. He talks about how checklists of “dumb stuff” can save us from disasters in life and death situations.
The term “Technical Debt” was coined by Ward Cunningham (one of the authors of Agile Manifesto).
Have you ever come across a bug that had complex logic, and was incredibly hard to fix?
Books are a massive source of knowledge. Before we list all the books here, we want to discuss why we think it’s essential for programmers to read them.
Open-source software (OSS) is the holy grail for developers. It is a hub of innovation through intense collaboration in this era of agile software development.
Ever saw SonarQube laden with thousands of maintainability and security issues? Looking at those dashboards, we often believe we’re looking at the code’s state, but there is more to it.
On multiple occasions, I have worked on projects where I learned how critical testing is and that not all tests are the same.
Most projects that I see facing serious problems lack tests. You should write tests for two things
Learning is the most vital part of a software developer’s life. Being so busy that one stops learning is neither desirable nor helpful to one’s career.
Once again, you would think that the software development community has moved past this point, but I still get many teammates who want to “save memory” using HashMaps instead of POJOs.
Once I was asked in an interview (I was the interviewer!) What do you do in situations where the customers don’t want you to write test cases, or they want you to deprioritize the activity of writing test cases.
Have you ever seen code in your module, which was so complex that you decided to copy and paste it entirely rather than changing it to accommodate your requirement?