The US has yet to have a huge problem like making the currency unusable. I bet if that happened elections in the US would be very different. By the way there are midterm elections as well so there are elections every 2 years.
So no money can change hands without lots of technology and probably an internet connection.
How do you deal with small purchases from small vendors? An example would be a child's allowance.
Argentina is a democracy. Vote the idiots out of power.
I too have worked on systems that have been in documentation hell. On the other hand I have been lost in systems that have had no documentation. It is all about balance. Too much documentation is bad. Too little documentation is also bad. Too many meeting is bad. Too few meeting is also bad. Finding the happy medium is the key.
Which is why I hold all processes are flawed, the best process is no process.
You are delusional if you don't think you have a process. For example you stated that you review requirements docs until you are satisfied they are complete. That is part of a process. Just because you don't label it does not meant that it is not a process.
If you're not going to follow a strict guide then there is no point giving it name.
As with all labels, the idea is to give a starting point to quickly describe a process. Labels are never 100% exact.
No two companies use exactly the same process. Most use some version of waterfall. Some use a version of agile.
The less overhead you introduce into software developer the more enjoyable it is.
It works until two teams start stepping on each other's toes due to lack of process.
The waterfall method MUST be preformed exactly like this:
No, waterfall is a guideline and not a strict rule.
Steps 1 and 2 are done by your project management team.
Step 3 is done by you and I doubt you can do that in half an hour for a large system.
Step 4 is done by you.
If step 5 is done by you then you are leaving yourself open to coding only testing to what they got right.
You also do step 6 or nothing gets out. These steps do not need to be done by separate people. They are just separate phases.
By the way, there is a continuum between strict waterfall and Agile. Few companies are on either end. The way you work is closer to waterfall than agile and it is a defined process.
You just described the waterfall process.
Well my last project used 40 developers, 3 countries and 3 time zones and got a product delivered ahead of time.
Who wrote documentation? Who agreed who should do what parts? How were implementation decisions made? I bet there was a lot of structure that you may not be aware of. If all you did was work to a single spec then I bet you were not in design or management. They used a process.
The number of developers is completely irrelevant, look at Linux for instance, hundreds of developers, all on there own and yet the product comes together perfectly.
With a lot of work done on the API that all programmers must follow.
A number of people working on the same project with no discussion and no documentation is just anarchy.
For instance when I write large software projects, I just start coding, I pick a place to start at and go. I wait until I have large testable blocks completed and then debug and integrate them. I don't follow and form of standard development process and yet have never been held up via a deadline of meeting request.
That's great for a project where one person works on it. It does not work when you have many more people working in teams on different parts that all must work together. The biggest ting your "process" lacks is coordination and coordination is necessary when more than one person is working on a project. The more people the more coordination is needed. In a team what happens when one member changes code that breaks code from other team members? That is where APIs and process comes in.
The only things you need to write good code are the right language, the right platform and proper requirements.
There are more than one way to implement requirements and that has to be discussed and documented within the teams.
Have you ever worked in a team on a project? From your comments I doubt it.
Here are a couple of points;
1. Many musicians have families and work to create an inheritance for them. If there is no copyright past death there is no inheritance.
2. Music corporations are not going to pour millions into a rising star if they can get no return if the artist dies.
giving copyright to corporations for 200 years.
Bye the way, The limits are death of artist + 70 years or 120 years from date of creation for works for hire. Where does the 200 years come from? I haven't seen an artist live for 130 years after copyrighting a work.
If the false positives are low enough people can make basic preparations.
Anyone in an earthquake zone should already have made basic preparations.
You might want to check out the Vancouver Development Cost Levies. They go toward the cost of the infrastructure you mention and are not small. Levies like this exist in most jurisdictions.
When these small houses were built there was lots of room and fewer people. That has changed and there are more people who need to live in the same area. Neighbourhoods will change and densify. The only alternative is to grow outward and that is not a viable option as it creates land use and traffic issues.
As for the aesthetics issues, older homes are built very inefficiently. There is a lot of wasted space. Newer construction has to use the space more efficiently to allow more people to live on the same lot. Newer construction will be boxier as it is more space efficient.
Growth is like a balloon. You either let it grow up or, if you try to push it down, it will grow out. Neighbourhoods will change. Deal with it.
In both cases you need to get data from the reference station in real time
I didn't see them mention a reference station at all.
But not by companies in the US.
Disks travel in packs.
