Best book that I have found in > 15 years of programming and teaching threaded programming is "Concurrent Systems" by J. Beacon - she describes the really hard parts very well.
It's not the actual programming that is hard in threaded programming; it's figuring out how to structure your design and understanding what you can get out concurrency and where the pit falls are.
but I would give her a cell phone with long distance, a laptop for her work, and a car that does not break down in dodgy neighborhoods. In addition I would give her an emergency credit card with enough coverage to clear her out of any bad situation.
Or yet another "Let's put our code, where our mouth is!" - lets get some ideas, get a group started, and start on the framework.
Outlook is absolutely one of Microsoft's killer aps, and it is a good idea, but needs to be done right: No VTP (virus transfer protocol), build in security, separation between data and code etc.
Maybe a PostgreSQL DB, qmail, with an XML protocol slapped on top of it. (Feel free to insert your favorite piece of free software that can do the job.)
It is so obvious that it hurts, and it is so obvious that it will happen despite MS trying to patent the principle of sending mail over the internet.
Slashdot Mirror
I love your analogy, but I would rephrase the catch:
You can even sell the barn, but you cannot take it away from anybody.
15 years ago the senior sysadmin at my university was encouraging the students to play with Linux/GNU tools.
Best book that I have found in > 15 years of programming and teaching threaded programming is "Concurrent Systems" by J. Beacon - she describes the really hard parts very well.
It's not the actual programming that is hard in threaded programming; it's figuring out how to structure your design and understanding what you can get out concurrency and where the pit falls are.
Best,
but I would give her a cell phone with long distance, a laptop for her work, and a car that does not break down in dodgy neighborhoods.
In addition I would give her an emergency credit
card with enough coverage to clear her out of
any bad situation.
/Soren
Uhh I smell a new project coming up!
Or yet another "Let's put our code, where our mouth is!" - lets get some ideas, get a group started, and start on the framework.
Outlook is absolutely one of Microsoft's killer aps, and it is a good idea, but needs to be done right: No VTP (virus transfer protocol), build in security, separation between data and code etc.
Maybe a PostgreSQL DB, qmail, with an XML protocol slapped on top of it. (Feel free to insert your favorite piece of free software that can do the job.)
It is so obvious that it hurts, and it is so obvious that it will happen despite MS trying to patent the principle of sending mail over the internet.
/Soren
.sig(h!)