I only have the word of the internet to tell me that Tsundoku is the condition of acquiring new books without reading them. My metric for this condition is my list of books I own but have yet to read:
- the last three parts of Christopher Tolkien’s Histories of Middle-Earth
- Strategic Information Management: Challenges and Strategies in Managing Information Systems
- Hume’s Enquiries Concerning the Human Understanding
- Europe in the Central Middle Ages, 962-1154
- England in the Later Middle Ages
- Bertrand Russel’s Problems with Philosophy
- John Stuart Mill’s Utilitarianism and On Liberty (two copies, different editions, because I buy and read books at different rates)
- A Song of Stone by Iain Banks
- Digital Typography by Knuth
- Merchant and Craft Guilds: A History of the Aberdeen Incorporated Trades
- The Indisputable Existence of Santa Claus
- Margaret Atwood’s The Handmaid’s Tale
And those are only the ones I want to read and own (and I think that list is incomplete – I bought a book on online communities a few weeks ago and currently can’t find it). Never mind the ones I don’t own.
And this is only about books. What about those side projects, businesses, hobbies, blog posts and other interests I “would do if I got around to it” and never do? Thinking clearly about what to do next and keeping expectations consistent with what I can do is an important skill, and one I seem to lack.
A full-stack software engineer is someone who is comfortable working at any layer, from code and systems through team members to customers.
My current record of FOSDEM attendance sees me there once per decade: my first visit was in 2007 and I’m having breakfast in my hotel at the end of my second trip. I should probably get here more often.
Unlike a lot of the corporate conferences I’ve been to in other fields, FOSDEM is completely free and completely organised by its community. An interesting effect of this is that whole there’s no explicit corporate presence, you’ll see companies represented if they actually support free and open source software as much as they claim. Red Hat doesn’t have a stand, but pick up business cards from the folks at CentOS, Fedora, GNOME, ManageIQ…
When it comes to free software, I’m a jack of many trades and a master of none. I have drive-by commits in a few different projects including FreeBSD and clang, and recently launched the GNUstep developer guide to add some necessary documentation, but am an expert nowhere.
That makes FOSDEM an exciting selection box of new things to learn, many of which I know nothing or little about. That’s a great situation to be in; it’s also unsurprising that I know so little as I’ve only been working with free software (indeed, any software) for a little over a decade.
Coercion over configuration.
There was no need to build a package management system since CPAN, and yet npm is the best.
Every time a new programming language or framework is released, people seem to decide that:
It needs its own package manager.
Simple algorithms need to be rewritten from scratch in “pure” $language/framework and distributed as packages in this package manager.
This is not actually true. Many programming languages – particularly many of the trendy ones – have a way to call C functions, and a way to expose their own routines as C functions. Even C++ has this feature. This means that you don’t need any new packaging system, if you can deploy packages that expose C functions (whatever the implementation language) then you can use existing code, and you don’t need to rewrite everything.
So there hasn’t been a need for a packaging system since at least CPAN, maybe earlier.
On the other hand, npm is the best packaging system ever because people actually consume existing code with it. It’s huge, there are tons of libraries, and so people actually think about whether this thing they’re doing needs new code or the adoption of existing code. It’s the realisation of the OO dream, in which folks like Brad Cox said we’d have data sheets of available components and we’d pull the components we need and bind them together in our applications.
Developers who use npm are just gluing components together into applications, and that’s great for software.