KISS

Software Development Principles for Engineering Managers, Architects, and Developers

Here are some of the principles that every software professional (be it an Engineer, Architect or Manager) needs to understand and apply them. YAGNI – You Aren’t Gonna Need It: The YAGNI principle states that a developer should not build functionality just because it might be needed later. Basically it says do not build any code/features for a product that are not currently needed. This principle will prevent you and your team from spending countless hours planning for some grand, imaginary and unknown future scenario. YAGNI will help you and your team from over engineering something based on what you think will be needed in the future. When applied in the right sense, time is not wasted on 1) Coding functionality that is not currently needed 2) Rewriting future functionality actually needed but is quite different from what was anticipated. It is based on the idea that things change with…

Team Clairvoyant

ClairvoyantGivesBack – How do we know we have a great team?

  While we usually talk about technology here, today we would like to take the opportunity to thank all the employees at Clairvoyant who participated in a team charity event at FMSC on Tuesday. This is one of the posts that will give a small glimpse into our culture and team spirit we strive for at Clairvoyant. Our team of volunteers gave an hour of their time to help pack food for the most needy kids in the world. A small Clairvoyant team of 15 members, along with few other volunteers helped pack one meal for nearly 11,000 kids at FMSC. It is a sad fact that nearly 6200 kids die of starvation everday worldwide. While this used to be a much higher number till not too long ago, efforts by various organizations have reduced this number significantly. We are just glad to contribute in our own way. While we…