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
Togetherness “Togetherness” is a fittingly nauseating name for an old ideal in planning theory. This ideal is that if anything is shared among people, much should be shared. “Togetherness,” apparently a spiritual resource of the new suburbs, works destructively in cities. The requirement that much shall be shared drives city people apart. When an area of a city lacks a sidewalk life, the people of the place must enlarge their private lives if they are to have anything approaching equivalent contact with their neighbors. They must settle for some form of “togetherness,” in which more is shared with one another than in the life of the sidewalks, or else they must settle for lack of contact. Inevitably the outcome is one or the other; it has to be; and either has distressing results. City residential planning that depends, for contact among neighbors, on personal sharing of this sort, and that cultivates it, often does work well socially, if rather narrowly, for self-selected upper-middle-class people. It solves easy problems for an easy kind of population. So far as I have been able to discover, it fails to work, however, even on its own terms, with any other kind of population. Jane Jacobs, The Death and Life of Great American Cities Doing community classcommunity