In Search of Organic Software An Article by Pirijan Ketheswaran pketh.org Two different kinds of farms can grow vegetables. One is a factory farm built for scale, and the other takes the time to grow more expensive but healthier plants without pesticides. Will everyone appreciate the difference? Of course not, but the latter plants are labelled ‘organic’ to give us the information and the choice, so that those of us who do care can make better decisions. So maybe we should have ‘organic’ software as well, made by companies that: Are not funded in such a way where the primary obligation of the company is to 🎡 chase funding rounds or get acquired (so bootstrapping, crowdfunding, grants, and angel investment are okay) Have a clear pricing page Disclose their sources of funding and sources of revenue softwarebusinessfarming
How I Build An Article by Pirijan Ketheswaran pketh.org In 2014, I wrote about my belief that design and engineering are best when tightly woven together. That’s truer now than ever. If I’m feeling confident, I’ll jump right into my text editor…From here, more functionality is added and the code is tweaked until the feature looks and feels right to me. Whether it’s something simple like this, or prototyping a new interaction like multi-connect, there’s no substitute for designing with real code. In rare cases when I have ideas or plans that I’m less confident about, it’s time to break out the paper, pens, and markers, Because the Kinopio interface elements and aesthetic are full-grown, I almost never use traditional design software anymore. makinginteractioninterfaces
Why Software is Slow and Shitty An Article by Pirijan Ketheswaran pketh.org Roman empire militaryBuilding is never a straight lineConversations, not commandments Planning doesn't make for better software softwareperformance
Mediocratopia An Article by Venkatesh Rao www.ribbonfarm.com I once read a good definition of aptitude. Aptitude is how long it takes you to learn something. The idea is that everybody can learn anything, but if it takes you 200 years, you essentially have no aptitude for it. Useful aptitudes are in the <10 years range. Leveling up aptitude You need to make the step forward skill
Leveling up aptitude Your first short story takes 10 days to write. The next one 5 days, the next one 2.5 days, the next one 1.25 days. Then 0.625 days, at which point you’re probably hitting raw typing speed limits. In practice, improvement curves have more of a staircase quality to them. Rather than fix the obvious next bottleneck of typing speed (who cares if it took you 3 hours instead of 6 to write a story; the marginal value of more speed is low at that point), you might level up and decide to (say) write stories with better developed characters. Or illustrations. So you’re back at 10 days, but on a new level. This kind of improvement replaces quantitative improvement (optimization) with qualitative leveling up, or dimensionality increase. Each time you hit diminishing returns, you open up a new front. You’re never on the slow endzone of a learning curve. You self-disrupt before you get stuck. The interesting thing is, this is not purely a function not of raw prowess or innate talent, but of imagination and taste. learningcreativitytastepractice