Why I am keeping myself away from Barcamp Bangalore planning

I have been part of Barcamp Bangalore for 9 years now and its been more like a part of my life. I have played many roles there, from keeping the website up, readying it for the next edition, making the Android App, sometimes acting like a product manager by telling others what to do and what not to, sometimes acting like a project manager by constantly keeping tabs on folks who have deadlines to keep, sometimes acting like a finance guy to takes care of sponsorships and expenses. It felt almost like running a bootstrapped startup where no one gets paid but gives you a different kind of satisfaction. Its been fun all these years working with so many different people that I dont want to name folks for the act of missing even one of them will be criminal on my part. But I must say, each one of the folks have taught me something and each have a quality I admire and try to build into my life ( but sadly sometimes I fail at it, obviously they are just so awesome)

But this year I decided to not be part of the planning team. I have usually seen this happens when there is an internal struggle in the team or the folks have been upto something completely different and are head down in that one. Well for me its none of them.

I have seen that sometimes when you are the defacto leaders of the team, the team becomes dysfunctional once the leader is not there, like what happened to foss.in. Even Barcamp Bangalore once struggled when one fine day a few of the leaders decided that they have other priorities. I want to make sure that Barcamp Bangalore goes on even though I am not there. Me and Daaku have been kind of been there the longest and with Daaku not being there last time around, his absence was sorely felt during the entire time but the team was able to work around that.

In hope there are multiple leaders in the team who can steer Barcamp Bangalore to the continuous success it has been, I decided to leave the team to run the show without me. I decided to be on the sidelines of everything. I just am watching these amazing folks run the show this time and will be providing the help needed at the time( which I am sure they dont need). And I am now just waiting for the dates for next BCB to be announced.

Like every year, yes my session idea is already there in my head which I will post as soon as registrations open at http://barcampbangalore.org .  

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