jeremyis

13 ms·

1. 31.▲
   by jeremyis 6y ago

   If you're concerned about leaving your house due to COVID, the Oculus Quest 2 ($300) has helped with feeling trapped a little bit. I feel like I'm in the environment when I have the goggles on. And the exercise apps have been a gr
2. 32.▲
   by jeremyis 6y ago

   I just looked up Dyson Sphere Program. What have... you done. Haha looks awesome - thanks!
3. 33.▲
   by jeremyis 6y ago

   Really interesting piece. I like how it discusses various seemingly disparate issues and ties them together. > In our codebase, we have hundreds of these jobs, each with their own run_config. If you look at this codebase as a database, y
4. 34.▲
   by jeremyis 6y ago

   I know this kind of misses the point, but Factorio is one of the most addictive and rewarding gaming experience I've had. Beware: within months it ate up collectively hundreds of hours from myself and members of my friend group.
5. 35.▲
   by jeremyis 6y ago

   I think it’s time of liquidity for double triggered RSUs. That’s what big pre IPO companies give and at IPO all the accrued RSUs are taxed as income.
6. 36.▲
   by jeremyis 6y ago

   Thanks! What would it take for you to integrate it?
7. 37.▲
   by jeremyis 6y ago

   Got it. thanks!
8. 38.▲
   by jeremyis 6y ago

   Hi - thank you so much for the kind words. What features would you need in order to use it?
9. 39.▲
   by jeremyis 6y ago

   Got it! For A/B testing, we have that on our roadmap, though I think you could implement a poor man's version like this: K:V would be: testing_data: { exposure: 0.10, colors: ['green', 'red'], } /&#x2F
10. 40.▲
    by jeremyis 6y ago

    Hi! Thanks so much for your comment! Could you expand a bit on what you'd like with A/B testing? All of the values can be fetched across projects / clients, it's essentially a simple K:V store with broad libraries. For e
11. 41.▲
    by jeremyis 6y ago

    Thanks! Curious - why do you state mid sized companies specifically?
12. 42.▲
    by jeremyis 6y ago

    Hey - thanks for the comment. The vision for Config.ly is slightly different than what I think you described. In my mind there's "ENV VAR" which are secrets and has things like Doppler or many of the other things mentioned he
13. 43.▲
    by jeremyis 6y ago

    Hey! Config.ly Co-founder here. I agree that utilizing a database/S3 or rolling your own lightweight version is a big competitor to Configly. I'm not sure if you saw it, but I tried to highlight some of the reasons we think Config
14. 44.▲
    by jeremyis 6y ago

    Thank you for the kind words and really thoughtful comment! If we build a Python / Django library, would you integrate Configly? If not, what would it take? I think you hit the nail on the head for a core use-case: deployment processes
15. 45.▲
    by jeremyis 6y ago

    Hey! Doesn't come across as dismissive to me at all. It's a good question. You could think of this as Redis hosting (configured to be durable!) + UI with features like version history, lightweight type checking (and potential for
16. 46.▲
    by jeremyis 6y ago

    This is also a great idea. I really like the idea of having a tool to fetch the values from Config.ly and make that part of the build process. Thanks!
17. 47.▲
    by jeremyis 6y ago

    This is BRILLIANT! Thanks for the suggestion.
18. 48.▲
    by jeremyis 6y ago

    Hehe - that's cool. Thanks for the explanation.
19. 49.▲
    by jeremyis 6y ago

    I really love this idea. Thanks.
20. 50.▲
    by jeremyis 6y ago

    Not at all! You provided a ton of useful info. Thanks!
21. 51.▲
    by jeremyis 6y ago

    Thanks!
22. 52.▲
    by jeremyis 6y ago

    Thank you - building a backend is a great idea. We’ll look into it.
23. 53.▲
    by jeremyis 6y ago

    Im Jeremy! Good feedback, we’ll get to adding something. Thanks
24. 54.▲
    by jeremyis 6y ago

    (I don't see an option to reply to your other comment -- I'm guessing it's too deeply nested, so replying here) >I think if battery/data even becomes a concern, you have already put too much data into config and proba
25. 55.▲
    by jeremyis 6y ago

    Thanks for the feedback. The goal right now is not to store sensitive data in Config.ly - your read API keys will be on your clients - and so in theory anyone who can read that source code can fetch your keys. > Who has access to each cl
26. 56.▲
    by jeremyis 6y ago

    You definitely could use S3! I think I view some advantages of using Config.ly as: - Updating content is way simpler. Even non technical folks can do it. (and soon you'll have revision history) - I think with the S3 library you can use
27. 57.▲
    by jeremyis 6y ago

    Makes sense and you could definitely do that. I could be wrong, but I think some folks would want their other clients -- even their server -- retrieving that value from that one single source. So when you roll an Android app, you'd als
28. 58.▲
    by jeremyis 6y ago

    Thank you :-)
29. 59.▲
    by jeremyis 6y ago

    Thanks for the great feedback. That's something we can definitely give more priority to. I actually had an iOS library version that would poll infrequently in a background thread and had a synchronous API. Something like: Configly.init
30. 60.▲
    by jeremyis 6y ago

    Hey thanks for the insightful comment! I'm sympathetic to your thought here on having an external service and going with a simple approach. Situations with a slow deployment process has been a big motivator for building Config.ly -- an