A Mathematician’s Lament: on education

Paul Lockhart wrote an accessible read on what is wrong with math education and the popular perception of math that is reinforced in culture that has been shared on the Web in quite a few corners. It deserves a wider read: “A Mathematician’s Lament”:

The art of proof has been replaced by a rigid step-by step pattern of uninspired formal deductions. The textbook presents a set of definitions, theorems, and proofs, the teacher copies them onto the blackboard, and the students copy them into their notebooks. They are then asked to mimic them in the exercises. Those that catch on to the pattern quickly are the “good” students.

The result is that the student becomes a passive participant in the creative act. Students are making statements to fit a preexisting proof-pattern, not because they mean them. They are being trained to ape arguments, not to intend them. So not only do they have no idea what their teacher is saying, they have no idea what they themselves are saying.

Even the traditional way in which definitions are presented is a lie. In an effort to create an illusion of “clarity” before embarking on the typical cascade of propositions and theorems, a set of definitions are provided so that statements and their proofs can be made as succinct as possible. On the surface this seems fairly innocuous; why not make some abbreviations so that things can be said more economically? The problem is that definitions matter. They come from aesthetic decisions about what distinctions you as an artist consider important. And they are problem-generated. To make a definition is to highlight and call attention to a feature or structural property. Historically this comes out of working on a problem, not as a prelude to it.

The point is you don’t start with definitions, you start with problems. Nobody ever had an idea of a number being “irrational” until Pythagoras attempted to measure the diagonal of a square and discovered that it could not be represented as a fraction. Definitions make sense when a point is reached in your argument which makes the distinction necessary. To make definitions without motivation is more likely to cause confusion.

Related:

Kevin Devlin: “Lockhart’s Lament – The Sequel”

Slashdot: “A Mathematician’s Lament — an Indictment of US Math Education”

G.H. Hardy:

A mathematician, like a painter or poet, is a maker of patterns. If his patterns are more permanent than theirs, it is because they are made with ideas.

Screaming Architecture: on systems

In “Screaming Architecture” Uncle Bob lays out one of the biggest wins by designing to the problem domain, instead of your weapon (ahem.. framework) of choice:

“If you system architecture is all about the use cases, and if you have kept your frameworks at arms-length. Then you should be able to unit-test all those use cases without any of the frameworks in place. You shouldn’t need the web server running in order to run your tests. You shouldn’t need the database connected in order to run your tests. Your business objects should be plain old objects that have no dependencies on frameworks or databases or other complications. Your use case objects should coordinate your business objects. And all of them together should be testable in-situ, without any of the complications of frameworks.

Anemic Domain Model: on systems

Martin Fowler wrote a piece in 2003 that addresses a subtle anti-pattern – developing your domain model code devoid of behavior. It’s a short, interesting read, that is related to the development of fat controllers in MVCish applications: “AnemicDomainModel”:

“In general, the more behavior you find in the services, the more likely you are to be robbing yourself of the benefits of a domain model. If all your logic is in services, you’ve robbed yourself blind.”

The history and background of Processing

Vimeo: Eyeo Festival: “Ben Fry & Casey Reas – Eyeo Festival 2011”

A short presentation where they give the background and insight into the future of a tool that has empowered artists, programmers, journalists, and story tellers in the same medium.

Thank you CmdrTaco and Slashdot

Rob Malda and Slashdot have done more to establish working, successful patterns for others to follow in online communities on the Web that few others (Metafilter, IndyMedia, and Salon.com come immediately to mind), can match, and are recognized for. Everyone keeps re-inventing elements of what they established, and missing lessons they learned the hard way.

A huge thank you to them all, and a good luck on your next endeavors Rob “CmdrTaco” Malda. Slashdot the community, and Slashdot the idea, has been a huge influence in my life and helped to show the world that online communities on the Web can work and help people connect.

Related:

Wired.com: Slashdot’s CmdrTaco Looks Back at 10 Years of ‘News for Nerds’

A few thoughts on Steve Jobs stepping down as Apple’s CEO

Apple is far more than the creation of one man. A casual scan of Folklore.org, a site focused on its history, will tell you that.

But so would Steve Jobs.

He’s created a culture at Apple that is going to go on long with out him.

A few reads about Jobs stood out for me today and I’d thought I’d share them here:

WSJ: Steve Jobs’s Best Quotes – as someone said on Twitter, you could avoid reading a few business/programming/design tomes and just absorb these and be better off.

His Stanford University commencement speech: ‘You’ve got to find what you love,’ Jobs says. He ties in his life history as an adopted child of working class parents, into his pursuit of his dream, the failures he encountered, and the lessons that he absorbed that made him stronger. There’s a bit about life, death, perspective and mission. It is worth reading in full. There are reasons it went viral. You can watch it on YouTube as well. But the text is best.

Anil Dash on “What they are ‘protecting’ us from” connecting Jobs liberal, working class background, with his success, and wondering why some are fighting the policies that enabled stories like Job’s to be possible.

You won’t find much Apple fandom here and I’m not going to wax poetic about Apple products, but in a way, for programmers of a certain age like myself, one of the leaders of the personal computing revolution is now walking off his most visible stage and we have much to be thankful for.

So thank you everyone at Apple, Pixar, and NeXT, and thank you Steve Jobs for providing inspiration, and the foundation for so many careers reflecting creativity, communication, and passion.

Java on… Heroku!!!!

Heroku adds suport for Java: Heroku for Java.

Take note of how simple a basic Java web app can be. Sure it’s not Sinatra or Flask, but it is still mighty simple.

Folks who claim that ‘Java is dead’ or that it should die, aren’t facing up to where it shines and what it provides. It has a place alongside Python and increasingly JavaScript in my tool belt.

I’m a happy polygot programmer and have used Groovy, and custom DSLs in Java to help speed application development by enabling those who are closest to change, to be able to harness it.

The Web is 20

I’d like to say thank you to Tim Berners-Lee and all those who were part of making the Web happen.

The original announcement (where? on Usenet of course!)

W3C

Design Issues for the World Wide Web

World Wide Web Foundation

Weaving the Web

See also: Dan Gillmor’s thank you