Skip to main content

Being Cloud, Social and Mobile is the next step in being humans?

In the past few days the computer science world lost two of the most valuable gems, Steve Jobs and Denise Ritchie. While Steve jobs was the people hero, Denise Ritchie was a computer science hero. While the two did the things they did decades apart, there was one common trait shared by both of them, they both worked hard to make things simpler and build a platform for others to take charge.

Looking at C programming language no one will say its simpler but if you compare with the assembly language before C you will know the simplicity of it. Looking at Steve Jobs inventions right from the Mac to the iPad, they also tell similar story, the inventions were made for simplicity.

An ad for iPhone simply states, what do you want to do with this phone? No jargons, no complexities. The c language had similar concept, what do you want to do? Printf? Scanf? getCh? Computer engineers will know these keywords, for others they are part of c programming language. Only the ones who have worked or taken a class in assembly language (I took two one for microprocessors and other for microcontrollers, how glad am I to work with force.com) will know the power c have to them.

If we have to learn one thing from both these visionaries, it is, make things simple. They both strived hard to make complex things very simple. Simple so that everyone could use them. In CRM this is the simple problem we try to solve, how do I connect to my customers easily? How do easily understand what they are saying?

Most importantly where are they complaining?

Most of these customers now are social, they are using the social channels to communicate. It makes sense to meet them halfway there, by quickly migrating to SCRM, the company can bridge the gap between complains and customer service. The employees of the company who will be constantly in touch with the costumers, will be using the smart phones. It makes sense to give them the flexibility of mobile access, so that they can work freely with the customer.

Finally using cloud systems also makes sense. We live in subscription based economy, business users need not understand the complexity or the concept of server software. There is a concern about data privacy but that can be addressed by a trustworthy vendor. Simply code in your username and password and start using it.

We are in this world for a limited time, instead of increasing complexity of the things we do, let's make things simple. Many suits won't agree to this but business should be as simple as using an iPhone.

Simple. Easy. Enhancing.

Comments

Popular posts from this blog

Video: Top ten tips on how not to ruin Salesforce implementation

Another presentation for the London Salesforce Developer Group using mobile app. 
When it comes to Salesforce development, we all know what it takes to deliver stuff. Having a certified professional helps you gain a knowledgeable partner but what about the things such as common sense?  We all know how to deliver things on client requirements but what about things that are not mentioned by the client. We will be discussing in details things that will enhance the user experience, focus on tips to read your customers mind and have a bit of perspective on the user experience.

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…

Four secrets to improve the usability of your visualforce/Lightning pages on Salesforce

In the immortal words of a certain machine returning back in time, I am back. For now. After procrastinating for over a year and drafting a lot of rants- I am back with a very important coding lesson for you. For now.

When we are designing a Visualforce page or an app or a lightning component (added that only to trick google) or any web page for that matter, we often tend to wrap up things quickly. Ask anyone on the team, how to design a good User Experience? and the person will immediately throw buzz words like Bootstrap, angular and other useless libraries (did someone squint?)

Ok, Bootstrap, Angular-Js, and all the libraries are really cool and are useful in designing a fabulous UI. They are helpful in creating responsive pages that will work on all the devices but this post is not about those. Nope. For the purpose of this post, all the external libraries and buzzwords you use to decorate your resume are useless. (Adding Angular JS in your resume for a Salesforce consultant posit…