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
The rational model of design Engineers seem to have a clear, if usually implicit, model of the process of design. It is usually an orderly model of an orderly process as the engineer conceives it. The notion that the design process should be modeled as a systematic step-by-step process seems to have first developed in the German mechanical engineering community. Herbert Simon independently argues for design as a search process in The Sciences of the Artificial. He was motivated to lay out a strictly rational model of design precisely because such a model was a necessary precursor to automating design. His model remains influential even if today we recognize the "wicked problem" of original design as one of the least promising candidates for AI. In software engineering, Winston Royce independently introduced a seven-step Waterfall Model to bring order to the process. In fact, Royce introduced his waterfall as a straw man that he then argued against, but many people have cited and followed the straw man rather than his more sophisticated models. Even if ironically, Royce's seven-step model must be considered one of the foundational statements of the Rational Model of Design. Frederick P. Brooks, Jr., The Design of Design Large combinatorial spacesThe ordering of steps