On online collaboration and our obligations as makers of software An Essay by Baldur Bjarnason www.baldurbjarnason.com Is it the notetaking system that’s helping you think more clearly? Or is it the act of writing that forces you to clarify your thoughts? Is it the complex interlinked web of notes that helps you get new ideas? Or is it all the reading you’re doing to fill that notetaking app bucket? Is all of this notetaking work making you smarter? Or is it just indirectly forcing you into deliberate, goalless practice? Towards a crap decisionSo much knowledge not being applied notetakingbloggingsoftwarethinkingcommonplace
What do I need to read to be great at CSS? An Article by Baldur Bjarnason www.baldurbjarnason.com A rule of thumb is that the importance of a blog in your feed reader is inversely proportional to their posting cadence. Prioritise the blogs that post only once a month or every couple of weeks over those that post every day or multiple times a day...Building up a large library of sporadically updated blogs is much more useful and much easier to keep up with than trying to keep up with a handful of aggregation sites every day. bloggingcsscodelearningrss
136 things every web developer should know before they burn out and turn to landscape painting or nude modelling An Article by Baldur Bjarnason www.baldurbjarnason.com The best way to improve software UX is regular direct observation, by everybody on the team, of the work done. Have some personality. Minimalism is garbage. Metaphors are fantastic. Naming things is fantastic. Try to write HTML that would make sense and be usable without the CSS. The buyer is quite often wrong. That fact never changes their mind. Working on a functioning app’s codebase does more to increase its quality than adding features. A good manager will debate you, and that’s awesome. The term ‘project’ is a poor metaphor for the horticultural activity that is software development. Two Hundred Fifty Things an Architect Should Know wwwworkuxcollections
Nobody gives a hoot about groupthink An Article by Baldur Bjarnason www.baldurbjarnason.com Two relatively common ‘fashions’ today are real-time collaboration and shared data repositories of one kind or another. Both increase productivity in the naive sense. We work more; everybody is more active; the group feels more cohesive. The downside is that they also both tend to reduce the quality of the work and increase busywork. On that of the highest authorityPersonal Information Management (PIM) productivitycollaborationinformation
Form follows failure Imagining how the form of things as seemingly simple as eating utensils might have evolved demonstrates the inadequacy of a "form follows function" argument to serve as a guiding principle for understanding how artifacts have come to look the way they do. Reflecting on how the form of the knife and fork has developed, let alone how vastly divergent are the ways in which Eastern and Western cultures have solved the identical design problem of conveying food to mouth, really demolishes any overly deterministic argument, for clearly there is no unique solution to the elementary problem of eating. What form does follow is the real and perceived failure of things as they are used to do what they are supposed to do. Clever people in the past, whom today we might call inventors, designers, or engineers, observed the failure of existing things to function as well as might be imagined. By focusing on the shortcomings of things, innovators altered those items to remove the imperfections, thus producing new, improved objects. Different innovators in different places, starting with rudimentary solutions to the same basic problem, focused on different faults at different times, and so we have inherited culture-specific artifacts that are daily reminders that even so primitive a function as eating imposes no single form on the implements used to effect it. Henry Petroski, The Evolution of Useful Things Against form follows functionForm follows function evolution