Archive for the 'domain specific languages' Category

I Wish I Knew That Before Getting This Job – Slides and (Long) Notes

As I said here before I was in Brazil some weeks ago to present at a conference. I had a really great time over there with some amazing people and would like to thank Caelum for their hard work in creating such a great conference. I’m making the slide deck and notes available in my […]

Watch Your Language!

It was one of my first days in the job. I was hired to head the development of several products for a media company and my new boss and I went to my first meeting.
The room was full of different types of people. You could tell those who were media producers from the managers […]

Tag Clouds: See How Noisy Your Code Is

If you follow this blog then you probably know that one of current interests is expressive design, either using Domain-Driven Design or Domain-Specific Languages. Here is a presentation about this topic.
One of the tricky things about expressive code is that it is very hard to see how noisy a code base is. What I found […]

Expessive Design - Slides

Just posted slides for a presentation I gave this week for one of our clients.
Expressive Design (in 20 minutes)
View more presentations from Phillip Calçado.

It was a very nice session where we talked about the hard work that is introducing such ideas in a corporate environment as those are finally reaching mainstream.
Notice that in this presentation […]

Presentation Slides: Macros in 20 Minutes

We just started holding 20 minutes presentations during lunch time in the ThoughtWorks Sydney office. For the first session I gave a not-that-short talk on Lisp macros using Clojure. The slides are below.
Lisp Macros in 20 Minutes (Featuring Clojure)
View more presentations or upload your own. (tags: thoughtworks clojure)

It turns out that 20 minutes is too […]

Where do Acceptance Tests go to Die?

My colleague Sarah Taraporewalla posted an interesting text on acceptance testing. She doesn’t believe in this technique. I’ve been thinking of acceptance tests for some months now and think that she has a valid –a bit too radical but still valid- point.
My main problem with acceptance testing is that they are too wasteful.

They are temporary. […]

Internal DSLs and Paradigms: Declarativeness

I’ve been experimenting a lot with Internal Domain-Specific Languages (or embedded DSLs if you prefer the classic and more accurate term) during my recent projects and by doing that I’m facing the real benefits and caveats of that technique.
One of the biggest issues with embedded languages is that is very hard to get developers’ minds […]

JavaScript, Internal DSLs and Keyboards

Ajaxian.com published an article on Ojay, an interesting JavaScript library that rests on top of Yahoo!’s YUI. The library has a DSLish way of expressing form validation rules, like in these snippets from their website:

form(’signup’)
.requires(’username’).toHaveLength({minimum: 6})
.requires(’email’).toMatch(EMAIL_FORMAT, ‘must be a valid email address’)
.expects(’email_conf’).toConfirm(’email’)
.expects(’title’).toBeOneOf([’Mr’, ‘Mrs’, ‘Miss’])
.requires(’dob’, ‘Birth […]

Expressive Domain-Specific Languages for Firewalls

Prael wrote a blog post about Domain-Specific Languages used in firewall definition. He points to Cat in the Red Hat’s recipes for firewalls in Linux and in BSD (the Windows port of that).

Now, I’ve always preferred BSD-style firewall configs. But I’ve never seen before such a painfully clear example of *why* I prefer them. If […]

Please let Binding#eval receive a block

I was very happy to see that Ruby 1.8.7 made a method named Binding#eval public.
This method is very useful when you need to mix two Domain-Specific Languages. In Ruby you often evaluate a block in a different context than where it was defined, using instance_eval and friends. The problems is that a block can […]




About

You are currently browsing the Fragmental.tw weblog archives for the domain specific languages category.

Longer entries are truncated. Click the headline of an entry to read it in its entirety.





Creative Commons License

This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License.