I’ve presented at ThoughtWorks Melbourne tech forum today. Tech forums are short presentations we have 2 times a month, a nice excuse to get people around the office, enjoy free lunch and discuss about some geeky stuff. We had a very nice talk about Internal Domain Specific Languages.
Feel free to download the slides and the […]
Archive for February, 2008
Internal DSLs @ ThoughtWorks Tech Forum
Published by February 26th, 2008 in domain driven design, domain specific languages, fluent interfaces, language adaptation, language oriented programming, object orientation, ruby, software design, thoughtworks and trends. 7 CommentsArchitecture is About People: Sharing Models
Published by February 17th, 2008 in domain driven design, layers, object orientation, software architecture and software design. 4 CommentsIn this follow-up to the previous post on Architecture let’s visit a problem that lots of project have and most face as an unavoidable thing.
I have seemed this a lot in the past years. Once I worked at a product company that develop a very complex and distributed system. We had three different groups among […]
Internal DSLs: Can’t use your tools here
Published by February 11th, 2008 in domain specific languages, fluent interfaces, language adaptation, language oriented programming, ruby, software design and trends. 1 CommentI’m migrating a pet project to RSpec’s StoryRunner. I’ll probably blog something about the tool itself soon but I wanted to talk about something that I noticed since the tool heavily uses Domain-Specific Languages.
I’m writing user stories using the Internal Domain-Specific Language (you can also use an external DSL) and just realized something that enforces […]
Static Types for Long Feedback Cycles?
Published by February 6th, 2008 in agile, groovy, java, object orientation, ruby, software architecture, software design, thoughtworks and trends. 4 CommentsJay Fields wrote a post named “Static typing considered harmful” where he gets to some interesting conclusions.
Type verification provides very little confidence that an application works. The little confidence it does provide comes at the cost of being confined by the type system. Verifying types is better than testing nothing at all. But, only verifying […]
Superstars in your Domain Model?
Published by February 6th, 2008 in object orientation and software design. 3 CommentsYesterday an interesting question arose in my team: [in your Domain Model] is it ok to have an objects that lots of others depends on?
Let’s get a very common example: Money. Money is generally a Value Object (Eric Evans/Martin Fowler’s Value Object, not Sun’s Transfer Object thing) that generally is referenced by lots of […]
