We all talk about following best agile practices like TDD, code readability, no duplication and refactoring continuous code.

But in general, it is very hard to follow these practices while writing the production level code. Many times, we end up with a massively complicated code that no one wants to read or refactor. In this case, maintenance becomes a nightmare and leads to inefficient code.

As a growing organization, we at CoffeeBeans were not unknown to these problems. We lacked a proper platform for sharing knowledge about best practices of writing efficient code following proper agile practices. …

As machine learning is currently being utilized to decide everything, from stock prices, advertising, marketing, to medical diagnoses. It has never been more important to look at the decision-making process of these machine learning models and algorithms. Unfortunately, a good portion of currently deployed machine learning systems, are prejudiced in way of sexism, ageism, racism — you name it.

We are often quick to say that the way to make these machine learning models less biased, is to simply come up with better algorithms. However, algorithms are only as good as the data fed to them. …

Proof of concept (PoC) vs prototyping vs spike!!!!
Frankly to me all are same and throughout this article I will stick to the term PoC.
Looking up for definition of PoC I stumbled upon wikipedia which says,

Proof of concept (PoC) is a realization of a certain method or idea in order to demonstrate its feasibility, or a demonstration in principle with the aim of verifying that some concept or theory has practical potential.”

Phew!!! Thats a very heavy definition.
To me PoC is something which proves if stuff works or not. Anything beyond this and the whole fun around PoC gets sucked out.
A new project is about start and it comes with its own package of unknowns. 3rd party integrations? Explore a new graph based db? Flink vs Spark?
How does one estimate these unknowns? Obviously one can spend eternity in answering these questions but clients really don’t care about your anxieties.
They just care about time. And making blind assumptions without any validation can make or break a project.
Thats where PoCs are invaluable to quickly and efficiently validate our assumptions and gain clarity in regards to making important desciosns. …

By 2012 almost everyone got a smartphone. Back then, there was excitement about those devices. Remember how you used to spend good enough time on app store hunting the cool and kick ass apps.

Times have changed now and people are reluctant to download apps.


There are billions of apps now. And every single player bombarding user to download theirs.

Users have tried so many good and bad ones. With experience we have seen that the great apps have stood out and people trust recommendations more than going on an app spotting safari

**The apps that shouldn’t: **There are many apps that shouldn’t really be apps. I would like to have applications for listening to music or chatting with friends. But an app for renewing your life insurance doesn’t really make sense. I do it once a year. They can make a good responsive mobile website. …

Although, this is an old and dusted topic the points I intend to discuss here are based on my 7 years of experience with mobile app development.

Image for post

Hybrid vs Native Battle

Yes, no doubt that Native app can apparently give a better user experience. And no doubt that if you have budget constraints going native is a challenge. But there are a few points that we need to consider before making the decision. Especially, when there are so many beautiful hybrid app development platforms now.

  1. What is the purpose of the app? If the app is a utility and adds to the existing business you are doing, it is worthy to consider a hybrid app. If the app itself is the main business, think if you really need a native app? I suggest native only if you have to use a lot of native features like GPS, user experience needs to be kickass, and if you have the money. Most of the banking apps have gone for hybrid, to give you an example. …

Four simple but solid factors for any startup to succeed. This is based on my experience in more than 4 startups.

Image for post
  1. Idea: “*Of course your idea has to be great.” *Nonsense. It doesn’t have to be great. Even a mediocre idea executed brilliantly can do wonders compared to a great idea delving forever into your brain. So don’t be limited or overwhelmed by your idea. Shut up and Startup!
  2. **Execution: **How you execute your idea can be broadly classified by below:

a. The features: Start with minimal features for your MVP but these features have to be differentiators. In today’s competitive world there’s a high chance that your idea is already being implemented by others. That's good, that means there is a market for your product. …

The lighthouse customer or early adopter is the guy who has shown initial interest in your product and is willing to give it a try. If you make him happy, there is a good chance that you will grow quicker.

Image for post

You go to an event, there are 100s of people. It is practically impossible to talk to everyone. And then also, you collect so many business cards and forget who’s who.** How do you make sure you effectively network with the right people?**

Event apps are great to help where you can check the profiles of the attendees, see what's trending in the event, and stay updated by sharing posts and pictures. It definitely improves the effectiveness of any event.

Having said this, the event apps are transient and hence it is a challenge for getting them installed by the attendees. …

So you have an idea? Great. Many people are going to tell you to quickly come up with a prototype or an MVP and validate the acceptance of the idea. You start working on it and a month goes by for your MVP to shape up. Awesome.

What if I tell you that you can start validating your idea the very day the idea strikes you? **Have you heard of Dropbox getting famous without any servers but just with a video? **Well, with my experience I can say that there are many cases when you can confirm your idea without the MVP itself. …

Asha, one of the finest employees in her organisation, fell into a financial crisis a year back, for reasons outside her control. She missed some payments on EMI and her credit score suffered. This is making difficult for her to get a new job and is worsening her financial situation. Which in turn, is making it even more difficult for her to find a job.

This isn’t the truth, at least as yet. But you know that you are not very far from this reality. The reality where algorithms will start judging you and take more decisions for you. …


CoffeeBeans Consulting

CoffeeBeans helps small, medium and large businesses unlock the true potential of technology and AI to solve some of their most pressing challenges

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store