?

Log in

No account? Create an account
July 25th, 2006 - Adventures in Engineering — LiveJournal
The wanderings of a modern ronin.

Ben Cantrick
  Date: 2006-07-25 18:01
  Subject:   [MeFi] Industrial pics by Joe Nishizawa
Public
  Music:"I've done... questionable things."


Nishizawa-san, flipping through the pages of your book “Deep Inside” one gets sucked into this technical-magic-wonderland. I can’t believe that those places actually look like that - better than any CG setting I have ever seen. Bladerunner would simply be jeallous! Even the lighting is perfect in pink and green!

Oh no, absolutely no computer graphics involved in these photos. That’s essentially what those places look like - for example one right below Hibiya Junction. Lightings and everything is just captured as it was there - I didn’t even use a flashlight! It’s magic: you first hear the car noises on the ground level and as you descend slowly, suddenly, this vast and silent space unfolds in front of you.


http://www.pingmag.jp/2006/07/24/japan-underground-photography/
5 Comments | Post A Comment | | Link



Ben Cantrick
  Date: 2006-07-25 22:13
  Subject:   [Digg] The N habits of highly defective windows programs.
Public
  Mood:Annoying, yet obnoxious!
Generally, when I get a program from a client who is having problems, I can solve most of the problems by looking for the items I describe here. My track record is that I have been shown code on a page, or on a screen, containing one or more of the techniques I discuss here, and I point to it and say "There's your problem!", usually within the first 30 seconds. It sometimes takes another ten or twenty minutes to explain to the programmer what has gone wrong as a consequence, and demonstrate exactly what can go wrong in the future, but thus far I've never been wrong in my assessment. On one recent consulting trip, I spotted a Sleep() inside a WaitFor..., and said "there's the problem", and then explained "Your program will fail under the following conditions (a), (b), (c) and the behavior it will exhibit on failure will be (d), (e) and (f)" and they said "Yes, that's exactly where and how it is failing!". As it turned out, there was nothing wrong with that part of the program that a complete rewrite wouldn't solve.

http://www.flounder.com/badprogram.htm
1 Comment | Post A Comment | | Link






browse
May 2015