Mon Mar 17 17:25:31 GMT 2008
From
/weblog/software_engineering/team
1. Hiring is the most important thing you do at work and always hire people smarter than you
2. A manager’s success is all about making his/her reports successful in what they do
3. You cannot move up in the company unless you train your replacement
4. It is all about “relationships” and not “products”
5. Only viewpoint that matters is that of the customer
6. There is a big difference between products that customers will “buy” vs. products customers “like”
7. Be “market driven” and not be “marketing driven”. There is a big difference
8. Have technical and business arguments with colleagues as long as none of it turns personal
9. Have meetings before the meeting
10. Trying and failing is a lot better than failing to try
11. Execution is the key to being successful
http://gopalshenoy.wordpress.com[..]arnt-at-solidworks-in-the-last-11-years/
(google search)
(amazon search)
Sat Nov 17 02:03:59 GMT 2007
From
/weblog/software_engineering/team
Have the idea of starting minor interest group / user group of various technology inside a company. Hope someday it happened and these information help
http://egjug.org[..]ow-to-make-a-successful-java-user-group/ Fishbowl (conversation), setup a small group from large group for team discussion -
http://en.wikipedia.org/wiki/Fishbowl_%28conversation%29 http://jchyip.blogspot.com/2007/11/fishbowl-standup.html
(google search)
(amazon search)
Mon Oct 22 16:25:14 GMT 2007
From
/weblog/software_engineering
http://www.whattofix.com/blog/archives/2006/10/signs_you_have.php You might not be agile if. . .
1. The ��Send/Receive�� and ��Save As�� buttons initiate most team communication.
2. Your whiteboards are mostly white.
3. ��Test-driven�� still refers to your car.
4. You don��t yet know what PHB stands for. (It's the "pointy haired boss" in the "Dilbert" comic strip.)
5. You know that CPM stands for critical path method of project management, and continue to rely upon it.
6. You spend more time trying to manage project dependencies than remove them.
7. Someone still believes in the ��Can��t Chart.�� (Oops, that��s the Gantt chart.)
8. Developers only develop, testers only test, and managers just manage.
9. Simplicity is presumed to be simple.
10. A change control board meets . . . ever.
http://www.versionone.net/Resources/AreYouAgile.asp http://www.jamesshore.com/Blog/Its-the-Software-Stupid.html
(google search)
(amazon search)
Sat Mar 03 04:43:34 GMT 2007
From
/weblog/software_engineering/team
Various tools and approach to Preserving Knowledge, I think the best is to
build custom webpage like what I does :-)
http://discuss.joelonsoftware.com[..]iscussGroup=3&cReplies=#discussBody12480
(google search)
(amazon search)
Thu Mar 01 07:32:47 GMT 2007
From
/weblog/software_engineering
These are the reasons why I think fixed scope and price contracts are bad for
the customer. It's why we at ThoughtWorks avoid this model as much as we can.
It is possible to do a FixedPrice contract in an agile manner, but it's not
wise to fix the scope.
http://martinfowler.com/bliki/FixedScopeMirage.html
(google search)
(amazon search)
Fri Jan 12 02:40:28 GMT 2007
From
/weblog/software_engineering/testing
A tools that support test base on log output for legucy program -
http://texttest.carmen.se/ And other similiar tools is vise -
http://www.artima.com/forums/flat.jsp?forum=106&thread=171323 Both sound very useful for test legucy code
(google search)
(amazon search)
Sun May 07 12:26:42 GMT 2006
From
/weblog/software_engineering/SCM
A very nice example that use subversion as a datasource at other application, great idea IMHO:
http://www.onjava.com/lpt/a/6571
(google search)
(amazon search)
Mon Nov 28 10:01:35 GMT 2005
From
/weblog/software_engineering/project
The problem with big projects like Java or rewriting Unix or designing the Sparc chip is that they require a five-year commitment. So when you come right down to it, I had to decide, "Do I want to push this big rock up a hill again?" Not this time.
Bill Gates faced a similar choice with his Longhorn project. He probably has a lot of great ideas and all these brilliant people, but he also has this antecedent condition he has to take into account?Xkeeping it somewhat in sync with the old Windows. So the beautiful vision may fail because it has to be compatible. I've often wondered why they can't, for once, do something new. I mean really, really new? But then, when I asked myself that same question, that's when I knew I had to leave Sun.
http://www.fortune.com/fortune/print/0,15935,490598,00.html
(google search)
(amazon search)