Re: How long can you work on a programming team before things get stale?
I would like to add to this by saying that some of the most
illuminating experiences I've ever had as a developer were in
situations where I spent a long stretch being grossly unproductive,
frustrated with my team, and feeling like I was learning almost
nothing at work.
Sometimes the grindstone is a very good teacher :)
-Debo
On Fri, Jun 4, 2010 at 11:03 AM, Aaron Weiker <aaron@...> wrote:
> I think this is focusing on the wrong thing. To me a job comes down to just
> a few crucial things.
>
> Do I feel productive?
> Do I like my team?
> Am I still learning at the pace I want?
>
> If I can't answer yes to all of these questions, then it is time for change.
>
> -Aaron
>
> On Fri, Jun 4, 2010 at 7:43 AM, Kurt Häusler <kurt.haeusler@...>
> wrote:
>>
>> I would agree with that. I guess it supports the notion of a
>> journeyman rather well.
>>
>> It does reach a point however where it conflicts with the
>> craftsmanship focus on building long-term relationships with customers
>> and the software that continually evolves to deliver them value, but I
>> guess at this point the focus is less on learning at the technology
>> level and moves to keeping up with changes at the personal and
>> business levels.
>>
>> In fact, there may even be more challenges, and thus more potential
>> for growth in maintaining brownfield software long term
>>
>> From what I understand from reading Software Craftsmanship, craftsmen
>> don't write throw-away software and spend a lot of time maintaining
>> brownfield code, and thus probably don't have the luxury of starting
>> lots of greenfield projects and may not have such a great need or
>> desire for learning all the shiny new tools.
>>
>> I suspect that there are other areas in which craftsmen can grow,
>> because they have such long-term relationships with codebases and
>> customers, that may be somewhat deeper or more profound than the
>> learning that a journeyman undergoes in his first year or two of a new
>> job.
>>
>> I don't know, as I tend to change jobs every couple of years, but I
>> hope there are still opportunities for growth when working for a long
>> time in one place, as I do intend on finding a role where I feel
>> comfortable (but not too comfortable, comfort zones absolutely kill
>> growth) embedding myself long term, and developing the sort of long
>> term focus talked about in Software Craftsmanship. Some things just
>> can't be built in a couple of years too. I can easily imagine a
>> software "masterpiece", or program comparable to the grander works of
>> the historical craftsmen, simply requiring an effort lasting somewhere
>> between 10 years and a lifetime.
>>
>> I wonder if things ever got stale halfway through building a medieval
>> cathedral.
>>
>> On Fri, Jun 4, 2010 at 3:56 PM, <at> TheSandyWalsh <sandy@...>
>> wrote:
>> > Does a craftsman have to set his own agenda and/or move around
>> > frequently to keep learning?
>> >
>> > Do you fear "running out of time" to develop your craft?
>> >
>> >
>> > http://www.sandywalsh.com/2010/06/how-long-can-you-work-on-programming.html
>> >
>> > --
>> > 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@...
>> > To unsubscribe from this group, send email to
>> > software_craftsmanship+unsubscribe@...
>> > 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@...
>> To unsubscribe from this group, send email to
>> software_craftsmanship+unsubscribe@...
>> 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@...
> To unsubscribe from this group, send email to
> software_craftsmanship+unsubscribe@...
> 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@...m.
To unsubscribe from this group, send email to software_craftsmanship+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/software_craftsmanship?hl=en.