Sat Mar 20 11:41:09 GMT 2021
From
/weblog/misc
http://javarevisited.blogspot.com.au[..]articles-every-programmer-must-read.html A great reading
Jerry Weinberg: The 10 Commandments of Egoless Programming
Dare Obasanjo: Top 10 Signs Your Software Project is Doomed
Omar Shahine: Top 10 Tips for Working at Microsoft (or Anywhere Else)
Michael McDonough: The Top 10 Things They Never Taught Me in Design School
Andres Taylor: Top 10 Things Ten Years of Professional Software Development Has Taught Me
Steve Yegge: 10 Great Books
-
http://www.codinghorror.com/blog/archives/000822.html Steve McConnell, The Ten Most Important Ideas in Software Engineering
http://www.yourdonreport.com[..]important-ideas-in-software-engineering/ Step 1 - Isolate
Step 2 - Eliminate
Step 3 - Code Ruthlessly
http://rdegges.com/how-i-program-stuff http://www.beabetterdeveloper.com[..]/2013/06/what-makes-great-developer.html Programming and typing -
http://swreflections.blogspot.com.au[..]ramming-thinking-or-typing-thinking.html http://www.inside.com.tw/2014/08/11/9thing_as_software_engineer http://simpleprogrammer.com[..]11-rules-all-programmers-should-live-by/ 10 Software Engineering Laws Everybody Loves to Ignore -
https://www.netmeister.org/blog/software-engineering-laws.html
(google search)
(amazon search)
Sat Jan 16 13:52:07 GMT 2021
From
/weblog/misc
John: "Ken... What advice would you give Java programmers?"
Ken Orr: "Don't define yourself as Java programmers."
It is better to be clearly wrong than to be obscurely right.
UML was developed to meet the design needs of programmers. We need tools focussed on meeting the design needs of users.
Master more than one design/programming paradigm.
http://weblogs.java.net[..]s/archive/2006/03/ken_orrs_advice_1.html And similar general advise for programmer from another guy:
http://www.codeproject.com/gen/work/standaloneprogrammer.asp The Pragmatic Programmers suggest learning a new language every year. This has already paid off for me. The more different languages I learn, the more I understand about programming in general. It's a lot easier to solve problems if you have a toolbox full of good tools.
http://www.onlamp.com/lpt/a/3691 More challenging projects every programmer should try -
https://web.eecs.utk.edu/~azh/blog/morechallengingprojects.html https://www.infoq.cn/article/k5CpCGNqgfErqTol2SpX
(google search)
(amazon search)
Wed Aug 19 17:07:20 GMT 2015
From
/weblog/misc
http://blog.objectmentor.com[..]articles/2008/03/20/musing-over-mutation Will experience hurt innovation? -
http://manincentral.blogspot.com/2008/01/out.html You Are Solving The Wrong Problem, what is the right problem? it is how to retry very quick -
http://www.azarask.in/blog/post/the-wrong-problem/# Most real innovation is done by crazy people doing crazy things. The keys are:
* Learn all you can before you go adventuring.
* Don't be afraid to make mistakes.
* Only make new mistakes.
* Keep your eyes open.
* Don't just look straight ahead: develop your peripheral vision.
* It's the things that go in unexpected directions are the most important.
One of the classic stories of serendipity and invention is the color mauve. -
http://weblogs.java.net/jag/page7.html#63 Translation of article from Aaron Swartz -
http://www.inside.com.tw/2013/01/15/aaron-swartz-howtoget-b http://www.inside.com.tw/2013/01/15/aaron-swartz-howtoget http://cn.wsj.com/big5/20130116/HPJ071809.asp The most interesting things I've learned about innovation -
http://jchyip.blogspot.com.au[..]t-interesting-things-ive-learned_16.html How should company drive innovation -
http://cn.wsj.com/big5/20130201/inn074913.asp http://cn.wsj.com/big5/20130930/inn073142.asp Issue from government driven society -
http://cn.wsj.com/big5/20130930/bch090746.asp?source=rss 領導者如何激發創新？ -
http://cn.wsj.com/big5/20130916/inn073006.asp http://www.infoq.com/articles/culture-learning-innovation 在我看來，人貴在敢於主動挑戰挫折。立下宏大目標；體驗巨大挫折。不止我一個人是這麼認為的。 -
http://cn.wsj.com/big5/20131104/inn074022.asp?source=rss From Imagination to Innovation -
http://jchyip.blogspot.com.au[..]4/03/from-imagination-to-innovation.html
(google search)
(amazon search)
Tue Sep 03 15:00:23 GMT 2013
From
/weblog/misc
Don't keep ppl interrupted -
http://blog.ninlabs.com/2013/01/programmer-interrupted/ common mistake at software house -
http://jroller.com/page/rolsen?entry=the_same_mistakes_over_and 1.- The all code is crap, except mine, attitude.
How to fix it: Don’t criticise others people code
2.- The “I fix that in a second” catastrophe.
How to fix it: Don’t trust yourself when carrying delicate activities.
3.- The “That will only take a second” misconception.
How to fix it: remember that is very likely that you will find so many things which you didn’t foresee when you start developing that is worth multiplying the estimate to cover for those
4.- The ego spiral.
How to fix it: Leave your ego at home. Big egos are one of the biggest non technical issues for any programmer. Keep in mind some basic considerations when making decisions.
5.- “It wasn’t me!”
How to fix it: No need to cry, or to perform seppuku, (aka harakiri), when we make a mistake.
6.- The demotivated genius.
How to fix it: Discipline. Unfortunately, there isn’t any other remedy I can think of.
7.- The premature programmer.
How to fix it: Probably the two easiest ways to help a programmer understand if some code is done are peer reviews and demos.
http://www.makinggoodsoftware.com[..]2011/05/23/top-7-programmers-bad-habits/ The naive approach to system replacement
List all the features the current system does
(Package) Compare with features in the new package; customise new package to match old package
(Custom) Build all features in the new system
This is how you waste time and money to build something that people will hate.
A better approach to system replacement
Understand the job that the users are doing. What are their goals? What are the activities they are doing to achieve those goals? How does the existing system support those activities?
Design the new system to support the user's goals. NOTE: This may have very little overlap with how the old system worked AND, I can almost guarantee, will consist of a lot less features.
But won't people be annoyed with the changes unless you match the old system?
http://jchyip.blogspot.com.au[..]8/system-replacements-are-not-about.html
(google search)
(amazon search)