Top Down, Bottoms Up
The whole is greater than the sum of its parts. - Aristotle
In our efforts to get up and running, we have mostly concentrated on graphic design, user interface languages (HTML, CSS), and workflow fundamentals. In
Once you have passing familiarity with the topics covered in this chapter, you should feel confident about beginning to apply for jobs. You will be able to (1) describe internet software systems (top-down), and (2) describe how you would implement certain parts of those systems (bottom-up).
Note the repetition of the word “systems” in those described abilities. A primary consideration in structuring the content of this book is to enable you as a systems thinker. In the context of software development, a systems thinker is someone who consciously considers the overall software system before developing an individual part of it.
It is important to realize that you do not need to know how to describe of the minutiae of any particular software system. The day-to-day labor of a software engineer is actually to discover and implement minutiae. But by demonstrating a conscious consideration of the basic pieces of a typical frontend software system, you demonstrate an ability to build individual parts of it in such a way that integrates with and enhances the whole system. This is the sort of programmer that (good) employers want to hire.
- Are you going to software meetups and connecting with the community? This is the #1 thing you can do to help yourself get a job!