Discussion on the topic of Software Craftsmanship and group meetings. ()

Todd Sedano | 23 Mar 2012 00:16

maiden speech - multithreading

Short version: what would you tell someone who was trying to improve at ______ ? (see last sentence of email)

This last fall at SCNA in Chicago, I presented findings from my class "The Craft of Software Development" where each master student studying software engineering created a learning plan designed to work on an area of known weakness to further themselves in our craft. I appreciated the community's feedback about my class. (If you don't remember me, we also did some dancing at the start of my session. You were magnificant.)

This year, I'm asking for your input on my students' learning plans. If you have personal experience in one of these learning areas (or have guided an apprentice), I'd love to get your input.

What is something that has worked for you to become more of an expert in the named area?

(I've debated how to present this request to this group. There are eight topics. Perhaps it is better to have one email with everyone replying to it. Perhaps it is better to have eight email threads where people who only care about TDD can just offer advice on how to get better at TDD. Because there hasn't been a lot of traffic on this mailing list recently, I've decided to post four emails today and four emails tomorrow. If this was a colossal lack of judgement on my part, please mute any thread that you aren't interested in. And I'm sorry.)

I really appreciate your time and input,

Todd Sedano
Director of Software Engineering
Carnegie Mellon University
Silicon Valley Campus
Developing Software Leaders (TM)
T: 650-335-2812

For me Software Craftsmanship includes the notion of understanding multithreading and concurrency. As multi-core computers are very common, it's extremely useful technique to master. It's the only way to solve some asynchrony problems. So I want to get better at writing multithreading programs. What does the community think will help me improve in this area?

--
You received this message because you are subscribed to the Google Groups "software_craftsmanship" group.
To post to this group, send email to software_craftsmanship-/JYPxA39Uh4Ykp1iOSErHA@public.gmane.orgm.
To unsubscribe from this group, send email to software_craftsmanship+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at http://groups.google.com/group/software_craftsmanship?hl=en.

headers

Doug Bradbury | 24 Mar 2012 00:44

Re: maiden speech - multithreading

We introduce concurrency in our apprenticeship program with our http server project. Apprentices build an http server that must respond to multiple, concurrent requests. This usually forces them into at least an introduction to the topic.

Doug

On Thu, Mar 22, 2012 at 6:16 PM, Todd Sedano <todd.sedano-UCMPtG0cbvw3uPMLIKxrzw@public.gmane.org> wrote:

Short version: what would you tell someone who was trying to improve at ______ ? (see last sentence of email)

This last fall at SCNA in Chicago, I presented findings from my class "The Craft of Software Development" where each master student studying software engineering created a learning plan designed to work on an area of known weakness to further themselves in our craft. I appreciated the community's feedback about my class. (If you don't remember me, we also did some dancing at the start of my session. You were magnificant.)

This year, I'm asking for your input on my students' learning plans. If you have personal experience in one of these learning areas (or have guided an apprentice), I'd love to get your input.

What is something that has worked for you to become more of an expert in the named area?

(I've debated how to present this request to this group. There are eight topics. Perhaps it is better to have one email with everyone replying to it. Perhaps it is better to have eight email threads where people who only care about TDD can just offer advice on how to get better at TDD. Because there hasn't been a lot of traffic on this mailing list recently, I've decided to post four emails today and four emails tomorrow. If this was a colossal lack of judgement on my part, please mute any thread that you aren't interested in. And I'm sorry.)

I really appreciate your time and input,

Todd Sedano
Director of Software Engineering
Carnegie Mellon University
Silicon Valley Campus
Developing Software Leaders (TM)
T: 650-335-2812

For me Software Craftsmanship includes the notion of understanding multithreading and concurrency. As multi-core computers are very common, it's extremely useful technique to master. It's the only way to solve some asynchrony problems. So I want to get better at writing multithreading programs. What does the community think will help me improve in this area?

--
You received this message because you are subscribed to the Google Groups "software_craftsmanship" group.
To post to this group, send email to software_craftsmanship <at> googlegroups.com.
To unsubscribe from this group, send email to software_craftsmanship+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
For more options, visit this group at http://groups.google.com/group/software_craftsmanship?hl=en.