|
CEO Nadella will headline day-long event, trumpet Windows 10 for consumers For those with lots of bandwidth who need a nap at work
|
|
|
|
|
I recommand some coffee and snacks to ensure that it is fun to watch it.
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
Take a sip whenever someone slips and calls it, "Metro"
Shots every time someone says, "super excited."
Chug if it crashes.
TTFN - Kent
|
|
|
|
|
Kent Sharkey wrote: Shots every time someone says, "super excited."
You know there is a limit how much one can drink, right?
--
"My software never has bugs. It just develops random features."
|
|
|
|
|
I'm heavily invested in stomach pump manufacturers. I need to boost that market.
TTFN - Kent
|
|
|
|
|
Kent Sharkey wrote: super excited.
I hoped that thing disappeared with Ballmer
|
|
|
|
|
When it comes to language usage on GitHub and Stack Overflow, the stalwarts reign I thought Java was at a 10-year low or something? Oh wait, that was yesterday.
|
|
|
|
|
In the cloud and on premises, Microsoft's deluge of product revisions is sure to please the whole gamut of users. Been so long since I heard about them.
|
|
|
|
|
|
Where they went?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Sure, they're like those one hit wonder acts of the 80s. Always planning a comeback tour.
|
|
|
|
|
By now we should all know that we don’t know how to measure programmer productivity. "How long is a piece of string?"
|
|
|
|
|
Management:- The art of making it harder for us to work in vain pursuit of making us work harder.
|
|
|
|
|
I agree.
Which is the more productive route from point A to point B?
A_______C
\ |
\ |
\ |
\ |
\ |
\ |
\|
B
|
|
|
|
|
Is there a bar at C? That would help me decide.
TTFN - Kent
|
|
|
|
|
Bear in mind that every corner has at least a bar, a gas station, and a Starbucks.
|
|
|
|
|
Going over C means more "output": more lines of code, more meeting, charts and test cases. Maybe getting new fellows and promoted to the managment
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
It could also mean more testing, error handling, and documentation.
|
|
|
|
|
Actually, if products were actually spec'd in sufficient detail to enumerate the different UI's, the functional requirements, the DB model, services, etc., it actually is pretty easy to estimate how long a product should take to manifest. But nobody does those things, because they take time. Granted, there's a certain amount of change that occurs during development, but it's usually not unmanageable.
So, I'm not sure how the heck you can measure programmer productivity if you don't have a decent spec against which estimate task times. And besides, productivity is an individual thing and based on experience -- my productivity sucks when I'm writing Javascript, but I still get the job done. But if I had a spec that said "this function, in Javascript, should take an hour to write, document, and test" and I did it in 4 hours, well, then you'd have a basis for my productivity in Javascript.
Marc
|
|
|
|
|
Exactly. If you don't know where you're going you'll never get there and you'll never know how long it'll take. The same is true if you don't know where you're starting from.
Marc Clifton wrote: "this function, in Javascript, should take an hour to write, document, and test --- given this skill set and experience" FTFY
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
|
|
|
|
|
"It doesn't matter how you get there if you don't know where you're going." -- The Flying Karamazov Brothers
|
|
|
|
|
There is a concept in Agile called Velocity[^]. This is a prediction of how long it will take a development team to complete a specific unit of functionality.
It takes time to measure velocity as it is based on previous projects, so the greater the body of previous project work to use as a basis, the more accurate will be the velocity.
In its simplest format, velocity is an estimate of how long it will take to complete a project based on the time taken to complete similar project previously.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Did you read the article?
Velocity is one of the ways he discusses and dismisses.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging 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
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
He doesn't dismiss the use of velocity at all. What he states is that velocity is more useful as an indication of predictability than performance, which is a fair comment.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Dominic Burford wrote: In its simplest format, velocity is an estimate of how long it will take to complete a project based on the time taken to complete similar project previously.
I can tell you without velocity.
98% of the work will be done in 2% of the time. The rest 2% of the work, will need at least 99% of the time.
And that, in ideal conditions.
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.
|
|
|
|