One day, after I am done with -insert reason here-, I will have a bad ass, well thought out backup solution.
For some reason you’re “insert reason here” was dropped by lemmy. I guess a sequential less-than/greater-than messes with it.
One day, after I am done with -insert reason here-, I will have a bad ass, well thought out backup solution.
For some reason you’re “insert reason here” was dropped by lemmy. I guess a sequential less-than/greater-than messes with it.
And we already do this - every culture has a form, some more ingrained than others.
During WWII (and the Cold War), Allied analysts, spies and diplomats found learning Russian particularly difficult for just this reason.
Very good point about Agile.
As an end-user (that is, the IT staff that will be deploying/managing things), I prefer less-frequent releases. I’d love to see 1 or 2 releases a year for all software (pipe dream, I know). Once you have a handful of packages, you end up with constant change to manage.
I suspect what we end up with is early adopters embracing the frequent releases, and providing feedback/error reporting, while people like me benefit from them while choosing to upgrade less frequently.
There are about 3 apps that I’m a beta tester for, so even I’m part of that early-adopter group.
“raw dogging the Internet”… I chuckled out loud