I’m a software architect: I create designs for large-scale software systems. Generally, I do the initial coding for the core system and then hand off ongoing work to a team that works inside the framework I created. This way, the project gets the benefit of my design expertise, and the core parts get the benefit of my coding skills. Plus, of course, I get to write the hard bits and leave the less interesting parts for other people.
It works pretty well. What makes it work even better is when I come into a team that already has an existing implementation, but wants to start over with a blank slate. I’ve done that a few times now, with notable success. It’s sort of complementary to the multiplier effect I described above: by drawing on the team’s hard-won knowledge of the problem domain, I can attack problems I wouldn’t know how to handle on my own.
My favorite example of this sort of mutual multiplier is the M1 project I did at eCal.
|
|
|
|
|
|
|
Mastodon |