Hi there!
I'm working on a page for developers to send to their managers to help make the case for purchasing a @PairWithTuple subscription.
If you manage devs and control purchasing decisions, I'd love to hear what you think about it.https://tuple.app/maybe
Are there questions you'd likely have that I didn't cover? Are any parts unconvincing and need reworking? Am I missing out on a great opportunity to X?
-
-
You have a typo in this sentence "and are currently rolling it out the entire engineering org" I also agree with the previous suggestion that it would be nice to explain the benefits of pair programming, perhaps after the second question.
-
I'm not the intended recipient, but I wonder if the 'Why is Tuple so expensive?' is the right question or answer (is the answer a bit too self-serving?). Perhaps 'Is Tuple expensive?' As your homepage nicely states: No, it pays for itself in happier, more productive engineers!
- Još 1 odgovor
Novi razgovor -
-
-
I might add something quick about the benefits of pair programming to the "what is pair programming" section, or maybe a link? It's not obvious why pair programming is a good thing.
-
*might not be obvious to non-devs
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.