Vous l'avez déjà ?
Repliez vers l'arrière Repliez vers l'avant
Ecoutez Lecture en cours... Interrompu   Vous écoutez un extrait de l'édition audio Audible
En savoir plus
Voir les 2 images

The Computer Boys Take Over - Computers, Programmers, and the Politics of Technical Expertise (Anglais) Relié – 17 septembre 2010


Voir les formats et éditions Masquer les autres formats et éditions
Prix Amazon
Neuf à partir de Occasion à partir de
Format Kindle
"Veuillez réessayer"
Relié
"Veuillez réessayer"
EUR 46,85 EUR 40,75
click to open popover

Offres spéciales et liens associés


Les clients ayant vu cette page peuvent être intéressés par ces liens sponsorisés

  (De quoi s'agit-il?)

Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.

  • Apple
  • Android
  • Windows Phone
  • Android

Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.



Idées cadeaux de Noël
Idées cadeaux pour les enfants, les passionnés de high-tech...et plus encore! Retrouvez notre sélection rien que pour vous.

Détails sur le produit


Les clients ayant vu cette page peuvent être intéressés par ces liens sponsorisés

  (De quoi s'agit-il?)

Commentaires en ligne

Il n'y a pas encore de commentaires clients sur Amazon.fr
5 étoiles
4 étoiles
3 étoiles
2 étoiles
1 étoile

Commentaires client les plus utiles sur Amazon.com (beta)

Amazon.com: 3.5 étoiles sur 5 6 commentaires
11 internautes sur 13 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 Historical insights into the computing industry, with implications for computing education 7 juillet 2013
Par Mark Guzdial - Publié sur Amazon.com
Format: Format Kindle Achat vérifié
A fascinating book that covers a critical part of the history of the computing industry, when computing shifted from being a science and engineering marvel, to a business necessity. That transition created an enormous need for computer programmers, and lead to the creation of programming languages (e.g., Fortran, COBOL, ADA) and the development of "software engineering" in response to the "software crisis." The author argues that the responses to that transition leads us to the characteristics of the modern computing industry. For example, he argues that the (failed) attempts to professionalize computer programming is what led to the retreat of women from the field. As a computing educator and education researcher, the book gave me new insights into the role that education plays in software engineering, the "software crisis," and the future of our field. Highly recommended.
5.0 étoiles sur 5 It was a great pick up 31 mai 2016
Par Amazon Customer - Publié sur Amazon.com
Format: Broché
These readings were few of the many books which kept me intersted from cover to cover. It was a great pick up, even for a novice reader at university.
0 internautes sur 1 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Five Stars 29 février 2016
Par Amazon Customer - Publié sur Amazon.com
Format: Format Kindle Achat vérifié
Best yet from an IT professional who was there through the entire period!!
Jon H.
0 internautes sur 8 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Five Stars 22 octobre 2014
Par Mariacristina Sciannamblo - Publié sur Amazon.com
Format: Relié
On time!
6 internautes sur 39 ont trouvé ce commentaire utile 
1.0 étoiles sur 5 He should have talked to competent professionals 19 juillet 2013
Par Art Lover - Publié sur Amazon.com
Format: Relié
First of all, as pointed out in another review, this book is seriously out of date - the basis being things that happened prior to 1980. But what bothers me the most about this book is the total lack of understanding of what a software engineer is. I don't know where Ensmenger got his information, but what he calls software engineering is not what a true software engineer (or any of the professional or technical societies in computing) would call software engineering. Even in the 1970's, when Ensmenger was writing his PhD thesis, the field of software engineering was emerging and those who are competent in that field knew a lot that Ensmenger seems to have missed. True, the term "software engineering" has been bandied about by many who lack a true understanding of what it means to use engineering techniques to build software, but that doesn't excuse such ignorance in a man who purports to be a competent historian. Software factories and the like were once the darlings of managers who wanted to crank out pedestrian software at low cost, but they were not software engineering (and they have largely been supplanted by techniques that require more competence). Ensmerger's view of ADA sounds like he's been talking to a bunch of ADA haters. ADA has its problems, but some of the most competent software ever produced was written in ADA - because it had to be properly engineered for safety reasons.

The implication that software engineering was created so we could develop software with marginally competent programmers is insulting to software engineers and highly inaccurate. It's like saying we created electrical engineering so we could do applied physics with marginally competent physicists. Or we created the field of medicine, with all of its licensing and board certifications, so marginally competent physicians could perform. A true expert practitioner in any field realizes the importance of having high quality tools and processes that form a foundation or infrastructure or scaffold, if you will, upon which they can apply their expertise most effectively. This is what software engineering provides to the software developer and the best ones understand its value.
Ces commentaires ont-ils été utiles ? Dites-le-nous

Rechercher des articles similaires par rubrique


Commentaires

Souhaitez-vous compléter ou améliorer les informations sur ce produit ? Ou faire modifier les images?