4 ms·
I wish more companies were doing this. What could be the factor that would prevent all companies to do the same, apart from laziness? Am I the only one interes
by robinhood 8y ago
I wish more companies were doing this.
What could be the factor that would prevent all companies to do the same, apart from laziness?
Am I the only one interested by the changes that are made on the tools that I like? I'm the kind of guy who reads all release notes.
- pluc 8y agoThere's a matrix-style screensaver for OSX that uses something similar (global events via API) to populate the 'matrix characters' with actual code. Useless, but conceptually rather fitting. https://github.com/winterbe/github-matrix-screensaver https://github.com/winterbe/github-matrix-screensaver
- itsderek23 8y agoA lightweight approach we've started at my company: 1. Create a GitHub Repo dedicated to user-facing issues (https://github.com/scoutapp/roadmap https://github.com/scoutapp/roadmap) 2. Customers can subscribe to issues they are interested. 3. When resolving an issue, we reference it in the git commit, which closes the issue and notifies the issue subscribers. We're a developer tool, so it's a familar flow for our customers.
- blueline 8y agoNeat approach. I've also seen public facing trello boards used to varying success (at the very least to give users a hopefully clear picture of what features/issues are prioritized)
- mgiannopoulos 8y agoThe Beeminder folks are doing this since 2011 http://uvi.glitch.me/ http://uvi.glitch.me/
- dreeves 8y ago2633 User-Visible Improvements and counting! We've averaged exactly 1 per day for over 7 years. :) We also tweet them all to http://twitter.com/beemuvi http://twitter.com/beemuvi
- dguo 8y agoI've been using https://headwayapp.co/ https://headwayapp.co/.