AI is excellent for decision taking. Great opportunity to replace managers not really managing anything. Statistical analysis to recognize the freeloaders. AI to replace the underachievers without any man management skills whatsoever. Back to 10 people having one boss instead of the other way around.
...You still have to buy gas.
You still have to buy replacement blades and generators...
As you wouldn't for gas turbines?
Face it, with wind power the cost of fuel is 0 and that makes up for a significant part of the running costs. Eventually, like with every development known to us, all other running costs will be optimized.
Walk out the door. Look slightly left and you'll see Moe's old fridge. It's been there since he was "evicted" by the local mobsters. Shame he fell terminally ill during the process. Throw out anything decaying and take it. Don't take Mimi's fridge. That SOB never worked and was thrown out for that reason.
Now take the computer you stole and rip out anything identifying it. Also get rid of fingerprints. Hope the owner that dies in a pool of blood never noted the serial numbers of each and every component. Fully clean the drives. You know the drill, use dd.
Punch a hole in the side of the fridge for cabling.
At our organisation I'm responsible for two large (sub)systems -1 DB with more than 6E12 records and one critical online and batch document processing system- and a handful of smaller ones. We don't run any software to track bugs.
We work in a way to avoid the chores of tracking bugs by dividing our software into smaller components with clearly defined interfaces. Typically, after a release where testing wasn't what it should have been, an overseeable period of instability starts and issues are dealt with until total stability sets in. Usually one person leads the development of a component and a second person is knowledgeable.
We reengineer stuff only to improve performance or quality. As interfaces are set that's not too big of a problem. (Even though making stuff simpler and better is actually very hard.)
Not saying this is applicable to any organisation. But in short I'd say to divide your problem and to fix all bugs until all issues are fixed. Have a lead developer and a backup for each component. Have an experienced developer (one that can actually code) dividing big problems up into smartly smaller ones.
A lazy manager's dream; Disneyfication of complex stuff and let minions graft away.
Visual programming works well until tedious stuff like exception handling and complex transaction processing kick in.
Once I observed a well spoken, nice and bright guy implementing a relatively easy web service in something called TadeXpress. Every issue that could have come up did. Performance, exception handling, inability to easily link to stuff I wrote. Eventually TadeXpress was kicked out and good old programming was reinstated.
As with anything, the devil is in the details. Visual programming still isn't done well. If it were most of us would actually be using it.
At one point company towns used to have company doctors. Now we have hospitals.
You don't seem to get that health isn't a company's core business -unless you're business is a hospital/clinic/GP, etc...
Outsourcing recurring tasks -cleaning, local production, etc...- that can employ people 100% is essentially bonkers. If buying services from a company is cheaper that means your managers mainly consume capital and don't pull their weight.
Outsourcing your strategic analysis/development means you make it easier for your competitors to have access to your IP.
The tough part of management is to set up a system whereby everyone and anyone continues performing and doesn't stagnate. Outsourcing is the easy way out.
Floor got cleaned cheaply and everyone got home early. Long live outsourcing!
Of course I didn't RTFA! With respect to outsourcing there's no difference between strategic and daily tasks like cleaning and strategic planning. Both need to be done short and long term. I can understand outsourcing occasional tasks but daily and strategic stuff will always be needed. Outsourcing of those tasks is a sign of utterly bad management.
I mean, all we/.ers want is a terminal emulator. And when we get frisky and need graphics, perhaps Eclipse and a browser. Any Linux distro has these nowadays.
I'd go through great lengths to not having anything to do with you.
The day you bought hotmail I jumped.
Do you really think I'd hand you over control to my email?
Stop sniffing glue!
When and if I become a hipster farmer, I want to chill during my tractor experience. And when I call for support I want the call center to be supportive and say to me that I'm OK. The actual problem mustn't be mentioned as it is so coarse to do so.
No, I'd only want to sit in a comfy chair. On mild days wearing sun glasses. Contemplating the world. Gently stroking my Al Qaeda beard. Feeling good about how good I feel.
And when the harvest fails I'll activate the suing experience that will take care of the tractor experience provider.
But all the way I'll smile like an idiot behind my beard. Let us do farming and it suddenly becomes cool, neat and a doddle.
...If I listen to the computer, I can't remember shit. If a passenger looks at the map and does essentially the same function, I can remember everything fine and well...
Could it be a default distrust of humans performing a repetitive and error prone task? So you listen more critically and perhaps engage in a conversation instead of simply executing tasks the navigator gives you.
Perhaps a bad navigator is exactly what we need. One that gets it right roughly but where map knowledge produces a better result.
My navigator is actually not that good. It's 6 years old, hasn't all the newest addresses and roads, and therefore sometime takes a bad route. Not only do I overrule it often but I feel good (smug?) for doing so.
Then again, I'm fascinated by maps. Like reading them. Knowing roads very few people take. Understanding that geography has mostly causal dependency on geology.
Slashdot Mirror
/. liking this? It hosts the crappiest I have ever seen.
induce terrorism.
I mean, american football players aren't necessarily rocket scientists or eloquent poets.
Now, what are we gonna do with it.
Here here, an allusion to rule 34.
Too many negative connotations with MS. Nice guys until they're on the winning hand. And then they turn into big, cocky scoundrels.
AI is excellent for decision taking. Great opportunity to replace managers not really managing anything. Statistical analysis to recognize the freeloaders. AI to replace the underachievers without any man management skills whatsoever. Back to 10 people having one boss instead of the other way around.
As you wouldn't for gas turbines?
Face it, with wind power the cost of fuel is 0 and that makes up for a significant part of the running costs. Eventually, like with every development known to us, all other running costs will be optimized.
I switched from gmail to outlook.com, partly to live a Google-free life...
Out of the frying pan into the fire.
Walk out the door. Look slightly left and you'll see Moe's old fridge. It's been there since he was "evicted" by the local mobsters. Shame he fell terminally ill during the process. Throw out anything decaying and take it. Don't take Mimi's fridge. That SOB never worked and was thrown out for that reason.
Now take the computer you stole and rip out anything identifying it. Also get rid of fingerprints. Hope the owner that dies in a pool of blood never noted the serial numbers of each and every component. Fully clean the drives. You know the drill, use dd.
Punch a hole in the side of the fridge for cabling.
Put the computer inside the fridge.
Fire up fridge.
Close door.
Boot computer.
Close door again.
Observe.
Post findings.
Have lasagne your granny made.
Feel good about life.
Think about Moe with fake sentiment.
At our organisation I'm responsible for two large (sub)systems -1 DB with more than 6E12 records and one critical online and batch document processing system- and a handful of smaller ones. We don't run any software to track bugs.
We work in a way to avoid the chores of tracking bugs by dividing our software into smaller components with clearly defined interfaces. Typically, after a release where testing wasn't what it should have been, an overseeable period of instability starts and issues are dealt with until total stability sets in. Usually one person leads the development of a component and a second person is knowledgeable.
We reengineer stuff only to improve performance or quality. As interfaces are set that's not too big of a problem. (Even though making stuff simpler and better is actually very hard.)
Not saying this is applicable to any organisation. But in short I'd say to divide your problem and to fix all bugs until all issues are fixed. Have a lead developer and a backup for each component. Have an experienced developer (one that can actually code) dividing big problems up into smartly smaller ones.
A lazy manager's dream; Disneyfication of complex stuff and let minions graft away.
Visual programming works well until tedious stuff like exception handling and complex transaction processing kick in.
Once I observed a well spoken, nice and bright guy implementing a relatively easy web service in something called TadeXpress. Every issue that could have come up did. Performance, exception handling, inability to easily link to stuff I wrote. Eventually TadeXpress was kicked out and good old programming was reinstated.
As with anything, the devil is in the details. Visual programming still isn't done well. If it were most of us would actually be using it.
If only Chromebooks came with a shell of some kind and a way to run Eclipse, I'd buy one as a throw away item.
At one point company towns used to have company doctors. Now we have hospitals.
You don't seem to get that health isn't a company's core business -unless you're business is a hospital/clinic/GP, etc...
Outsourcing recurring tasks -cleaning, local production, etc...- that can employ people 100% is essentially bonkers. If buying services from a company is cheaper that means your managers mainly consume capital and don't pull their weight.
Outsourcing your strategic analysis/development means you make it easier for your competitors to have access to your IP.
The tough part of management is to set up a system whereby everyone and anyone continues performing and doesn't stagnate. Outsourcing is the easy way out.
Floor got cleaned cheaply and everyone got home early. Long live outsourcing!
Of course I didn't RTFA! With respect to outsourcing there's no difference between strategic and daily tasks like cleaning and strategic planning. Both need to be done short and long term. I can understand outsourcing occasional tasks but daily and strategic stuff will always be needed. Outsourcing of those tasks is a sign of utterly bad management.
Does that mean men can give birth too any time soon?
Not saying I wish to bear children. But it'd stifle a few abject misandry opinions.
I mean, all we /.ers want is a terminal emulator. And when we get frisky and need graphics, perhaps Eclipse and a browser. Any Linux distro has these nowadays.
Would Chinese Wikipedia then be losing 1/6 of its user base? Analogous to the Turkish version.
pigeon
I blame version control. GIT!
Anything worth doing is worth overdoing. A hail to code optimization!
Initially, the optimized function bool::willIBefired() will always return true.
After optimization the result actually must be one of true or false.
Lesson learned: Don't let context influence optimization.
Surely you want to hear my life story. What else on a drab Sunday like this. (The sun actually shines brightly.)
I Built an Elektor TV Games Computer. Programmed 2650 assembly but I was too young and actually sucked at it.
Then came Basic but I didn't see/have an actual purpose.
My first job I got for knowing Prolog and Pascal.
First significant projects were actually in C.
Then Java. Huge amounts!
C-like syntax rocks!
Dear MS,
I'd go through great lengths to not having anything to do with you.
The day you bought hotmail I jumped.
Do you really think I'd hand you over control to my email?
Stop sniffing glue!
Sincerely
When and if I become a hipster farmer, I want to chill during my tractor experience. And when I call for support I want the call center to be supportive and say to me that I'm OK. The actual problem mustn't be mentioned as it is so coarse to do so.
No, I'd only want to sit in a comfy chair. On mild days wearing sun glasses. Contemplating the world. Gently stroking my Al Qaeda beard. Feeling good about how good I feel.
And when the harvest fails I'll activate the suing experience that will take care of the tractor experience provider.
But all the way I'll smile like an idiot behind my beard. Let us do farming and it suddenly becomes cool, neat and a doddle.
The FSF should open farming offices in California, Iowa and Texas. (Top 3 agricultural producing States)
Never thought Merritt and Wyatt would push the FSF envelope.
Could it be a default distrust of humans performing a repetitive and error prone task? So you listen more critically and perhaps engage in a conversation instead of simply executing tasks the navigator gives you.
Perhaps a bad navigator is exactly what we need. One that gets it right roughly but where map knowledge produces a better result.
My navigator is actually not that good. It's 6 years old, hasn't all the newest addresses and roads, and therefore sometime takes a bad route. Not only do I overrule it often but I feel good (smug?) for doing so.
Then again, I'm fascinated by maps. Like reading them. Knowing roads very few people take. Understanding that geography has mostly causal dependency on geology.