[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] iX CeBIT Forum 2010 Talk
|
Hi,
Sounds great. If you need any slides, let me know and I can email you
the powerpoint slides from ESE for instance, or if you want
illustrations from the Buckminster book.
On the topic of questions and possible confusions...
...some have a hard time with the fact that the headeless build is the
same as the IDE build, and think that using "the IDE when building
headlessly" is a huge overhead. They do not seem to get their head
around the fact that is just a bunch of bundles that just happens to be
used in headless fashion or inside an IDE. Somehow they think that "IDE
bits" are heavier to use than "non IDE bits" :)
A piece of general advice...
... try to stay high level, there are many concepts in Buckminster -
lots of terms etc. at it is easy to overwhelm the audience by explaining
too much too early (heads tend to explode :) - hence the very simple
summary slides in the beginning of our Buckminster presentation - even
if things get more complicated later, the simple images and ideas from
the start of the presentation hopefully sticks to people's minds.
Regards
- henrik
On 1/8/10 2:35 PM, Carsten Reckord wrote:
Hi,
iX, a popular German IT magazine, organizes an annual forum on the
CeBIT. This year one focus is on experience reports for agile software
development processes.
I was asked to submit a talk on our (obviously positive :)) experience
with setting up a Continuous Integration server with Buckminster and the
Hudson plug-in. Without having prepared the talk yet, the idea is to
present an introduction of Buckminster and the Hudson plug-in followed
by (or mixed in with) our lessons learned and some best practices and
maybe finishing with a brief overview of some more advanced topics like
coverage, obfuscation or "Composing for Updatability" your product the
Buckminster way.
I'd like to ask if, from your experience with other talks so far, there
are any typical questions that keep coming up or typically difficult
points or misconceptions that should be cleared preemptively? And if you
have any other suggestions or comments, of course feel free to fire
away, too.
Best regards,
Carsten
