Quality software, n. 2007: "we release when it's ready" 2017: "we're always ready to release"
-
-
that doesn't seem right to me
2 replies 0 retweets 0 likes -
Admittedly I have no data to back up my claim... perhaps just something to ponder on.
1 reply 0 retweets 0 likes -
I've found, counterintuitively, practicing full continuous deployment increases velocity and quality.
1 reply 0 retweets 1 like -
But you have to do it correctly. Break things up into very small, shippable units. Automated tests are included in the def of "shippable"
1 reply 0 retweets 1 like -
Right. Continuous deployment forces automation which improves quality.
1 reply 2 retweets 2 likes -
Think back to punched cards - slow to deploy == more thought upfront in general. Not saying we go back to cards though!
1 reply 0 retweets 0 likes -
Ok I see what you're saying. I took the original post as commentary on how CI/CD has changed the industry.
1 reply 0 retweets 0 likes
The up front thought fundamentally restricted the kinds of things you could build because frequent contact w/ reality is critical for design
-
-
Think about the quality of something like Office 2003 vs Dropbox Paper or Google Docs.
2 replies 0 retweets 0 likes -
And no, I am not going to accept claims that Office 2003 was actually very high quality software and lolweb.
0 replies 0 retweets 1 like
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.