You don't like our record on the environment? Because you have to deal with the inevitable concentration of pollution that results from your population densities?
Fine. Whey don't you grow your own food, mine your own minerals (and process them), and generate your own energy within your city limits. Cities can just STFU as long as they consume all the goodies that everyone else produces. You want carbon neutral food (for example)? We'll stop delivering it. You can just get your butts out to the farm and do your shopping there.
That's the essence of all economics. If you trace the components back to their source, its a few cents worth of sand, aluminum oxide and other ores and petroleum. Everything else is labor, licensing fees and debt service.
And taxes. So one could accurately say that an iPhone X costs $1000. Paid to Apple Jersey. Net profit for Apple USA: $0.
Why does the state tell cities they can't do something
Because 'the state' actually consists of a bunch of legislators. Who can be bought really cheap. I guess Comcast could buy the voters. With something like decent broadband service. But that would be too expensive.
And we'll call it WiMax. And we'll sell it under a name, like Clearwire. And since it isn't encumbered by that nasty last mile problem, like it's FTTH competition offering 1G speeds, it will be great.
Better to pay $0.05 for a needle that $5000 for an infection...
Different pockets. Obamacare picks up the cost of the infection. And I doubt the needle exchanges and safe injection sites only cost us 5 cents a hit. What with all the (publicly funded) outreach and counseling made available to each addict that walks in the door, it's probably more like a few hundred dollars per needle.
It may not be up to the employer alone. Current tax policies strongly discourage the use of individuals as subcontractors. You have to be an employee of someone. And by that logic, you have to be 'supervised'. Your customer might not like doing this as much as you dislike it. But if you (as the customer) leave a loophole allowing them to claim status as an independent business (and gain access to the associated tax benefits), the IRS (and local taxing authorities) will jump down your throat.
You pay a 1099 for a product not "productive time."
That depends on the nature of the contract. Are you paying for a deliverable? Or per hour? Current government policies strongly discourage individuals providing services as subcontractors. So any mention of hours and that person falls into the employee category, due a benefits package, the right to collective bargaining, etc.
developed by screen-scraping/recording user actions and not by programming.
That results in very poor test coverage. Unless you begin to approach the infinite number of monkeys playing with an infinite number of keyboards. And it does nothing at the module/unit test level. There, you need to write test stubs.
warmer temperatures and a stormier upper atmosphere helped keep damaging chemicals chlorine and bromine from eating ozone from the layer that protects the Earth's surface from harmful ultraviolet rays
Developers tend to need time to ponder a problem and then rapid-fire out lines of code until they have a working solution. A very binge-and-purge style of work.
Not really. That's the sign of a coder that's in over their head. Take a problem, break it down into smaller components until each one is easily understood and solvable. The idea that software development is some sort of art that can only be done by some flash of insight often leads to garbage being cranked out on the eve of a deadline.
The developer is never going to be rewarded for finding bugs in their own code.
Developers shouldn't be examining or testing their own code. Dev A writes module X. Dev B tests X. The, dev B writes module Y, which is tested by dev A. Etc, etc.
their objective is to finish the feature and move onto the next issue
Your feature isn't finished until it is bug free. If devs don't get credit for completion until the QA is signed off, they will make a better effort to get it right the first time.
Having developers do some QA will teach them what pitfalls to watch for. And make them better devs as time goes by. The argument that development and QA have different mindsets is both wrong and harmful. Devs need to code with eliminating bugs as a priority. Not just hope that QA will catch them before product release.
This is how it is typically done in engineering. A designer will hand their work over to another engineer to be checked. And the roles are swapped, so everyone gets to do both tasks. The person who finds the errors learns not to make them in their own work.
Slashdot Mirror
who is this "for chan"?
Some sort of Mongolian throat singing fan site.
n/t
You don't like our record on the environment? Because you have to deal with the inevitable concentration of pollution that results from your population densities?
Fine. Whey don't you grow your own food, mine your own minerals (and process them), and generate your own energy within your city limits. Cities can just STFU as long as they consume all the goodies that everyone else produces. You want carbon neutral food (for example)? We'll stop delivering it. You can just get your butts out to the farm and do your shopping there.
That's the essence of all economics. If you trace the components back to their source, its a few cents worth of sand, aluminum oxide and other ores and petroleum. Everything else is labor, licensing fees and debt service.
And taxes. So one could accurately say that an iPhone X costs $1000. Paid to Apple Jersey. Net profit for Apple USA: $0.
Why does the state tell cities they can't do something
Because 'the state' actually consists of a bunch of legislators. Who can be bought really cheap. I guess Comcast could buy the voters. With something like decent broadband service. But that would be too expensive.
And we'll call it WiMax. And we'll sell it under a name, like Clearwire. And since it isn't encumbered by that nasty last mile problem, like it's FTTH competition offering 1G speeds, it will be great.
Fooled me once.
Better to pay $0.05 for a needle that $5000 for an infection...
Different pockets. Obamacare picks up the cost of the infection. And I doubt the needle exchanges and safe injection sites only cost us 5 cents a hit. What with all the (publicly funded) outreach and counseling made available to each addict that walks in the door, it's probably more like a few hundred dollars per needle.
How many pounds of this do you have to apply per acre? It smells just like the stuff we've always used.
It may not be up to the employer alone. Current tax policies strongly discourage the use of individuals as subcontractors. You have to be an employee of someone. And by that logic, you have to be 'supervised'. Your customer might not like doing this as much as you dislike it. But if you (as the customer) leave a loophole allowing them to claim status as an independent business (and gain access to the associated tax benefits), the IRS (and local taxing authorities) will jump down your throat.
You pay a 1099 for a product not "productive time."
That depends on the nature of the contract. Are you paying for a deliverable? Or per hour? Current government policies strongly discourage individuals providing services as subcontractors. So any mention of hours and that person falls into the employee category, due a benefits package, the right to collective bargaining, etc.
Oblig. xkcd.
Next time your car runs into a pothole on the street
That's why I drive a big SUV.
I paid my taxes. And they went to buy needles for some addicts.
They could use "Bored of the Rings".
"So, how do you like this weather?"
It also makes no sense that the Air Force is in the weather satellite business at all.
Why not? They've got to fly through it.
The Navy has to navigate through it and the Army has to march through it. But the Air Force is generally in charge of Things That Fly.
Weather is important tactically.
developed by screen-scraping/recording user actions and not by programming.
That results in very poor test coverage. Unless you begin to approach the infinite number of monkeys playing with an infinite number of keyboards. And it does nothing at the module/unit test level. There, you need to write test stubs.
warmer temperatures and a stormier upper atmosphere helped keep damaging chemicals chlorine and bromine from eating ozone from the layer that protects the Earth's surface from harmful ultraviolet rays
They probably used Excel.
Developers tend to need time to ponder a problem and then rapid-fire out lines of code until they have a working solution. A very binge-and-purge style of work.
Not really. That's the sign of a coder that's in over their head. Take a problem, break it down into smaller components until each one is easily understood and solvable. The idea that software development is some sort of art that can only be done by some flash of insight often leads to garbage being cranked out on the eve of a deadline.
The developer is never going to be rewarded for finding bugs in their own code.
Developers shouldn't be examining or testing their own code. Dev A writes module X. Dev B tests X. The, dev B writes module Y, which is tested by dev A. Etc, etc.
their objective is to finish the feature and move onto the next issue
Your feature isn't finished until it is bug free. If devs don't get credit for completion until the QA is signed off, they will make a better effort to get it right the first time.
This.
Having developers do some QA will teach them what pitfalls to watch for. And make them better devs as time goes by. The argument that development and QA have different mindsets is both wrong and harmful. Devs need to code with eliminating bugs as a priority. Not just hope that QA will catch them before product release.
This is how it is typically done in engineering. A designer will hand their work over to another engineer to be checked. And the roles are swapped, so everyone gets to do both tasks. The person who finds the errors learns not to make them in their own work.
And my best QA people couldn't have coded their way out of a paper bag.
Then who wrote your QA test scripts?