10 Things Excellent Web Developers Must Know to Improve Their Development Skills
|
"Development is more than just writing code" comes from Dan Frost of 3EV. He explained some things that should be paid attention to during the development process in an article. The original content is as follows: Developers are the main force in creating the digital world. They should not only play the role of programming tools, but should have higher requirements for development work. So, in what aspects can developers improve their development capabilities? Let me talk about my ideas below. My suggestions may not be comprehensive, but I hope they can be of some help to you. 1. Don’t just focus on the code. Nowadays, everyone can write code. Many amateurs can also build websites and write applications. Programming is no longer a rare thing. With the popularization of the Internet, many people can learn programming simply by self-study, but both self-taught and professionally trained developers have some of the same problems. I have interviewed some highly educated candidates. Most of them have obtained computer degrees, taken AI courses, and have various computer level certificates, but they still lack some very important understandings. Developers should not only focus on the code, but also pay attention to two aspects of development work - horizontal and vertical. For example, developers should know how to collaborate with others in a team and should also be clear about the system-level design in the development project. I think people who work with developers should read this article as well. Because the more you know about development, the higher your requirements can be when working with developers. For example, you can ask them to summarize the issues under discussion, extract the core functions of the system, and use pictures and examples to demonstrate the functions implemented by the application.  3. Internet influence: You can get many answers by simply searching for development technologies on professional websites. Such as framework knowledge, browsers, CSS and JS. Search engines will help you find the frameworks, platforms, and trends you need to follow. And these things are just our tools, they help us structure the project, but they are not the key to the success of the project. Even if a developer understands every detail of the system, masters all API functions and new CSS techniques, he may still develop a meaningless product. Developers need to know how to use the tools, but they also need to understand the audience, which is the users, the team, and other developers. They need to understand how well their tools fit into the environment (in other words, the environment of the product) and how useful the tools are. There is a type of developer described as "wide and deep". This type of developer knows how to work in a team and at the same time masters the core technology of development. If they join the project, it will greatly improve the project progress and change the pace of the project. Without them, non-technical personnel will be stuck in some trivial details and stagnate. 4. What we need I'm currently making a list of everything needed to build a website and manage a host, which can serve as a basic guide for newcomers to learn technology. We modify the contents of the list through continuous discussion, hoping that this list can provide a good start for newcomers. The list we provide covers most of the knowledge needed for learning and development. There are classic and commonly used tools, as well as some new tools. In development practice, these tools are very helpful in promoting the progress of the project. The tool accumulation of excellent developers should be richer than knowledge of programming languages, CMS, and frameworks. Because you need scheduling, testing, CI, and enforced version control (teamwork, not just by yourself), and you can't just understand a few guidelines, you also need to understand the core concept of the project. 5. DevOps These auxiliary tools and techniques are applicable to the DevOps model (DevOps is a general term for a set of processes, methods and systems to promote communication, collaboration and integration between development, technical operations and quality assurance departments). For a long time, the competition between "operation" and "development" in the DevOps model has been difficult to distinguish. Operations is primarily about keeping things running. Development is used to create new things (often to stop things from working). This contradiction led to endless disputes between the two camps. If the developer does not fully understand the product, the functions he develops will often not match the product, and the code written in this way will not be suitable for the product. Because they did not consider the product's usage environment, their coding ignored the coordination with the product and focused on improving the functionality. Be aware that these details can lead to horrible latency, which is exacerbated by remote server management. If you want to be a good developer, you should learn in depth all the tools used in the development process. Once developers all learn how to use these tools, there will be great progress. Continuous deployment and the related practices of DevOps have become a standard, and developers or companies that haven't yet explored these concepts are falling behind. If you don't keep up with the pace of development, someone else will surpass you one day. There are many introductions to the concept of "DevOps" on the Internet. This concept is different from PHP, MySQL or Rails. It is a set of methods to reduce the risks of software and engineering collaboration. The DevOps concept focuses mainly on scheduling, automation, and keeping the production line running faster and better. If you use this development model, you will find that developers can have good teamwork between other departments and other companies. If they work with a third party via an API, they research what issues might arise on the other side. But if they work with server administrators, they only care about how they need to configure and how their software is installed on the server, which leaves a lot of problems. 6. Debugging Code Onion's CTO Michael Greer gave a great answer to the question about the skills that web developers must have: “Lazy”: Refuse to do the same thing twice - write a script or algorithm to do it “Cowardly”: Test frequently, worry about overload and code impact “Reckless”: Try new things frequently “Cowardly” is another word for attention to detail. You know, 99% of a developer's life consists of debugging and testing. What developers need to understand is that fixing an application requires more than just knowing how to pick out the error code; it also requires excellent problem-solving skills. For example, to solve the problem of users’ invoices not being able to be downloaded, you don’t need to spend a day developing the function of generating PDF files. You can simply set the page to printable. Sometimes a link can solve a problem better than a week of programming, and a programmer who only knows how to write code will find it difficult to think of such shortcuts. Despite the availability of a wide variety of testing tools, testing remains a curious blind spot for developers. Developers should learn to use unit testing, Selenium, load testing, and profiling tools like Xhprof. You should also learn to use some performance monitoring tools, such as NewRelic, which can help you keep your application as memory-intensive as possible. Debugging is also a key step in development. Therefore, developers should not only learn how to use debugging tools, but also know how to debug a problem - I would like to add a little bit of debugging to Michael Greer's list: "Impatient": Ignore unimportant issues and spend time solving real problems. The above are some basic principles. Developers must learn to grasp the main points and ignore the secondary ones. A true master developer can find problems without even looking at the code. Unfortunately, many people tend to blindly ponder an insignificant problem for dozens of hours or even days, and use the same method dozens of times to solve a problem.  Developers need to understand the business, operations, and business processes, which will be very helpful in development work. Only by understanding these can developers develop products that meet user requirements. Some developers can show extraordinary productivity not only because of their fast coding ability and profound knowledge of the stack, but more importantly because they understand the real needs of users. Going back to my original point, development is becoming easier and the market is becoming more competitive for developers. If you want to be more outstanding, you must understand business needs and develop products that satisfy customers. Therefore, developers should pay attention to the market. Understand how data changes over time. From a developer's perspective, these data should change along with currently popular or soon-to-be popular technologies. It seems that when your client comes up with a new idea, you should consider the actual needs of users and make a budget in advance. (In contrast, the worst-case scenario is when developers claim their new technology can solve all problems.) Developers need to master many aspects - such as understanding every field of the terminal database. If the data changes, how will the client display it? Is there a better way to solve the problem? Database administrators often think that the outside world's response to the database is very bad, but in fact they show the outside world a very bad database. The world is full of chaos and unexpected situations, and database administrators must learn how to deal with them. 8. Drawing and Writing Drawing is the most direct way to describe things. Developers must be able to present their ideas on a whiteboard or paper. A good developer should be able to express his intentions clearly by drawing prototypes on paper. It's hard to gain trust if developers only nod, talk, or use editors to demonstrate. The best code starts with a quick sketch prototype; failing many times will make you succeed faster. 9. Have fun If you have to spend dozens of hours to solve a problem, how would you deal with it? Learn to enjoy the process - even if it's just normal work. The worst attitude you can have as a developer is to have no interest in your team's work. Unfortunately this is a very common situation and it often happens because developers don't see themselves as part of a team. (Passionate programmers will make themselves "have more fun at work", you can try it too) Web and application development is still an emerging field, and the development of computer technology requires more advanced developers. Developers cannot be satisfied with the status quo and need to engage in advanced development as soon as possible to improve the efficiency of development work. 10. Stay sharp This is the last important thing I want to say: Stay sharp, seek competition, and be the most picky one in any team. The most critical and annoying developer on the team is often the one with the strongest development capabilities, while everyone else is often content with the status quo. If the team lacks these high requirements, it will easily lead to slow progress and reduced competitiveness. It is a good habit to improve your own requirements. Developers can also gain more experience through projects outside of work and learn to summarize the feedback and criticism they receive from these projects. The more criticism you get now, the less criticism you will receive in the future. When one day you start to consider the requests made by others more comprehensively, you will become a hot senior developer. |
<<: Docker Compose installation and usage steps
Recommend
HTML form and the use of form internal tags
Copy code The code is as follows: <html> &l...
MySQL optimization strategy (recommended)
In summary: 1. Consider performance when designin...
Simple implementation method of two-way data binding in js project
Table of contents Preface Publish-Subscriber Patt...
CSS3 realizes draggable Rubik's Cube 3D effect
Mainly used knowledge points: •css3 3d transforma...
FastDFS and Nginx integration to achieve code analysis
FastDFS & Nginx Integration: The tracker is c...
How to use mysql index merge
Index merging is an intelligent algorithm provide...
MYSQL master-slave replication knowledge points summary
An optimization solution when a single MYSQL serv...
What is a MySQL index? Ask if you don't understand
Table of contents Overview From Binary Tree to B+...
Detailed explanation of the six common constraint types in MySQL
Table of contents Preface 1.notnull 2. unique 3. ...
React.js framework Redux basic case detailed explanation
react.js framework Redux https://github.com/react...
404 error occurs when accessing the homepage of tomcat started in Docker mode
Scenario: When starting tomcat in docker (version...
Example of how to create a local user in mysql and grant database permissions
Preface When you install MySQL, you usually creat...
MySQL 5.5.56 installation-free version configuration method
The configuration method of MySQL 5.5.56 free ins...
A thorough understanding of js native syntax prototype, __proto__ and constructor
Table of contents 1 Introduction 2 Prerequisites ...
The latest graphic tutorial of mysql 8.0.16 winx64 installation under win10
In order to download this database, it takes a lo...