Thread.current.to_s

I've Made Ten Thousand Fried Eggs and Didn't Know What I Was Doing Sunny-side-up eggs.

This is to inform the two and a half people reading this blog that I left my consulting career at ThoughtWorks for the Silicon Valley Internet startup scene, joining Scribd.

Many years ago, yours truly was remembered (fondly, I hope) by some people in Jakarta, Indonesia as "that Russian who never sleeps".

Some friends of mine are working in a small IT organization, trying to adopt agile principles and methods.

For the last few months, I've ben away from the Ruby land, doing first a Java and now a .NET project.

Here is a scenario that seems to play out all too often.

In the previous post, I described a mismatch in the abstraction level between automated UI tests and business requirements that those tests purport to express.

Ask a Java developer in my neck of the woods to create a web application (of the usual "shovel some data from Oracle to HTML" variety) and s/he will probably come up with an instant architecture.

Over the years, I have seen many projects that tried to implement automated acceptance tests by driving application under test through a UI.