lucaswilric

4 ms·

1. 1.▲
   by lucaswilric 6y ago

   Others have suggested starting with the small things - email, text messages, etc. I agree; those are good places to practice. I've gotten a certain amount of benefit from exposing my work to trusted test readers. Sometimes that's
2. 2.▲
   by lucaswilric 9y ago

   I think there are better ways to solve the problem of maintainers burning out. Encouraging code contributions is a good thing, it encourages people to suggest solutions to their problems. I think it fails to solve the burnout issue, though,
3. 3.▲
   My Journey into the Bubble(rdbl.co)

   2 points by lucaswilric 10y ago|0 comments
4. 4.▲
   Using an in-memory hash vs. a MySQL table(rdbl.co)

   2 points by lucaswilric 10y ago|1 comments
5. 5.▲
   Is Your Stand-Up Worth the Time?(rdbl.co)

   3 points by lucaswilric 10y ago|0 comments
6. 6.▲
   Welcome to the Bike Shed: Surviving consultation when everyone has an opinion(rdbl.co)

   2 points by lucaswilric 10y ago|0 comments
7. 7.▲
   by lucaswilric 10y ago

   It's feasible, as long as you can tolerate a bug for a short time. The advantage is that once you notice a bug, there's less in the way of getting a fix out to production. And let's face it: we're all tolerating bugs in
8. 8.▲
   Preparing for Continuous Delivery: Understanding your deployment process(rdbl.co)

   5 points by lucaswilric 10y ago|4 comments
9. 9.▲
   Customer Journey Modelling and Hypothesis Validation(artplustech.com)

   2 points by lucaswilric 10y ago|0 comments