SivaLabs

If you are feeling overwhelmed by the rapid pace of technological advancements, especially in the field of AI, know that you are not alone. The AI landscape is evolving at an unbelievable speed, with new ideas and tools emerging every day. This can be both exciting and daunting, as it challenges our understanding of what’s possible and forces us to adapt quickly.

You may encounter conflicting narratives: a CEO claims that in 9 months a 90% percentage of code will be written by AI, YouTubers who became AI Experts overnight tell you that “AI will take over the world by 2030”. And then suddenly, you come across a Tweet or a LinkedIn post saying AI is not yet good enough for the real world projects.

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.

Social media is a double-edged sword. Depending on how you use it, it can be really 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.

I work as an Architect/TechLead/SeniorDeveloper depending on client engagement. And, Java is the primary programming language that I have used most of my career. In recent years I got an opportunity to work with Go, NodeJS and .Net Core technologies too. I find Java, especially with SpringBoot, a solid platform to build enterprise grade applications.

Java is and has been the primary programming language I have used throughout my career. If I want to build something quick for a prototype or if I need to pick the tech stack with a tight deadline then Java is my first choice. Especially after Java 8 it becomes more and more feature rich and powerful.

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 variety 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?

I am Siva, working as a Software Developer in Hyderabad, India. Working as a Software Developer is very exciting as you see new things coming in every day. If there are no new things, at least we put a new fancy name to some old concept and celebrate (#microservices) :-). But in my opinion, working as a Software Developer in India is a little bit different and hard too. A few things are good, and a few things are bad.

IT is one field where you can find new things coming every day. These 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 a better way of building software systems. But as with any architectural style, there will be pros and cons to every approach.

Before discussing the good and bad sides of the MicroServices approach, first, let me say what I understood about MicroServices.