NYPL/engineering-general

Make "Fixing Quickly..." more generic?

Closed this issue · 4 comments

I definitely ❤️ the "Fixing Quickly vs Ideally" sentiment but I wonder if there's a way to express this in a more generic way so it's more universally applicable. Maybe more in-line with some of the principles expressed in the Agile Manifesto:

Two relevant principles come to mind:

Simplicity--the art of maximizing the amount of work not done--is essential.
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

I'll take a first try though it's really rough:

Velocity vs. Ideal
Simple solutions, delivered quickly are often better than ideal solutions. “Quick fixes” are acceptable if they are documented and agreed upon by other developers.

Your statement is better at expressing the tradeoff than what we currently have in the document.
I'll also throw in a pearl (perl?) from The Pragmatic Programmer:

"Great software today is often preferable to perfect software tomorrow."

Do you want to send a PR?

Also - I think your statement as is - can be included and is an improvement.

Cool! I tweaked the value based on the Perl you quoted from The Programatic Programmer. Love that.

Closed via #5