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
Agile as Trauma An Essay by Dorian Taylor doriantaylor.com The Agile Manifesto is an immune response on the part of programmers to bad management. Many a corner officeIntramural brownie pointsFeature factories agilemanagement
Many a corner office I want you to consider instead the possibility that Waterfall came to exist, and continues to exist, for the convenience of managers: people whose methods are inherited from military and civil engineering, and who, more than anything else, need you to promise them something specific, and then deliver exactly what you promised them, when you promised you’d deliver it. There exists many a corner office whose occupant, if forced to choose, will take an absence of surprises over a substantive outcome. surpriseplanning
Intramural brownie points Features don’t work, in the sense that they can be easily gamed. A brittle and perfunctory implementation, done quickly, is going to score more intramural brownie points over a robust and complete one. If the question is "does product A have feature X?" then the answer is yes either way. features
Feature factories We use the term feature factory as a pejorative to designate companies addicted to adding features, while accumulating incalculable so-called technical debt. This situation is driven by management for the convenience of marketing, and I am skeptical that a more faithful application of Agile principles will correct it. Indeed, I suspect Agile processes are constitutionally vulnerable to this kind of compromise. The presence of a feature can only indicate to a user if a goal is possible, behavior will determine how painful it will be to achieve it. ux