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

[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

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

Image
1. One Company A/B Tested Hybrid Work. Here’s What They Found. - Recent research has revealed that a hybrid work model, where employees work from home three days a week, can significantly boost employee satisfaction and reduce turnover rates. This not only improves employee morale but also saves companies millions of dollars in recruitment and training costs. To successfully implement a hybrid model, businesses should prioritize rigorous performance management systems, coordinate team and company-wide schedules, and secure leadership support. Moreover, executives should experiment with different management practices to optimize their approach and maximize the benefits of hybrid work. My Take : There have been too many debates about remote work versus office work. I would have loved to see data comparing the effectiveness of remote, hybrid, and office-based work. I've worked at companies that mandated office work, like Tata Elxsi, where we didn't have laptops and had to rely on...
Read more

[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