How We Beta Test at LaunchDarkly
By - circleci
Hey there launch darkly marketing drone No. 342. Good to see you. Again.
So, the problem, as we have discussed before, is your entire company appears to built around the concept of the IF statement.
There is nothing wrong with that. You do you.
However, this you see is a programming forum. We're looking for the actual technical detail. Show us the admin interface. Is it built into an external product? How do we interface with that? Is it something we host ourselves? What tech stacks do you support?
Furthermore, how do you recommend handling dependencies between features? What happens when a feature gets promoted to full time usage? Do we just keep the flag forever? Or do we then have a dev task to remove the flag code? The if statement I mentioned before? How about a post about taking a new feature through from start to finish. Concept to delivery and everything in between.
Because it all seems to me like it can only handle stuff like entire independent features or simple throwaway style changes.
And for that I can use an if statement. I can even have that if statement based off config, or even some code! Egads.
Why do we need you? In technical terms please.
Has anyone worked with these guys? What are your thoughts?
I am going to ignore the whole testing in production thing entirely. I'm sure you actually mean something like "gather feedback on a fully working internally tested feature" rather than "just throw code into prod and hope the if statement keeps it contained"
>Just because it has a computer in it doesn't make it programming. If there is no code in your link, it probably doesn't belong here.