I came across the following graphic on retention:
Many programs focus on teaching students a mastery of the fundamentals. However, in many technical fields education is short lived and continuous learning is the norm. Does learning to learn then trump a mastery of the fundamentals?
If we become autodidactic masters, would we not then be able to overcome any learning gaps?
Much graduate work at MIT, by its nature, is independent learning. At the undergraduate level I see good efforts in this direction but the promise is still unrealized. In either case, I think MIT does better than most colleges at creating self teachers.
My personal learning cycle is:
1) Build a knowledge base
- read, read, read
2) Test your knowledge
- test, experiment, and challenge
3) Summarize and structure your findings
- write, write, write
4) Teach what you have learned
- explain it to others
The process is often iterative in steps and in cycle.
Something that was not obvious to me was "self feedback". On a traditional teaching structure, the feedback comes from the instructor. In self teaching, you give feedback to your self.
An old one, entered here for reference
<configuration>
<system.web>
<webServices>
<protocols>
<add name="HttpGet"/>
<add name="HttpPost"/>
</protocols>
</webServices>
</system.web>
</configuration>
I have been working on some software that "really" needs to play well with others.
I used my usual tricks with services but there we still some platforms that did not like my SOAP. Getting down into the guts of the problem I found problems with the MS header "SOAPAction". After cleaning up my WSDL and adhering strickty to WSI I found that MS thought all my web methods had the same SOAPAction. After some research I found the magic attribute:
[SoapDocumentService(RoutingStyle = SoapServiceRoutingStyle.RequestElement)]
The MS error:
The methods getVendorVersion and poll use the same SOAPAction ''. When the RoutingStyle of the XML Web service is SoapAction, SOAPAction values must be unique across methods on the XML Web service. You can change the SOAPAction with the Action parameter to the SoapDocumentMethod or SoapRpcMethod attributes, or you can specify a RoutingStyle of RequestElement on the XML Web service.