A bit on my new job and a lot about the old/current
I'll be joining MS DSL team in UK by the end of this month, at last –
after one month delay… Me and my wife are expecting it to be very interesting
and challenging.
In my current position I'm Microsoft sub contractor in one of Elbit
systems command and control project. I'm glad that all my employers (Taldor,
Elbit and Microsoft) support me in my decision to go forward and advance professionally
and really coming towards me by letting me work although I resigned already
(some sort of a flexible resignation).
I learned a lot in Elbit, first of all I started in IT industry and done
mostly IT type projects – winform or web frontend, web service/WCF/com+/other
transport layer and business logic and data access layer with some sort of a
database at the back (SQL Server usually) – a standard data/user driven
application.
In Elbit the story was completely different. The project I'm working on
is message driven (100% distributed) and I'm part of the SDK team (and
extensibility team but I'll write about this later on). This team consist of
highly skilled senior developers – when we had brainstorms it's really fun to
be able to receive a great and a quick feedback in various perspectives at once
– network, performance, configuration, distribution product management and
deployment – all of this is crucial in order to be able to provide the best
solution for defined problem; Beside the great team, we had a lot of
developer-goodies - an implementation of WCF-like layer (the project started in
VS2005 beta), WF-like layer, Publish-subscribe mechanism, distributed
configuration and state. Basically developer's heaven!!!
I mentioned earlier that I was part of the extensibility/cm team; well
in Elbit they created a specialized team that is responsible on builds, TFS/VS
extensibility. The main goal of this team is to provide the best conditions and
tools for the developers, so they'll be concentrated on developing high quality
product and not configuring builds or wondering what wrong in case of failure.
In the extensibility perspective we created an extensibility framework
(very similar to the power
commands infrastructure) and created various tools for developers – merge utility
(by work item), deep history for item (over branches) and much more.
In the next couple of posts I'll try to bring various takeoffs from the
wonderful and educating experience I had.
1)
Insights to development,
deployment and management in large scale application.
2)
MSMQ – how to detect
various problems and handle them.
3)
Deep history tool.
Although it looks like a good bye post it's not good bye yet (and even
not good bye it's "we will probability meet in a convention so see you
laterJ"