85 posts found
I'm sitting in the faraday cage of the climbing centre, with no Internet access to distract me, so I'm watching the kids attempt the different walls. Some are starting on a slightly angled wall, then progressing to a vertical wall with lots of hand holds. Others are learning to tie ropes, belay and navigate overhangs etc. It got me thinking a lot about the problems we solve.
Obviously, we need to actually write some code to build the features, and fix the bugs, and refactor away the technical debt. However, often there's a choice and it's in those moments that we should always prioritise communication
The visible progress in rowing is the sliding back-and-forth but the "hidden" effort from your legs is what actually makes you go faster. We should focus on the hidden effort in software too.
A run-through of how I manage windows on macOS using Amethyst, an automatic tiling window manager
Tools we used at Podia in 2020