If you know that, it's 'premature' to optimize it. Unless of course the 'one time run' will take weeks, better test it against real world datasets. I've seen DBAs lock up systems with update scripts that would have run for _years_ (for apparently simple schema updates).
Not all early optimization is premature. Redefining 'premature' as you just did, doesn't change the basic truth.
A good team can produce results with any POS methodology, even SCRUM. Typically despite the formal methods, not because of them.
Stats can prevent circular blame pointing? Not in my experience with the 'barely competent'.
When network operations go from acceptable to too slow, it's been my experience that people who don't know what they are doing have been fucking with them. e.g. Six outer joins to the same table. queries that were building temp tables but nobody noticed etc. Sure sometimes the data volume has grown or you've gained a bug from a update of the underlying OS or libraries. But 90% of the time is was someone who thought something was simple, but were wrong.
My method works when you are dropped into a project you've never touched before to firefight. Lack of symbol tables (middleware team) quickly reveals the real problem, if it's with project organization. Even in that example, you add to the middleware unit tests and are on track to a solution as quickly as possible given the constraints.
libs that add breakpoints to examine how long processes are taking
You'd think someone who's been here as long as you would have heard of profilers.
Your first tool should be performance monitor. In my experience most slow tasks will show 0% CPU utilization for a large part of the wait. Because some coder has never heard of firing queries asynch, then doing local work while waiting.
So everybody on this forum who was actually educated about maps being distorted and globes being very common in school is wrong?
The fact that flat maps are distorted was and is common instruction, EVERYBODY does it, using a globe as the primary instruction tool. It's a way of crossing between history/geography/math, which teachers love.
Many of our globes were from earlier periods and included old political boundaries, also educational. I know globes were common for all of living memory. I've seen 100 years of old globes lined up in a middle school library.
Teaching the fact that all flat maps are distorted is good. Just replacing one map with another and not referencing the globe is just agenda driven PC stupidity.
The right way to do it to reference various distortions, especially nautical charts which distort land areas to accurately show oceans. When I was a kid, to start they had pull down maps with various distortions, N. polar projection, S. polar projection, Mercator etc etc. And a fucking globe.
I recall an Africa centric map in a textbook that was used as a concrete illustration, along with a nautical chart that showed the gulf of Mexico relatively undistorted.
All flat maps will be distorted. The PC dweebs don't teach that 'maps are distorted' they replace the maps with new ones distorted to overemphasise other parts.
This is a non-issue raised by an idiot who is very bad at geography.
Slashdot Mirror
I pay $70/month for 100 Mb/sec from Comcast.
If you know that, it's 'premature' to optimize it. Unless of course the 'one time run' will take weeks, better test it against real world datasets. I've seen DBAs lock up systems with update scripts that would have run for _years_ (for apparently simple schema updates).
Not all early optimization is premature. Redefining 'premature' as you just did, doesn't change the basic truth.
It's a stretch to claim you only ship code with no known bugs. To claim you ship bug free code is just silly.
Non 'show stoppers' are documented and worked around, every day.
A good team can produce results with any POS methodology, even SCRUM. Typically despite the formal methods, not because of them.
Stats can prevent circular blame pointing? Not in my experience with the 'barely competent'.
When network operations go from acceptable to too slow, it's been my experience that people who don't know what they are doing have been fucking with them. e.g. Six outer joins to the same table. queries that were building temp tables but nobody noticed etc. Sure sometimes the data volume has grown or you've gained a bug from a update of the underlying OS or libraries. But 90% of the time is was someone who thought something was simple, but were wrong.
My method works when you are dropped into a project you've never touched before to firefight. Lack of symbol tables (middleware team) quickly reveals the real problem, if it's with project organization. Even in that example, you add to the middleware unit tests and are on track to a solution as quickly as possible given the constraints.
You see a client sitting at 0% utilization, you click 'break all' in the debugger. You're looking at the offending block. It's real useful.
Then you start into the logs to see how it got there, if it's not obvious.
It's a particularly useful method when faced with unfamiliar code that is sucking big wet donkey balls.
Two types of performance. If you don't get 'time to market' nobody will ever see the delay to complain about it.
Which isn't an excuse for just plain bad programming. Which is a constellation of potential mistakes.
How long has it been since you've seen a /. discussion without a 'trump sucks' crappost?
Just learn to tune-out the screaming babies.
You only ship bug free code? Someone is lying, to yourself perhaps.
You are arguing against the misquote: 'Early optimization is the root of all evil'.
Not the accurate quote: "Premature optimization is the root of all evil'.
If you know a block of code is low, tight and potentially slow, it is not premature to write it with efficiency in mind from day one.
You can optimize for dev time or CPU time. Which is cheaper?
The inexcusable is optimizing for neither. e.g. server side javascript.
You'd think someone who's been here as long as you would have heard of profilers.
Your first tool should be performance monitor. In my experience most slow tasks will show 0% CPU utilization for a large part of the wait. Because some coder has never heard of firing queries asynch, then doing local work while waiting.
Too expensive. Muslims will kill each other if given half a chance and a hand sized rock each.
This is a very bad sign for Uber, its employees and contractors.
What has this done to the price of out of the money, medium term, puts on Uber? They can't have been cheap, even before this.
Excellent. Keep it up.
Washington post and NYTimes are staffed by Clinton press operatives. Have you been paying attention?
Link is broken and an obvious lie anyhow.
So everybody on this forum who was actually educated about maps being distorted and globes being very common in school is wrong?
The fact that flat maps are distorted was and is common instruction, EVERYBODY does it, using a globe as the primary instruction tool. It's a way of crossing between history/geography/math, which teachers love.
Many of our globes were from earlier periods and included old political boundaries, also educational. I know globes were common for all of living memory. I've seen 100 years of old globes lined up in a middle school library.
You can get globe beach balls for a buck or two.
It's already been a shit show.
If you let dogs shit in the house without consequences, expect a super shitty house.
How should I react to an obvious lie?
True believers gonna believe. Especially in these times, they need their security blanket. But they are just like Fox now and there is no changing it.
Does fox's ratings prove it's objective? There goes your argument.
The evidence is: One of the recordings ended up in a Clinton operatives hands. It didn't just magic itself there.
Fair enough, your story is: You never saw a globe in school. I'm still calling bullshit, they aren't expensive.
The rest of /. also went to middle school and high school and can make their own judgements on your honesty regarding globes and geography curriculum.
Teaching the fact that all flat maps are distorted is good. Just replacing one map with another and not referencing the globe is just agenda driven PC stupidity.
The right way to do it to reference various distortions, especially nautical charts which distort land areas to accurately show oceans. When I was a kid, to start they had pull down maps with various distortions, N. polar projection, S. polar projection, Mercator etc etc. And a fucking globe.
I recall an Africa centric map in a textbook that was used as a concrete illustration, along with a nautical chart that showed the gulf of Mexico relatively undistorted.
All flat maps will be distorted. The PC dweebs don't teach that 'maps are distorted' they replace the maps with new ones distorted to overemphasise other parts.
This is a non-issue raised by an idiot who is very bad at geography.
Like I said, the dim bulbs didn't 'get it'. You were likely playing grabass while they tried to teach it.
If you had paid attention you would know _all_ maps are distorted. The PC dweebs just prefer one distorted in a different way.
I don't believe your class didn't have globes.