11–20 of 43 posts
Sorry I just don't understand the article. Can anyone rephrase?
The main point of the article appears to be: > You always have to design both “the product” your customers want and “the environment” in which your product will run in production. Thus any software product begins with two obvious categories of “work to be done.” People ignore this because it seems [counterintuitive.][going_there]
I am the author of the post and I approve this summary :)
Okay, I'll take it at face value. Can you name a few competent programmers who are also competent book / story writers ?
Okay, I'll take it at face value. Can you name a few competent programmers who are also competent book / story writers ?
Earlier quoted context omitted.
The main point of the article appears to be: > You always have to design both “the product” your customers want and “the environment” in which your product will run in production. Thus any software product begins with two obvious categories of “work to be done.” People ignore this because it seems [counterintuitive.][going_there]
Hey you saved everyone a click! I am the author of the post and I approve this summary :)
Okay, I'll take it at face value. Can you name a few competent programmers who are also competent book / story writers ?
Earlier quoted context omitted.
Hey you saved everyone a click! I am the author of the post and I approve this summary :)
Your blog archive (where the title links to) seems to be broken.
Just wondering if I'm the only one, but I like my logs to be the narrative of what's happening in the system.
Okay, I'll take it at face value. Can you name a few competent programmers who are also competent book / story writers ?
I started taking communication and story telling pretty seriously about 9 months ago and the data on my 2 latest courses (where I tried to create a cohesive narrative of the content) shows the completion rate being quite a bit higher than my older courses.
Are there other things at play? Maybe, but I'm 100% convinced it takes more than "raw programming talent" to be a good programmer in general.
When it comes to designing library code or public APIs, I would rather use code written by someone with 5 years of writing / story telling experience and 2 years of coding experience vs someone with 10 years of coding experience but can't communicate well at all.
Chances are the 2nd person wouldn't be able to see the "big picture" stuff when it comes to designing APIs, and when it comes to API design, the big picture is the most important thing. The implementation details of each function is the easy stuff (since you're a Google search away from solving most technical problems).
There's also many other factors that matter besides your code. For instance, if I can't even find your project, or your documentation is lack luster then it doesn't matter if you wrote the most elegant code in the universe, I'm not going to use it.
Okay, I'll take it at face value. Can you name a few competent programmers who are also competent book / story writers ?
Ellen Ullman
Jon Evans