Archive

Archive for the ‘Career’ Category

Be an Inventor, Be Innovative

January 29, 2009 Ali 2 comments

CEO of Boeing, Jim McNerney gave this great speech which I happened to find today while browsing. This is really awesome, a must-read.

 Its bit of a long reading (transcript of speech), so I am also highlighting few points of speech (to tempt you read whole text :) ) to summarize things that I really like to remember and add some of my (valuable :) ) comments.

 1.    Jim highlighted difference between Invention and Innovation. Frankly don’t we use these words as synonyms, well there is a big difference between the two. However the fact is inventors are always very limited souls who really create/discover something, many innovators adds features and work on improving the invention. Both touch lives of millions and literally change the way we (humans, at large) live our lives

 2.    Jim highlights five biggest myths of innovation

  Myth #1: The iconoclastic, crusading researcher, working out of a “skunk works” or bootlegging operation, is responsible for most innovation.

Myth #2: It’s all about technology. The techies are the only innovators.

Myth #3: It has to change everything. Like Captain Kirk in Star Trek, anyone who cares about innovation should seek “to boldly go where no man has gone before.”

Myth #4: Innovation is a matter of serendipity. Or accident. Or luck. As with Archimedes, it’s the happy thought that comes to you when you least expect it.

Myth #5 Discipline and creativity are mortal enemies. They cannot coexist. And discipline, by the way, is the bad guy. For innovation to flourish, the “suits” and the “bean counters” — or the managers and the accountants — have to get out of the way and accept that the creative process is inherently mysterious and unmanageable. (That’s what makes it so much fun.)

 OK lets pause here for a second and think how many times we have heard about myths and how many of us really believe in above. Jim’s counter-arguments on these myths are very interesting and just so factual and true.

 Fact #1: Innovation is a team sport, not a solo sport. It depends on a culture of technical sharing and openness to others. It takes people working together across different groups, disciplines and organizational lines to make it happen. It also takes real leadership in charting the course and inspiring people to reach for the highest level of performance supported by a never-ending focus on integrity.

Fact #2: Innovation can and should occur in all areas of business. It’s not solely about technology; it’s about creating value for the customer in many different ways. If you define innovation as taking a task — any task — and finding a way to do it better, so that the customer benefits, it becomes clear that innovation is part of everyone’s job.

Fact #3: In engineering, as in business, always sweat the small stuff. Incremental doesn’t mean insignificant; it often means just the opposite. Never-ending incremental improvements are vital both to sustaining current business and to opening new opportunities.

Fact #4: The “eureka” moment — while exciting — is rare. As Thomas Edison said (and we all remember this well), “Genius is 1 percent inspiration, 99% perspiration.” Even in the laboratory, innovation should not be left to happenstance. Like in other parts of the business, the effectiveness and productivity of a company’s R&D efforts should be measured … and managed … to eliminate duplication of effort; to maximize returns; and to ensure the company pursues the right products, with the right partners, and does all the other things it has to do to maintain a customer-oriented perspective.

Fact #5: In a business environment, you can’t have creativity without discipline because — like it or not — not all ideas are created equal. You need the rigor and discipline both to say ‘no’ on some projects and to put the pedal to the metal on others. As a project moves from the lab … through marketing and manufacturing … and into the field, there is a continuing need for discipline. At every stage, you must ask whether the project is on target to deliver a compelling value proposition to your customer — and, in the business-to-business world, to your customer’s customers.

 3.    Due to inventions and innovations in transportation, communication and information processing, global competition has become more intense, businesses have become more focused on creating practical and measurable value for the customer. Therefore..

Gone is the day when big engineering-oriented companies like Boeing would put technology into a product just because we could do it.

Gone is the day of the independent inventor within the corporation who isn’t asked … and isn’t expected … to know anyone else outside of a small group of engineers.

Gone is the say when most technical ideas and input come from within your own company or institution.

 4.    And then Jim gives example of Boeing 787 Dreamliner – Really Impressive!

Here is link to full transcript of speech

 I like speech because Jim talks about power of invention, how this changes world around us, how innovation (even tiny, small ones) cause human progress, this is all so exciting! Relate this to my belief that currently best ground for innovation and inventions is ‘Software Engineering Industry’. That doesn’t mean invention & innovation is dead in other fields, what I mean is we are living in an information age, lots of lots of data flows from one end of globe to another, from computers to newest gadgets, thus millions and billions and trillions and gazillions of bits of information gets process along the way, and our key to future inventions and how we humans will be leading our lives in next 50 or 100 years is how effectively, intuitively and comprehensible we will be processing this information. Software Industry gives you opportunity to play with this information all around, think of new ways to bring change in lives, dream and invent new ways of improving manual, disintegrated processes around us, bring power of technology to everyone. With cheap hardware and cloud computing around, I believe we software professionals are in best position ever in the human history to dream, invent and innovate. Best luck to us all :)

70-504 – Microsoft Certification Exam on Windows Worflow Foundation

November 4, 2007 Ali 4 comments

This post now has sequel here on preparations for 70-504

Few months before in one quiet boring evening, I was checking my emails when I saw one from LionBridge; inviting me to be part of a team working on preparing new exam on Windows Workflow Foundation for Microsoft!…. moment I read the email, I knew boring moments have ended and following months are going to be fun, and trust me they were! I worked with few amazing guys at LionBridge, a company with an impressive profile, works on lots of different areas of computing, one of which is to provide certification exam material to companies like Microsoft. I wrote items for new exam, which were evaluated for Microsoft’s defined standards by LionBridge, this was followed by lots of discussion and eventual approval of them.

Having signed NDA with LionBridge, I cannot comment on anything related to exam, not even harmless details (like how many areas of Workflow Foundation will exam cover) which everyone one would know once exam get announced by Microsoft. Rather, I would like to talk about what I felt very strongly about Workflow Foundation (WF) during these last few months of exam preparation.

Unlike its cousins; WPF, WCF, you would have noticed WF didn’t get that big reception from industry yet nor does it create that “sensational” effect in your mind. Its not as sexy as WPF is, and it doesn’t have those buzzwords (communication, web service, etc.) in its pocket like WCF. Still I believe WF is going to change the way we program in much drastic manner, unlike WPF, WCF. I don’t mean to compare three .NET 3.0 technologies, the point I am trying to make is, WF is about how you can make your deep core logic behind applications ‘customizable!’, it gives you power to make such intelligent robust application that Business Analysts or even clients can customize to their needs. It helps you writing batch jobs, services, routine chores in better fashion, and also gives you power to expose your application via web service, or have them executed as desktop application. You can run your ASP.NET web application page-flow workflow on WF, and you can have core business intensive software, designed on WF with its ease of designing, power of customization and liberty of being exposed as web service, called as background service or simply kicked by a desktop program. WPF is only about user interface, WCF is about communication, but WF is going to be backbone of variety of software. THIS is the reason I believe slowly but with its immense power and suite of facilities, WF will penetrate into our industry and change the way we program! ….therefore, I would strongly recommend brushing up your WF skills, and be among the first 100s who would pass 70-504 – Microsoft’s yet-to-be-announced certification exam on Windows Workflow Foundation. Don’t miss chance of putting this jewel on your resume! [One question, that may be asked why was I selected by LionBridge for writing exam? I think this may be because of this blog and/or my articles on Workflow Foundation at CodeProject.com]

This post now has sequel here on preparations for 70-504

Must Read Today – New Links (31 July 2007)

July 31, 2007 Ali Leave a comment

Must Read Today – New Links (27 July 2007)

July 27, 2007 Ali Leave a comment

Must Read Today – New Links (26 July 2007)

July 26, 2007 Ali 1 comment

My Programmer Personality

June 7, 2007 Ali Leave a comment

 Your programmer personality type is:

   PHTB

You’re a Planner.
You may be slow, but you’ll usually find the best solution. If something’s worth doing, it’s worth doing right.

You like coding at a High level.
The world is made up of objects and components, you should create your programs in the same way.

You work best in a Team.
A good group is better than the sum of it’s parts. The only thing better than a genius programmer is a cohesive group of genius programmers.

You are a liBeral programmer.
Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We’re not writing on paper anymore so we can take up as much room as we need.

Thanks to http://www.doolwind.com/index.php?page=11 

Why every programmer should read Grisham?

May 23, 2007 Ali Leave a comment

.. or any other lawyer stuff for that matter.

Well, thats what I believe and I have reason for this. While reading (non-technical stuff) helps in building intellectual level, gives knowledge of what world looks like and works outside computer and alpha geek environment, off course reading is fun, BUT it helps in everyday programming job as well. This is what I believe and here is reason for believing so.

I work for a company that specializes in retail products, we have suite of applications including EPOS, stock management system etc. Development process is; Analysts studies client requirements, formal product definition document is produced, program specs are based on the document which act as input to development team. Story remains a happy one till here, but thats it.

What follows is; developers produces prototypes based on program specs, analysts never like them, arguments begins here over program specs. Specs gets modified, development gears up, deliverables are produced, if analyst is happy this time, then client cries over something now. When you check it in documents, thing that client is now objecting to, are found to be part of specs/product definition file. You ask client to refer docs, clients then muses over it, then ramble for sometime and then agrees to changes specs, which means re-development (cost to be incurred by client!) and same cycle continues. This is life, right! no complaints. But point is; you should understand what point 1.ii.a means in page 5 of specs and what impact it has on 20.vi.z in page 50, and this understanding is not enough, you should be able to project your concerns / explain rationale behind certain decision to analysts/client when confrontation/confusion happens/arises. You have to even fight sometime and project your case to product manager in times of dispute to get resolution. That is not only soft skills are important, ability to understand specs, correlate different points and advocating why you made certain decision effectively is also important, otherwise your analysts/client will ever treat you with stick and never have good opinion about your skills.So what Grisham has to do with it? hey don’t you read about lawyers in it, how they project their case, how good they are in understanding certain act of some law and how they correlate different corollaries of laws and how effectively do they present it in court. Well, learn from it, we programmers should also have some lawyers genes in us.