Welcome Visitor!
 There might be a number of reasons why you've reached this site. You
could be looking for some of
my articles,
maybe especially the
.NET Remoting FAQ. Quite likely you might also be looking for
information about the
Advanced .NET Remoting books. (The second edition will be out in March
2005. Sorry, only C# this time.)
If this is not what you've been coming
here for, let me tell you a little bit about
the person behind these works and how I
might be able to directly help you in your
projects.
Today
Even though a lot of developers might connect my name with .NET
Remoting, I have actually spent the past three or so years working with all
distributed application technologies in the .NET Framework: ASP.NET Web
Services (and WSE), Enterprise Services, System.Messaging (MSMQ), and .NET
Remoting (and of course, fundamental technologies like NLB, clustering, and
various databases). I was lucky to work with a number of really great
customers on improving scalability, performance and reliability of their
critical Windows- or Web-based applications. Together with my previous
experience in the development of enterprise-level Java applications (in the
telecommunications business), I can say that I have indeed learned a whole
lot about scalability, performance and reliability in the last five years.
(This focus on backend technologies however also means that I still can't
create a reasonably good looking Windows Forms frontend ... but that's an
entirely different story).
If this sounds interesting for you or
your project, I think we should get in
touch.
Consulting
Even though I have definitely noticed
that technical people (including me) somehow
see some seriously negative connotations in
the word "consultant"", I did not yet come
across a better description for the kind of work I do. My idea behind
consulting might however differ slightly from the usual one.
In my opinion,
there are a number of ways in which you can acquire certain knowledge. The
best - and most durable - is by personal experience. The only drawback is
that it takes a lot of time. A whole lot. And you need to be exposed to
different projects with their own set of issues. These two points are a
luxury which few professional developers and architects can afford.
That's why most of us developers and architects usually turn to a second option: to learn from the
experiences of others. Articles, books, conferences, and training courses
all work together in making you an expert in a given topic by listening to,
or reading about, experiences of others. All of these means differ in price,
immediacy and size of the audience. (A magazine article will usually be
quite generic in its tone as it has to be applicable for a large number of
readers. A training course on the other hand allows the trainer to focus on
just a handful of participants.)
Consulting - in the way we see it - is
the most direct way of knowledge transfer:
You will get answers to your very own
questions without having to spend time
listening to or reading about things you
already know. It's like having your own
personal trainer - in my case especially for
distributed applications, performance and
serious scalability.
If this approach to consulting sounds interesting for you and your
projects, I think we should talk to each other. You can reach me at
ingo.rammer@thinktecture.com
or at +43 676 7909563. (Please leave a message - in case - as I'm travelling
quite often. I will call back.)
With best regards,
Ingo Rammer
|
Ingo Rammer