Rehan Ahmed

With the initial lack of interest in CS expressed in unequivocal terms in the summary section, I have yet to disclose the crucial moment and an unforgettable experience during the time spent at the CS institution. The aforementioned, whose details will emerge shortly, continues to remain the critical determining factor between leaving the institution after stipulated duration without any interest in CS at all or with some interest and information to serve as the foundation for further knowledge acquisition.

After failing to manage the mandatory passing percentage, even if by just 2 marks, in the core Data Structures course, while attending the repeat course in the summer of 98, I found myself under the tutelage of an individual exuding such infectious enthusiasm for the subject — in fact so infectious that he managed to not only resuscitate the gasping soul of a bright student in me but also elicit an unrivalled performance from an individual initially profoundly uninterested in the proceedings. Never before in my life had I met an individual exuding such enthusiasm for the subject matter, eagerness for sharing it with his charges, and unparalleled commitment to the task at hand, nor have I since then found another individual, instructor or otherwise, with such qualities. Having spent 16 or so years in the educational system, I have an inkling that the quest to find another individual with such qualities would prove an exercise in futility. During the 3 years of the officially designated degree term, for whatsoever I managed to learn or develop an interest in — the C++ programming language and code refinement techniques — only this individual deserves the credit for ensuring that I would leave the institute with interest in at least some aspects of computer science.

Sheeraz Fazal

Although I spent approximately a year or so as part of the team being led by the person, however, as the management at that time had initiated a sophisticated and intricate financial fraud which eventually led to an utterly unexpected but eventual declaration of bankruptcy — the involvement must have netted them millions of dollars for their involvement — hence I could not benefit much from his experience. During that phase of uncertainty which involved extended periods of inactivity interspersed with short phases of unusually intensive activity demanding 12 – 14 hours long days, although I failed to learn much from the individual, however, I would remain forever grateful for his advice to thoroughly read Bjarne Stroustrup’s authoritative and definitive text titled “The C++ Programming Language,” a treatise on his brainchild and considered by many the C++ bible. In the aforementioned text, the author details not only the constructs and mechanisms offered by the language but also how to use them in a more professional manner. The team lead not only brought the creator’s work to my attention but also advised in an emphatic manner to read the work thoroughly, and for this, as stated earlier, I would remain forever grateful to the fellow.

Considering that the fellow now resides in the US, depending upon his availablity, if a professor in that area would like to hire him as a TA (Teaching Assistant), then I offer my unreserved endorsement. During my days at the CS institution, which now enjoys the status of a university, I failed to meet another individual in that capacity willing to take the responsibility as seriously and enthusiastically as he did.

Exceptional Works of Scholarship on C++ and Their Authors

After spending a couple of years in the industry, during which I lost a job and resigned from another, eventually halfway through the year 2002, based on the realization that I needed to further dramatically the scant understanding of the tools and techniques in which I had managed to develop some interest, I started perusing texts on C++, designing and producing efficient programs, and techniques employed by the CFront team for compiler optimization. During this odyssey to gain a better and deeper understanding of what many consider a somewhat esoteric programming language, I found the works of Bjarne Stroustrup, the creator of the programming language, and Stanley B Lippman wholly indispensable resources for any C++ programmer aspiring to gain better and deeper understanding of the language and the facilities it offers to design more robust and maintainable applications. Although the language has since the year 2004 undergone major changes, however, owing to various reasons, I have failed to stay abreast of the latest developments.

Without Proper Guidance, The Road to Web Development Contains an Abundance of Potholes, Pitfalls, and Misleading Signage.

When I made the switch to browser based UI development in 2007, I had never used CSS and HTML until then, and considering that the ascendance of Google had probably surpassed the expectations of even the most optimistic of investors, I had also not remained immune from overreliance on the search giant for knowledge acquisition. In retrospect, I probably lost over a year trying to stitch together acceptable interfaces and functional JavaScript applications by relying on instant answers, which rarely come with either the cautionary notes or references to requisite information to utilize that morsel of information correctly. As JavaScript provides ample control over arranging DOM elements, so to compensate for the lack of information, the brute force mechanism remained the standard approach during that first year.

Although the realization to adopt a better strategy to gain proficiency in a new technology took much longer than I would like to admit, nonetheless, after a year or so of trial and error approach to synthesizing acceptable interfaces and applications, I eventually concluded that without a thorough reading of the CSS standard, UI development using CSS would remain a continuous struggle. However, despite perusing the CSS 2.1 standard, I would have found expanding on the knowledge acquired through that reading alone a laborious and burdensome task without the willingness, regardless of their motivation or reasons, of the following individuals to share their knowledge with the masses.

  1. Christian Heilmann

    With the online publication where I first discovered Mr. Heilmann’s work employing word count as the barometer to ascertain the value of the accepted works, authors must feel awash with the temptation to inflate the word count by digressing. To the same authors, the editing phase involving judicious retention and elimination of content must resemble the ever so delicate balancing act of traversing successfully a patch of perilously thin sheet of ice.

    However, without ever making the reader feel burdened with unnecessary and irrelevant musings, within the span of an article on JavaScript unmistakably written for JS novices, Mr. Heilmann transformed me from a 3rd class JavaScript programmer to an acceptable or above average JavaScript programmer. From an individual whose HTML content used to resemble a spaghatti of HTML and JavaScript to a person fully aware of separation of concerns and capable of writing semantic HTML without the signs of functionality contaminating the document.

  2. Louis Lazaris

    As a user, I have benefitted greatly and on many occasions from the intellectual, financial, and other investments made by Google to improve the quality of results that it serves to its users, however, as to rank well on their results page, the content has to have certain characteristics ranging from word count, appropriate use of the keywords, structure of the document, few dozen other ranking signals, and finally to the ease of comprehension of the text, the trickle down effect of the aforementioned has started to show in the writings of those switching from blogging to book writing, especially in technology sector. Literary works of more and more authors writing for the technology sector now bear resemblance with articles written to rank well on the Google’s result page.

    With more and more authors now treating books as a collection of essays and using tone and language more suited to blog writing, Louis has so far managed to buck the trend, at least in the paid works. Other than some of the articles on the his front-end development focused website, although I have only read a book and an article written for the Adobe Developer Connection, I found the works not only quite informative but also meeting the expected standards of quality. Whether Louis plans to continue to adhere to personal standards, I certainly can not say — I have yet to develop the ability to read people’s minds — however, based on whatsoever I have read thus far, I undeniably associate articles and works packed with information yet devoid of digressions there to inflate the word count.

  3. Heydon Pickering

    Although I’ve only read an article written by the fellow, and I undoubtedly disagree with its introductory paragraph — vive la diffĂ©rance, as stated by Mr. Pickering in the article — however, except for the first paragraph, I found the approach to styling the documents discussed by the fellow the perfect methodology for utilizing the already available anchors. If I had to suggest an article to a neophyte on how to style an HTML document, I would certainly ask the novice to read Mr. Pickering’s views. Since coming across the aforementioned article, I have gone through another article, so the count now stands at two.

  4. Craig Buckler

    Although Craig rarely indulges in wordplay, keeping the articles short and focused, however, regardless of the length of the posts, I have certainly learnt a new technique or two from his posts that regularly appear on

  5. Chris Coyier

    On many a occasion, tips and tricks shared by Chris have allowed me to focus on the actual work instead of perusing the CSS standard or investing time and effort in trial and error approach to find a solution. Considering that I have benefitted from the material produced or work done by Chris many a times, so I would like to thank him for making available the work of the CSS working group in easily digestable chunks annotated with information on browser quirks and pitfalls.