(a) Dont have passion for technologyIt is also true that knowing how to create applications ,however new the API or technology was still not peanuts.and whats the big deal in just knowing how to do something without understanding the underlying funda's .Now hold on here .If you think knowing how the data is represented or the various layers of business logic or knowing the syntax for comppiling on the command line is is 'geeky thoery' - then you are so so wrong . Like i was .
(b) Are in it for something good on their resume, CDs and t-shirts
Because like i found out later - any one with a encouraging learning curve would in a week or two be able to :
- connect to a DB and give security
- make ur app talk to a webservice
- xml feed or data representation for ur mobile devices
- windows forms !
For all those who thought .net was all there was going on ,and that developers cant live without the wizards .Other notions that spring up are that ppl in MS have no clue of what the hell is happening outside windows, cant live without a pretty looking IDE , and are basically guys who found this the easiest thing to do .
NO ....i repeat NO way. And i wish i could explain in details with each of you who think otherwise.I'd probably try to elaborate on why i say so. Take a look at some of the developer tools ,contrary to pupoular belief that the work that happens in MS ,is done on VS.
( NOTE : Also check out the complete list of pre-release products included in the Visual Studio 2005 Beta 2 Go-Live License )
For Office and Business solutions and products tht have interesting API 's spaning across :
- Access
- Data Analyzer
- Excel
- FrontPage
- InfoPath
- Information Bridge Framework
- Live Communications Server 2005
- Live Communications Server 2003
- Office
- Office Developer
- OneNote
- Outlook
- PowerPoint
- Project
- Publisher
- Visio
- Visual Studio 2005 Tools for Office
- Visual Studio Tools for Office, Version 2003
- Word
In fact Sriram tells me that ,the good ol 'command line' makes a comeback for him at Hyderabad for his work But the topics that got me really all excited were :
- Virtual Device Drivers for MS-DOS Applications or Special Hardware
- Microsoft STI : Still Image Device
- Microsoft Windows Internals
- Writing Windows Wdm Device Drivers ( PS: you can check out more on Getting Started with Windows Drivers and the Windows Driver Model (WDM))
- Developing Drivers with the Windows Driver Development Kits(DDK's)
- Writing Windows VxDs & Device Drivers
- Hardware ,Display Compatibility Test kits & DVD Test Annex
- Windows Native API References
- Microsoft Active Accessibility 2.0 Software Development Kit Tools ( check out accesability code samples here , and a gr8 list of resources here )
- The Real-time Communications (RTC) Client
- Rotor and so on
A model of an API call
What Are the Differences Between a 16-Bit Windows API and a 32-Bit Windows API?* Case sensitivity.
* Unicode or ANSI options.
* Parameter data types.
...more here
Then found this dated to 1994,that talked bout Creating Useful Native Visual Basic and Microsoft Access Functions.For Getting started with System programming in Windows ,you can check out WHDC for :
System and Device Design - Designing for Windows compatibility and reliability from the beginning prevents much rework later.
Driver Development - Microsoft provides the Windows Driver Development Kit (DDK) and a collection of testing tools to help you build reliable, stable, and secure drivers.
Logo Program Testing - To supplement your company's quality assurance practices, the Windows Hardware Quality Labs (WHQL) testing programs and the Windows Hardware Compatibility Tests (HCT) will help ensure that your hardware and drivers qualify for the "Designed for Windows" logo.
Qualification Service - Windows Quality Online Services provides the Web site infrastructure that you use to qualify your products for Microsoft logo programs and to list them in product catalogs and directories.
Product Maintenance - Windows Quality Online Services offer several methods for maintaining and distributing drivers, including the ability for your company to view Windows Error Reporting (WER) data associated with driver failures.
Well heres to the start of some serious and exciting stage of system level programming ... Cheers to that .
End of Part - 1 .
