Expect all days of the week blocked

Well it all started with a small revolution called Mobile Monday, Bangalore. It was an initiative of some minds behind the mobile technology in Bangalore(Keshav, S R Raja, Rajan & Rajiv). It was actually a success.

The reason behind the success of the Mobile Monday has been its unique concept. The community meets every 3rd Monday of the month. They have a set agenda and people with passion. So much so that many communities in Bangalore are planning to adopt a similar approach. Like all good things he success of this has lead into a next step, which make use of Saturday. Now what rhymes best with Saturday, well one of thing is Startup. So here we have Startup Saturday. An interesting concept building momentum. What I expect next is the following, Testers Tuesday, Web Wednesday, UX Thursdays, FOSS Friday, Startup Saturday and finally Sleepy Sunday. Guys at least Sunday deserves a break :-)

Anyways I dont see this thing not materializing. For a very simple reason, the community is Bangalore is strong and growing. Each one of community has a lot of share and work with. Probably building this sort of a community is the first step towards making a Google, Yahoo and hopefully not MS :-P When people meet, they think twice as much. This is what will seed innovation and surely take the Indian IT to the next level.

Comments

The Ancient Mariner said…
are u the 100rab from Orkut?One wonders if u r the one from chandigarh and IPCM...
February 22, 2008 11:03 PM
100rabh™ said…
Nope....I am 100rabh from Bangalore
February 22, 2008 11:48 PM
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