troy55_yort55

4 ms·

1. 1.▲
   Show HN: We built Atono because we kept losing context(atono.io)

   1 points by troy55_yort55 1y ago|0 comments
2. 2.▲
   Try: Feature flags shouldn't require a separate service(atono.io)

   3 points by troy55_yort55 1y ago|1 comments
3. 3.▲
   by troy55_yort55 1y ago

   Hey HN! We built something interesting at atono.io - feature flags that live directly in your user stories, not in LaunchDarkly. The insight: Every time a dev wanted to flip a flag, they had to context-switch to another tool, find the right
4. 4.▲
   by troy55_yort55 1y ago

   Good point! We’ll look into a ‘progress enhancement’ strategy to adjust our content delivery based on browser configuration. Any interest in having a look at the app?
5. 5.▲
   Seeking Jira Survivors(atono.io)

   2 points by troy55_yort55 1y ago|3 comments
6. 6.▲
   by troy55_yort55 1y ago

   We are actively building a new approach to jira, putting dev's in control of more of the lifecycle and better support for x-functional teams. We are in need of critical feedback as we're starting to build what we love and need mor
7. 7.▲
   by troy55_yort55 2y ago

   Sometimes the flag management is more complex than dealign with config - but it's not ideal. Hardcoding flags can be difficult to manage across different environments, regions, customers, etc. Atono.io has flags built right into the st