Douglas Crockford talk about WEB

This is a nice talk about how the web evolved and where it should have been as of this day. According to Douglas Crocford, instead of progressing into new technology, we are degrading our technology into where it all started.

Shocking !!! isn't it !!! .. listen to him from his own voice. His discussion has roots back from Herman Hollerith and the 1890 census. In the begin of this episode, I couldn't imagine how this gentleman brought the relation from the good olden days to now-a-days AJAX and JSON. Am convinced with his idea, and certain facts that he is mentioning about are REAL. According to him, we are doing research on the great thoughts that are published way back in the history by many great scholars. Outstanding ..

During the discussion, he mentioned the failures of Java. Another interesting point is that he tells where and how Microsoft could be successful in the key failures of Java. All these days I've seen the failures vs success points of these both technologies from the point of a Developer, but after this Webcast, I realised the areas as visualised by the real researcher. Yes, he has a vary valid points to give attention towards introducing the new bugs to the application at every new release. One more point that he highlighted about the "Open Source" vs "Proprietary Source" as, at the open source there is no single responsibility towards the bugs introduced / induced onto the source. Where as the proprietary source takes the responsibility and fixes them as a patch to the application. Yes!! that too convincing to me.

This is the first time am giving attention to such talks. Probably because of this, I felt that this talk has many points to give attention. Anyhow, overall this is a great talk and every mind that want to contribute to the progress of our technology, should listen to him and put some thought process towards these points.

Did you listen to this ??

Comments

Post a Comment

Popular posts from this blog

Network Intrusion Detection using Supervised ML technique

Declaimer This is my initial version of the synopsis for PhD studies. There are plenty of things that i have to complete before i prepare the final version. Thus, this would be the alpha version. Due to the length of the blog post, will not be posting the entire draft. 1.Title of the thesis Network Intrusion Detection using Supervised Machine Learning Technique with Feature Selection 2.Introduction Intrusion Detection System, IDS, is a development which improve the network security and defending the information of the association. The IDS encourage the network chairman to recognize any malicious action on the network and alarms the executive to get the information made sure about by taking the appropriate activities against those attacks. An intrusion alludes to any unauthorized access or malicious usage of data assets. An intruder or an attacker is a true element that attempts to discover a way to increase unauthorized access to data, causes hurt or take part in different
Read more

Common mistakes by Interviewer

Now-a-days am conducting few interviews for our organization. While sitting in the other side of the table, I've visualized why most of the interviews fail with me. But when conducting these interviews, most of the candidates are attending with self confidence that they are suitable for the mentioned role and attend without preparation. When people do some real preparation, they tend to fail due to lack of awareness at the interviewer towards interviewing techniques. Having failed in many interviews, I've learned that the interviews fail because of the following... Reflection (or) Mirroring: The interviewer tends to see self within the candidate. The interviewer starts to compare self with the candidate and evaluate. This evaluation is totally personal. The yard stick for measuring the candidature is not generalized, but influenced.   Template (or) Checklist: The interviewer has a template of a questionnaire. The interviewer measures the candidate with respect to the list of st
Read more

Keep the system active, to avoid the auto lock

Most of the corporate offices will have a policy for screen locking. While working with a long running applications at background, like the automation scripts for testing the applications, it would be difficult to maintain the unlock state of the screen. Thus, we found a technique to keep the system active with a cheating technique. Below is the powershall scripts that keeps the system active ' I am clicking on NUMLOCK for every 5 seconds to keep the system awake Set objNetwork = CreateObject("Wscript.Network")'to get user name numOfHours=inputbox("Hi " & objNetwork.UserName & ", How many hours you want me to be awake? :->") 'time variable conatins the time in hours Set WshShell = WScript.CreateObject("WScript.Shell") 'Creating an object for clicking keys from keyboard numOfMilliSecs=numOfHours*3600*1000 'converting hours to milli seconds While numOfMilliSecs>0 'runs until tym becomes zero WshShell.Send
Read more