To me it only makes sense to start writing the documentation once the codebase has reached a certain degree of maturity. If you are constantly refactoring and recoding everything all the time, like in the beginning of any project, documentation is just a plain waste of time.
That is a great idea assuming you already know how your solution is supposed to work and behave within the boundaries of available resources. In which case you probably already did the application before. If you already did the application before why are you coding it again? Copying your own code isn't exactly hard.
If you want something simple you don't program in C++. It's a convoluted mess of a language so of course no amount of documentation is going to solve that problem. Unfortunately there are little choices (except C of course) if you want to write reasonably portable high performance code.
I'll trade the supposed mess of learning Android which is mostly plain standard Java with its own UI and mobile specific APIs to learning Objective-C and a whole enchilada of Apple designed APIs which are not used anywhere else thanks.
Actually if it is an API we are talking about Javadocs work great. Examples are also nice. Real documentation? If the API cannot be understood just by reading the Javadocs then You Are Doing It Wrong! The API sucks.
Papers used to make money with ads and they couldn't track users either. These people just want more money from each user which understandable. However the problem is this information can be used to do all sorts of user profiling not necessarily for marketing purposes.
In Babylon 5 the Minbari have a stealth device which basically makes their ships invisible to radar. Infrared isn't as much of a problem because they use gravimetric propulsion i.e. reactionless drive so sorry but there are no large IR signatures like in chemical propulsion. Of course such propulsion systems only belong in the realm of science fiction.
The first jet fighters weren't that great. Besides immense reliability issues their performance was not that awesome. The Hawker Tempest did 700 km/h while the Me-262 did 900 km/h. Maximum altitude and range were slightly better for the Hawker Tempest. The P-51 had similar performance to the Tempest.
Google Maps has 3D view using WebGL. I suspect the iOS "Google" apps are actually made by Apple. There is no way they would be so crappy if Google was actually doing them.
How about letting Google test and release a standalone map application before they obsoleted the old one? No of course. The users might actually like it better so why not force them to use your shit.
1. ICE are like 20%-25% efficient at converting the energy in the fuel into movement. Electric engines and batteries? Over 90%.
2. Regenerative breaking saves around half of the energy used to move a vehicle in an urban setting.
So even if it was 1:40 those factors make it 1:5. Much easier to solve.
Slashdot Mirror
You probably haven't been following the hikes in the price of commodities or the stories of people selling stock in oil and resources they don't have.
You are assuming the specifications make sense or are actually what the client wants which isn't necessarily the case.
To me it only makes sense to start writing the documentation once the codebase has reached a certain degree of maturity. If you are constantly refactoring and recoding everything all the time, like in the beginning of any project, documentation is just a plain waste of time.
To save waste? More like to increase profit.
That is a great idea assuming you already know how your solution is supposed to work and behave within the boundaries of available resources. In which case you probably already did the application before. If you already did the application before why are you coding it again? Copying your own code isn't exactly hard.
Wiki documentation can be great if the people editing the wiki aren't a bunch of morons. Make of that what you will.
If you want something simple you don't program in C++. It's a convoluted mess of a language so of course no amount of documentation is going to solve that problem. Unfortunately there are little choices (except C of course) if you want to write reasonably portable high performance code.
Oops UTF-8 was Ken Thompson and Rob Pike. Oh well AWK it is.
Nah he just designed AWK and helped design UTF-8.
I'll trade the supposed mess of learning Android which is mostly plain standard Java with its own UI and mobile specific APIs to learning Objective-C and a whole enchilada of Apple designed APIs which are not used anywhere else thanks.
Actually if it is an API we are talking about Javadocs work great. Examples are also nice. Real documentation? If the API cannot be understood just by reading the Javadocs then You Are Doing It Wrong! The API sucks.
Papers used to make money with ads and they couldn't track users either. These people just want more money from each user which understandable. However the problem is this information can be used to do all sorts of user profiling not necessarily for marketing purposes.
In Babylon 5 the Minbari have a stealth device which basically makes their ships invisible to radar. Infrared isn't as much of a problem because they use gravimetric propulsion i.e. reactionless drive so sorry but there are no large IR signatures like in chemical propulsion. Of course such propulsion systems only belong in the realm of science fiction.
No. The EU levyed fines based on the sales of Microsoft in the EU.
Which end run around the court? US patent law != German patent law and in fact the patents even need to be filed separately.
The first jet fighters weren't that great. Besides immense reliability issues their performance was not that awesome. The Hawker Tempest did 700 km/h while the Me-262 did 900 km/h. Maximum altitude and range were slightly better for the Hawker Tempest. The P-51 had similar performance to the Tempest.
Darl McBride? Nice?
They already bought two companies to make this wonderful POS app. I guess they can buy more.
Google Maps has 3D view using WebGL. I suspect the iOS "Google" apps are actually made by Apple. There is no way they would be so crappy if Google was actually doing them.
This is more alpha than beta.
It doesn't do what you think it does. It is mostly interesting for fun and kicks. Try doing anything useful with it.
How about letting Google test and release a standalone map application before they obsoleted the old one? No of course. The users might actually like it better so why not force them to use your shit.
Google maps also has 3D views. Heck it even supports WebGL.
It beats investing in Facebook stock.
2. Regenerative breaking saves around half of the energy used to move a vehicle in an urban setting.
So even if it was 1:40 those factors make it 1:5. Much easier to solve.