Today's Topic Summary

Group: http://groups.google.com/group/software_craftsmanship/topics

• maiden speech - maintainable javascript code [1 Update]
• maiden speech - multithreading [1 Update]
• maiden speech - algorithms [1 Update]
• maiden speech - test driven development [1 Update]

 maiden speech - maintainable javascript code

Todd Sedano <todd.sedano-UCMPtG0cbvw3uPMLIKxrzw@public.gmane.org> Mar 22 04:16PM -0700  

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 maintainable code. I
want to get better at writing maintainable javascript code specially in
heavy-browser web game. What does the community think will help me improve?*


 

 maiden speech - multithreading

Todd Sedano <todd.sedano-UCMPtG0cbvw3uPMLIKxrzw@public.gmane.org> Mar 22 04:16PM -0700  

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?*
*
*
*
 
*


 

 maiden speech - algorithms

Todd Sedano <todd.sedano-UCMPtG0cbvw3uPMLIKxrzw@public.gmane.org> Mar 22 04:16PM -0700  

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 knowing how to use powerful problem
solving techniques. I don't have a background in computer science, so I
never studied algorithms. I want to get better in this area; what does the
community think will help me improve?*


 

 maiden speech - test driven development

Todd Sedano <todd.sedano-UCMPtG0cbvw3uPMLIKxrzw@public.gmane.org> Mar 22 04:15PM -0700  

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 'Test-driven
development'. I have always written unit tests after writing the code. So
TDD literally turned my software development model upside down. **I am
trying to use TDD but when I face a complex software problem, I find myself
reverting back to code first and test later. This is mostly because my
productivity is severely hampered due to my lack of experience in thinking
the TDD way. What does the community think will help me improve in this
area?*
* *
*
 
*


 

You received this message because you are subscribed to the Google Group software_craftsmanship.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To unsubscribe from this group, send email to software_craftsmanship+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/software_craftsmanship?hl=en.

--
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.