Explore >> Select a destination
|
You are here 
|
twobithistory.org | ||
| | | | |
usethe.computer
|
|
| | | | | ||
| | | | |
www.hillelwayne.com
|
|
| | | | | Take the following code: a = 1 a = a + 1 print(a) A common FP critique of imperative programming goes like this: "How can a = a + 1? That's like saying 1 = 2. Mutable assignment makes no sense." This is a notation mismatch: "equals" should mean "equality", when it really means "assign". I agree with this criticism and think it's bad notation. But I also know some languages don't write a = a + 1, instead writing a := a + 1. | |
| | | | |
www.laputan.org
|
|
| | | | | Program components must be designed for reusability. There is a set of design techniques that makes object-oriented software more reusable. Many of these techniques are widely used within the object-oriented programming community, but few of them have ever been written down. This article describes and organizes these techniques. | |
| | | | |
robdodson.me
|
|
| | | Hi, I'm Rob. I write about front-end development and accessibility. | ||
