You write that you use Scrum with a kanban board, and a single list of bugs. How do you manage the list?
I don't think the problem here is necessarily the tools, but might be the process. Do you ever groom the backlog/bug list? How do you prioritise your bugs? You may wish to look a bit on the team culture and think carefully about how you are dealing with older tickets.
It also sounds like you are building up a debt of bugs, which isn't necessarily the end of the world, but you may want to ensure that you triage and process the bugs in some form.
That solution has worked so well that few feel the need to use IPv6.
I wonder what will happen to force the issue?
The non US part of the world runs out of addresses and migrates to ipv6. The US will realize they've fallen behind and try to catch up.
According to this study at CAIDA, the US got 62% of the ipv4 addresses. According to a talk I heard a while ago, organized by the WLUG, the rest of the world, especially asia, is slowly adopting ipv6.
This have already been done in sweden
on
Cashless Society
·
· Score: 1
The banks launched something that seems to be very similair in sweden a couple of years ago.
It flunked rather heavily, mostly since there wass already a very widespread use of visa or mastercard.
My previous visa card had a chip for using that payment method in it, and I never used it on the same grounds as everyone else. Why split my money and put a part of it in a chip where I can never use it for anything else then payment?
And actually pay for using it?
To show how much money you had on that card, they had special readers that you could carry around on your keychain. Some banks gave them away for free and some of them sold the viewers.
As to the flunking of the entire system?
The people never used it due to the fact that you locked the money into the cards and very few shops had them.
And the shops never used the system since so few people used it.
It's almost entirely gone now.
They wouldn't really have to do much reserach.
What if a modular system for exploits is used?
It would be possible to make the worm, give it some basic exploits that are well spread to start with, and then add more modues and remove others with the help of the p2p net.
You wouldn't even need to do research, security mailinglists could be enough.
You write that you use Scrum with a kanban board, and a single list of bugs. How do you manage the list?
I don't think the problem here is necessarily the tools, but might be the process. Do you ever groom the backlog/bug list? How do you prioritise your bugs? You may wish to look a bit on the team culture and think carefully about how you are dealing with older tickets.
It also sounds like you are building up a debt of bugs, which isn't necessarily the end of the world, but you may want to ensure that you triage and process the bugs in some form.
According to this study at CAIDA, the US got 62% of the ipv4 addresses. According to a talk I heard a while ago, organized by the WLUG, the rest of the world, especially asia, is slowly adopting ipv6.
The banks launched something that seems to be very similair in sweden a couple of years ago. It flunked rather heavily, mostly since there wass already a very widespread use of visa or mastercard. My previous visa card had a chip for using that payment method in it, and I never used it on the same grounds as everyone else. Why split my money and put a part of it in a chip where I can never use it for anything else then payment? And actually pay for using it? To show how much money you had on that card, they had special readers that you could carry around on your keychain. Some banks gave them away for free and some of them sold the viewers. As to the flunking of the entire system? The people never used it due to the fact that you locked the money into the cards and very few shops had them. And the shops never used the system since so few people used it. It's almost entirely gone now.
They wouldn't really have to do much reserach.
What if a modular system for exploits is used?
It would be possible to make the worm, give it some basic exploits that are well spread to start with, and then add more modues and remove others with the help of the p2p net.
You wouldn't even need to do research, security mailinglists could be enough.