Datacrow without the java software#
Then I noticed something: almost everything in the book can be applied to the work we do as software designers. I bought it because I'm interested in architecture. I don't think there's a single mention of computers in the whole book. Yeah, OK, it's a book about architecture. I read this before starting college, and decided that I wanted to major in "Godel Escher Bach." My primary criterion for choosing courses was to cover topics that were raised in this magnificant, panoramic, and brilliantly interesting book: AI, cognitive science, computer science, philosophy, psychology, music, and art are woven together magically.Ī Pattern Language: Towns, Buildings, ConstructioĬhristopher Alexander, Sara Ishikawa, Murray Silverstein, et al.
Godel, Escher, Bach: An Eternal Golden Bra This book goes a long way towards relating engineering and philosophy. our work is a significant a part of our lives, and we need a philosophical understanding to make sense of it.
Some people's attitude towards programming is that it's a nifty way to pay the bills. Nobody understands the emptiness, the banal loneliness, and the quest for personal connection of modern age North America like Coupland. Douglas Coupland's portrayal of life at Microsoft in the early 90s was so stunningly on-target it floored me - but then he went further and provided a moral and ethical understanding of what was going on that hadn't quite occurred to anybody. Nothing quite captures the feeling of being a young programmer at a big software company as well as Microserfs. For many of these young programmers life outside of work is pretty lonely and empty, which works great for Microsoft, because you put all your energy into the really fun part of the day, developing cool software. There's nothing to do, and you're a computer geek, and the fun toys are at work, so chances are, after getting your take-out dinner at the Taco Time driveup counter, you'll just be bored so you'll go back to your plush office with a view of mountains and 100 foot evergreens and code. Here's an important thing to understand about working at Microsoft right out of college. You'll see a lot of overlap between the ideas in this book and my wholly unoriginal (surprise, surprise), although the emphasis here is on getting control of the scheduling process. Steve McConnell captures a lot of the development management ideas that Microsoft figured out in their first decade or so of developing software on a large scale. Understanding this book is a prerequisite for thinking correctly about managing software teams. This book is most famous for discovering the principle that adding more programmers to an already-late project makes it later, but that's only the tip of the iceberg. not just once, but once a year.Ĭertainly one of the classics of software project management, this book first appeared a quarter of a century ago, when Fred Brooks tried to run one of the first very large scale software engineering projects (the OS/360 operating system at IBM) and became the first person to describe how radically different software is from other types of engineering.
It is the one thing every software manager needs to read. I can't recommend this book highly enough.
Datacrow without the java full#
Why are there so many jelled SWAT teams at Microsoft that are remarkably productive? Mainly because Bill Gates has built a company full of managers who read Peopleware. Why do managers give so much leeway to their teams to get things done? That's in there too. Ever wonder why everybody at Microsoft gets their own office, with walls and a door that shuts? It's in there. The best way to describe it would be as an Anti-Dilbert Manifesto. This book was one of the most influential books I've ever read. The book was by Tom DeMarco and Timothy Lister. Among the floppy disks, mouse pads, and post-it notes was a stack of small paperback books, so I took one home to read. As summer interns at Microsoft, my friends and I used to take "field trips" to the company supply room to stock up on school supplies.
0 kommentar(er)
