Open Coffee Club, Bangalore...What should we be doing

Last time around I had promised Ramjee about writing a post on Open Coffee Club and my thoughts on how to improve it. So here it is.

Well I feel that OCC is a good concept. I think there may be some other similar motived events happening in Bangalore itself. But surely many do not know about it. One thing could be we could coordinate with those people, if any.

Another thing is that if we are meeting fortnightly then its better we meet with a theme. Lets plan for whats going to be discussed at the meet. The interested audience would definitely be present there. Also it gives the member time to prepare themselves with ideas and questions before hand. This I think is also necessary considering we are going to meet a lot more often.

I loved the one to one discussions that we had as a group after the initial talks. Though they are fruitful but then a starter is required by means of the initial talk. I will give you the example that the introduction laid ground for further discussions at the last meet. I hope you guys will agree with me.

Meeting place as Brewhaha may not be attractive for the poeple there. I think we need to find a better place. I would suggest that if any of the member knows of some college which can provide us with space on a Sunday morning would be good. It would be better if the college is centrally located.

Hari had aid that 10am should be starting time. But I beg to differ. Its really difficult reach any place in bangalore that early on a Sunday morning. Its as good as rushing to office on a Sunday morning.

I really think OCC has got onto a good start thanks to Ramjee and Vaibhav.

Comments

Post a Comment

Popular posts from this blog

[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

[15th December 2024] Interesting Things I Learnt This Week

Image
1. Why you should never use !! in Kotlin - Using double-bang operator(!!) is a bad practice; multiple alternatives cover every other possible case. Using it is a hack and a shortcut that will backfire while not saving you much time at the time of writing using it. You shouldn’t use it unless you're writing a short personal script. My Take : The double-bang operator (!!)  which throws null pointer exception in Kotlin might very well be considered " Billion Dollar Mistake ." While it offers a concise way to assert that a variable is not null, I believe it's preferable to have slightly more verbose code that explicitly handles nullability and avoids potential runtime exceptions. Null pointer exceptions have plagued programmers for decades, and introducing a feature that can easily lead to them seems counterproductive. I'm uncertain whether all Kotlin linters currently check for excessive or inappropriate use of the !! operator, but if yours don't, I strongly re...
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