Python configuration on Windows 7
-
Just spent two long hours and now I am able to use gdata to list all documents in google docs.
This is primary because of unclear instruction and real attempt by Nagesh to read them.
Side Note: Instruction in Ruby were much more clearer and I was able do same activity in 5 minutes
Conclusions: Don't blame tools, blame the documentation craters.
-
@Nagesh said:
documentation craters
We have pot-holes in our documentation too. Well - at least where such documentation even exists...
-
@PJH said:
@Nagesh said:
documentation craters
We have pot-holes in our documentation too. Well - at least where such documentation even exists...Yes is big trouble with entire existence of IT.
-
@Nagesh said:
@PJH said:
I suggest you avail yourself of the services of google and look up what 'craters' are. Look up 'creators' while you're there.@Nagesh said:
documentation craters
We have pot-holes in our documentation too. Well - at least where such documentation even exists...Yes is big trouble with entire existence of IT.
-
@Nagesh said:
Yes is big trouble with management of those in IT.
FTFY.
Oddly enough, I find those who complain the loudest about lack of documentation are those most resistent to creating it - developers.
-
@PJH said:
I suggest you avail yourself of the services of google and look up what 'craters' are. Look up 'creators' while you're there.
Dang. I didn't even realize it was a stupid typo until this post. I thought "documentation craters" was a pretty decent description of most manuals.
-
@boomzilla said:
@PJH said:
I'm almost certain it wasn't actually a typo.I suggest you avail yourself of the services of google and look up what 'craters' are. Look up 'creators' while you're there.
Dang. I didn't even realize it was a stupid typo...