Last lecture.
Alots of words has been written about Team System for Architercts.
mmm... Wait, are you kidding? Is someone really using this? in real life? (not just in The Matrix :))
I don't know, I've been lecturing about Team System for some time now, and except for a few words I don't alot the say about that.
So it's really interesting to hear someone talks about it for more than five minutes.
I got to say that still the DSLs which come out of the box looks promising but it's hard to tell how organizations will adapt them.
From all the editions in VSTS, this is greatest enigma to me.
I'm thinking real hard about the next questions:
- What are the real life scenarios of those diagrams (or if is not enough for you, custom DSL languages)? What points in the ALM process do I need to definitely recommend a customer, you really should need a diagram here, and if you go pass the learning curve you will benefit greatly. Either by lack of knowledge on my behalf or because I don't take it into account in my thinking I've never got to this point. I really interested to hear about your real time experience with those diagrams.
- Suppose we are certain we want to integrate those features in our ALM, how to integrate this into the customer process? other editions are really easy to integrate, Developers always like new features, Testers appreciate the connectivity with the developers over test results, DBA's are in a vacuum so they don't really have a choice here.
From Eliaz's lecture DSL engine looks pretty cool and improves alot since the last time I checked it out. All new IDE features, still the usibility questions arises but I guess one need to think out of the box, because a solution for a problem which requires DSL really don't come naturally to me
Got any insights about all those questions and issues arised, please share.
Last words, Oslo is going to be big, need to gather as much information about that as possible.
Ariel