I can trace Angular’s beginnings to 2009, on a project called Google Feedback. We’d
gone through months of frustration with our development speed and ability to write
testable code. At around the six month mark, we had around 17,000 lines of front-end
code. At that point, one of the team members, Misko Hevery, made a bold statement
that he’d be able to rewrite the whole thing in two weeks using an open source library
that he’d created as a hobby.
I figured that a two week delay couldn’t hurt us that much and we’d at least be entertained
by Misko scrambling to build something. Misko missed his time estimate. It took three
weeks. We were all astounded, but even more astounding was that the line count for
this new app had dropped from 17,000 to a mere 1,500. It seemed that Misko was onto
something worth pursuing.
Misko and I decided we’d built a team around the concepts he started with a simple
charter: to simplify the web developer’s experience. Shyam Seshadri, this book’s coauthor,
went on to lead the Google Feedback team in developing Angular’s first shipping
Since then, we’ve developed Angular with guidance both from teams at Google and
from hundreds of open source contributors around the world. Thousands of developers
rely on Angular in their daily work and contribute to an amazing support network.
Welcome to the proceedings of the 23rd International Conference on Scientific
and Statistical Database Management held in Portland, Oregon, where it celebrated
its 30th birthday. The first incarnation of SSDBM (then called the Workshop
on Statistical Database Management) took place in Menlo Park, California,
in December 1981. Since...
Database Access with Visual Basic is the only book that takes an object paradigm approach for component-based solutions to modern, distributed enterprise implementations.
Database Access with Visual Basic's major emphasis is on solutions, not technology. Rather than rattling off a list of features, diagrams, and acronyms, this...
The software business is challenging enough without having to contend with recurring errors. One way repeating errors can be avoided is through effective software measurement. In this volume, Ebert and his co-authors offer practical guidance built upon insight and experience. They detail knowledge and experiences about software measurement in an...