Reddit Posts
Mentions
Was crypto just a beta test and we were dopes involved in UAT?
There's nothing wrong with software engineers and lots of code. There's something wrong with software engineers who try to be something they're not, e.g. economists. I code the tools that the rocket scientists use. That doesn't mean I know anything about rocket science, and I rely on their expert feedback (UAT) to make sure my tools give them what they need. In other words, they give me sample inputs, and they verify the outputs. In the case of crypto, there are no experts to give the software engineers good sample inputs, and no experts to verify that the outputs are good, because the "experts" are all just other software engineers or VCs.
I'm a dev, my team never rushes updates. When we get pressure from higher ups we just tell them we need 15 more days when we actually need 5, they give us 10 days. The time is enough to test the update in UAT before moving to PROD
Let me see if I understood correctly. You sent LRC from one wallet to another. You had your private key in .TXT format. But for that to work you have to disable 2FA ? Because your wrapper simply uses login credentials from .TXT as identifier I see you are on UAT, so I guess security is more laxed ?
open source baby, where UAT is passed before the definition phase is over. They also needed 0 meetings to decide if the payments should be reversible or not. The whole set of requirements was probably: 1. let's do the bitcoin thing Is there any other instance when someone can launch a proven product, and be the first to do so?
Why isn't this done on UAT environment???
Yeah now that actually sounds like a much more reliable metric. Depends on how much (and who) is testing to find the bugs though, no? Like if its an internal UAT team can they be found, fixed, and not reported? Is that a possible scenario?
Yes Typically you have 3. A development environment for development and testing. A lot of development can be done here across multiple developers so you aren’t necessarily having a stable environment. A testing environment which has much more up to date data, is restricted on any changing development, and is available to test. The other is your production environment or the “real world” environment. You may introduce a 4th between your initial testing environment and your production to include something like a public test net. Which is just a “UAT”, user acceptance testing environment. This just ensures that the everyday user is not having issues and also instills are confidence. You can also introduce additional environments but typically you don’t do too much as you have to maintain them all, keep them in sync, and a whole bunch of other support things.
I assume you mean UTC (not UAT)
But it UAT had a major dip, do you think it will continue?