How do you evaluate people who think programming is easy?

I recently entered a relatively small start-up company. The boss is a person who does not understand technology. Then the two of us completed the project according to the boss's needs. Halfway through the project, the boss came over to check on the progress and started to ask us why it was so simple. It took so long to make something, and it only started on two Tuesdays. I have only one backend and one frontend to assist in the requirements, architecture and design of the entire system. Many things were considered in the later stage, including using webpack, jq, vue.js, and js for the front end. Use PHP and Laravel frameworks for the backend, and use composer management packages to minimize reinvention, such as overtrue's easywechat, etc., to shorten development time as much as possible, and the progress can be followed by the git version controller. But I started to feel that my boss didn't respect the technical staff, and I couldn't stand it. How should I treat those who think programming is easy?

Reply content:

There are many types of people who think programming is easy. Some people not only understand it themselves, but also have good basic skills and solid skills. Maybe your job is just a simple and easy task in their eyes. Of course, you should humbly ask for advice from such people. After all, it is rare to meet them.

As for the type of boss you have, is he probably the legendary one who has everything ready and only needs the coder? Usually in this situation, it's better to talk about salary increases or something; if you have solid skills, you can also talk about finding a few subordinates, but if that doesn't work, just quit. If the salary is very high, it will be related to whether you are worth the price; if the salary is very low, it will be related to the issue of whether it is worth doing.

It’s normal for people who invest in entrepreneurship not to think highly of technology, because in most cases the technology stack these people need is not necessarily too complicated, and you are not irreplaceable. People will always think that programmers are looking for Just come, it’s his capital and ideas that make money. If you don't understand it yourself, it is only possible for you to change this view if you have suffered a defeat yourself.

I hope your leaving will be his loss. In your case, you should have agreed on a construction period and a plan before starting work. What your boss cares about is the timing and results, not the technology you used. Of course, he can't estimate that he hasn't asked you yet, and it's his fault. . Put aside these money-related factors.

I had a roommate in college who always thought the code I wrote was simple, but he didn’t know that what he wrote was worse than shit in my eyes. His technical skills have been in ACM for half a year without winning any awards. He often writes projects for school teachers. He knows a little bit about backend, java, and python. He likes cloud computing, big data, data mining and other advanced things. Nouns, without any mathematical foundation but keen on these things. He once told me that in his eyes, computers only have three things: databases, computer network principles, and operating systems. I also tried to correct him and told him that graphics, PLT, algorithms, compilers, distribution and other things are also very interesting, but it was all in vain. He often shows off things like identification codes to me.

The conclusion I came to is: don’t discuss technical issues with people whose vision and skills are lower than yours (a while ago, there was a PhD student who didn’t know how to get into MIT and insisted on telling me that he must use Python to get started). Your boss may not understand how cool or difficult these technologies are. He just wants a result. Just do what you should do. I'm curious to ask how much work is required for this project of yours?

How familiar are you with webpack, jq, vue.js laravel composer?
How familiar is the front-end with webpack, jq, vue.js...
Just curious... Here’s some useful information, because working programmers will encounter this kind of problem at one time or another.

The boss comes to catch up on the progress
How to deal with it?

First smile, pretend to be a veteran who has written 100 billion lines of code, and take it out gracefully Details of requirements (what, you don’t have?), tell him that some seemingly simple functions require writing a lot of code. This sentence is not an explanation or an excuse, but an attitude of me telling you a fact.
A random picture is being developed Requirements detailed flow chart, you can also add the time you spent.

Then, after the function is ready, it still needs to be tested. If, boss, you find a test girl, the development progress will be much faster. It’s normal for the boss to not understand technology. If he understood it, what else would he need from you? This is the same everywhere
The most important thing you should do now is to let him know the logical flow of development and all the details that need to be considered during development, so that he understands that the program is not as simple as he imagined...it will be easy later.
If by chance he doesn’t understand you, then there is no way to follow your heart~ Answering "How to evaluate people who find programming easy" will not solve your current situation.
The reason is that this person is your boss, not a passerby that you can ignore.

What you need to solve is "how to face the boss who thinks programming is easy".
You can report your current work content to your boss according to his needs, so that your boss can realize the progress and importance of your work.
Or you can find a company that respects technology more, and you won’t have the problem you have now.

I don’t know how long you have been working. Maybe you need to know that “communication with non-technical people is also a very important skill for technical people”. If it's true as you said, then there's no point in giving in. A layman can't understand an expert, but he must respect an expert. I suggest a detailed description of the development schedule of the entire system and a detailed breakdown of the function points.
Clearly describe the development time of each function point, accurate to human days, and then add buffer.
Explain clearly how long it will take to meet product requirements and why. In fact, it is the same as persuading the PM. The boss here is the PM. He proposes product requirements to the technical department and conducts repeated discussions and finalization. Then we make a development schedule based on product needs. If the boss doesn’t agree, we’ll discuss it again. Whether it’s cutting down product features or adjusting the architecture, it’s okay.
In this way, the boss will know the specific reason. I suggest you try it Isn’t this what our boss is talking about? During group meetings, he told me every day that this is simple and that is simple. As a result, sometimes I heard him talk about many basic aspects with small problems. Don't know how to communicate at all. . .