<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Standing on the Shoulders of Giants!</title><link>/members-area/personalblogs/b/blog/posts/standing-on-the-shoulders-of-giants</link><description>Researchers publish for a variety of reason, suchs as claim to a discovery, sharing their findings, cordon of their research area so that everyone knows what they are working on so that they will look in a different direction, allowing them to travel</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Standing on the Shoulders of Giants!</title><link>https://community.element14.com/members-area/personalblogs/b/blog/posts/standing-on-the-shoulders-of-giants</link><pubDate>Thu, 26 Apr 2012 19:23:07 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:a68695cb-dbf7-49fa-8895-0e9fba470c8e</guid><dc:creator>DAB</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;I agree, many young engineers do not look at old research as much as they should.&lt;/p&gt;&lt;p&gt;Personnally, I find a much better level of detail in older papers than a lot of the new papers.&amp;nbsp; In part, because the researcher writing the paper assumes that the reader is already deeply familiar with the background.&amp;nbsp; I think this approach is wrong.&amp;nbsp; To be fully useful, you should always provide at least a quick overview of the subject so that you can set up a context in which the reader and assess your claim of improvement.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I have read too many papers that present their approach and then leap to the &amp;quot;Quit Everything is Done&amp;quot; (QED) without really providing the data needed to reach that point.&lt;/p&gt;&lt;p&gt;I also dislike papers that include hundreds of references.&amp;nbsp; Yes it may show that you at least looked at a lot of past research, but it is more useful to cite those that contributed to your idea and led you to your new development.&amp;nbsp; The term &amp;quot;Keep It Simple&amp;quot; KIS should always be invoked.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;So if you are writing research papers, keep it simple, set up a context for your idea and then include data that demonstrates your achievement.&amp;nbsp; Only then can you postulate other potential applications for you idea.&lt;/p&gt;&lt;p&gt;Papers writen just to keep your publication count up are generally useless to working engineers who really could benefit from your detailed understanding of the technical issues.&amp;nbsp; You just need to simplify the information so they can quickly grasp what you did and can agree that you have a good idea.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Just a thought,&lt;/p&gt;&lt;p&gt;DAB&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=13974&amp;AppID=293&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>