Написав кілька сотень слів про свій недавній досвід. Я займаюсь розвитком і підтримкою великої системи на Clojure. Але не придумав куди запостити, тому виклав там, де ніхто не побачить https://t.co/ZiGqtxBFq7 :)
Підпишіться, ще щось напишу. Можливо навіть цього року :)
You rarely solve hard problems in a flash of insight. It's more typically a slow, careful process of exploring a branching tree of possibilities. You must pause, backtrack, and weigh every alternative.
You can't fully do this in your head, because your working memory is too limited. Writing is the external medium that affords the time and precision necessary.
Serious thinking must be done in writing. And that's why you can't outsource your writing, because then you're outsourcing your thinking.
У нас якось дизайнер залишив свій особистий номер телефону в макеті сайту. Здається, про реліз він дізнався раніше, ніж нам прилетіло сповіщення в слак :)
Behind every great product there’s at least one engineer who knows the entire stack, takes problems personally, and jumps in and solves them.
Without regard to ownership, credit, or chain of command.
If you don’t know who this is in your company, I have bad news for you…
It's only possible if the whole project scope is in team's hands and there is clear vision of what the product needs to be.
It doesn't work if product vision is fuzzy or there is underlying complex business process you're trying to navigate. It just takes time.
We did something like this recently. 4 week deadline with full team working exclusively on a single thing. It was successful (we shipped before a deadline) and the most fun project I can remember in a while.
The key insight with Shape Up was to give up on software estimates entirely. Flip the script. Pick a budget but leave the scope flexible. Then ship the very best you can do within that budget. Works like magic. Great software shipped every 6 weeks. https://t.co/q5VJVnZhoB