From my experience a lot of people connect to the internet through their modem/router/gateway instead of a direct connection, this usually means NAT.
Even though it is interesting to see how quickly an unsecured system can become hijacked, I wonder how many people are still connected directly to the internet?
In my opinion, there is no ideal process, tool and language. It always depends on a lot of things like type of customer, software/hardware architecture, expected team size, etc. I've seen a lot of companies trying to standardize on requirements and/or software configuration management tools but failed because they were unable to unify their process. Small teams work differently than large teams an usually require a different approach. Project managers should analyze their project and choose their process and tools on beforehand. Experienced developers, architects, requirements, test and configuration managers should advice the project manager and make a decision in best interest of the project. In my opinion, that would be a good foundation for a succesful project.
Standardizing on one process, tool, modelling or programming language would just be stupid since you would restrict your company in their ability to optimize their productivity and quality.
Slashdot Mirror
From my experience a lot of people connect to the internet through their modem/router/gateway instead of a direct connection, this usually means NAT. Even though it is interesting to see how quickly an unsecured system can become hijacked, I wonder how many people are still connected directly to the internet?
In my opinion, there is no ideal process, tool and language. It always depends on a lot of things like type of customer, software/hardware architecture, expected team size, etc. I've seen a lot of companies trying to standardize on requirements and/or software configuration management tools but failed because they were unable to unify their process. Small teams work differently than large teams an usually require a different approach. Project managers should analyze their project and choose their process and tools on beforehand. Experienced developers, architects, requirements, test and configuration managers should advice the project manager and make a decision in best interest of the project. In my opinion, that would be a good foundation for a succesful project. Standardizing on one process, tool, modelling or programming language would just be stupid since you would restrict your company in their ability to optimize their productivity and quality.