This is great and all, but the only way it works is some sort of basic income scheme. Which means we need to come to the grips with the fact that there will be some people who to fuck-all and mooch off of the productive people. They'll never be rich, possibly not even comfortable, but we'll have to make it liveable.
No it doesn't. It costs him 18 cents in supplies. But I guarantee you it'd be cheaper for him to pay an intern $2 for the time it takes to brew the coffee, and get it to his desk. For him to spend the time doing it, is burning up his time at a much pricier rate.
Yeah, I had five at one point. Totally forgot about it because it was worth squat. But who are we kidding, I totally would have sold when it hit $10 each anyway for a free $50. This way I at least get to dream of that $50,000 I could've had.
That just makes you an asshole programmer regardless of what the principle is called. You don't need a "principle" to tell me not to use misleading function names. You don't need a principle to tell you not to invoke undefined behavior. Yes, it's all possible to do, but if your programmers are doing this crap, then a book on design principles is unlikely to be helpful.
Is the right pro, or against globalization? I thought free trade capitalism was an economic right-wing staple. It was only the looney leftist occupy-wall-street nutters that were against free trade.
Disaster may hit the planet, but we've had hundreds of millions of years of multicellular life, and humans are likely the most adaptable variety yet. I don't think there's any reason to suppose humans will be completely wiped out by any global-scale disaster that doesn't wipe out essentially all land-based life. We haven't had one of those kind of disasters yet, so I don't see it happening any time in the next 1000 years.
Yes, there will likely be a disaster of global proportions, and I sure don't want to be around for it. I seriously doubt, though, that it could be an extinction level event for humanity.
Had mine at 25 - walked in, dropped the pants, lay down for about 10 minutes of Seinfeld. Took two Advil and got a ride home. Went to work the next day with no lasting pain or issues. Definitely no regrets.
I did go to a doctor who does only vasectomies though - dozens a days, so he's likely quite proficient at it compared to some.
Sparsely populated in Texas is a completely different thing from sparsely populated in Northern Canada. Loving county Texas has some 80 people in 1700 sq km. There's scarcely a spot in Texas more than 5 miles from a road.
Ellesmere island has around 150 people over 196,235sq km. Giant swaths of the north have absolutely no one living there at all. I haven't checked, but it wouldn't surprise me if you could draw out an area the size of texas with no one living there at all.
Winter roads are only drivable in winter. In summer they're just lakes and muskeg. I've lived in several communities that are fly-in (or boat-in) only all spring summer and fall, with just a few months of road access when everything freezes over. When it comes to arctic conditions on real roads, I'd certainly rather drive in -40 than just below freezing - snow is much grippier in the real cold than it is at warmer temperatures.
You'll still need someone to define the solution set - what a correctly looking program behaves like. In photo recognition, the problem is fairly well defined already and the hard part is writing the output. For most programs though, the hard part is deciding what the problem really is? Which data do we need to capture? Who can access it? Which aggregates/reports do we care about?
By the time you've answered all the relevant specification questions, you've basically solved the problem already without an expert system needed to get you the rest of the way. I guess you could argue, that that's what a compiler already is.
Never did more than make some pretty drawings. Of course I was in grade 2 at the time. I don't think any attempts to get me to understand the abstract concepts of programming would have gone anywhere.
This is why we need to completely drop the minimum wage and bring in a basic income. If something can be done by a robot, then there's no reason a human should be doing it. Productivity will keep going up with fewer and fewer workers needed, but we're still going to have people who need to live and consume.
This isn't data like health or tax records - those they're keeping. It's things like fisheries data from the 1950s - what was caught where and when, which birds were living in northern Saskatchewan in 1985, etc... It's largely mundane data, but when researchers need to look for trends in trying to manage fishing quotas, being able to get that old data is invaluable.
Re:The problem is that landfills are too cheap
on
Recycling Is Dying
·
· Score: 1
That seems like a surprisingly reasonable way to do things. It would be great if more communities would follow that example.
Re:The problem is that landfills are too cheap
on
Recycling Is Dying
·
· Score: 1
This is the critical short-fall in over-emphasizing the individual right. It's not merely short-sightedness. Each individual can be perfectly rational in not doing the extra work to sort recycling, as there is almost no benefit to them to do so, and essentially no harm if they don't - in fact if recycling is charged for, then there is a loss for them to recycle. From that point of view, one would be foolish to recycle.
However, on a large scale, it's a benefit to each individual if everyone recycles, so it's again rational to vote for measures that force everyone to pay for recycling through taxes, and to fine people for not sorting recycling.
Why not write your game server in C/C++ with garbage collection, nice arrays, debugging, nice strings and an ide? Leaving those out seems like you're intentionally making things difficult on yourself.
Corn isn't pollinated by bees, its flowers aren't meant to attract them.
This is great and all, but the only way it works is some sort of basic income scheme. Which means we need to come to the grips with the fact that there will be some people who to fuck-all and mooch off of the productive people. They'll never be rich, possibly not even comfortable, but we'll have to make it liveable.
No it doesn't. It costs him 18 cents in supplies. But I guarantee you it'd be cheaper for him to pay an intern $2 for the time it takes to brew the coffee, and get it to his desk. For him to spend the time doing it, is burning up his time at a much pricier rate.
Yeah, I had five at one point. Totally forgot about it because it was worth squat. But who are we kidding, I totally would have sold when it hit $10 each anyway for a free $50. This way I at least get to dream of that $50,000 I could've had.
That just makes you an asshole programmer regardless of what the principle is called. You don't need a "principle" to tell me not to use misleading function names. You don't need a principle to tell you not to invoke undefined behavior. Yes, it's all possible to do, but if your programmers are doing this crap, then a book on design principles is unlikely to be helpful.
How is this any different than starting your own subreddit?
Is the right pro, or against globalization? I thought free trade capitalism was an economic right-wing staple. It was only the looney leftist occupy-wall-street nutters that were against free trade.
What's the real need to ensure that those who live get to live well? If we're all dead who the fuck cares what happened along the way.
Disaster may hit the planet, but we've had hundreds of millions of years of multicellular life, and humans are likely the most adaptable variety yet. I don't think there's any reason to suppose humans will be completely wiped out by any global-scale disaster that doesn't wipe out essentially all land-based life. We haven't had one of those kind of disasters yet, so I don't see it happening any time in the next 1000 years.
Yes, there will likely be a disaster of global proportions, and I sure don't want to be around for it. I seriously doubt, though, that it could be an extinction level event for humanity.
Just make sure it's with a good doctor, and a clean clinic. You don't want to get an infection in that area.
Definitely don't ignore this - the better your doctor, the easier your recovery will be.
Had mine at 25 - walked in, dropped the pants, lay down for about 10 minutes of Seinfeld. Took two Advil and got a ride home. Went to work the next day with no lasting pain or issues. Definitely no regrets.
I did go to a doctor who does only vasectomies though - dozens a days, so he's likely quite proficient at it compared to some.
Ellesmere island has around 150 people over 196,235sq km. Giant swaths of the north have absolutely no one living there at all. I haven't checked, but it wouldn't surprise me if you could draw out an area the size of texas with no one living there at all.
Winter roads are only drivable in winter. In summer they're just lakes and muskeg. I've lived in several communities that are fly-in (or boat-in) only all spring summer and fall, with just a few months of road access when everything freezes over. When it comes to arctic conditions on real roads, I'd certainly rather drive in -40 than just below freezing - snow is much grippier in the real cold than it is at warmer temperatures.
You'll still need someone to define the solution set - what a correctly looking program behaves like. In photo recognition, the problem is fairly well defined already and the hard part is writing the output. For most programs though, the hard part is deciding what the problem really is? Which data do we need to capture? Who can access it? Which aggregates/reports do we care about? By the time you've answered all the relevant specification questions, you've basically solved the problem already without an expert system needed to get you the rest of the way. I guess you could argue, that that's what a compiler already is.
Never did more than make some pretty drawings. Of course I was in grade 2 at the time. I don't think any attempts to get me to understand the abstract concepts of programming would have gone anywhere.
This is why we need to completely drop the minimum wage and bring in a basic income. If something can be done by a robot, then there's no reason a human should be doing it. Productivity will keep going up with fewer and fewer workers needed, but we're still going to have people who need to live and consume.
then selfies gone wrong kill more people than swimming in the ocean gone wrong
Except that they don't - because then you have to add in drownings, jellyfish attacks, lightning strikes, etc...
So taking a picture while hugging a lion or jaguar is still ok? What about Ligers? This seems like way too specific of a law.
This isn't data like health or tax records - those they're keeping. It's things like fisheries data from the 1950s - what was caught where and when, which birds were living in northern Saskatchewan in 1985, etc... It's largely mundane data, but when researchers need to look for trends in trying to manage fishing quotas, being able to get that old data is invaluable.
That seems like a surprisingly reasonable way to do things. It would be great if more communities would follow that example.
This is the critical short-fall in over-emphasizing the individual right. It's not merely short-sightedness. Each individual can be perfectly rational in not doing the extra work to sort recycling, as there is almost no benefit to them to do so, and essentially no harm if they don't - in fact if recycling is charged for, then there is a loss for them to recycle. From that point of view, one would be foolish to recycle.
However, on a large scale, it's a benefit to each individual if everyone recycles, so it's again rational to vote for measures that force everyone to pay for recycling through taxes, and to fine people for not sorting recycling.
Maybe not, but this 5-lb Y2K Milka bar was everything I could have hoped It would be.
void func() {
if (!AquireResource1()) goto end;
if (!AquireResource2()) goto cleanup1;
if (!AquireResource3()) goto cleanup2:
DoStuffWithResources();
Cleanup3();
cleanup2:
Cleanup2();
cleanup1:
Cleanup1();
end:
return;
}
Why not write your game server in C/C++ with garbage collection, nice arrays, debugging, nice strings and an ide? Leaving those out seems like you're intentionally making things difficult on yourself.
I'd also back the W-series. They're beasts - though the loss of the 17" model was sad.