|
Dan Neely wrote: The Greek situation is disappointing; if they had their stuff together and went all IPv6, they'd be able to sell almost 5 million addresses. And while $50 million is a drop in the bucket compared to their total debt problem, it's not like they're having any success elsewhere selling stuff off to pay it down.
And how much would it cost them to make the changeover? I'll bet that it's a lot more than $50 million.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
If #NoEstimates is the answer, what was the question? How about: it will probably be done before the heat death of the universe?
|
|
|
|
|
In the course of writing the proposal, I worked out a cost estimate for the software.
This is fine.
Perhaps "no estimates once the project is in flight that can be then used as a stick to beat developers with and cause a cycle of distrust that can destroy a functioning team dynamic" ... but that's a bit long for a hash tag.
|
|
|
|
|
Realistically (based on my esteemed experience) estimates and agile are orthogonal. The specs are usually so loose, the design so vague, the what-if's so undefined, that estimates in terms of concrete hours is useless.
Instead, estimates should be made as a percent of the scope of the entire project, which is artificially introduced as 100% = some time span, say a year.
Then, you estimate all the parts as a percentage, making sure they don't total up to more than 100%.
Now, when your project scope balloons, which it will because you are agile, what you do is add to the total time. Now, all your % estimate pieces (even the ones you've completed) suddenly have gained more time, which of course gets easily sucked up refactoring existing and writing new unit tests, because of course, you've hobbled the whole concept of Agile by forcing yet another discipline orthogonal to real progress, Test Driven Development.
But the point being that software creep no longer becomes an estimation of the new features and therefore extends the time to deliver, it is instead a % increase of all features in the entire project.
Anyways, that's how I now estimate an agile project. Actually, even if you don't do agile, I think that's a much more effective way of estimating scope changes.
Marc
|
|
|
|
|
The Internet of Things Security Foundation officially opens its doors today, September 24th, with the broad goal of securing the Internet of Things in an open manner, to allow the industry to flourish. Yes, yes: 'Secure all the things'. (It's like I'm a broken record)
record...record...record...
|
|
|
|
|
Apple, which once touted its hardware as invulnerable to hacks, may have become tech's biggest security threat. Several security breaches in iOS show just how big the problem is. Are question headlines irritating?
There. I think I finally found one that (for me) wouldn't be answered automatically with 'no'.
|
|
|
|
|
We’re proud to announce that we are partnering with Adafruit to release a new Starter Kit designed to get you started quickly and easily on your path of learning either electronics or Windows 10 IoT Core and the Raspberry Pi 2. This kit is available now at http://www.adafruit.com/windows10iotpi2 and includes a compatible set of sensors, electronic parts, wires, and cables that have been verified to work with Windows 10 IoT Core. It also has an SD card preloaded with Windows 10 IoT Core meaning you can start right away.
What’s next for Windows 10 IoT Core[^]
My robo-sheep project may yet see the light of day
|
|
|
|
|
Duncan Edwards Jones wrote: My robo-sheep project may yet see the light of day Sort of a Roomba for the lawn?
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed."
- G.K. Chesterton
|
|
|
|
|
Exactly. Room-baaaa!
(OK - more boringly a putative robot to kill rushes in pasture by targeted application of microwaves, instead of the current really very dangerous chemicals)
|
|
|
|
|
Just have it "eat" the rushes and then generate its own fuel, converting the cellulosic material to bioethanol/biobutanol.
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed."
- G.K. Chesterton
|
|
|
|
|
Does it also enforce "Get off my lawn" commands?
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Duncan Edwards Jones wrote: My robo-sheep project may yet see the light of day
The local hackers will have a field day!
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
I may need to use a field programmable gate array
|
|
|
|
|
With Google Contributor, you contribute a certain amount of money each month. That subscription means that you see fewer ads on the web, and you support the sites that you visit with your money. "Blackmail is such an ugly word. I prefer extortion"
|
|
|
|
|
To quote Dr. McCoy: "I'd give real money if he'd shut up."
Kent Sharkey wrote: "Blackmail is such an ugly word. I prefer extortion" So when is CP implementing this?
|
|
|
|
|
Recently, on an interview, I was explaining to an enthusiastic candidate what is TDD. Just like a table saw is a design methodology for a house
|
|
|
|
|
Pshaw... that requires a house saw.
|
|
|
|
|
Or a house saw factory builder pattern ...
|
|
|
|
|
TDD is an anti-pattern
|
|
|
|
|
Competitive coding, where programmers race to be the first to come up with the solution to complicated code challenges, has exploded in popularity as a place for Silicon Valley firms like Facebook and Google to find top talent. This blurb writer thinks they need a yellow card for silliness
Or 10 yard penalty, depending on which side of which ocean you live on.
|
|
|
|
|
I would not hire any of the participants.
|
|
|
|
|
|
Commentator: And Smith has selected a for loop...
Color guy: Interesting choice, that, I was sure he'd go for a while loop here...
Commentator: Oh no! Smith has tried to use a single-character variable name! There's a flag on the play!
Color guy: I see this time and time again with Smith. He needs to understand that a short-term gain will usually lead to a long-term loss.
|
|
|
|
|
Commentator: Meanwhile Johnson is compiling, will his code work on the first try?
Color guy: If it does Smith is done for!
Sounds exciting indeed...
Well, I guess this could actually work!
|
|
|
|
|
Commentator: Johnson presses Run...
Color guy: There's a buzz from the crowd.
Commentator: And now a fizz. Another two buzzes...
Color guy: Can Johnson go all the way?
Commentator: A fizz!
Color guy: Johnson has done it!
|
|
|
|