There are 80 millions of PlayStation 3 in the world:
There are 80 millions of PlayStation 3 in the world:
Don't forget that Motorola use the Six Sigma approach:
which is in opposition of the current trend of agility, where the focus is on delivering, while Six Sigma's focus is the process itself.
Unless they don't use Six Sigma on their phones...
you need to do it in less than 6 lines of code
This is easy !
For such short sequences of code, you can use SuperOptimization:
I remember reading that a sequence of 7 assembly opcodes required a few weeks of computation.
tells me that my MySpace account has been pawned, but I don't remember creating a MySpace account.
I believed that the anonymous poster was very proud of his pangram and wrote a bot to spam Slashdot, but I just noticed that the X and Z letters were not used.
This is nothing new.
The effort of every individual in a group of people has been measured by Ringelmann in 1914, for army's purposes.
Here is the original article: http://gallica.bnf.fr/ark:/121...
And the results are (number of people => measured effort)
1 => 100%
2 => 93%
3 => 85%
4 => 77%
5 => 70%
6 => 63%
7 => 56%
8 => 49%
This is called "Ringelmann effect" or more recently "social loafing".
As you can see, 8 people produce the same amount of effort than 4 individuals.
I maintain that this 2 weeks is completely arbitrary, and leads to unregular velocity during the session.
You'll get most work at the beginning, and the effort disappears at the end of the session.
The worst thing is that some of the nice features get cut in so many parts that we can only implement the least costly ones.
This leaves the whole features unfinished and creates a lack of satisfaction.
Perhaps it works well for new teams, but for experienced teams, this is a serious problem.
Also, an experienced manager will know when to negotiate (which is what agile encourages) and when to stop negotiating (which is what agile discourages).
What agile does for the developer is codifies "I have 2 weeks to code this specific thing, go away and let me do it".
I wanted to agree with you, but you are clearly too much obsessed by Scrum !
Frankly, this "2 weeks-sprint" is probably one of the least agile techniques.
It's like saying: we are in the Titanic, we need 10 miles to turn right. Hey, there is an iceberg in front. No, we need 10 miles, so we'll take 10 miles !
Agile is here to force managers focus on their work, and let the developers focus on their work.
Forget daily scrums, forget sprints, just do it in the agile way: as it comes.
How can I balance between planning/cutting tasks and coding/testing, when software changes during its development ?
I can assure you that 2 weeks sessions will not solve your problem !
What is the correct balance between "planning" and "doing" ?
"Doing" works for people with plenty of experience, but they are rare.
"Planning" works when the project is very complex, but it is rare
The correct cursor is something between "a little planning, a little doing, and we see what we reached", which is basically agile's definition.
I'd like to share my experience: I wanted to become an agile coach (yes, shame on me !).
This was because I saw the opportunity to help people become better, but that's not really what agile became nowadays.
And I realized that Agile is not for developers, but for managers.
In other words, it's not designed to help developers, but to make money out of managers.
You have to agree that the vast majority of managers are completely clueless, so they doubt about their own skills.
Agile, or most exactly Scrum and Devops, are designed to tell them: you don't understand software development ? No problem, you'll only have to follow a basic algorithm and we promise you that all your problems will disappear.
I agree that this is quite dishonest, but hey, the goal is to squeeze money out of companies, and managers can use their budget for this !
What is funny is that most agile gurus are not decent developers.
They'll explain that such agile game will help people realize something, but they are quite clueless regarding programming.
archive.org also provides downloads with BitTorrent
The success story is their ability to present something that has no value as something revolutionary and valuable.
Everything is in the pitch.
Indeed, it's the best solution, but France is special in the sense that some people resist despite common sense, like in the comic Asterix.
A few inhabitants refused to quit the village !
I'd like to share my own experience, since I'm self-taught programmer.
I started programming 35 years ago, on a pocket calculator (TI58-C), then moved onto some micro-computers.
At this time, I realized that that's what I wanted to do as my job.
So I spent a lot of time disassembling code, in order to understand how it was done.
Then I started to write my own games.
I finally got hired into a video game company, but I realized that working in a company could not provide me enough software education.
I bought the Art of Computer Programming, and I passionately read it.
Later, I entered programming contests, where I could explore combinatorial algorithms by practicing them.
Now, I'm equivalent to a software engineer, though I'm underemployed given my experience.
So yes, you can practice programming and acquire theoretical bases afterwards.
But most coders I met were satisfied with their level, never trying to challenge their knowledge.
I don't speak about learning new languages, but new ways to solve problems.
They are more dedicated to build their career.
Since I'm from France, I found some other articles explaining the real reasons, and they are pretty different from TFA.
First, Montreuil is 11 kilometers away from Paris, it's reasonably near and a lot cheaper.
You can check the photographs, the residents live only a few meters from the datacenter.
The problems appeared because Interxion would like to add an extension to the datacenter, doubling its capacity, and thus the noise it produces.
Here is a translation about the various causes:
In particular because of the presence of generators with combustion engine, of course designed for use in emergency power supply and when the monthly testing and maintenance, but also for refrigeration systems installed outdoors on terraces, designed to operate continuously, and because of a law daily traffic of 15 heavy vehicles.
Besides the sirens sometimes trigger during the night.
It's nice to have datacenters, but it's hellish to live nearby.
And if you are the owner of a house nearby, your house cannot be sold at a correct price.
In fact, it's quite easy to patent new ideas.
There are even methodologies for that: TRIZ https://en.wikipedia.org/wiki/..., SIT, ASIT or USIT.
The only problem is that these methods don't focus on "inventing" but on "improving" existing ideas.
So basically, it's not a very "creative" process, so "genius" is not required.
It is impossible to travel faster than light, and certainly not desirable, as one's hat keeps blowing off. -- Woody Allen