LinQ is often understood in terms of introducing a Domain Specific Language to work with data to C# and .Net in general. The fact is:it is not, and there is a considerable difference between LinQ syntax nature and a DSL. The problem is that DSL definition is blur enough to take anything interesting or cool under it!
In the rapidly spanning world of programming languages, I find myself buying and reading a lot of books about new and old programming languages. There are a few interesting concepts in each language, and if you think about employing more than one language in your projects then you better know about the existence of these concepts (see Paradigm based Polyglot Programming).
One thing that annoys me though about most programming language books is how raw they often are.
In Bryce Harrington’s opinion, document-oriented paradigm of user interface is not any longer optimal. Most often people deal with streams of information rather than static documents. Harrington advocates for a shift towards a new UI paradigm that would make stream management easier. Many tools and technologies are already based on stream-oriented approach; others are instrumental for adopting it.
There is a widespread opinion that a good DSL has to be English-like. Dave Thomas advocates against such approach asserting that DSL are not about getting as close as possible to natural languages and that having this as a guiding principle of DSL design can be rather detrimental. He also highlights what he believes is important in DSL design and provides some examples of successful DSL.
On JAOO 2007 I could, with the help of Floyd, organize a debate between Bob Martin and James Coplien about TDD and DbC. This is the most interesting debate about the subject I’ve ever heard of. A lot of things I wanted to say have been said here. And I am proud to announce it :)
http://www.infoq.com/interviews/coplien-martin-tdd
Thanks Cope, thanks Bob.
Today, many software project management and architecture approaches tend to parcel out work on a project creating hierarchical layers. This helps to simplify both developers work and management. However, the undelying information shielding among layers can potentially create a gap between developers and the software they are working on, if developers task are totally taken out of functional context.
This post has been originally posted on infoQ on Religion driven industry: buzzwords and checklists vs. thinking and inspection
James O. Coplien has recently argued that today’s industry is based on buzzwords and checklists. The use of some techniques and methodologies, TDD for instance, has become “a religious issueâ€. This prevents from inspecting possible tradeoffs and focusing on finding solutions that would be the most appropriate and the most cost-effective . (more…)
Posts I find interestingPowered by WordPress