Some tips and learning from cycling to work

For the past some days I have been cycling to work and overall its been a pleasant experience as yet. I thought I would share some of the learnings with this post. So here it goes in no particular order

1. Make sure your tyres have enough pressure in them. If it gets low, it will become difficult to ride it.

2. Make the seat position such that you can peddle on the full. It gives you more power and also prevents what’s called Biker’s Knee. By instinct we would like it such that our feet reach the ground easily. Never go by that.

3. Cycle fearlessly. Be on the left side of the road as much and possible, but never go to the extreme left. It might land you in trouble. You can surely take minor panga from the faster automobile users.

4. If in places like Bangalore, where you have too much ups and downs, keep trying different alternate routes so that you can take maximum advantage of the slope.

5. Dont wear headphone. You might not find out whats happening on the road. Sometimes I feel like the low sound making cars are better than ultra silent cars. You atleast realise if there one coming from behind.

6. In normal cycle brakes, sudden braking does not work well. It makes sense to gradually slow downhill by applying pulses of brakes rather than a constant one.

7. Cycle only if you are having fun doing it else it may become a burden on you.

Enjoy and happy cycling.

Comments

Anonymous said…
It was nice written about cycle tips which is very helful for all those who some times use cycle ....

Darshan

BPO solution
August 06, 2009 5:58 PM
100rabh™ said…
Darshan, thanks for all these nice words
August 07, 2009 9:50 AM
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

[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

[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