Tag Archives: History of Software Engineering

Episode 44: We Would Know What They Thought When They Did It

We would now what they thought when they did it, a call for a history of ideas in computing. Laurent Bossavit, author of The Leprechauns of Software Engineering, can’t work out who introduced the phrase “legacy code” (or why). Technical … Continue reading

Tagged | Leave a comment

Episode 43: what we DO know about software engineering

This episode follows from episode 42: what I have yet to learn. APPropriate Behaviour and its incompleteness comes up again The Software Engineering Body of Knowledge (and its incompleteness) come up again too; last mentioned in episode 41: professional software. … Continue reading

Tagged | Leave a comment

Episode 41: Professional Software

We talk about software engineering as a profession. ACM Code of Ethics Software Engineering Body of Knowledge (SWEBoK) BCS Code of Conduct

Tagged | Leave a comment

In which I misunderstood Objective-C

I was having a think about this short history of Objective-C, and it occurred to me that perhaps I had been thinking about ObjC wrong. Now, I realise that by thinking about ObjC at all I mark myself out as … Continue reading

Posted in cocoa, design, freesoftware, gnustep, nextstep, objc | Tagged | 1 Comment

On programmer behaviours that make Scrum so bad

Respectable persons of this parish of Internet have been, shall we say, critical of Scrum and its ability to help makers (particularly software developers) to make things (particularly software). Ron Jeffries and GeePaw Hill have both deployed the bullshit word. … Continue reading

Posted in agile, process | Tagged | Leave a comment

An Imagined History of Object-Oriented Programming

Having looked at hopefully modern views on Object-Oriented analysis and design, it’s time to look at what happened to Object-Oriented Programming. This is an opinionated, ideologically-motivated history, that in no way reflects reality: a real history of OOP would require … Continue reading

Posted in OOP | Tagged | Leave a comment

A hopefully modern description of Object-Oriented Design

We left off in the last post with an idea of how Object-Oriented Analysis works: if you’re thinking that it used around a thousand words to depict the idea “turn nouns from the problem domain into objects and verbs into … Continue reading

Posted in ooa/d | Tagged | Leave a comment

On industry malaise

Robert Atkins linked to his post on industry malaise: All over the place I see people who got their start programming with “view source” in the 2000s looking around at the state of web application development and thinking, “Hey wait … Continue reading

Posted in advancement of the self | Tagged | Leave a comment

On UML

A little context: I got introduced to UML in around 2008, at an employer who had a site licence for Enterprise Architect. I was sent on a training course run by a company that no longer exists called Sun Microsystems: … Continue reading

Posted in agile, architecture of sorts, design, software-engineering, sunw, tool-support | Tagged | 2 Comments

By doing it and helping others do it

We are uncovering better ways of developing software by doing it and helping others do it. It’s been 20 years since those words were published in the manifesto for agile software development, and capital-A Agile methods haven’t really been supplanted. … Continue reading

Posted in agile | Tagged | Leave a comment