It seems, to me, driver development is different from application development
at a large scale. I wonder how hard it is to develop a team in a relatively
small development house - let alone an efficient team. It is not possible to
get a lot of driver development job - so few programmers are interested to be
specialized at this area. And as you do not get driver developer easily you
can not manage project easily - and loss interest for future driver projects.
Strange situation.

--
Sincerely,
Maruf Maniruzzaman,
Software Engineer,
Dhaka, Bangladesh.
http://www.kuashaonline.com

Re: Driver development team by Maxim

Maxim
Sun Jul 08 02:54:53 CDT 2007

I would recommend to have 1 dedicated driver developer in your team in such
a case.

System-level development work can hardly be decomposed to several persons.
Usually 1 driver == 1 author, unless this is some huge module of >200KB binary.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"kuasha" <kuasha@discussions.microsoft.com> wrote in message
news:A9186975-E561-40B0-9A01-0C5AA8FBDA9E@microsoft.com...
> It seems, to me, driver development is different from application development
> at a large scale. I wonder how hard it is to develop a team in a relatively
> small development house - let alone an efficient team. It is not possible to
> get a lot of driver development job - so few programmers are interested to be
> specialized at this area. And as you do not get driver developer easily you
> can not manage project easily - and loss interest for future driver projects.
> Strange situation.
>
> --
> Sincerely,
> Maruf Maniruzzaman,
> Software Engineer,
> Dhaka, Bangladesh.
> http://www.kuashaonline.com
>


Re: Driver development team by Don

Don
Sun Jul 08 10:27:13 CDT 2007


"kuasha" <kuasha@discussions.microsoft.com> wrote in message
news:A9186975-E561-40B0-9A01-0C5AA8FBDA9E@microsoft.com...
> It seems, to me, driver development is different from application
> development
> at a large scale. I wonder how hard it is to develop a team in a
> relatively
> small development house - let alone an efficient team. It is not possible
> to
> get a lot of driver development job - so few programmers are interested
> to be
> specialized at this area. And as you do not get driver developer easily
> you
> can not manage project easily - and loss interest for future driver
> projects.
> Strange situation.
>
It is much worse than you think. First, driver development is typically an
individual effort. In some cases a small team can work on a single driver,
but this is rare. Also, there are many variations on driver types, someone
who does printer drivers is not likely to be any good at storage or
networking.

As you said driver development is different, it requires a level of quality
few applications can meet. A malfunctioning application is annoying, a bad
driver can take out the OS, or all the data. Also, drivers need to be
highly concious of secutity since they run as part of the system.

One of the worst things are the development houses who claim thousands of
man-years in driver development. What a piece of crap! To be an
experienced driver developer takes 5 to 10 years of experience, so if you
choose 5 that means they have 200 people with that level of experience,
somehow I think they are lying. Actually, I can say for sure since Walt
Oney and I both encountered situations where we lost bids to these firms,
then either saw queries on the newsgroups or were contacted directly by
people who were doing the work we lost and who had never done a driver.

My recomendatin to firms is contract out your driver development, unless
you have a number to do. In fact if you can hire two firms, one to do the
work, and one to review it. Of course as a consultant I am biased.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply



Re: Driver development team by Mark

Mark
Sun Jul 08 10:29:21 CDT 2007

Maxim S. Shatskih wrote:
> I would recommend to have 1 dedicated driver developer in your team in such
> a case.
>
> System-level development work can hardly be decomposed to several persons.
> Usually 1 driver == 1 author, unless this is some huge module of >200KB binary.
>
I agree with Maxim. You might have a 'Windows development team' or a
'Linux development team', and each such team might need one or two
kernel driver developers. Or you can always outsource the driver work to
us idiots.

--

=====================
Mark Roddy DDK MVP
Windows Vista/2003/XP Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com

RE: Driver development team by kuasha

kuasha
Mon Jul 09 04:12:01 CDT 2007

Thanks Maxim, Mark and Don. I understand better the cost and requirements of
driver development.