Two principles I've been teaching my 11 yo about programming: 1. Whenever you change a program, test it. 2. Adjust the size of your changes based on your confidence. Start with small changes. When those work, you can make bigger ones.
-
-
Minimum viable product. Do the simplest thing that could work. Do the next simplest thing that adds value.
-
It’s even more basic than that. It’s minimum functional iteration. It doesn’t have to be viable or a product.
- Show replies
New conversation -
-
-
Always fix the first error first.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
In what sens read-only? You couldn't compose emails?
-
Nope, first version just searched my own email, version two could search the user’s own email, and version three added “reply” function :)
End of conversation
New conversation -
-
-
1 of 2: The goal of testing is not just to prove that software does what it is supposed to do. It is also to demonstrate that the software doesn't do what it is not supposed to do.
-
2 of 2: Since this is impossible / impractical, only by writing test cases for even little changes can you have the confidence that the software doesn't do what it is not supposed to do - by validating everything that it is supposed to do.
End of conversation
New conversation -
-
-
I’m starting my 10 yo on his first solo-ish build for Spring Break. Did you start your kids off with a tutorial or have them start googling?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
My two cents, writing tests first can be very powerful even without any kind of framework
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Sounds you're teaching MVP(rogramming)...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.