Progressing from v2 to v3 boulders
To my experience V3/6B is the first "real bouldering" grade in most gyms. I mean one could pull thru virtually any V2/6A+ by applying some extra muscular tension, but most likely it wouldn't work starting V3/6B grade. One needs to develop basic footwork and body positioning skills to get there.

Good news. It is not that hard to develop those basic climbing technique skills. Just stick to your "doable" grade for a couple weeks or so with a somewhat strange attitude - you do not want to "send". "Success" of sending is nothing in the context of learning. Process of getting better is everything. You do want to perform any and every move like perfect. All moves and (even more important) transitions from one move to another should feel just right. Moves should feel natural and fun. If you feel a tiny bit of struggle stop here (and I mean it, read - jump off) and work the move (or transition from one move to another). Do everything possible and imaginable - rotate your heels, drop your knees, press your body left and right, seek for that "like perfect" move execution.

Often it is a good idea to reverse that tricky move - often we cannot execute a move due to lack of knowledge how should it feel after sticking to the next hold. When reversing move we start from that "after the move" position and we already know the "before the move" position, thus all we need is to decipher a way to transit from one position to another via some non-obvious coordination.

Basically my advise is to concentrate on climbing movements quality. There is a need to limit boulders stiffness to reduce the stress level so you can concentrate on the task. The last but not the least - do not stick to a particular wall angle, and holds type, and climbing style. The goal is to develop a broad set of footwork and body positioning skills.

P.S. Strive to repeat any and every problem was hard to send. The ultimate goal is to develop a solid climbing style so yet another "near impossible" project will be a nice warmup problem in a mere couple weeks.
april 2018
Tyre size
100/90-19 is the way Triumph supplied the bike from the factory
steering is very 'quick'
in theory this tyre is better for off road use
a lot of riders complain they are badly affected by different road surfaces, ruts, white lines, tar joins.

110/80R19 is the alternative fitting (belatedly approved by Triumph)
steering is slowed down but IMO still very responsive
ride through the front end is more supple
handling is IMO more secure
there is a good selection of road going radial tyres, most of which give much improved wet grip.
july 2017
« earlier      
academia actor-model adv aeropress aerospace airplay algorithms analytics api architecture arcteryx array audio availability backpacking baseball bash bayarea beauty beef beer benchmarking benchmarks best-practices bicycles book books bourbon bubbling business c canvas cap-theorem cascades cassandra challenge character-entities chartreuse cheat-sheet cheese chef chicken climbing clo clojure closure cocktail coffee coffeescript compatibility complexity computation computer-science concurrency cooking coroutines cors cql creation cryptography css cycling d3 data data-modeling data-structures data-types database databases delegation deployment depression diffie-hellman distributed-systems django documentation domain drinks dualsport ecma editors education efficiency eggs encryption engineering erlang events eventual-consistency exercise explain facebook failure fault-tolerance file-systems fish fishing fit food forecast framework functional-programming generator geocoding geodata gil gin gis git go goretex graphing hadoop ham hash hash-collisions hbase health heroku hike hiking hive home homebrewing http humility ie image indexing init insulation insurance interface internet-explorer io ipc italian java javascript jquery json jvm kafka kitchen knee languages learning life linguistics linkedin linux lisp literature lua lulz maintenance make manual map maps math memory messaging metaclass metaprogramming metrics mezcal migrations mock modeling mongodb monitoring moto motorcycle mountaineering msr mvum naming networks nginx nlp node.js nosql oauth ocean open-graph open-source operating-systems operations optimization outdoors papers parallelism partitioning patterns perceptual perfectionism performance perseverance persistence perspective philosophy php physics pizza pork postgis postgresql potatoes printer probability process productivity profiling programming progress projects provisioning psychology pubsub python quality quickcheck quote rails raphael raspberry-pi recipes redis refactoring reference reliability review rfc riak rides roads routes rst ruby running rye salad salmon scala scaling scheme science security sentiment sequence serialization server shell sherry sicp side sides signals simplicity ski skiing skill social software sorting soup sous-vide specification sphinx standards startup statistics stew storage stove stretching style stylesheets success svg synchronicity systems tacoma taste templating testing thought threading traffic trails travel turntable tutorial typing typography upstart usfs varnish veal vegetarian video vim vinyl virtualization visualization weak-reference weakref weather whiskey whisky wine wood workflow wtf x86

Copy this bookmark: