I'm a graphics programmer at Unity (the game engine), and recently I toyed around with Rails. That made me realize how much of assumed knowledge and jargon is in any particular field.
As a complete noob, all the information in Rails case sounds like "yeah you just rake your gems, bundle the capistrano and don't forget to bootstrap the angular node" -- stop, WHAT?! And all this while trying to do a very simple "hello, world" CRUD app.
I'd imagine graphics programming sounds exactly like that from outside, just with different words. "Oh yeah, you just swizzle your lanes, dispatch the predication queries and don't forget to Fresnel your BRDFs" (no, this sentence does not make any sense whatsoever).
Of course if I'd spend even a month in the Rails/web field, I could at least navigate without bumping into everything. Spending a year or two would probably make me comfortable. Same with game or graphics programming. The author of original blog post has been doing this for 20 years...
You know, it's funny how people out of our industry perceive us (at least in my experience) - I mean you say you're a programmer and it's immediately presumed that you just know computers and coding, but we have so many branches, languages, platforms at times it's absolutely overwhelming.
Outside of the basics of programming (you know algorithms, runtime analysis, basic code structure) we have almost nothing in common. It now starts to make sense why the big companies interview in these areas.
Try flask --> http://flask.pocoo.org/
That said, graphics engine development is very technically and mathematically advanced, I would say much more so than the web stack.