Context Distributed systems will fail. Things gets complicated as the data requirements / scale increases. It’s about how your system responds to partial failures and spikes. Fault is an incorrect internal state in your system. Failure is an inability of the system to perform its intended job, eventually means loss Read more…
Why services are needed One of two main reasons: You have multiple independent teams so the idea is to separate services to make independent progress and less alignment / communication / blockers. One of the components in the application has very different / higher scaling requirements than others, which makes Read more…
Company culture refers to the attitudes and behaviours of a company and its employees. It is evident in the way an organisation’s people interact with each other, the values they hold, and the decisions they make. (source) Culture defines how company builds products, how responsibilities are shared and how trade Read more…
Simplicity Focus on simplicity; be it – deployments, process, design, apis or people. First Principles The simplest explanation is usually the correct one — Ockham’s razor. Focus on quality not speed; quality code is easier to maintain and extend. Don’t break what ain’t broken. Don’t break what you cannot fix. Read more…
Why? Over the years we have been passionate about twitter platform and the potential it has. Although as primary developer I don’t tweet much bit still spend lot of time reading and following people across locations, political opinions, technologies etc. There are times when you are traveling, are at work Read more…
Managing your tweets and tweet lists If you have read our previous blog post we had proudly announced our new tool this time around to manage your tweets. To add more context on why would you might need such a tool: There is too much information on Twitter Tweets are not organized Read more…
As per Wiki’s deleted (Yeah! I found below content from Google’s cache) article on this
“Reinventing the wheel is a phrase that means to duplicate a basic method that has already previously been created or optimized by others..”
Lets get back a couple of steps, when development of software begins, it usually starts with a prototype, and when things start getting complex the development team starts taking out common code and create frameworks around it. These frameworks are then used / improved by the developers.
Read More!
I happened to visit a cyber cafe for some reasons, and I had to take the screenshot of the screen and Alas, for some (security :P) reasons, print screen was not working. Grrrr..
Luckily, the guy had JDK installed on his machine and I had some good 10 – 15 minutes to pull this up. So I decided to quickly use Java to capture the screen and thought to share the Utility with you. Offcourse! I have now added Swing help everyone out here.
You can skip the entire post and can play around with the code / utility with section downloads below –
Downloads –
[Q] So, what is Java Bytecode ?
[A] Bytecode is the heart of Java portability. Each Java program you write is first converted to a .class file (bytecode), which is then interpreted by Java interpreter.
Few days before I came to an interesting post, which provided a sample code in Java byte code format. Interestingly decoding the code to Java was no big deal as plenty of tools are available like JAD.
But it sparked something more than just the sample code, why is byte code important and why must a Java guy know that ?
Know Why!
With Storm, tables can be mapped to entities with @Table annotation. It works similar to most of the ORM solutions with few exceptions. Example Mapping: @Table(name = “DEMO_ENTITY”, version = 2) class Entity { @PrimaryKey @Column(name=”ID”, type = FieldType.INTEGER) private int id; } Every table must have a @PrimaryKey annotation, Read more…