[root] /weblog /software engineering




login:

password:

title search:




 

Sat May 10 01:36:41 HKT 2008

software engineering



(google search) (amazon search) second
download here

Sun Jun 15 23:41:46 HKT 2008 From /weblog/software+engineering/testing

refactoring unit test


Idea of how to refactoring test cases, summary :

Refactor production code with the tests passing. This helps you determine that the production code still does what it is meant to.
Refactor test code with the tests failing. This helps you determine that the test code still does what it is meant to.

http://googletesting.blogspot.com[..]07/04/tott-refactoring-tests-in-red.html

Collections of idea of testing private methods - http://www.infoq.com/news/2008/01/private-methods-tdd-design , may be it is a signal of refactoring?

(google search) (amazon search)





Fri May 09 23:44:24 HKT 2008 From /weblog/software+engineering

requirement


Summary: In this column, David Gelperin presents a problem familiar to many of us?what is the best way to record requirements? Given the limitations of static templates, how can we best manage high-volume, multidimentional requirements information? Read on and then share your experiences. - http://www.stickyminds.com[..]bjectId=5936&tth=DYN&tt=siteemail&iDyn=2

Why specs matter - Most developers are morons, and the rest are assholes. I have at various times counted myself in both groups, so I can say this with the utmost confidence. - http://diveintomark.org/archives/2004/08/16/specs

Explain why we should share the vision with the team - http://www.goodproductmanager.com[..]6/sell-your-requirements-to-development/

An OK article about scope changing management - http://www.projectperfect.com.au/info_scope_creep_mgmt.php

Using mind maps and story tree to manage requirement - http://epistemologic.com[..]-user-stories-mind-maps-and-story-trees/

Interesting software for requirement management - http://www.technobuff.net[..]app/product/showProduct.do?name=jfeature

Another angle to view requirement - not to blame, not to prevent responsible, just try to talk and solve problem is better than document - http://www.agileproductdesign.com[..]com/blog/requirements_considered_harmful

Template and sample for spec. - http://searchsoftwarequality.techtarget.com[..]et109stru&asrc=EM_NLN_2350433&uid=703565

If you want to be a good product manager, understand unmet needs and use that insight to drive requirements. - http://www.goodproductmanager.com[..]/2008/05/06/stop-gathering-requirements/

(google search) (amazon search)


Wed May 07 15:51:52 HKT 2008 From /weblog/software+engineering/testing

junit


A nice example of convert dbunit from using junit to testng - http://www.realsolve.co.uk[..]h/blog.php?name=philzoio&mydate=20050826

redirect junit output to a file - http://www.diotalevi.com/weblog/?p=43

invokeNCopiesWithTimeout, run a test ( in runnable() ) for n times and see if it ok for multi-thread likely or not - http://binkley.blogspot.com[..]/running-n-foreground-tasks-in-java.html

(google search) (amazon search)


Wed May 07 15:27:48 HKT 2008 From /weblog/software+engineering

project management


Only the programmer who is going to write the code can schedule it. Any system where management writes a schedule and hands it off to programmers is doomed to fail. Only the programmer who is going to do the work can figure out what steps they will need to take to implement that feature.

http://www.joelonsoftware.com/articles/fog0000000245.html

Never, ever let managers tell programmers to reduce an estimate. Many rookie software managers think that they can "motivate" their programmers to work faster by giving them nice, "tight" (unrealistically short) schedules. I think this kind of motivation is brain-dead.

http://www.joelonsoftware.com/articles/fog0000000245.html

Micromanagement or Macromanagement? http://boncey.org/2006_10_29_how_to_mentor_programmers

But, unfortunately, as a general rule, Project Managers have no training. Even if they do have training in the form of an MBA, MBA education is impractical and useless; the academic community has completely failed us in this respect. Furthermore, Project Managers are more often based on personal friendships and company politics; they are rarely based on management skill.
And, finally, most managers do not acknowledge that management is a skill that they must study and learn so they don't study or learn it.

http://discuss.joelonsoftware.com[..]DiscussTopicParent=8469&ixDiscussGroup=5

An explanation of agile, I think it is more about project management - http://blog.objectmentor.com/articles/2007/04/23/short-reach

Some common problem of software project management - http://ajaxwidgets.com[..]thomas/9_reasons_why_software_project.bb
http://ntschutta.com[..]ou-know-your-project-is-in-trouble-when/

http://www.goodproductmanager.com[..]roduct-management-vs-project-management/

Brief description of thoughtworks codejam - http://blog.nona.name/200804274.html

Listen first. Measure later. http://digerati-illuminatus.blogspot.com[..]gspot.com/2008/05/measure-or-listen.html

(google search) (amazon search)



Sun Apr 13 01:06:38 HKT 2008 From /weblog/software+engineering/team

leadership


Believe me, the objective was not to make decisions, but to create
the right environment so that the right decision would be made.
http://tech.groups.yahoo.com/group/leandevelopment/message/1952

A nice set of questions to ask for a leader - http://jchyip.blogspot.com[..]3/questions-on-influence-and-growth.html

In short, don't put your shoes on others' foot - http://www.inc.com[..]earned-in-the-army_Printer_Friendly.html

4 types of leadership style, well, I think he model leadership a little too simple - http://softwarecreation.org[..]s-the-best-leader-for-the-software-team/

(google search) (amazon search)




Sun Apr 06 01:21:46 HKT 2008 From /weblog/software+engineering/team

communication


Discussion toolkit - http://www.stickyminds.com[..]YCOLUMN&ObjectId=12875&objecttype=ARTCOL

Other tips - http://www.infoq.com/articles/satir-communication-model-teams

Appreciation inquiry, a communication tool helping adopting new thing - http://www.threeriversinstitute.org/AppreciatingYourWayToXP.htm

A lot of engineer will silence when under stress, how do you communicate with them that time? Here are some suggestions - http://now.eloqua.com[..]048&elq=1C1DC5420DC8451CB08AEBA44D4F6BC7

(google search) (amazon search)




Tue Mar 18 01:25:31 HKT 2008 From /weblog/software+engineering/team

Gopal Shenoy’s experience


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)


Tue Mar 18 01:25:31 HKT 2008 From /weblog/software+engineering/team

office


XP style office setup

http://www.scissor.com/resources/teamroom/
http://www.xp123.com/xplor/room-gallery/index.shtml

Programmers who have good working conditions and a personal investment in the end result will often volunteer overtime at crunch periods, or just when they have a particularly thorny problem to overcome and don’t want to go home
until it’s done.

http://fishbowl.pastiche.org[..]ings_will_continue_until_morale_improves

Use of kanban - http://www.infoq.com/articles/agile-kanban-boards

(google search) (amazon search)


Tue Mar 18 01:25:31 HKT 2008 From /weblog/software+engineering

sign of too much process


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)


Thu Mar 13 01:55:20 HKT 2008 From /weblog/software+engineering/testing

best practices


Test first/last is not important? Unit test either? What do you think? http://beust.com/weblog/archives/000477.html

* The name of the test should describe the requirement of the code
* There should be at least one test for each requirement of the code. Each possible path through of the code is a different requirement#
* Test the goal of the code, not the implementation

http://xprogramming.com/xpmag/testFirstGuidelines.htm http://www.theserverside.com[..]AppQuality&asrc=EM_NLN_761453&uid=703565 http://www.coopercode.net[..]og/2007/08/how-not-to-run-beta-test.html

A lot of links - http://it-techexperts.com/tutorials/tutorials.asp http://testingspot.net/ http://www.exampler.com[..]-links-biased-toward-exploratory-testing

The teaser: Fast, Isolated, Repeatable, Self-validating, and Timely. - http://blog.objectmentor.com[..]es/2007/08/02/not-a-task-but-an-approach http://blog.objectmentor.com/articles/2007/08/02/which-came-first

Corner cases - http://testobsessed.com[..]s/2007/02/testheuristicscheatsheetv1.pdf

One of the targets of TDD coding - http://haacked.com[..]e-code-is-about-managing-complexity.aspx

Design for unit test - http://www.theserverside.com[..]es/content/DesigntoUnitTest/article.html

Introduction to Lean project management - http://ossme.com[..]introduction-of-lean-project-management/

Push and Pull approach -
http://www.richarddurnall.com/?p=10
http://www.richarddurnall.com/?p=15
http://www.richarddurnall.com/?p=31

(google search) (amazon search)


Wed Mar 12 22:27:54 HKT 2008 From /weblog/software+engineering

productivity


> I followed this thread for a while and I've a question. What is an
> average number of "good" sloc a developer can produce daily?

> I know it depends on language, developer skill etc. but you, with your
> experience, how many good sloc will write today?

Today so far I deleted more than I wrote.

http://tech.groups.yahoo.com[..]/group/extremeprogramming/message/140866

(google search) (amazon search)


Fri Mar 07 02:29:52 HKT 2008 From /weblog/software+engineering/testing

Functional test


Selenium - Here is a video show how to record script using a firefox plugin: http://wiki.openqa.org/display/SIDE/Recording+a+Test (BTW, the plugin link: http://www.openqa.org/selenium-ide/), and here is a blog mentioned how to setup a test server to run batch of script altogather: http://agiletesting.blogspot.com[..]/web-app-testing-with-python-part-2.html

WatiN, alternative of selenium - http://blog.benhall.me.uk[..]2/how-to-unit-test-watin-mbunit-and.html another person saying this is better - http://jchyip.blogspot.com/2008/03/watij-vs-selenium-rc.html

And someone work hard on make FITness and Selenium work togather, more information can be found at http://www.cornetdesign.com[..]m/2006/09/fitnesse-selenium-wrapper.html http://gojko.net[..]ng-web-tests-with-fitnesse-and-selenium/

A story of how to overcome various issues of applying selenium in acceptance testing -http://blogs.atlassian.com[..]07/08/selenium_is_the_pain_worth_it.html

Here is a more complicated framework, not looking good but still keep it here as the concept is interesting - http://sourceforge.net/projects/cubictest

The most excellent implementation for my need - http://www.concordion.org/

http://www.jamesshore.com/Blog/Five-Ways-to-Misuse-Fit.html - Don't use it as junit, "The whole point of Fit is to use HTML to speak the customer's language and fixtures to translate that language to code. "

http://jroller.com/njain/entry/is_fitnesse_ready_for_enterprise - Version control is #1 issue at that article

http://www.jamesshore.com/Blog/Does-It-Work-Are-We-Done.html Why functional test is important

How much resource should put in functional test? http://c2.com/cgi/wiki?TestFoodPyramid

(google search) (amazon search)


Fri Mar 07 01:55:11 HKT 2008 From /weblog/software+engineering/team

Issues


Suggestion of how to due with deny - http://raminasser.com[..]to-do-when-projects-are-behind-schedule/

Common patterns of various issues and the recommended solution - http://www.aptprocess.com/whitepapers/risk/RiskToPatternTable.htm

Blame base management - http://digerati-illuminatus.blogspot.com[..]/poor-requirements-poor-coding-poor.html

Discipline always not focus at the issue, instead it often bring more other problems - http://blog.objectmentor.com[..]en-directed-at-the-symptom-not-the-cause

(google search) (amazon search)


Fri Feb 29 02:35:39 HKT 2008 From /weblog/software+engineering/testing

junit antipattern


http://www.exubero.com/junit/antipatterns.html

use thread in junit - http://softwareintegrityblog.com[..]blog/2007/11/05/false-positives-in-junit

issues of try to test everything, we need to get the balance for everything, not junit specific - http://www.nearinfinity.com[..]ay?entry=unit_testing_avoiding_extremism

Hard to test something? Unreadable tests? Slow running tests? It takes too long to write a test? Some solution suggested - http://www.stephenchu.com[..]/last-d-in-tdd-means-more-than-just.html

Comment out test so that the code compile - http://martinfowler.com/bliki/TestCancer.html

A list of TDD antipattern - http://blog.james-carr.org/?p=44

And the long discussion using random in unittest - http://tech.groups.yahoo.com[..]rivendevelopment/message/20458?var=1&l=1
Here is an example of using random in unittest, it actually same for every new instance! - http://www.skizz.biz/archives/000568.html


(google search) (amazon search)


Sun Feb 24 18:22:33 HKT 2008 From /weblog/software+engineering/team

meeting


It's Not Just Standing Up: Patterns of Daily Stand-up Meetings - http://martinfowler.com/articles/itsNotJustStandingUp.html

Tips for running daily meeting - http://www.haiphucnguyen.net/blog/?p=64

(google search) (amazon search)