Then you need to explain why those same incels forgot to hate all over the provided list of very excellent movies (except Avatar. Space Fern Gully was bad, IMHO; and didn't it have straight white male lead, anyway?).
I was about to say, "What about Tasha Yar," but then I remembered she wore ochre. But she was Chief Security Officer. Why wasn't she wearing red???? SOMEONE HELP ME.
It's absolutely fair to collapse Ext like that; after all, Ext, at least, kept a chain of compatibility over the same period NTFS did (both began in '93). But it has had, over the last 15 years, plenty of large-share competition with which it was incompatible (this is what I was addressing about GGP's gripe about Microsoft introducing system incompatibility), such as ReiserFS, XFS, JFS, etc.
Again, not trying to put NTFS on a pedestal; just addressing the notion that is was MS who fragmented the FS ecosystem.
If Microsoft was not so focused on file system incompatibility, it would have supported EXT2,3,4 a long time ago.
You're faulting the folks who picked an FS and stuck with it for 26 years, during which time Linux has at least 5 (that I can think of and used, at least) different file-systems that were the "new standard" all new installs should be on. Look, MS made a lot of boneheaded architectural decisions, but consistent backwards compatibility in their file system (regardless of how awful it is [and it is]) is not one of them.
It's over-reactionary anti-skeuomorphism. Designers collectively woke up, realized wood grain and 3D-contoured buttons have no place in UI, and proceeded to lose their collective minds.
No, designers are already all-in on green text. Users track green "calls to action" faster than any other color, and feel better about the action being the right one. You ever notice how those fake download sites all have big, green, "Download Now" buttons? It's psychology. (disclaimer: I have run too many of these damn UI/UX user trials)
He did in fact misspell "complement." Nevertheless, you understood and received his intended meaning; therefore, communication was successful. Anything beyond that is useless pedantry.
Your team would be being dogmatic about areas where the methodology itself is accommodating. You should use whichever of the two approaches that you think works.
Oh, I get it. So the big yellow box will convince the company to hire more quality testers where the hundreds of little yellow boxes on every single product backlog item did not.
Of course, that's not about "agile" or "scrum" it's about having a culture of trust vs a culture of manipulation.
Yes! This is why I hate holy wars about methodology. If you have a solid team, a competent manager, and that manager trusts his team, than any methodology can work. I prefer scrum. But I'd rather have a trusting manager without scrum, than a micro-manager who distrusts me with scrum (been there, done that, got the heart attack to prove it).
My old scrum team of 10 years had a policy of only considering half the available work hours when placing hours on tasks. More often than not, it was spot on. After 6 months our velocity projections were spot on, every sprint. After that I worked on a "scrum" team that packed everyone's sprint board with 40 hours/week of work.... but sprint "planning" ate one of those days.
Underestimating work availability and overestimating needed work was pejoratively called "sandbagging" on that team, and yet the former delivered project on the estimated date, and the latter never did, even once.
The flip side is that you never do any of the work that by nature is too big for a sprint.
But that's the point. If you follow the rules, you have to break down the project into discrete, manageable chunks. In the old waterfall days, we could have a nebulous, unplanned project take a year and have to be rebooted because the approach was not thought-out beforehand. The iron-clad story size limit forces a bare minimum of pre-planning.
And in my experience, there's no such thing as "a project too big and can't be split into smaller pieces." I absolutely do not believe such a thing is possible, unless the project is to write a single algorithm in a single method, and spend 3-months sprint doing it.
No, what you are describing is Server Push, which has nothing to do with this. Lazy load, in this context, means the browser does not request elements that would be rendered off screen ("below the fold") until they are needed.
No, no, no, no. TFS is not the place to provide details, or context for people unfamiliar with common lingo for the subject. Literally everyone who works in web design/development knows what lazy load/lazy fetch is. Put that shit TFA and keep the summary clean. If you want to know more, click TFL (the fucking link).
Say what you want, but Martha Stewart is an amazing businesswoman. Stock investor? Not so much. But the fact that is that she is a self-made billionaire with a media empire that survived her conviction and incarceration with aplomb.
That was the intention, but it didn't have the intended result. Year-over-year soviet defense spending was actually relatively flat; increasing only 1-3% from then until '85, when Gorbechav nuked the defense budget to make room for perestroika and force military autonomy on satellite states. What we don't know is whether any intangible psychological effect influenced how glasnost and perestroika played out.
Slashdot Mirror
I wonder if the court would have decided differently with a different president.
If so, our judicial system is as fucked as the other branches.
"under new authorities it was granted by President Trump and Congress"
Then you need to explain why those same incels forgot to hate all over the provided list of very excellent movies (except Avatar. Space Fern Gully was bad, IMHO; and didn't it have straight white male lead, anyway?).
Ok, that does make sense, especially if you think of Command Division as "command of ship" instead of "command of people."
The Sextagon!
I was about to say, "What about Tasha Yar," but then I remembered she wore ochre. But she was Chief Security Officer. Why wasn't she wearing red???? SOMEONE HELP ME.
It's absolutely fair to collapse Ext like that; after all, Ext, at least, kept a chain of compatibility over the same period NTFS did (both began in '93). But it has had, over the last 15 years, plenty of large-share competition with which it was incompatible (this is what I was addressing about GGP's gripe about Microsoft introducing system incompatibility), such as ReiserFS, XFS, JFS, etc.
Again, not trying to put NTFS on a pedestal; just addressing the notion that is was MS who fragmented the FS ecosystem.
If Microsoft was not so focused on file system incompatibility, it would have supported EXT2,3,4 a long time ago.
You're faulting the folks who picked an FS and stuck with it for 26 years, during which time Linux has at least 5 (that I can think of and used, at least) different file-systems that were the "new standard" all new installs should be on. Look, MS made a lot of boneheaded architectural decisions, but consistent backwards compatibility in their file system (regardless of how awful it is [and it is]) is not one of them.
It's over-reactionary anti-skeuomorphism. Designers collectively woke up, realized wood grain and 3D-contoured buttons have no place in UI, and proceeded to lose their collective minds.
No, designers are already all-in on green text. Users track green "calls to action" faster than any other color, and feel better about the action being the right one. You ever notice how those fake download sites all have big, green, "Download Now" buttons? It's psychology. (disclaimer: I have run too many of these damn UI/UX user trials)
He did in fact misspell "complement." Nevertheless, you understood and received his intended meaning; therefore, communication was successful. Anything beyond that is useless pedantry.
Well, it's been 20 years so far, so....
As someone from the deep south: there is zero level of courtesy in "bless your heart." It is an open-palm slap in the face.
I just changed my mind on marijuana. I am now 100% for it if it will get you to chill the fuck out.
Your team would be being dogmatic about areas where the methodology itself is accommodating. You should use whichever of the two approaches that you think works.
Oh, I get it. So the big yellow box will convince the company to hire more quality testers where the hundreds of little yellow boxes on every single product backlog item did not.
Don't be naive.
Of course, that's not about "agile" or "scrum" it's about having a culture of trust vs a culture of manipulation.
Yes! This is why I hate holy wars about methodology. If you have a solid team, a competent manager, and that manager trusts his team, than any methodology can work. I prefer scrum. But I'd rather have a trusting manager without scrum, than a micro-manager who distrusts me with scrum (been there, done that, got the heart attack to prove it).
Is "agile" the reason why paying customers are now unpaid beta testers for the vast majority of crapware foisted on us by software houses?
If they won't pay for proper QA under agile, what makes you think they'll do it under waterfall?
My old scrum team of 10 years had a policy of only considering half the available work hours when placing hours on tasks. More often than not, it was spot on. After 6 months our velocity projections were spot on, every sprint. After that I worked on a "scrum" team that packed everyone's sprint board with 40 hours/week of work.... but sprint "planning" ate one of those days.
Underestimating work availability and overestimating needed work was pejoratively called "sandbagging" on that team, and yet the former delivered project on the estimated date, and the latter never did, even once.
The flip side is that you never do any of the work that by nature is too big for a sprint.
But that's the point. If you follow the rules, you have to break down the project into discrete, manageable chunks. In the old waterfall days, we could have a nebulous, unplanned project take a year and have to be rebooted because the approach was not thought-out beforehand. The iron-clad story size limit forces a bare minimum of pre-planning.
And in my experience, there's no such thing as "a project too big and can't be split into smaller pieces." I absolutely do not believe such a thing is possible, unless the project is to write a single algorithm in a single method, and spend 3-months sprint doing it.
Well, then that's the shortest story I've ever read. But thanks for saving me the paperback price!
No, what you are describing is Server Push, which has nothing to do with this. Lazy load, in this context, means the browser does not request elements that would be rendered off screen ("below the fold") until they are needed.
No, no, no, no. TFS is not the place to provide details, or context for people unfamiliar with common lingo for the subject. Literally everyone who works in web design/development knows what lazy load/lazy fetch is. Put that shit TFA and keep the summary clean. If you want to know more, click TFL (the fucking link).
Say what you want, but Martha Stewart is an amazing businesswoman. Stock investor? Not so much. But the fact that is that she is a self-made billionaire with a media empire that survived her conviction and incarceration with aplomb.
That was the intention, but it didn't have the intended result. Year-over-year soviet defense spending was actually relatively flat; increasing only 1-3% from then until '85, when Gorbechav nuked the defense budget to make room for perestroika and force military autonomy on satellite states. What we don't know is whether any intangible psychological effect influenced how glasnost and perestroika played out.