davidwees's comments

davidwees | 12 years ago | on: The doctors give me 30 days to live, each post is potentially my last

There's one thing missing from your analysis: the life expectancies calculated this way include all deaths; someone who is 58 has managed to avoid some pretty dangerous parts of life, for example:

1. They did not die during their first year of birth. About 6 babies in 1000 die during the first year of birth in the US. 2. They did not die as a youth from depression or driving their car into a tree.

That being said, this histogram (logarithmic scale) suggests that one's odds of living to 100 are still somewhat low: http://www.benbest.com/lifeext/number.jpg

davidwees | 14 years ago | on: Please don't learn to code

If we attempt to look into the future, I think we see that computers are likely to permeate every aspect of our culture. If they continue to decrease in size as they have been doing, they may actually end up being embedded in much of the stuff we use.

We should also notice that programming itself has a huge gradient in terms of difficulty. Things like Scratch, and other block programming languages make the act of programming easier, where amateur developers can focus more time on trying to solve the problems they are working on, and less time figuring out which parenthesis they missed.

So we have two trends - that programming is becoming easier to do, and that computers are becoming more common. Both of these lead me to the conclusion that not being able to program will eventually be akin to being illiterate. You won't be able to use and modify many of the tools of the future without some programming skill.

Further, many people are developing some of the core programming skills in pieces. Look at http://ifttt.com/ for example. This is an example of using apps as procedure calls, and writing very short subroutines to handle tasks for you. It is a perfect example of how programming is beginning to permeate popular culture.

Soon, telling people not to learn how to program will be much like telling people not to write or not to do math - it will be a bit ridiculous. We will just need to be able to use better systems for keeping track of who is an amateur, and who is a professional, much like we do with writing and mathematics.

davidwees | 14 years ago | on: Please don't learn to code

I wrote an online attendance system for my school, which often come with way more features than we need and cost in the range of $50k. It's not $2 million, but $50k is a teacher's salary. In education, that's huge. It took me 2 weeks to set up, and another 4 weeks of testing with teachers to iron out all of the bugs, but now it is used every day by all of our teachers.

I've also used my ability to code to develop learning apps for my students. It's been incredibly valuable in my career.

davidwees | 14 years ago | on: What Silicon Valley gets wrong about math education again and again

Mathematical notation has been chosen, or developed over time, because it is highly efficient at communicating a huge amount of information in a short amount of space. It is almost as if the natural tendency of mathematical notation is to act a as a space-saving algorithm; the information content to notation ratio in mathematics is extremely high.

Most attempts to communicate this notation to computers has been difficult at best, with MathML being much too complex for humans to actually write, and LaTeX often requiring much looking up of the various short cuts that been developed, particularly for beginners.

Here's an example of some LaTeX to produce a mathematical diagram.

\png \definecolor{blueblack}{RGB}{0,0,135} \color{blueblack} \begin{picture}(4,1.75) \thicklines \put(2,0.01){\arc{3}{3.53588}{5.8888}} \put(.375,.575){\line(1,0){3.25}} \put(1.22,1.375){\makebox(0,0){\footnotesize$ds$}} \put(.6,.5){\makebox(0,0){\footnotesize$x=0$}} \put(3.36,.5){\makebox(0,0){\footnotesize$x=\ell$}} \dottedline{.05}(1.0,.575)(1.0,1.10) \put(1.0,.5){\makebox(0,0){\footnotesize$x$}} \dottedline{.05}(1.5,.575)(1.5,1.40) \put(1.5,.5){\makebox(0,0){\footnotesize$x+dx$}} \put(1.22,.65){\makebox(0,0){\footnotesize$dx$}} \dottedline{.04}(0.6,1.12)(1.25,1.12) \put(1.0,1.14){\vector(-1,-1){.45}} \put(.58,0.83){\makebox(0,0){\footnotesize$T$}} \put(.77,1.05){\makebox(0,0){\scriptsize$\theta(x)$}} \put(1.18,1.16){\makebox(0,0){\scriptsize$\theta(x)$}} \dottedline{.04}(1.5,1.41)(2.1,1.41) \put(1.5,1.44){\vector(4,1){.67}} \put(2.22,1.59){\makebox(0,0){\footnotesize$T$}} \put(1.95,1.45){\makebox(0,0){\scriptsize$\theta(x+dx)$}} \end{picture}

Can you tell what the final output of this LaTeX will be? (See http://www.forkosh.com/mathtex.html for the answer)

davidwees | 14 years ago | on: What Silicon Valley gets wrong about math education again and again

It would be nice if when teachers gave them feedback, they'd act on it. Unfortunately, it seems that any criticism of the Khan Academy is seen as an attack on the whole of the Silicon Valley, and every geek comes out to lead the charge against the educators suggesting that they have entirely the wrong approach.

Instead of viewing mathematics as a series of problems to be solved, each of which has a solution, maybe it would be neat of the Khan Academy actually spoke to some educators (and then publicly announced the results of this consultation)?

page 1