Konstantin Vlasenko

An engineer is someone who can make for a dollar what any fool could make for two. – Alan Kay

Category Archives: fine words

PowerTip: Finding 10 Largest Files

Can be usefull for PowerSlim tests. For instance, in the !|Query: PowerShell|…| Re-Posted. You can find the original here. You may need to find the largest files for possible clean-up when free space on a drive runs low. One way is to have PowerShell examine all file sizes, sort by file size descending, and then [...]

Beyond Acceptance Testing Framework

It looks like there are several acceptance testing frameworks (ATF) available (RobotFramework, Cucumber, Fitnesse on FIT, Fitnesse on SLIM, ZenTest, Concordion). Not sure if each of them are really ATF, but can say that Concordion is not a great choice. Fitnesse is the best ATF I know. But it’s up to you, which way to go. [...]

Top 10 reasons why teams fail with Acceptance Testing

http://gojko.net/2009/09/24/top-10-reasons-why-teams-fail-with-acceptance-testing/ … – Tests unusable as live documentation – Focusing on tools – Not considering acceptance testing as value added activity – “Test code” not maintained with love – No management buy-in – Underestimating the skill required to do this well …

A Time and a Place for Russia

http://www.nytimes.com/2010/01/29/opinion/29iht-edkhodorkovsky.html

Schools kill creativity

Check this out http://www.ted.com/talks/ken_robinson_says_schools_kill_creativity.html I heard a great story recently — I love telling it — of a little girl who was in a drawing lesson. She was six and she was at the back, drawing, and the teacher said this little girl hardly ever paid attention, and in this drawing lesson she did. The teacher [...]

The Renaissance of Craftsmanship (Robert C. Martin)

http://www.viddler.com/explore/oredev/videos/36/ You will not ever do things right The only solution is to continuously improve It is impractical for you to think that you can write a requirement correctly the first time One of the reasons we work in short iterations is that we can incrementally improve everything Make the code cleaner every time you [...]

Don’t try to use all innovations

Try to solve the problem with the well known tools. Try to use as less as possible tools while you automating something. Don’t try to expand your knowledge with the new tools or framework without clear understanding that the old one can’t really solve the problem. Only the “code-less” can be the reason for a [...]

Follow

Get every new post delivered to your Inbox.