When I first started as a technical people-manager, like many developers, I'd never really seen the value of 1-to-1s.
Over time, though, I've iterated on how I view and run them so that they're more valuable as a feedback mechanism for both me and the people in my team.
On reflection, here's a few observations and practices that I've found helpful - hope they're as useful to you as they have been to me!
"Most of the time, most people don’t need most of the power of bitemporality."
That said, bitemporality does provide us with a useful, rigorously defined mental model to help reason about time-oriented problems, the tools to implement it and, by approaching problems with this in mind, we become aware of edge cases we may have otherwise missed.
Naturally, we'd like to have our cake and eat it: we want the ease and performance of a traditional update-in-place database for everyday transactions and queries, but the safety net of a bitemporal database when we need it - and this is our primary success criterion for XTDB.
Naively mixing lazy-seqs and transducers in 'just a quick Clojure data transformation script', with unfavourable results. Hope it saves someone a trip down a rabbit hole!
Senior/Junior Clojure Developers + Angular developer - London, UK - Social Superstore
We're a small startup based in Aldgate, allowing people to create online shop-fronts containing products from a selection of thousands of retailers. Store owners can then review, endorse and promote their products to their social networks and blog audiences, earning a commission in the process.
From a store-owner's point of view, it's a cost-free, risk-free and logistics-free way to set up their online business - they manage the sales and marketing of their stores, we manage the technology.
We are looking for good Clojure developers with an interest in the retail industry to take our product from a working proof-of-concept to a thriving business. Being part of our first in-house team, you'd be a big part of shaping what we build, and how we build it.
Our technology stack is 100% Clojure on the back-end, Angular/ClojureScript on the front, on an AWS infrastructure.
There are several roles available, with salary ranging from £35k to £70k depending on experience, and share options.
If this is something you'd be interested in, great! To apply, or if you have any questions, e-mail me at james [dot] henderson [at] socialsuperstore [dot] com
Over time, though, I've iterated on how I view and run them so that they're more valuable as a feedback mechanism for both me and the people in my team.
On reflection, here's a few observations and practices that I've found helpful - hope they're as useful to you as they have been to me!
Please do share your own tips and tricks :)