Smart speakers such as echo or google home, have enabled us to do wonderful things with speech. Instead of just plain commands, they can also start a smooth conversation with you and do tasks for you, such as ordering food, making payments, reading news, listening to music, reading books, telling jokes, entertain your kids and a lot more stuff.
Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves. – Alan Kay
Writing code is simple. Yes, you read it right. It is simple, but writing code as readable as a fairy tale is an art.And art is not simple. Now why should we write readable code? Because our code is for humans first and machines later. If you are working alone that’s fine, but if you are working in a team (in most cases yes) you need to collaborate with your team members.
To achieve that, you need to write code which is easily understood by others.If your code is a puzzle for others, its not a good code. It might be working correctly, it might be very efficient but not readable.Now the chances…
View original post 1,189 more words
Facebook.com is the most popular social networking website which has more than 1.2 billion monthly active users. This number is increasing everyday, which in turn increases the data being generated exponentially. You can just imagine how much data is generated on Facebook in terms of text, images, videos, locations etc everyday.As per Facebook posts on code.facebook.com, their warehouse stores up to 300PB(peta bytes) of data with an incoming rate of 600 TB per day.Believe me, thats a lot of data.
For our not-so-tech users lets discuss something on bits and bytes.
- 1 Bit – A value of either 0 or 1.
- 1 Byte – 8 bits.
- 1 KB(Kilo Byte) – 1024 Bytes
- 1 MB(Mega Byte) – 1024 KB
- 1 GB(Giga Byte) – 1024 MB
- 1 TB(Tera Byte) – 1024 GB
- 1 PB(Peta Byte) – 1024 TB
- 1 EB(Exa Byte) – 1024 PB
- 1 ZB(Zetta Byte) – 1024 EB
View original post 797 more words
In general it is a very simple pattern. You just wrap your function/method/behaviour with another function which keeps track of the failures/success of the that function (service/DB calls) and opens or closes the circuit for you. Sounds simple enough. It is simple.
I have been learning and playing around with GoLang lately and it seem to be fun. At first being a Java developer it looks weird and complex, but once you start playing around it is quite fun. Why did I start learning Go ? - I read a lot about its features like being … Continue reading Quick to digest cheatsheet – for GoLang