|
New data from Twilio confirms that people have come to expect hyper-personalization during every single brand interaction. But there’s a catch, as the majority of consumers don’t trust brands to keep their personal data secure. 40% of users are deluding themselves?
|
|
|
|
|
In other news, researchers identify who responds to Nigerian emails and extended warranty calls.
|
|
|
|
|
That must be the 40% who haven't had to report fraudulent financial activity on their credit reports.
|
|
|
|
|
Based on a survey by Wakefield Research of 250 US software developers and architects, at a senior level within enterprises of 5,000 or more staff, it looks at the differences in goals, challenges and reasons for failure between business leaders and architects. "No plan survives contact with the enemy."
Or management decisions
|
|
|
|
|
One of my old Systems Engineering university textbooks provided an extensive list of reasons why projects fail. Every second point was "Poor planning".
Then we got "Agile".
|
|
|
|
|
"plans are useless, but planning is indispensable." - Dwight D. Eisenhower
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
Quote: [S]oftware architects...cite a 'lack of intelligent tools' as the number one reason for failure....'[T]oo complex,' 'inadequate skills or training' and 'failure to accurately set expectations' all tied for the second most common reason.
Then build the tools, you whiners! The article talks about redevelopment more than development, and if management has agreed to that, it shouldn't be hard to convince them of the need to build tools that will increase productivity.
The biggest reason for failure that I saw, multiple times, was trying to build a system that would replace a large one that had been around for a decade or more. This is virtually guaranteed to flush a ton of money down the toilet, because large systems grow out of successful small ones. The odds of success are low, even with skilled management and architects. And the fact they say they can do it means they have strong egos, and hubris is waiting.
|
|
|
|
|
Actually, the main problem with creating a new monolithic system to replace an existing monolithic system is that management doesn't understand the reason that it's being rewritten, which is to make it more maintainable and extensible. A given app rewrite can benefit from lessons learned with regards to past efforts to extend the existing version, as well as maintenance pain points regarding chosen architecture.
However, those benefits are flushed down the drain when management thinks it's a simple lift-and-shift operation, and then realize it's like writing a whole new app (both the front-end and the back-end). They don't want to put the money into it, because "it works the way it is", despite the fact that maintenance tasks are taking longer and longer (and they fail to grasp WHY that's the case).
Here's the way the conversation usually goes (and it happens every month or so):
Management: "Why does it take so long to add such and such feature?"
Dev: "Because the code base is 13 years old, and you won't approve a rewrite."
Management: "How long will a rewrite take"?
Dev: "One day."
Management: "There's no money in the budget for that kind of effort. Let's just keep it the way it is."
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
"He's just a small time civil rights attorney. When major firms started threatening him he started worrying that he'd get disbarred and backed off." "Seriously, when the going gets tough, you don't want a criminal lawyer, all right? You want a _criminal_ lawyer."
|
|
|
|
|
It's a tale as old as time:
Attorney decides to make a name for themself and get rich by suing a mega-corporation. Meets client. Realizes the client is a lunatic. Quietly returns to the sewer.
|
|
|
|
|
Artificial Intelligence, meet Natural Stupidity...
|
|
|
|
|
The software on ESA's Mars Express spacecraft is to be upgraded after nearly two decades, giving the orbiter capabilities to hunt for water beneath the planet and study its larger moon, Phobos. Don't turn off your orbiter while update is in progress
|
|
|
|
|
I guess someone figured it needed Bing to improve its search results... 
|
|
|
|
|
Let me guess; a calculator, speed tester and unit converter.
|
|
|
|
|
You sir, are a god among men. Thank you for that! 
TTFN - Kent
|
|
|
|
|
Trends for compensation, remote work, training, and more "Don't you know each cloud contains pennies from heaven"
|
|
|
|
|
Stack Overflow's latest developer survey shows that most developers are working remotely and favor a flexible working environment where they can use their favorite technologies. And snacks.
|
|
|
|
|
Some developers have been telling us that they want to use sound to help them understand what’s happening in their code. Sounds like a bug to me
Now your code can compete with the cicadas (but more often than every seven years)
|
|
|
|
|
Does anyone else find that the Microsoft login page is hosed up?
Currently, it only allows you to use credentials from another site (MS, Facebook, or Google). There is no place to actually specify credentials.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
A CMU team says the system can recreate audio from a speaker by looking at a nearby bag of Doritos. "If the van is rocking..."
|
|
|
|
|
The standard will launch in 2025 with 512 GB/s speeds. And eight times harder to find for sale
|
|
|
|
|
Will it be eight times faster, or eight times as fast?
The former means 9 times as fast.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
From a pedantic point of view, consider language as sort of a close relative to mathematics, you are correct.
But the way we use the language does not necessarily follow math rules. If you ask the man in the street, say "Car A drives 30 mph. Car B drives two times faster. How fast does car B drive?" I am quite certain that less than one in a hundred will answer "90 mph".
Math arguments are not always applicable to natural language. "8 times faster" is interpreted similar to "8 times as fast".
(And I am quite sure that you were not really in doubt about the intended meaning. You just found an opportunity to point out what you consider to be somebody else's mistake. Here I'll give you another opportunity: I could care less!)
|
|
|
|
|
trønderen wrote: I could care less!
You cared enough to respond.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Exactly. If I had cared less, as I say I could, I wouldn't have responded.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
