The Right And Wrong Reasons To Hate General Electric [View article]
kevyirish
Call me by my first name NYC. Your statements are like your profile. empty. I have not deleted any of my comments. To you I proved I know nothing Are you paranoid? Try to read all comments to this article. Each one has a time stamp. you also never answered my mismatch question.
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
arg1
if management stop paying bad programers they have more money to up the dividend and buy back more shares. getting kissed is great unless its your sister.
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
kirken
I have been using msft products since the early 80's. From ms-dos to windows, office and IE. Between updates, patches and security items. I have had more than 7500 changes to my systems over the years, don't you think it's excessive?. IE 7 had a flaw that my bank forced me to load chrome in order to get into their system. It took msft 6 1/2 weeks to fix the flaw now imagine not having access to your on-line banking functions.
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
abu
I glad you like my humor and as a stockholder, I like the dividends and the capital gains if it goes up enough. I grew up a decade before Gates and was taught that you don't repeat the same mistakes. Do you think we would have so many updates and the spaghetti codes if they had real good managers?
mikehart Microsoft Office's Spaghetti Code Mess A faster Office upgrade cycle is warmly welcomed, but it will mean messier code and more bugs. By John C. Dvorak So it seems Microsoft has decided to move from updating Microsoft Office every two to three years to a whirlwind upgrade cycle measurable in weeks. This should result in some incredible hilarity as weirdness ensues. The problem with Microsoft code is that it has mostly deteriorated to what people like to call spaghetti code, a patchwork quilt of subroutines. This means millions of lines of code with no overseer. In the golden days of coding there was one person who literally knew and understood all the code. This person could say no to code coming in, knowing that it would introduce complications and ruin it. Many open-source projects still have overseers but Microsoft has either fired or promoted these people away, replacing them with managers looking for a way out. Since there are many talented programmers at Microsoft, much of the spaghetti code is simply bypassed, leaving behind zombie code in most of its products. This would often be undocumented semi-dead code. You cannot just erase it because there may be some untraceable and obscure subroutine, that refers to it rarely and if it is not there, the system could crash. Many of the screwball crashes you experience with Microsoft software stem from this sort of situation. Of course, the crash reporting tries to resolve this as best it can. I'm guessing, though, that the zombie code is generally left in place where it can also crash a system by its inability to properly find all its pieces or to figure out how to return home. Microsoft will deny that it has a lot of spaghetti code, but there is no way around it at this point. The key is to live with it or manage it. I'd love to see Microsoft hire a vice president of spaghetti code management. This spaghetti code management is not going to be easy if hordes of Office coders are going to upgrade Office 365 on a more regular basis. They are going to run into never-ending issues and add more hitches in the process. I hope I'm wrong but this looks like a fiasco waiting to happen. I can see most of these upgrades turning into bug fixes and emergency patches as newer and newer code bumps into zombie code from years ago and creates havoc. You'd think that by now Microsoft, which has 94,000 full-time employees plus contractors, could assemble a team to recode the entire product from scratch. The company tries this sort of thing frequently and the best example was the NT team led by David Cutler which churned out Windows 2000. But when you look under the hood, there is still spaghetti code.
Windows 8.1 (Blue) will indeed feature the return of the Start button in desktop mode, The Verge reports, backing up a ZDNet report suggesting likewise. But it won't feature the return of the Start menu - the button will merely allow users to click their way to Win. 8's (oft-criticized) start screen. The Verge also backs up ZDNet in stating Microsoft (MSFT +4.1%) will provide an option to boot directly into desktop mode. (ValueAct: I, II) [View news story]
WIGIT5
Actually I think S B& Co(management) should pay for the their stupidity. True MSFT makes tons of money but if you add back all the costs for putting out products that have to be re-made or re-tooled and released all the bad programmers we would have more money in the bank than Apple.
The Right And Wrong Reasons To Hate General Electric [View article]
NOT A CHANCE YOU WORKED FOR A"MAJOR" WALL STREET" FIRM. THEY HAVE THREE REQUIRMENTS.
1] ABLE TO READ 2] BE POLITE 3] USE SPELL CHECK
NYC
The Right And Wrong Reasons To Hate General Electric [View article]
Call me by my first name NYC. Your statements are like your profile.
empty.
I have not deleted any of my comments. To you I proved I know nothing
Are you paranoid?
Try to read all comments to this article. Each one has a time stamp.
you also never answered my mismatch question.
The Right And Wrong Reasons To Hate General Electric [View article]
YOU REALLY HAVE NO CLUE
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
Thay was cute.
it has started my day with a laugh which I hope will last all day.
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
I'm so frustrated with Ballmer I would fire him an replace him with the first guy to the lunch room. I figure I have at least a 50% up side.
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
if management stop paying bad programers they have more money to up the dividend and buy back more shares.
getting kissed is great unless its your sister.
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
I have been using msft products since the early 80's. From ms-dos to windows, office and IE. Between updates, patches and security items. I have had more than 7500 changes to my systems over the years, don't you think it's excessive?. IE 7 had a flaw that my bank forced me to load chrome in order to get into their system. It took msft 6 1/2 weeks to fix the flaw now imagine not having access to your on-line banking functions.
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
I agree over time we will get win 8 however how many will be by upgrade (choice) or on a new device (not by choice)
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
I see where your coming from but my comments are about how poor management has been on controlling its programs and programmers.
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
I glad you like my humor and as a stockholder, I like the dividends and the capital gains if it goes up enough.
I grew up a decade before Gates and was taught that you don't repeat the same mistakes. Do you think we would have so many updates and the spaghetti codes if they had real good managers?
Microsoft's Management Is Surprisingly Good, But Is It Enough? - Memento Mori Part 3 [View article]
The only way you could rate Microsoft good is to compare it to the US Government.
Microsoft: Back With A Bang [View article]
Microsoft Office's Spaghetti Code Mess
A faster Office upgrade cycle is warmly welcomed, but it will mean messier code and more bugs.
By John C. Dvorak
So it seems Microsoft has decided to move from updating Microsoft Office every two to three years to a whirlwind upgrade cycle measurable in weeks. This should result in some incredible hilarity as weirdness ensues.
The problem with Microsoft code is that it has mostly deteriorated to what people like to call spaghetti code, a patchwork quilt of subroutines. This means millions of lines of code with no overseer.
In the golden days of coding there was one person who literally knew and understood all the code. This person could say no to code coming in, knowing that it would introduce complications and ruin it. Many open-source projects still have overseers but Microsoft has either fired or promoted these people away, replacing them with managers looking for a way out.
Since there are many talented programmers at Microsoft, much of the spaghetti code is simply bypassed, leaving behind zombie code in most of its products. This would often be undocumented semi-dead code. You cannot just erase it because there may be some untraceable and obscure subroutine, that refers to it rarely and if it is not there, the system could crash. Many of the screwball crashes you experience with Microsoft software stem from this sort of situation.
Of course, the crash reporting tries to resolve this as best it can. I'm guessing, though, that the zombie code is generally left in place where it can also crash a system by its inability to properly find all its pieces or to figure out how to return home.
Microsoft will deny that it has a lot of spaghetti code, but there is no way around it at this point. The key is to live with it or manage it. I'd love to see Microsoft hire a vice president of spaghetti code management.
This spaghetti code management is not going to be easy if hordes of Office coders are going to upgrade Office 365 on a more regular basis. They are going to run into never-ending issues and add more hitches in the process.
I hope I'm wrong but this looks like a fiasco waiting to happen. I can see most of these upgrades turning into bug fixes and emergency patches as newer and newer code bumps into zombie code from years ago and creates havoc.
You'd think that by now Microsoft, which has 94,000 full-time employees plus contractors, could assemble a team to recode the entire product from scratch. The company tries this sort of thing frequently and the best example was the NT team led by David Cutler which churned out Windows 2000. But when you look under the hood, there is still spaghetti code.
GE Posts Another Record Backlog, But Organic Growth Falters [View article]
THANK YOU
Most information I found was several union locals complaining
about cola.
GE Posts Another Record Backlog, But Organic Growth Falters [View article]
CAN YOU GIVE NUMBERS TO YOUR CLAIM OF PENSION OBLIGATIONS?
Windows 8.1 (Blue) will indeed feature the return of the Start button in desktop mode, The Verge reports, backing up a ZDNet report suggesting likewise. But it won't feature the return of the Start menu - the button will merely allow users to click their way to Win. 8's (oft-criticized) start screen. The Verge also backs up ZDNet in stating Microsoft (MSFT +4.1%) will provide an option to boot directly into desktop mode. (ValueAct: I, II) [View news story]
Actually I think S B& Co(management) should pay for the their stupidity. True MSFT makes tons of money but if you add back all the costs for putting out products that have to be re-made or re-tooled and released all the bad programmers we would have more money in the bank than Apple.