cvillecsteele
Re:Stop Building Traceability in Jira
on Monday March 23, 2026 @09:01PM (#47497371)
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 rebuilds the trace on every change. (That's what RTMify does)
Sequoia's Mission Accomplished
The Island of Misfit Startups: Part II (KesslerGym)
Island of Misfit Startups: Part I (LensReader)
Axioms of Polity
Re:Why do entrepreneurs engage in self-sabotage?
on Monday March 05, 2018 @01:50PM (#16523315)
So damn spot on. Read it.
Re:What happens when the Board of Directors begins to panic?
on Monday November 16, 2015 @12:14PM (#10575600)
Great narrative... Enlightening, and sobering.
Re:Rethinking caching in web apps
on Thursday October 04, 2012 @09:25AM (#4612162)
I'm not complaining. :)
Re:Rethinking caching in web apps
on Tuesday October 02, 2012 @09:41AM (#4601872)
At Room Key we're investigating Datomic. It's definitely interesting.
Re:Rethinking caching in web apps
on Tuesday October 02, 2012 @09:40AM (#4601864)
At Room Key we're using Amazon's DNS solution for load balancing (lowest latency).
Re:Rethinking caching in web apps
on Tuesday October 02, 2012 @09:39AM (#4601857)
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.
Re:Rethinking caching in web apps
on Tuesday October 02, 2012 @09:38AM (#4601854)
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.