My journey of being a planner at Barcamp Bangalore

I learnt about Barcamp Bangalore sometime in June or July 2007. I was fascinated by the idea of sharing ideas, learning about technology and talking about them as well. I attended a large lot of talks on both the days that it was there. I dont remember what all talks I attended, but they were not tied to any one technology or aspect at all. Plus everyone had equal rights to talk and you need not be that well known guy to talk about something you are passionate about. That was the best part of the entire event according to me.

Post event, I joined the yahoo mailing list and after a few days there was this call for anyone interested in planning the next one. I was excited to be part of it. A naive idiot, just a couple of years out of college, I thought wow, this going to be something. Then at the planners meet there were a lot of folks. But I remember Arun Ram, Hari, Jace a.k.a. Kiran(I found out that day), Srinivas and Keshav . I felt awesome to be able to contribute something here. It was made very clear that everyone was equal and could they would be heard.

From my blog about that day (http://the100rabh.blogspot.com/2007/10/barcamp-bangalore-07-winter-edition.html)

Soon after we left for our ways with the idea that we would be doing something good to start an ecosystem in Bangalore, which can actually make Bangalore truly a Silicon Valley.

As you could imagine, I was filled with a lot of optimism with that. We all wanted to experiment and make things better for the ecosystem. This is something I have not forgotten and keep on pushing things for the better.

I have been part of Barcamp Bangalore ever since and it has taught me a lot of things. More importantly it has kept my passion of technology alive regardless of what technology I have been working on in my day job. I could say a lot more about things I have learnt at Barcamp Bangalore but that for the next post.

Comments

Post a Comment

Popular posts from this blog

[24th November 2024] Interesting Things I Learnt This Week

Image
1. AI Makes Tech Debt More Expensive - The core argument is that generative AI significantly widens the gap between codebases with low and high tech debt. Companies with clean code can leverage generative AI to write code much faster, while companies with messy legacy codebases struggle to adopt these new tools. This widens the gap between the two codebases, making tech debt even more expensive for companies with outdated systems. My Take : Legacy systems inevitably accumulate technical debt. A common analogy for this is the state of urinals over time: missed targets lead to increasing mess, keeps pushing people away from urinals and leading to more mess in turn. AI-powered coding tools could potentially accelerate the accumulation of tech debt. However, skilled engineers can leverage AI to reduce and even eliminate it. Ultimately, AI is just a tool, and human judgment remains crucial for making informed decisions. I hope AI will be used responsibly to drive positive outcomes. 2. Make...
Read more

[17th November 2024] Interesting Things I Learnt This Week

Image
 1. Booleans are a trap : Booleans, while seemingly simple, can introduce complexity and limitations into domain modeling. When used to represent complex states, booleans can lead to unclear code and potential errors. To avoid these pitfalls, consider using enums or enum sets. These approaches provide a more expressive and maintainable way to model complex states in your applications. My Take : I wish I had learned this earlier in life. When working with Google Docs, I realized the limitations of booleans. Expanding boolean-based behaviors often led to adding more fields, making the system complex. Enums would have provided a simpler solution. The problem wasn't just the booleans themselves, but also the need to pass them through multiple layers of the stack, often requiring additional parameters. Another important aspect of enums is the inclusion of an " enum not specified " state. This state explicitly indicates that an enum value hasn't been set, which can be usef...
Read more

[1st December 2024] Interesting Things I Learnt This Week

Image
1. C++ Pitfalls - this article, explains some of the pitfalls you can fall into when programming in C++ and shares their experience with them. This includes Operator precedence, Arithmetic conversion rules, Right bit-shift, Implicit conversions and Order of evaluation.  My Take : We've all read about JavaScript's quirks, leading to unexpected outputs. But let's remember that such behaviors aren't unique to JavaScript. Even languages like C and C++ have their share of ambiguities and compiler-specific behaviors. While it's tempting to dive deep into these intricacies, I've found that focusing on clear, consistent, and unambiguous code is often more practical. However, understanding these nuances is essential for any experienced programmer. It helps us avoid pitfalls and write robust, reliable code. Remember, mastering a language isn't just about writing "Hello World." It involves delving into its intricacies, including its counterintuitive and ambi...
Read more