This book is based on the seven Steps of web development, as I said in the repractise Introduction: Web Development seven days. Of course it's also an APP, a guide to how to become a growth engineer.
Writing process
Yesterday, I wrote the first draft of this ebook (which can be read and downloaded on GitHub) and already had 75,505 words.
In 8 weeks and 49 days, the total was submitted 477 times, and 212 files were modified.
Received the star of 1.4k+:
At the very beginning, my position on the book was to sort out what I had learned- to growth myself. Because the input is the best output:
It's not easy to sort out what you're learning, but it's a particularly interesting thing. In the process, I found myself needing to fill a series of basic knowledge. I read dozens of books again. Today, because of the work, many skills, techniques, knowledge points have been lost.
And these implementations should be the basic knowledge that needs to be replenished. Such as:
- I have forgotten the algorithm and the data structure to a certain extent. All this knowledge I learned many years ago, and later days have not been used well.
- I've even forgotten a lot of familiar concepts, probably because I didn't use them much, and then I didn't remember them.
It's a particularly good thing to know that you don't know. Like this feeling, anyway I do not want to learn those who do not know, temporarily maintain some sense of urgency.
So what is growth enginnering?
Full stack Engineer
In our preface, we compare two different engineers--the whole stack and the experts. The whole stack can rely on learning ability to expand the knowledge system, while the experts are deep into a certain field. The question is, what is an all-stack engineer? , namely:
They are able to build and deploy a complete, working application on their own without the help of anyone else.
And most people know the whole stack of engineers, is the full stack of experts , that is, all the knowledge points below are proficient.
As software development costs go down, the industry is ushering in an era of post-boom dominance, where the younger developers use more advanced technology . The so-called expert theorists I've seen have had to move to the full stack.
Those who do not like to contact their unfamiliar areas, stagnant experts, like advocating the whole stack useless .
Those who do not like to contact their unfamiliar areas, stagnant experts, like advocating the whole stack useless .
Those who do not like to contact their unfamiliar areas, stagnant experts, like advocating the whole stack useless .
There are different differences between people: introverts can go deep into a field, and extroverts can grow full stacks. Just the way people go to the whole stack is not the same process!
Programming is just a part of the whole stack, and the whole stack is just part of the skill.
Growth Engineer
The definition of a growth engineer is simple: continuous learning.
Now that we are all developing an application, we also have enough technology to be a growth Hacker:
Now that we're all developing an application, we can also be a hero in the Big Data world:
Now that we've developed a complete application, we'll be able to develop full-platform applications:
Full stack Growth Engineer's Guide
we all learn, but sometimes we just don't know what to learn .
Therefore, this is an instructive book. Don't expect to learn all the knowledge from this book, but he can help you build a knowledge system -something that other technical books lack. It can tell you what you can learn and then read what the book is.
The directory is as follows:
- Growth: Full stack growth Engineer's Guide
- All-Stack engineers are the future
- A History of technological innovation
- The core problem of software development: communication
- The experts of large companies and the full stack of small companies
- The future of all-stack engineers: no stack
- Basic Knowledge Article
- tool is only secondary
- webstorm or Sublime?
- language is also a tool
- Tools for Productivity
- Quick Start software
- IDE
- DEBUG tools
- Terminal or command prompt
- package Management
- Environment setup
- Learn The art of a good language
- One language learning experience
- output is the best input
- How to apply a new technology
- Web Programming Basics
- from browser to server
- from HTML to page
- HTML
- hello,world
- Chinese?
- Additional HTML tags
- summary
- CSS
- about
- styles and targets
- selector
- more interesting CSS
- JavaScript
- hello,world
- javascriptful
- Object-oriented
- other
- front-end and background
- Background language selection
- JavaScript
- Python
- Java
- php
- Other
- MVC
- Model
- View
- Controller
- more
- background as a service
- API Evolution History
- background-as-a-service
- data Persistence
- file storage
- Database
- search engine
- Front-end frame selection
- Angular
- React
- Vue
- jQuery Department
- foreground and background interaction
- encoding
- encoding process
- building system for Web Apps
- build process for Web Apps
- Web App build combat
- git and Versioning
- Tasking
- How to Tasking a book
- Tasking Development task
- Write code just in code word
- built-in index and external engine
- portal site
- built-in indexes and external engines
- How to write tests
- test pyramids
- how to test
- test aliases
- test-driven development
- red-green-refactoring
- Test advance
- readable code
- name
- function length
- other
- Code Refactoring
- renaming
- extracting variables
- refining functions
- Intellij idea refactoring
- Refinement Function
- Inline Function
- query supersedes temporary variables
- refactoring to design mode
- over design and design patterns
- on-line
- isolate and run environment
- Isolate hardware: Virtual machine
- Isolate operating system: Container virtualization
- Isolation bottom: Servlet container
- Isolate dependent versions: Virtual Environments
- Isolated Runtime Environment: language virtual Machine
- Isolated language: DSL
- LNMP schema
- Web cache
- database side Caching
- application-tier caching
- front-end caching
- client-side Caching
- HTML5 offline caching
- configurable
- Environment Configuration
- Run mechanism
- function switch
- Automation Deployment
- dependency and package warehouse
Build Package
- upload and install packages
- data Analysis
- Build-measure-Learn
- Ideas-build
- products-measure
- data-Learn
li> data Analysis
- Identify requirements
- Collect data
- analyze data
- Show data
- User Data analysis: Go Ogle Analytics
- audience
- traffic get
- mobile apps
- site Performance
- Site Performance Monitoring
- Web site performance
- seo
- crawler and index
- what sites need SEO?
- SEO Basics
- content
- UX Primer
- What is UX
- what is simple?
- Advanced
- User experience features
- Cognitive design
- Continuous delivery
- Continuous integration
- Continuous Integration System
- Continuous integration process
- Continuous delivery
- Basic facilities
- Continuous deployment
- Continuous learning
- Continuous reading
- Continuous programming
- Continuous writing
- Legacy systems and code changes
- Legacy code
- How to modify Legacy code
- Site Refactoring
- Speed optimization
- function enhancement
- Module refactoring
- Review and Architecture Design
- Self-summary
- Retro
- The process of Retro
- Three dimensions
- Schema mode
- Pre-engineered architecture
- Evolutionary architecture: Embracing change
- Surfaced design
- Intent-oriented
- Refactoring
- Patterns and Evolution
- Everybody's a architect.
- How to build a blog system
- Related reading materials
- Schema decoupling
- From MVC and micro services
- CQRS
- CQRS with Micro Services
Download and preview: Https://github.com/phodal/growth-ebook
The book of the most novice programmers of the 2016: The Growth Engineer's Guide