4 ms·

just code. code well.

by the1 14y ago

sethg 14y ago
You can code, code well, and then discover that the feature you just implemented was something that the upper management actually didn’t consider to be very important, or that they wanted something completely different from what you thought they wanted. That’s the sort of failure mode that Scrum and other development methodologies are trying to protect you against.
- pnathan 14y ago
  This is an incredibly big deal. If the customer didn't order it, it doesn't matter how well you coded.
- the1 14y ago
  I tend to think bringing in agile specialists and installing scrum process to save the project is a bit dogmatic. If you worked on a project for sometime and wrote/rewrote a lot, you probably know what's needed to be written. It's fairly unlikely the scrum process actually helps at that point. What keeps you going at it is probably "faith" you built through out the year since the onset of scrum installment... and, just a habit. If you are afraid of writing unneeded, unimportant, and unpopular things enough to label them as a "failure", your focus may be to find needed and important things for your audiences. Your focus may be to read the draft to a select sample audiences everyday, every week, continuously, and apply various analytical techniques to different statistical models you built from the feedbacks to overcome your fear of rejection, and "manage" direction, completion, and shipment of your writing. Or just write. A lot. And read. A lot. You'll "get" trends. You'll "get" what works and what doesn't. Of course you need feedbacks. Of course you need plans and management especially if you are co-writing with many authors. But my focus is still to write.
brazzy 14y ago
That's kinda like saying that all you have to do to win the Superbowl is "just play. play well."
- andyzweb 14y ago
  the team with the most points wins.
- mongol 14y ago
  Exactly. And then it turns out you excel in playing squash.
njharman 14y ago
1) code is minor part of delivering software that customer is willing to pay for. 2) "code well" is such a broad affirmation as to include using Scrum/Agile/something else to ensure that the code we deliver, works, is what customer wanted, when they wanted it, and cost < revenue.
jimbokun 14y ago
Code what well?

just code. code well.

by the1 14y ago

just code. code well.

sethg 14y ago

You can code, code well, and then discover that the feature you just implemented was something that the upper management actually didn’t consider to be very important, or that they wanted something completely different from what you thought they wanted. That’s the sort of failure mode that Scrum and other development methodologies are trying to protect you against.

pnathan 14y ago
This is an incredibly big deal. If the customer didn't order it, it doesn't matter how well you coded.
the1 14y ago
I tend to think bringing in agile specialists and installing scrum process to save the project is a bit dogmatic. If you worked on a project for sometime and wrote/rewrote a lot, you probably know what's needed to be written. It's fairly unlikely the scrum process actually helps at that point. What keeps you going at it is probably "faith" you built through out the year since the onset of scrum installment... and, just a habit. If you are afraid of writing unneeded, unimportant, and unpopular things enough to label them as a "failure", your focus may be to find needed and important things for your audiences. Your focus may be to read the draft to a select sample audiences everyday, every week, continuously, and apply various analytical techniques to different statistical models you built from the feedbacks to overcome your fear of rejection, and "manage" direction, completion, and shipment of your writing. Or just write. A lot. And read. A lot. You'll "get" trends. You'll "get" what works and what doesn't. Of course you need feedbacks. Of course you need plans and management especially if you are co-writing with many authors. But my focus is still to write.

brazzy 14y ago

That's kinda like saying that all you have to do to win the Superbowl is "just play. play well."

andyzweb 14y ago
the team with the most points wins.
mongol 14y ago
Exactly. And then it turns out you excel in playing squash.

njharman 14y ago

1) code is minor part of delivering software that customer is willing to pay for. 2) "code well" is such a broad affirmation as to include using Scrum/Agile/something else to ensure that the code we deliver, works, is what customer wanted, when they wanted it, and cost < revenue.

jimbokun 14y ago

Code what well?