http://www.artima.com/weblogs/index.jsp?blogger=bv Artima Weblogs is a community of bloggers posting on a wide range of topics of interest to software developers. http://www.artima.com/images/artima88x33.gif http://www.artima.com/ http://www.artima.com/weblogs/viewpost.jsp?thread=253855 In "The Feel of Scala," a talk I gave at Devoxx which is now available on Parleys.com, I show Scala solutions to real problems to help you get a feel for the language. Along the way I demonstrate how you can get many of the productivity benefits offered by dynamic languages using alternative static techniques in Scala. http://www.artima.com/weblogs/viewpost.jsp?thread=252702 I've observed two, often competing aspects of code readability: clarity of the programmer's intent (the "what") and clarity of the implementation (the "how"). What does code readability mean to you, and what do you think is the best way to maximize it? http://www.artima.com/weblogs/viewpost.jsp?thread=251945 Last week I released a new version of ScalaTest (0.9.5) that includes a "matchers DSL" for writing more expressive assertions in tests. In this post I show differences between ScalaTest matchers and those in Ruby's RSpec tool, and discuss some of the general differences in DSL creation in Ruby and Scala. http://www.artima.com/weblogs/viewpost.jsp?thread=246279 The next version of ScalaTest will include a set of matchers. These matchers demonstrate the kind of DSL notation you can create in Scala. In this post, I give a sneak preview of ScalaTest matchers, and ask for feedback. http://www.artima.com/weblogs/viewpost.jsp?thread=245965 The latest version of ScalaTest includes a trait named SpecDasher, which when mixed into a Spec facilitates a more concise expression of specification-style tests. It is deprecated, however, and may be removed in a future release depending on user feedback. What's your opinion? http://www.artima.com/weblogs/viewpost.jsp?thread=245958 The latest version of ScalaTest, a testing tool for Scala and Java developers, includes a concise way to test private methods and support for behavior-driven development. http://www.artima.com/weblogs/viewpost.jsp?thread=245420 Artima's first published book, Programming in Scala, made its bookstore debut last week at the Devoxx conference in Antwerp, Belgium, where it sold out. Twice. http://www.artima.com/weblogs/viewpost.jsp?thread=232028 In the most recent release of ScalaTest, I've placed some guidelines in the documentation for how to avoid the use of vars in testing code. In this post I include those guidelines and ask for feedback. http://www.artima.com/weblogs/viewpost.jsp?thread=223156 Tonight I released a new version of ScalaTest, which contains a few changes to the way in which you express assertions and a Suite discovery feature. This release contains all the features that I plan to have in version 1.0, so it is ready for a few months of beta testing. http://www.artima.com/weblogs/viewpost.jsp?thread=222678 Today I released a testing tool written in Scala, which can be used to test Scala or Java code. It is intended primarily as a tool for testing Scala code, but can also be used as a low-risk way to get started programming in Scala, by writing tests in Scala for production code written in Java. http://www.artima.com/weblogs/viewpost.jsp?thread=220890 This week we released an early access version of the book, Programming in Scala, in PDF form. With this work, Artima enters the world of book publishing for the first time. In this blog post, I explain what we did and why, and what this means for Artima in the future. http://www.artima.com/weblogs/viewpost.jsp?thread=211172 In my previous post I brought up the topic of code formatting. This time I'd like to bump it up a level of abstraction to the structure of the code itself. To what extent do you think teams should establish policies for code structure, and what do you think is the best way to structure flow in the presence of potential errors? http://www.artima.com/weblogs/viewpost.jsp?thread=210268 To what extent should a project or company have a coding style policy, and how and to what extent do you think it should be enforced? http://www.artima.com/weblogs/viewpost.jsp?thread=209353 To what extent does the productivity of dynamic languages come from the lack of typed variables versus the reduction in "finger typing" required when you don't have to declare the types? The technique of type inferencing in static languages may shed new light on this old debate. http://www.artima.com/weblogs/viewpost.jsp?thread=197511 For those of you who are programming in C#, what would you say are the biggest sources of pain, or at least discomfort, when using C#.