Are you joking? This is the kind of thing that leads to flaky tests. I was always counseled against the use of randomness in my tests, unless we're talking generative testing like quickcheck.
or, maybe, there is something hugely wrong with your code, review pipeline or tests if adding randomness to unit test values makes your tests flaky and this is a good way to find it
or, maybe, it signals insufficient thought about the boundary conditions that should or shouldn't trigger test failures.
doing random things to hopefully get a failure is fine if there's an actual purpose to it, but putting random values all over the place in the hopes it reveals a problem in your CI pipeline or something seems like a real weak reason to do it.
I'm not really sure what point you're making. Is the point that it is harder to to secure more things? Is it that security events happen more frequently the higher your number of employees goes?
If so, I bristle at this way that many developers (not necessarily you, but generally) view security: "It's red or it's green."
Attack surface going up as the number of employees rises is expected, and the goal is to manage the risk in the portfolio, not to ensure perfect compliance, because you won't, ever.
Yea, that user made the most ridiculous statement.
I think the Onion did a piece saying something like "Netanyahu dead, Trump must go back to being the only president of the United States", and while satire, is a bit enlightening of the actual situation here.
In the case of the "Gulf of America" thing there was a clear and open statement by the executive that they wanted the maps changed (note that even in the US the name is still legally "Gulf of Mexico"). Apple and Google both decided to acquiesce to curry favor.
TMK there is no current government order to eliminate large swaths of Lebanon from maps. So the fact that Apple is doing this (seemingly on its own, despite all other mapping services reflecting the original place names) is the thing I'm explicitly calling out as being weird.
My understanding is parallel branches allow multiple changelists to be applied to a single workspace. eg you can have multiple WIP fix branches active in your feature branch workspace and not worry about polluting your feature branch with unrelated/duplicated commits.
Worktrees are multiple workspaces, each in their own directory, sharing a single git repo. This is helpful because you reduce the overhead and the CLI command juggling for fully separate clones.
I have no idea what approach is better for your multi-agent scenario.
One of the authors, John Hughes did a talk on property-based testing at Clojure West some number of years back. Worth a watch if you're interested: https://www.youtube.com/watch?v=zi0rHwfiX1Q
Funny you should mention that. I just used a two sentence prompt to do something straightforward. It took careful human consideration and 3 rounds of "two sentence" prompts to arrive at the _correct_ transformation.
I think you're missing the cost of screwing up design-level decision-making. If you fundamentally need to rethink how you're doing data storage, have a production system with other dependent systems, have public-facing APIs, and so on and so forth, you are definitely not talking about "two sentence prompts". You are playing a dangerous game with risk if you are not paying some of it off, or at the very least, accounting for it as you go.
Yes, both. A good example why is for example, as muscle memory grows it will bias your note selection when improvising. Sometimes you really need to slow down to consciously force yourself to explore other sounds. Once you've done that, you need to wear it in again so it sounds natural in your playing.
Absolutely. You can get "locked in" to certain patterns / phrases just via muscle memory and familiarity. Need to balance that with a little improv to find new patterns phrases you like, and then can train those in via muscle memory.
reply