|
Dan Neely wrote: The article does say the new IT plan is due by the end of the year,
Yeah. A plan.
|
|
|
|
|
Keep it working?!?!
How did they get it working!?!?
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
|
here:
I just heard about this yesterday. Just curious, is it possible to write an Android app to manage/block these kinds of messages?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Kevin Marois wrote: is it possible to write an Android app to manage/block these kinds of messages?
Yes - I just left you a voice mail with instructions...
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
You might take a gander at BroadcastReceiver , and the TelephonyManager constants. I just took a cursory glance and noticed several that dealt with voice mails, but I did not verify anything.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
If people would be half as smart at doing life improvement things than inventing new nuisances, this planet would be a better place to live.
|
|
|
|
|
Rage wrote: If people would be half as smart at doing life improvement things than inventing new nuisances, this planet would be a better place to live. You don't need "smart" people, you need "willing" people.
As I said in other conversation, the problem is "benefits", very few people gives a crap about things where no $$$$ involved.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Rage wrote: inventing new nuisances Feed the inventors to the various endangered species, and allow natural selection to take its course.
Software Zen: delete this;
|
|
|
|
|
If Kleptomania is a disease, can you take something for it?
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Where do you steal these from?
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
|
if an item is buy-one-get-one-free are they compelled to take an even number of them?
This internet thing is amazing! Letting people use it: worst idea ever!
|
|
|
|
|
Hard to say, since kleptomaniacs tend to take things literally.
/ravi
|
|
|
|
|
I hoard you are you steal posting these things?
If you "take it for what it's worth" are you an upscale kleptomaniac?
"Taking it with a grain of salt" is not for the hypertensive kleptomaniac.
And now, I'll take leave of this thread.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I'm sure there's a Pilfer it!
Everyone has a photographic memory; some just don't have film. Steven Wright
|
|
|
|
|
I can't see your point. And I cannot see my watch, anymore.
|
|
|
|
|
|
I stumbled upon this book (
Scenario-Focused Engineering: A toolbox for innovation and customer-centricity (Developer Best Practices) Microsoft Press[^] )
It puts forth a very interesting idea about how handle the SDLC. It's not really Agile, but it is iterative.
The really interesting thing is a very nice list of Keys To Successful Software Dev:
*** strong vision
*** deep sense of empathy for users
*** iterative approach
*** healthy productive relationship between engineering and the UX design team.
I think that is a very good, succinct list because if you think about it and consider what happens if any of them are missing from a project then you know the project is in danger of flopping.
Everyone Works Together All the Time
Basically what all these methodologies come down to is : Everyone works together, all the time.
But not a lot of people want to do that. And it doesn't happen a lot.
There is a lot of separation on software dev projects. People get complacent in their cubicles and just code along. Product Owner (manager or whatever) doesn't provide enough vision. Iteration doesn't really occur because you can't keep bothering the users and users don't want to be bothered. UX team sees things their way and doesn't want to have to change things now that they are solidified.
If You Were Developing a Product With Chance of Making $1,000,000
Contrast that to a project where you stand the chance to make a $1 million.
You'd probably be like, "ok everyone get in the room and start cranking this thing out."
Discussions would happen. Iteration would occur. People would become opinionated and vision would occur. Where there wasn't any vision it would be driven towards and forced. UX and devs would iterate. Devs would develop in chunks and others would be provide feedback quickly.
People would be more pro-active in getting (forcing) users to respond to iterations of the product. And devs would want users to like the product so they'd buy it (so devs could get their $1 million).
Maybe we should call this the :
Monetary Motivation Methodology
|
|
|
|
|
raddevus wrote: Monetary Motivation Methodology Or simply call it "working together to achieve a common goal"
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
How's your Unicorn Ride over the rainbow with the butterflies, going? Pretty well, then.
|
|
|
|
|
Here's a nice one; we evolved to identify cheaters in such social constructs, because they drag the group down
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: Here's a nice one; we evolved to identify cheaters in such social constructs,
No, no. We've promoted them to positions in management.
(And here, I'm speaking of large(r) companies. Small(er) companies don't have this problem as much because essential functions are generally done by essential people. While larger companies tend to have more space for such individuals to hide. I remember one guy -- at a very large company I worked for -- who you could literally hear snoring in his cubicle each day.)
|
|
|
|
|
Usually that is only attributed to government employees; people who work for large capitalist companies are all hard-working honest people
raddevus wrote: I remember one guy -- at a very large company I worked for -- who you could literally hear snoring in his cubicle each day Shows that some bosses should have more supervision
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: Usually that is only attributed to government employees; people who work for large capitalist companies are all hard-working honest people
No one wants to admit it but the one and best principle that describes all humans (not just public or private workers)is: lazy.
Suppose you and another fellow are paid $100 to dig a hole.
One of you will dig the hole and the other will insure that the hole is dug.
You get to choose which job you will do.
You do not need to tell me that the other fellow is the one who will be digging the hole. I already know.
|
|
|
|
|
When exploited to productive ends, I think laziness can be a virtue. I try to be efficient, because I'm too lazy to be anything else.
So, let's torture your metaphor a little. If I only had one hole to dig, I'd just dig it. Given a sufficient number of holes, I'd choose option C: find or invent something to dig the holes for me.
I seldom find supervising to be any less work than simply doing it myself
|
|
|
|
|
Eric Lynch wrote: When exploited to productive ends, I think laziness can be a virtue.
I agree, as we all know the best programmers are the lazy ones.
Eric Lynch wrote: If I only had one hole to dig, I'd just dig it. Given a sufficient number of holes, I'd choose option C: find or invent something to dig the holes for me.
Yes, you will be digging holes the rest of your life.
Purchasing something to do it is not possible on your ditch digger salary.
And, inventing and/or building something to do it is a waste of time.
You have The Fellow at your service. He's already been invented and built.
All you have to do is apply the proper motivation. Now all you need is a stick or a carrot.
Again, on your ditch digger salary you probably cannot afford carrots so most likely you'll do a one-time purchase of a nice stick.
|
|
|
|