SivaLabs

In the software development world, once in a while a new ideology or process or technology will be introduced. And, the whole developer community goes crazy on that shiny new stuff. A decade ago it was Agile/Scrum, then DevOps, then SRE and now Platform Engineering. Somehow, I got curious about what is all the fuss about Platform engineering and read a bit about it, and I felt “Oh, people realized that DevOps is a good idea but impractical, and they are correcting it now”.

SocialMedia is a double-edged sword. We can put it to good use or become addicted to it and suffer. The challenge is, it is hard to know when it became addiction. Most of the time we get to know that we are addicted to it once we started suffering. I use social media, especially Twitter, very much mainly to keep up with what is going on in the tech world. I must say Twitter helped me in several ways throughout my career.

Few months ago I asked on Twitter “why you think Java is complex?” to understand others perspective. I'm really surprised looking at so many people assuming #Java is complex than other languages. I worked with mostly Java and in recent years I worked with Go, NodeJS too. But I feel Java is less complex and more productive. Any specific points why you think Java is complex? — Siva (@sivalabs) April 1, 2022 And, I got many responses(opinions, insights) and I compiled all the responses into this blog post My attempt to understand why people perceive Java as complex.

Social media is a double-edged sword. Depending on how you use it can be really be helpful or become a source of pressure and frustration. I don’t use Facebook and Instagram much, but I use Twitter and recently started using LinkedIn too. Twitter is my primary source of technical information. I follow many good people in Java Community. Twitter is a great platform to connect with those awesome people and I learn a lot from what they share.

I worked at different types of IT organizations including small 20 people company, world’s largest bank, start-ups etc. Working at a service based company is both very interesting and at times frustrating depending on the client. On the positive side you get to work on different types of domains/applications, different tech stacks, and you may get to learn verity of organizational cultures. On the downside you may end up working with “Typical traditional enterprise organizations” which makes you question your career choices!

When I observe old people I notice one interesting thing. They don’t usually react aggressively like teenagers do. Even when they have to deal with difficulties in life they deal with it calmly. Even when some people undermine them they simply give a smile and move on rather than trying to prove they are wrong. I wonder is growing older makes them wise? Looking at some people I know who is in their 50’s, I can confidently say No, becoming older doesn’t make them wiser automatically :-)

IT is one field where you can find new things coming everyday. Theses days the whole developer community websites are flooded with MicroServices and Docker related stuff. Among them the idea of MicroServices is very exciting and encourages better way of building software systems. But as with any architectural style there will be pros and cons to every approach. Before discussing what are good and bad sides of MicroServices approach, first let me say what I understood about MicroServices.

Last week I got to take interviews to hire senior java developers with around 5 years of experience. But after the interview process is over I felt like the frameworks makes developers life easier but at the same time making them dumb. Everyone puts almost all the new frameworks on their resume claiming they have “Strong, working experience on Spring, Hibernate, Web Services etc”. Here is how the interviews went on.