cvillecsteele

5 ms·

1.
by cvillecsteele 7mo ago
the annotation is the easy part. The hard part is knowing whether REQ-123 is still satisfied after 67 subsequent commits touch that file. git blame can't tell you that. You need something that scans the current working tree and rebuild
2.
Stop Building Traceability in Jira(rtmify.io)
3 points by cvillecsteele 7mo ago|2 comments
3.
Sequoia's Mission Accomplished(colinsteele.org)
2 points by cvillecsteele 9mo ago|0 comments
4.
The Island of Misfit Startups: Part II (KesslerGym)(colinsteele.org)
1 points by cvillecsteele 9mo ago|0 comments
5.
Island of Misfit Startups: Part I (LensReader)(colinsteele.org)
1 points by cvillecsteele 9mo ago|0 comments
6.
Axioms of Polity(colinsteele.org)
1 points by cvillecsteele 9mo ago|0 comments
7.
by cvillecsteele 9y ago
So damn spot on. Read it.
8.
by cvillecsteele 11y ago
Great narrative... Enlightening, and sobering.
9.
by cvillecsteele 14y ago
I'm not complaining. :)
10.
by cvillecsteele 14y ago
At Room Key we're investigating Datomic. It's definitely interesting.
11.
by cvillecsteele 14y ago
At Room Key we're using Amazon's DNS solution for load balancing (lowest latency).
12.
by cvillecsteele 14y ago
Since we send the visitor off to the owning hotel chain's website to book, we don't have to manage the complexity of update such as you're describing.
13.
by cvillecsteele 14y ago
Hi, I'm the author. We are a new online travel agency (OTA), like pricline, et. al., but different in that we don't take the booking - we send you off to the actual hotel website to book.