Share Your Knowledge and Experiences
来源:互联网 发布:药品数据 编辑:程序博客网 时间:2024/06/01 10:46
Share Your Knowledge and Experiences
Paul W. Homer
From all of our experiences, including both success and failure, we learn a great deal. In a young industry like software development, disseminating this experience and knowledge is vital in helping sustain progress. What each team learns in its own tiny little corner of the world is possibly influential across the globe.
Realistically our fundamental knowledge base for software development—that is, the knowledge that is absolute and theoretically correct—is small compared to what is necessary to successfully develop a project. To compensate, we guess, rely on intuitive judgments or even pick randomly. In that, any major development project generates empirical evidence into what works and what fails.
We’re gradually working through the permutations, which we want to apply back to the industry as a whole.
At an individual level, we are all trying to grow and come to understand how to build larger and larger systems. The course of our careers will take us toward ever-increasing challenges, for which we want our past experiences to help guide us. Being there is one thing, but to get the most from the experience we often have to rationalize it. The best and easiest way of working through it is to attempt to explain it to another person.
The act of discussing something always helps to show its weaknesses. You don’t really understand something until you can explain it easily. It’s only by putting forth our explanations and discussing them that we solidify the experience into knowledge.
Another point is that while we may have had specific experiences, the inferences we draw from them may not be entirely correct in the overall context.
We may not have been as successful as we thought, or as smart as we wanted. Of course, testing your knowledge against the real world is scary, particularly when you find out that something dear is myth, incorrect, or was never true, it’s hard to be wrong.
Ultimately, we are human beings so not everything in our minds is correct, not every thought we have is reasonable. It’s only when we accept our flaws that we open up the possibility of improving. The old adage about learning more from failure always holds. If our ideas and beliefs do not stand the test of a debate, then it is better we find out now than build on it later.
We really want to share our knowledge and experience to help the industry progress; we also realize it helps us to understand and correct it. Given the state of so much of our software, it is clearly important for us to take every opportunity to share the things we know, what we think we know, and what we’ve seen. If we help those around us to improve, they’ll help us to reach our full potential.
Paul W. Homer
From all of our experiences, including both success and failure, we learn a great deal. In a young industry like software development, disseminating this experience and knowledge is vital in helping sustain progress. What each team learns in its own tiny little corner of the world is possibly influential across the globe.
Realistically our fundamental knowledge base for software development—that is, the knowledge that is absolute and theoretically correct—is small compared to what is necessary to successfully develop a project. To compensate, we guess, rely on intuitive judgments or even pick randomly. In that, any major development project generates empirical evidence into what works and what fails.
We’re gradually working through the permutations, which we want to apply back to the industry as a whole.
At an individual level, we are all trying to grow and come to understand how to build larger and larger systems. The course of our careers will take us toward ever-increasing challenges, for which we want our past experiences to help guide us. Being there is one thing, but to get the most from the experience we often have to rationalize it. The best and easiest way of working through it is to attempt to explain it to another person.
The act of discussing something always helps to show its weaknesses. You don’t really understand something until you can explain it easily. It’s only by putting forth our explanations and discussing them that we solidify the experience into knowledge.
Another point is that while we may have had specific experiences, the inferences we draw from them may not be entirely correct in the overall context.
We may not have been as successful as we thought, or as smart as we wanted. Of course, testing your knowledge against the real world is scary, particularly when you find out that something dear is myth, incorrect, or was never true, it’s hard to be wrong.
Ultimately, we are human beings so not everything in our minds is correct, not every thought we have is reasonable. It’s only when we accept our flaws that we open up the possibility of improving. The old adage about learning more from failure always holds. If our ideas and beliefs do not stand the test of a debate, then it is better we find out now than build on it later.
We really want to share our knowledge and experience to help the industry progress; we also realize it helps us to understand and correct it. Given the state of so much of our software, it is clearly important for us to take every opportunity to share the things we know, what we think we know, and what we’ve seen. If we help those around us to improve, they’ll help us to reach our full potential.
- Share Your Knowledge and Experiences
- Share Your Knowledge and Experiences
- share the oracle experiences
- knowledge share
- knowledge share | rpm解压
- http://gmeets.com ----Store, share and tag your favourite links
- Test Your UML Knowledge
- Your Knowledge Portfolio
- Experiences
- thanks for your share
- Share-nothing and Share-everything.
- Knowledge and Hard Work
- Knowledge and Hard work
- Knowledge and experience
- It Takes Two to Tango (myself, and your unprotected file share)
- User experiences with HLS and AutoESL's AutoPilot
- thread and share variable
- C++ Knowledge share: 3 kinds of template parameters
- 直方图均衡化(色调均化)(一)
- android 4.0 HttpURLConnection. getInputStream() 为空的问题
- inotify实例
- 清除应用的数据和关闭Wifi、BT、GPS,及清除wifi密码和wifi热点
- android weiget 实时数据更新
- Share Your Knowledge and Experiences
- php常用函数
- UVa 167 - The Sultan's Successors
- IOS单例模式及单例模式的优缺点
- getopt实例
- js学习
- ActiveSync失败和RTC的关系
- 常规递归和尾递归的性能比较
- 使用OpenCV实现内存中图像数据的RGB-->HSV转换