I've decided to publish this blog post because it depicts the way of organizing the work that is non-linear, highly async, and requires constant navigation across vast amounts of multi-dimensional, interconnected data. IMHO such a problem space requires a very unorthodox approach. This is a story about how I've managed...
Writing documents is so passé nowadays. The (software development) industry has removed this activity from typical software crafts(wo)men agendas nearly completely. The longest written forms we have to deal with are usually: commit messages, user stories in Jira, integration test specifications in some Cucumber offspring, and PR comments....
Dunno about you, but no one, ever taught me how to take notes properly. I mean - theoretically, it's not a big deal. You listen, you pay attention, you write down the most critical information and potentially underline or highlight stuff that has especially caught your attention, for whatever reason....
I'm not keen on this word. "Grooming". I've been doing it (sort of) long before I've learned about the thingie named Scrum, but until this very day I haven't convinced myself to call it that way. Grokking domain, crunching through problems, knowledge mining, functional decomposition - all these work better...
> This short article is all about: the end of non-fiction books (?!), how to extract (& preserve) KNOWLEDGE out of raw information, what kind of tools can be used to support this process, why it requires more effort than just understanding the written words. Few days ago someone has linked me a...
> This blog post is all about: why task trackers & basic note-taking apps are not enough anymore, where's the border between the need of handling structured & unstructured data, why we need some sort of a database (but with a flexible UI on the top) and what's the current direction of an...
