Scott Meyers
Educated at Brown University and later at Stanford University, Scott Meyers built his professional life across several overlapping fields — a combination that has shaped the kind of work he produces.
Meyers was born in the United States in 1959. His academic path took him first through Brown University and then on to Stanford University, two institutions that provided the educational foundation for his subsequent career. That career has drawn on more than one discipline, with Meyers working as an engineer, a computer scientist, a programmer, and a writer.
All of his work has been conducted in English. The range of occupations attached to his name — engineering, computer science, programming, and writing — points to someone who has operated across both technical and written domains throughout his professional life. Whether engaged as a programmer, an engineer, or a writer, Meyers has moved between the practical and the expository sides of his field.
As a living subject, Meyers holds citizenship in the United States, the country where he was also born. His education at Brown and Stanford, combined with occupations spanning engineering, computer science, programming, and writing, form the documented outline of a career that has never settled neatly into a single category.
Quotes by Scott Meyers
A non-virtual function says, you have to do this and you must do it this way. A virtual function says you have to do this, but you don’t have to do it this way. That’s their fundamental difference.
Lightstone’s Convolution Principle: The concurrent development of multiple features operating on intersecting componentry will take longer to complete than the sum of the schedule estimations for each.
Do that, and the best you can hope for is that people will ignore you. More realistically, you’d be skinned alive, or possibly sentenced to ten year hard labor writing microcode for waffle irons and toaster ovens.
... the results are undefined, and we all know what 'undefined' means: it means it works during development, it works during testing, and it blows up in your most important customers' faces.
A non-virtual function says, you have to do this and you must do it this way. A virtual function says you have to do this, but you don't have to do it this way. That's their fundamental difference.
Do that, and the best you can hope for is that people will ignore you. More realistically, you'd be skinned alive, or possibly sentenced to ten year hard labor writing microcode for waffle irons and toaster ovens.
Lightstone's Convolution Principle: The concurrent development of multiple features operating on intersecting componentry will take longer to complete than the sum of the schedule estimations for each.
The market is in free-fall. This is certainly not a technical picture. The Nasdaq is falling apart and you don't know where the bottom will be.
The concern is that there is a steady drip-drip about this, and it will become part of the common knowledge about cookware even though people won't get PFOA from cookware.