Red Hat watched its stock tumble 6.4% on Thursday as Wall Street digested the open-source software firm's latest results and details on the drag its recent JBoss acquisition will have on its profit this year.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-07
No. I mean time spent in the planning stage. Unless you want a project to end in disaster, you don't just start writing code and pull stuff out of thin air as you go along.
And this would have what in common with R&D. R&D is R&D, planing is planing. Two completely separate parts.
R&D is about getting new (not yet) things/methods done.
Planing is a project when you plan how to achieve result with already known methods. (Research part in planing problem has nothing in common with R&D, it is only involved in problem or goal research)
Example:
Lets say I code for .net. I have to plan my distributed app to work remote. After long and carefull consideration I decide on using Remoting (which I wouldn't). Did I create remoting? No. I only decided on using remoting during my project planing.
MS R&D software department made remoting.
This is common difference between R&D and planing.
Edited 2006-07-01 20:31
Member since:2005-10-08
Member since:
2005-10-08
> f by 'research' you mean debugging what they've written, then yes.
> But as an industry the average amount of time on R&D by developers
> is closer to 1%.
No. I mean time spent in the planning stage. Unless you want a project to end in disaster, you don't just start writing code and pull stuff out of thin air as you go along.