While going through the second chapter of Shape Up book, just want to summarise some of the key points of it. Real-world scenario with “calendar feature” was perfectly broken down to the points, except of “point-zero” that is constantly missed out in Cyprus: With only six weeks to work with, we could only build about a tenth of what people think of when they say “calendar.” The question became: which tenth?...
Basecamp started off in 2003 as a tool we built for ourselves. At the time we were a consultancy designing websites for clients. Information would get lost in the game of telephone between the client, the designer, and the person managing the project. We wanted Basecamp to be a centralized place where all parties could see the work, discuss it, and know what to do next. It turned out lots of companies had this “information slipping through the cracks” problem....
Matt Mullenweg, the founding developer of WordPress and the founder of Automattic, joins Basecamp co-founder David Heinemeier Hansson for a spirited debate about tech monopolies, power in open-source communities, and how to be good stewards of the modern web that they helped build. Listen on Rework.fm
While striving to minimise the footprint of production compiled JS code for some of my side projects, I found this great collection of nice, but sometimes controversial, repositories. Problems with Moment.js: It is highly based on OOP APIs, which makes it fail to work with tree-shaking, thus leading to a huge bundle size and performance issues. It is mutable due to OOP APIs and non-pure functions, which cause bugs like these....
Evan You explains the principles behind the changes in Vue 3.0 at VueConf Toronto 2019 — Read on vuetoronto.com/videos/design-principles-of-vue-3-evan-you/
If you’re still not convinced by this, there’s a more details version of it here.
This talk goes back to 2007, but still valid. Especially in this hype moment of Headless CMS apps popping up every single day, providing its own vision of Content Delivery API’s.
Great article recently published by Dries Buytaert, founder of Drupal project, describing the balance of makers and takers in open source community: Small Open Source communities can rely on volunteers and self-governance, but as Open Source communities grow, their governance model most likely needs to be reformed so the project can be maintained more easily. There are three models for scaling and sustaining Open Source projects: self-governance, privatization, and centralization. All three models aim to reduce coordination failures, but require Open Source communities to embrace forms of monitoring, rewards and sanctions....
That moment is really the turning point,” Barbara Burian, a research psychologist at NASA who has studied Qantas Flight 32, told me. “Most of the time, when information overload occurs, we’re not aware it’s happening—and that’s why it’s so dangerous. So really good pilots push themselves to do a lot of ‘what if’ exercises before an event, running through scenarios in their heads. That way, when an emergency happens, they have models they can use....