economics-software

I ordered this book because I couldn't get our I/T (Information Technology) department to adopt a regular training methodology, such as Dick & Carey. It seems like most I/T staff, and I/T trainers in particular, wanted an approach to developing training that was specifically aimed at I/T. This book really helped. It covers most of the issues I faced in convincing our I/T staff to set up a formal I/T training program, and even got the HR and OE/OD folks to come along. The chapters are sequenced well, the content is easy to read, and the forms and checklists are a HUGE time saver! Even if you know how to develop training, this book can save you time, money, and maybe some blood pressure medication!

I am extremely impressed with this software! I ordered this before I took the exam for the third time! I noticed alot of the questions on the test were also seen in this practice software!

Despite a sensationalistic title and a poorly designed cover, The Plot to Get Bill Gates is a wonderful piece of reporting. Rivlin, while an obvious admirer of the technology tycoons, presents a fairly unbiased (though tilting a little in favor of Bill Gates) story about the growth of Microsoft, the computer industry in general, and the ever growing group of anti-Microsoft competitors. It does a very good job of describing all the players in this game, following the industry for the past twenty years, and explaining the technology so even computer illiterates like myself can understand. Rivlin obviously did a tremendous amount of research, interviewed hundreds of technologists, and really put his findings together well. This book is well written (though the flow is sometimes interrupted when Rivlin seems to remember something he forgot to add earlier and makes a long tangent out of it), very interesting (though nothing terribly original is presented if you are well acquainted with the technology industry), and entertaining. I would highly recommend it for people who want to learn more about Gates, other technology tycoons, the technology industry, or just want a look at how competitive companies operate and interact.

In a world of silicon, power-grabs, and excesses of wealth, personalities often overshadow technology. The author describes these larger than life ego-driven titans with truth as well as tongue-in-cheek humor. After describing Mc Neely and Ellison, Bill Gates perhaps seems more human.

One of the best technology-driven "exposes". As a Novell NetWare CNE (naturally belonging to the anti-Softie bunch), I found out more about Eric Schmidt than I knew before. Here's hoping that his network operating system, in competition with Microsoft, will be challanged for the better. Personality-wise, according to the author, he is already there.

The most interesting significant dialogue in the book focused around the battle between Oracle's Larry Ellison and Bill Gates, on the subject of the network computer (NC). Gates was so competitive, the author points out Gates dated Ellison's ex-wife, that's sick! Gates personal life is appalling. Don't get caught up in Gates personal life, however, disgusing; look instead at the company - he built.

Ellision marketed NC as the window operating system killer. The battle became a marketing and Public Relations battle more than a technology feasiblity battle. NC technology over credited the consumer burden of a supposedly costly operating system. In reality the windows operating system cost only a very small portion of the PC cost. PC technology invested billions to research and development. Such that, Intel and AMD research and development increased computational power, decreased cost, and PC components were more integratable. IBM technology reduce cost for harddrives and increased storage capacity. The PC component assembly standardized allowing various components to work together. Different manufacturers produced the mother boards, memory chips, and CPUs. Shifts in technology manufacturing to Asia reduced operating costs. Bill Gates did not believe the NC would replace the windows operating system. Gates more correctly access the pulse of the customer which was richer sets of business functionality. Consumers had become accustomed to powerful desktop applications.

At the same time desktop PCs were becoming a common and expected business expense, PC technology was proving to be an acceptable server technology running business great plains financials, sql server, exchange server, merchant server, and .net middleware applications.
Windows weakeness in massive parallel processing has been gaining in strength with each new generation of operating system. Unix had a twenty year head start in the area of symetrically parallel processing, however, Microsoft will become the leader in this field.

Software price barriers for small too medium size businesses were removed giving them affordable software and hardware infrastructures, offer by PC technology and Microsoft. Microsoft respond back too NC threat by a few of their own PR tactics. However, in the end the PC itself attracted consumers to continue buying.

On tactic was the acquistion of WebTV. Microsoft spent $420 million to buy WebTV. The first time, I saw WebTV, it didn't seem that impressive. However, consider this, as fiber optic technology investment increases and provides infrastructure for massive data bandwidth increases equal to 100,000 times modem bandwidth than Web application support becomes the bottle neck. Which company will build the software to control the information? Will the java based companies control the information or will the dot net companies? My bet is dot net technology will be the developers choice.

The WinTel PC technology is gaining more strength and effectiveness and considered as reliable servers. The benchmark must be value returned and cost per user. Why doesn't Microsoft build a dot net framework for Unix? I believe because it is unnecessary. Microsoft next generation of Operating system will scalable and powerful enough to run enterprise scale applications. Many ERP companies are realizing this shift. The investment in software development will converge on this fact and dot will experience rapid acceleration of momentum. The NC paradim was doomed because - it didn't match reality. I like the mainframe concept of change it once and effect all the users. The dot net framework provides the equivalent concept, fantasic!

Development training and marketing has always been a strong trait of Microsoft. Technology is Microsoft's religion. 100 hour weeks, with sleeping back hanging on the door, break rooms without tables, fat content food distributed as incentives to continue working, and the desire to dominate every techology sector. Gates established a culture of paronia, where every competitor was a real threat. Developers worked late into the evening and start early in the morning. Gates slept better if they worked late. The end result was a trememous amount of business functionality translating into wealth. The plot to get Bill Gates is much more about a plot to develop a capalistic culture producing jobs, wealth, and empowering the worker into a knowledge worker instead of a corporate cog.

Visual Studio.net and particularly Internet technologies have shifted strength to Microsoft development technology. C# will takeover java technology. The technology infrastructure is richer and eventually more large companies will abandon java for c#. The microsoft technology is far superior. The PC technology is more powerful. Microsoft is moving fast. The media underestimates their force.

Fiber optics will only increase the demand for more software development. Standardized APIs will empower developers to create more areas of business functionality reducing the cost of business. Voice, video, and data information will be transport over very fast network communication lines. You can bet on the fact that Microsoft technology will run the middleware guaranteeing integrated systems maintain their integrity. The dot net framework simplified component management and allow leveraging of object across multiple network computers. In the past DLL hell made Microsoft windows too complex. The dot net framework greatly simplifies the problems of managing components.

This reference is good for a base of terminology for Project Management. Unfortunately, because the difference between an IT project and a Construction project is so great, the BOK can only address high-level concepts. The golden nugget is that what the BOK does address are time-tested standards that help all project managers.

Why do you make a Charter? What goes in it? What do you get out of it? The BOK answers all these questions. By following the framework, your projects will have a fighting chance and not get caught up in a tangle of disorganization.

As for the PMP-applicability of this reference, it does not address contracts, team-building, or ethics, which are all required for passing the test. When I studied for the test, I spent about 5% of my time studying the PMBOK and 95% on other reference materials. I earned my PMP after 5 weeks of studying, without memorizing anything from the BOK.

I found having the PMBOK in Adobe Acrobat format to be a real convenience and prefer it to the paper version. Note: while you can download a copy of this document from PMI's web site, it's a preview version that is missing chapters 2, 4-12 and appendices A through F. Therefore, if you need a copy of the PMBOK 2000 version your options are to purchase either the CD ROM or the book.

PMI has put a lot of work into this version. Compared to the 1996 version this one reads better, shows clearer relationships between knowledge areas, and has been greatly expanded in some of the knowledge areas - most notably risk management and earned value project management. The CD ROM version that I am reviewing has additional refinements that make this media easier to work with. The 1996 version in electronic format was a collection of standalone Adobe Acrobat files, this version is a single Acrobat file that makes good use of Acrobat's navigation features.

If your reason for buying the PMBOK 2000 is to prepare for the Project Management Professional certification you have two choices: CD ROM or book, because this is the primary source of test questions. Heed the previous reviewer's comments that the 2001 examinations will also use the 1996 version as a basis for test questions. If you are buying this book to implement project management processes that conform to the PMBOK and work in the computer industry I recommend that you also look at Information Technology Project Management by Kathy Schwalbe. That book presents a project management approach for IT projects that is closely aligned to the PMBOK.

This CD ROM contains is the electronic form (Adobe Acrobat format) of a set of guidelines that represent two things: (1) a De Jure standard for project management, which is the American National Standard classified as ANSI/PMI 99-001-2000 and (2) one of the primary resources that you need to thoroughly know in order to successfully pass the Project Management Professional(PMP)certification examination. NOTE: According to the Project Management Institute candidates seeking PMP certification in 2001 will also be responsible for the content in the older PMBOK dated 1996 also available from Amazon.com.

What it contains: this CD ROM is identical in format and content as the hard copy versions of the PMBOK 2000 edition. Its 211 pages are divided into four sections that are comprised of 12 chapters and seven appendices.

Section I consists of three chapters that introduce the guide and briefly describes terms and definitions. It also provides an overview of the nine knowledge areas and 39 processes embodied in the project management framework. Chapter 2 adds a brief piece on the role of project offices, which was not in the 1996 edition. Chapter 3 appears to have taken a few ideas from the British PM standard, PRINCE 2 (PRojects IN a Controlled Environment) because more attention appears to be given to phases and interactions among phases. Another interesting thing I noted about Chapter 3 is the inclusion (although brief) of iterative development. If you are in IT/IS you will recognize how this can be aligned to the Rational Unified Process or other iterative development approaches.

The nine chapters in Section II address each of the nine knowledge areas and their associated processes. The knowledge areas are: project integration management, scope management, time management, cost management, quality management, human resources management, communications management, risk management and procurement management. The knowledge areas and processes in the 2000 edition have undergone some refinement and expansion from what is in the 1996 edition: Chapters 4 and 10 have a lot more material on earned value (I recommend Earned Value Project Management, 2nd edition as an augment to the PMBOK because the authors of that book were instrumental in adding earned value to the PMBOK), Chapter 6 touches on theory of constraints (a good book that extends this is Project Management in the Fast Lane by Robert Newbold), and Chapter 11, risk management, has been expanded to include six processes instead of four that were covered in the 1996 edition.

Section III is a collection of seven appendices, of which Appendix G, Summary of Project Management Knowledge Areas, is the most valuable. Section IV is a glossary and index.

It's a given that if you are pursuing PMP certification the PMBOK is a must. The burning question is whether or not you should get the hard copy or CD ROM version. I personally prefer the hard copy version because of the way I read (not to mention the eyestrain from reading off a monitor). However, the CD ROM version is a lot more portable, and you can print out the entire PMBOK or selected sections for offline reading. There is also something to be said for the way the CD ROM version is hyperlinked, making it a convenience. I have it in both formats, but you will have to decide which is most convenient for you - or spend the extra money and get the book and CD ROM.

These books are awful! I am a IS Manager for a school district and the typo's I found were frustrating. For example, I used it as a quick reference for the proper UNC path for user profiles. I kept racking my brain for two hours trying to figure out why it wasn't working. I finally realized that the path they had written down (\\server_name\winnt\profiles)(p.346 in NT server 4 book) was completely wrong!!! The proper path shopuld be \\server_name\profiles\username.

Sorry, just venting. Buy the Exam crams if you want to be MCSE. I struggled with the Sybex books for 6 months. I bought the Exam Crams and passed all 6 exams in 5 months

Jeff Tangen MCSE

I bought the boxed set, but I didn't use them to pass the 3 required exams: NT 4.0 SERVER, SERVER IN THE ENTERPRISE AND NT 4.0 WORKSTATION. Why? Because each book is huge, I tried reading through the first couple of chapters of NT Server 4.0 and ended up quitting because the information was very basic. It's really good for people who have absolutely no networking knowledge at all, because it covers basic networking. I have used the program and taken some classes so I found these books a waste of time for me. I wanted to save time (who has time to waste reading a 500 to 600 page book when you can read one that's half the size)so I used Sybex's MCSE core requirements NOTES instead. These books cut through all the unnessary stuff and give you the information you need to pass the exams.

However, I must say that I would not have passed if I did not use the practice tests put out but Transender corporation. the question's used in the exam notes book's did not prepare me for the exams. In conclusion, If you want to pass read the MCSE CORE REQUIREMENTS NOTES AND KNOW THE INFORMATION ON THE TRANSENDER EXAMS AND YOU WILL PASS. I hope this helps. Good luck.

But so far, I give the books 3 stars. I hope they will help me achieve my dream of being a blackjack wizard.

I bought this book hoping to find the real "case against Bill Gates", or more specifically against Microsoft. Goodness knows he and his cronies made plenty of secret business deals that, exposed to the light of day, would really damage the company. A book detailing (and, more importantly, documenting) all these things I've been trying to tell people for years would at the least make me seem less of a wild-eyed conspiracy theorist among my peers.

But, unfortunately, this book seems to concentrate mainly on what kind of a person Bill Gates is, including a truly baffling amount of coverage of Bill's courting of some woman who worked for Microsoft. I don't care about that [stuff]; I want to see the LEGAL case against him, not things that belong in the gossip column.

Thus disillusioned, I never finished the book, so for all I know it may contain what I hoped to find, but if so, it's not in the first half of the book.

This book covers the time frame from 1989 to 1998, focusing on the activities of Microsoft, its competitors and the government's antitrust effort over that period of time. The investigator of Microsoft and Bill Gates would do well to include this volume on their list, though it must be seen in conjunction with other works such as HARD DRIVE and OVERDRIVE, to get a complete picture. This book has much to recommend it. The stories behind the government efforts and frustrations in bringing Microsoft and its boss to task for its monopolistic and predatory practices are thoroughly presented. The basic patterns that Microsoft has used to gain its apparent stranglehold on both operating systems and software applications are well documented. The strengths of the book are in the story telling, the detailing of events ... sometimes to the point of "being there". The author's forte and the real value of the book, in my opinion, lies in the strength of the story telling. Ms. Goldman Rohm's ability to bring colour and texture to the events that she records lifts potentially flat information to memorable vitality. Her "characters" (and there are oodles of them in this Microsoft saga) are usually given shape through telling physical description, record of signature behaviours, and nick names (D'Artagnan). The environment in which events occur is given flavour and detail. To a degree that one would not expect in such a work, qualities of a good novel or play are used ... happily, as there are so many characters and so many events. Two helpful features of the work are: the list of main players found at the beginning of the work, listed according to "team" (ie. FTC, Microsoft, etc.) and position AND the italicized synopsis and hilite package found at the beginning of each chapter. Even with these features and the imaginative chapter titles (ie. Chapter 1: Double Bill> referring to Bill Gates and Bill Neukom), this reader still had his problems keeping it all together. The material is multitudinous and chaotic as reality tends to be. I personally could have done with a chart of major events, dates, and characters. Ms. Goldman Rohm has done a commendable job of making the people and events real and memorable. I personally thank her for her poetry and Ray Noorda's.

Microsoft's public relations armies must have come out in swarms to disparage this incredible, factual book that was the first to expose scores of predatory practices Microsoft engaged in to lock up the market. (If you read some of the statements Microsoft made in public about it, you will not believe it! Compare the review in The Nation, versus the Wall St. Journal, which is against the very existence of antitrust law to begin with!) This book came out before the antitrust trial began and turned out to be prophetic, given Judge Jackson's recent ruling. A must read ! Also see Rohm's book "Under the Radar." This book was highly controversial for one reason: it's GREAT, and exposes the ugly practices of a very dishonest band of senior executives--not a pretty picture for those who prefer to see Bill Gates as a hero.

I found the book to be a reasonably enjoyable read, however I must say that the author's high opinion of himself seems to shine through on almost every page and really put me off. We don't want to know about his boats, wealth, etc... just the story would do.

I read a different version, and the cover had just him on the front with a really self satisfying grin. And there were NO photos in the book to relate the story to!

Could have been much better.

This book is so closely aligned with Jim Clark's view of the world that the real drama of software development is lost. Clark claims he's not a whiner, but he spends page after page downing SGI and Microsoft. I would rather that he had spent time focusing on the lives of his programmers, in the way that a far better book, Show-Stopper!, by G. Pascal Zachary, did. In Show-Stopper!, real tension and non-stop action builds as Windows NT is built. That book has little to do with Bill Gates, but instead hones in on the intimate life details of David Cutler and his NT crew. In contrast, Netscape Time has ever redundant and tiresome themes, which if eliminated, would have halved the size of the book. Clark takes credit for founding the company but then, humbly at least, admits that Marc Andreesen and his NCSA crew are the real genius behind Netscape. Maybe someone will write that story in more detail sometime.

Would you spend twenty dollars to spend about 8 hours listening to Jim Clark reminisce about starting SGI and Netscape? Then buy the book.

For those familiar with the struggle of trying to accomplish something innovative, you will find his story strangely familiar. For those trying to innovate something on the Internet, you will find this book very encouraging. For those who read between the lines, you will find that it's not about the money, it's about "getting it" and being right, and money is the proof statement in this brave new world.

Clark's direct no-nonsense style can be in your face at times, and you can see why the dense just couldn't get it, because no one likes being shouted awake from a deep sleep. But like most prophets, Clark sees no profit in beating around the burning bush. It seems to be a trait of the innovator.

There is some real insight buried among the stories, as well as advice on how to deal with VCs and dilution of equity, problems many of us look forward to having.

This should be an audio CD, since it is more of an epic poem than a book. It would be great to have a DVD version with addition points of view and multimedia. Netscape made the Internet a multimedia experience; it would seem only fitting that a book by its founder would do the same.

Pekka Himanen has written an extended essay on theme he thinks is the changing force and imperative within the creators of the information society. He calls it the Hacker Ethic to contrast the Protestant Ethic made famous in Max Weber's classic text.

I think the theme the book is about is extremely important and most people in our society do not understand its effects and functions at all. To some degree Himanen is on the ball and makes the picture clearer to a layman. The first part of the book is about the work ethic where Himanen defines what Hacker's Ethic is about. This is the best part of the book.

Himanen starts defining Hacker's Ethic as a general attitude towards work in the information society. For example a car mechanic can be a "hacker" in his field of expertise. Described by Himanen, in the center of hacker ethic is information sharing. It is held as a duty to share interesting information with like-minded people. In some sense the hacker ethic is a counterforce to the market culture. Hackers enter into information creation and exchange motivated by enthusiasm, joy and passion, not just money. Working times of a hacker are individual and optimized. In overall, hierarchies and rules from above are not driving creative individuals in the information centric fields of our society.

Great stuff. But in some directions Himanen's essay is unfortunately not very profound and lacks touch of reality. This comes in part two which is about "money ethic". To me there is no insight or originality in his thoughts. I believe the worst writings about money I've ever encountered originate from philosophers, idealists, elitists and other guys who are somehow closer to higher superstition than the raw reality of street-level business world. - Brainstorming in the third and last part named "the nethic" is somewhere between the first and the second part. Personally, I don't find it very convincing.

How great hacker Himanen may be, his book is sold as one interesting product of commercial culture, which hopefully entertains and attracts the short attention-window of its target consumers. If you were an average american consumer interested in current societal issues would you buy a book from Pekka Himanen. - From who? No problem, on the cover of the book are printed the names Linus Torvalds and Manuel Castells. Torvalds has actually written a short intro to the book - that has no connection to Himanen's essay. Castells for his part has made a short summary of the main points from his three volume The Information Age (1996-1998) in the end.

I'm only 1/4 of the way through so far. I find it amusing that the author, obviously a believer in his writings, chooses to sell his book rather than provide it free of charge for all to download. This seems to go against the hacker ethic ;).

That aside, thus far it appears to be a worthy read. Reading the first three chapters has given me a slightly different perspective on my job and gave me a reason to be proud of my authority complex. Tomorrow I am going to revolt againt my bosses and tell them I'll work when I want to (If anybody reading this is looking to hire a developer with hacker ethics I will be needing a job tomorrow).

The Hacker Ethic is a late 1990s Information Age treatise. The author, a gifted and young sociologist, posits that the Protestant Ethic is gradually giving away to a new paradigm, and that the new paradigm will be much more effective and functional than the old paradigm. Seems simplistic, but much of Himanen's treatise is excellent and hard to ignore.

If I can fault the work, it would be along the lines that it can misinterpreted by slackers as a way of mindlessly rebelling against employers and western culture altogether. Too many Generation X advocates will take this like Charles Manson took the White Album. This is a solid, introductory work not to be read by nihilists.

Overall, I think Himanen is a very promising figure in the Information Age and will probably make a great long-term contribution to global society. I expect bigger and better things from him in the future.

This book is useful if you're already quite familiar with common valuation methods and can fill in the jumps & gaps. However, if any of the areas you're looking at is new to you or if you would like a more logical, well-reasoned approach or simply a discussion of all the various valuation methods in use, buy Damodaran's text instead.

This book was the prescribed & provided reference in the Corporate Finance department I worked in but most of my colleagues and I purchased our own copies of Damodaran's text "Investment Valuation, Wiley, Aswath Damodaran", which is superior in breadth as well as logical description of valuation processes.

I liked this book. In Russia it is one of the most popular books on valuatuion. But when I can get the perfect excel support for Investment Valuation by Aswath Damodaran or good web support for Valuation Methods and Shareholder Value Creation by Pablo Fernandez, I ask the authors, why don't they put supporting material in disk? I think that the price of their sowtware ($94.50) is too high compairing with the book ($56 with discount), because there is no supporting materials - only 1 spreadsheet (from my point of view does not conform to McKinsey, as the leader of consulting business). I hope, for the 4-th edition we will have a good excel support.

I hoped that McKinsey would have something new to say on this subject. There are two corporate finance texts and various finance books that cover the ground better or at least as well, so it is hard to see why this book was written.

In light of recent corporate shenanigans with off-balance sheet products, it is unforgiveable that this book doesn't address how lack of value can be disguised using off-balance sheet products. Total return swaps, an off-balance sheet financing tool, isn't discussed, and credit derivatives, another off-balance sheet tool aren't even discussed. For coverage of these topics and offshore vehicles, read "Credit Derivatives" by Tavakoli.

This book has many good ideas, but most people have probably thought, heard, or read them elsewhere. It is an enjoyable, humorous read, however. For those with limited business backgrounds it would make a great starting point.

Microsoft is one of the most successful business of all time. They are also a very hard competitors. Bill Gates is a man that must win at all costs, even if he has to bend, brake or change the rules. For more information and dirt on Mr Gates read the book 'Hard Drive' by James Wallace & Jim Erickson.

Ignoring Mr Gates wicked ways for a moment this book looks at the day to day running of Microsoft at the ground level. It outlines some very intelligent business practices. It really highlights the differences between a successful business like Microsoft and the mediocre businesses that I (like most people) end up working for. The real difference between Microsoft and most companies is that Microsoft expects more out of their employees, rewards them for working hard and doesn't play guilt and blame games that distract the employees from doing better work.

Julie Bick is never dry or boring and illustrates the points she makes with anecdotes from day to day life within the company. Other reviewers make a big deal out of this book being so thin but then again any information added would just be padding. This is one of the best business business books I've ever read, and should be a required text at any business school.

Excellent quick reading that seems like common sense, but if it was we'd all be doing this right?

Julie Bick hits it right on the nose. Some of the items we've all heard before. However, some were very new to me.

I plan on reading the next one. To give you a flavor of the contents below is an outline of the entire book:

-----------------------------------------------------------------

INTRODUCTION

1.All I really needed to know about running a business I learned at Microsoft

a.SETTING UP TO PLAY

i.Eat your own dog food, but don't believe your own press releases

ii.Examine your mistakes

iii.Let people fail

iv.Sometimes tankers can look like speedboats

v.Let your employees hear your customers

vi.Don't bet against your own teams creativity

vii.Tailor your message to your customer

viii.Every process can be improved

ix.Stay small

x.Act like a leader

b.WINNING THE GAME

i.If you can't win, change the rules

ii.Think three moves ahead

iii.Hit em, where they ain't

iv.You can change your image

v.Win-win deals: what they care about and what your care about

vi.Try it out in the real world

vii.Make big bets

viii.Big events make good deadlines

ix.Give your employees a piece of the pie

-----------------------------------------------------------------

2.All I really needed to know to do my job well I learned at Microsoft

a.BECOMING AN EXPERT

i.The elevator test

ii.Know who your customers are and who just isn't yet

iii.The swot team

iv.Know the business inside and out

v.Know the questions your boss is going to ask

vi.Make decisions as if you owned the company

b.GETTING THE JOB DONE

i.Work smart not long

ii.I don't know is okay, especially coupled with I'll find out

iii.Humor can get you out of sticky times

iv.Real employees do eat lunch

v.Creativity is not a one man job

vi.If you are going to drop the ball, arrange for someone to catch it

vii.Their experience versus your instinct

viii.Work faux pas

c.MANAGING YOUR MANAGER

i.Make your boss look good

ii.Don't waste your boss's time

iii.Bring solutions not problems

iv.Prepare your manager for bad news early

v.See how your boss works and what (s)he needs

vi.Let 'em know how they're doing

vii.Give your boss two chances

viii.If you bail out from a bad boss

ix.Don't burn bridges

-----------------------------------------------------------------

3.All I really needed to know to be a good boss I learned at Microsoft

a.LEADING

i.Communicate the strategy

ii.Give your team time

iii.Give your team a hill to climb over

iv.Give credit

v.And take blame

vi.Act the way you want your team to act

vii.Send your team into Bill Gates

viii.Prepare a class of successes not a successor

b.GETTING THROUGH THE ROUGH SPOTS

i.It's almost never as bad as you think it is

ii.Stay flexible your job may change completely in six months

iii.Be the designated jerk for your team

iv.Beneath you? Not Beneath the results

c.A GOOD BOSS GETS THE BEST TEAM

i.Manage your team one person at a time

ii.Mentor your team

iii.Friend versus Boss

iv.No surprises at review time

v.Hire smart and don't rush

vi.Keep the atmosphere fun

-----------------------------------------------------------------

4.All I really needed to know about communication I learned at Microsoft

a.WORDS

i.Your style

ii.What did that question really mean?

iii.Details implies truth

iv.Presenting versus Selling

v.Praise publicly, chastise privately

vi.Give actionable feedback

vii.There's always one more person that needs to know

viii.Why publish?

b.MEETINGS

i.Do you really need to go to the meeting?, and once there must you stay?

ii.Discuss the analysis, don't present the data

iii.Solve controversial issues in advance

iv.Running the meeting

v.Attendance tricks

c.EMAIL

i.Know your email commands

ii.Look closely at the recipient's name you just typed

iii.Email has no social skills

iv.Watch out for email forgery

-----------------------------------------------------------------

5.All I really needed to know about managing my career I learned at Microsoft

a.GETTING THE JOB YOU WANT

i.Know yourself before you choose your job

ii.No one cares more about your career than you

iii.Fix your sights on the corral, not a fence post

iv.Sometimes the frog job can make you a prince

v.Figure out what you'd do in the job before the interview

vi.Bring your ammunition to your job interview

vii.Keep your one page resume up to date

viii.Decide the three messages or attributes you want to convey

ix.If you were a small animal, how small would you be?

b.STAYING ON TRACK

i.A career is a long time

ii.Have your own personal board of directors

iii.The 360-degree review

iv.Think two jobs ahead

v.Keep it in perspective

vi.There is no enemy within

vii.Ten ways to balance work and life