What do programmers do when they can t work on a project?

Programmers are developing sources when they can't make projects. When you're working hard and you're not getting results, the next step is to try open source. Many programmers build software for the pleasure of creating solutions and releasing them for everyone to use.

Some people publish ** that have been used by their programmers in commercial projects.

Think about what you would do if you were to solve it on your own. Then you can write pseudo** on the paper first, and then knock it out and run. In comparison with the teacher's ** to see what the difference is, and then make up for the shortcomings, so I am more impressed.

Even the best programmers run into unsolvable software engineering problems. Encountering such a problem does not necessarily mean that you lack skills or knowledge. Programming is not an easy job, and we can maintain the level of productivity you want by taking an unorthodox approach and ensuring that the submissions are of high quality**.

I think that when programmers can't work on a project, they should do something else to pass the time. Because I've tried all directions, but they just don't work. I lost hope, so I started to want to quit my job.

I felt like I should change jobs and become a bartender or something, at least researching and testing what to add to a beer wouldn't take me hours. <>

Personally, I still have to think about it. Writing ** is a creative process. It's like writing **, it doesn't mean that you can write a ** if you know all the words and know the sentence structure.

It's really not a quick fix. When you meet a need, you have to ponder, how can you achieve it? How to achieve better?

Use txt to jot down your thoughts first, so you don't have to rush to knock them. Think about it and write it later.

I think programmers take a break when they can't work on a project. If I spend hours on a problem and still can't find a solution, I end up feeling like it's a waste of time. I'm not talking gibberish – I just feel like "no one can die without regrets".

Then I'm going to take a break and rest my head.

Think about the idea clearly, and then roughly draw the modules you need, and write a pseudo** for each module. After the thinking is straightened out, we will refine it**. **It's about writing more and imitating others**.

When you write for a long time, you are proficient in language, and your thinking is straightened out, and you will naturally get up quickly.

When I can't write **, I swipe Douyin, watch the epidemic, eat melon seeds, and chase serials.

Take a break You've been in front of your computer for n hours. Typing on the keyboard is becoming a burden, and you wonder if the keyboard is the boulder that Sisyphus is pushing. Coffee cup after cup.

I didn't dare to drink it anymore, because I couldn't have ***, my heart was beating faster, my body trembled involuntarily, and I broke out in a cold sweat, but I still couldn't produce any **. <>

I wanted to take a break, but my mind was still thinking about it.

I'm thinking about how to return the project, and I'm thinking about the middle, and I don't have a foundation.

The syntax of Go is close to that of C, but it is different for the declaration of variables. GO supports the Junk feature. GO's parallel model is based on Tony Hall's Communication Sequential Process (CSP), and other languages that adopt similar models include OCCAM and LIMBO, but it also has features of PI operations, such as channel transmission.

Plugin support has been opened up, which means that some functions can now be dynamically loaded from Go.

If you can't write it, go to the community to see if there is anything similar for reference.

When programmers first worked, most of them were modifying programs, constantly reading books, reading cases, and reading **. In fact, it is still a very boring and monotonous job, but after this hard and boring life in the early stage, you can also experience the joy of the success of the program.

Xiaoqiang is a typical programmer, he studied computer science when he was in college, so when he chose the direction in his junior year, he also chose the real program system, and after graduation, he went directly to Beijing, because programmers are easy to find jobs in Beijing, and the benefits are okay. After Xiaoqiang entered a medium-sized company, he began his own path as a programmer. At the beginning, it was really boring and boring, simple work, is to deal with ** every day, every day with their own computer as a companion, the whole person looks very tired, but there is no way, just keep modifying the program**, and then combine it with other cases, or just look for books to read**.

In short, as a programmer, Xiaoqiang, in the two years after graduation, the daily work is almost like this, constantly researching, researching programs, writing according to the needs of customers, and then testing, modifying, and testing again, every day is almost the same content, but every day is different, although it is boring, single, but also very fulfilling, sometimes even in the middle of the night will remember, some of their own programs are not quite right, but can be more optimized.

Xiaoqiang felt that those days were very hard and tiring, there was no leisure life, few friends, and no time to fall in love. But when I see that the ** test I wrote is successful, and the program I wrote can be officially launched, the joy and excitement are indescribable, the hard work and sweat when I just worked, boring and boring, as if everything was worth it.

I'm not a programmer now, but I was close to becoming one, and I've been through their lives for months. So I don't know what it will look like after a few years of work, but I still know a little bit about what it was like when I first started working.

Needless to say, he must be a rookie, he should have just graduated from college or just came out for an internship before he graduated. It is estimated that the first feeling of newcomers to the workplace is, how is this different from what I learned in school! I don't know how it is now, and I don't know much about other schools, anyway, when I went to do an internship, I found that many of them were outdated technologies.

And the company for the newcomers who have just come in, usually will not assign any particularly important work, more will be assigned a master to take, although I did not have a master at the time, but the company specializes in centralized training for newcomers who have just arrived, that is, to tell the newcomers some of the skills used in the work first, just like a class, but to learn something closer to practical application.

I trained for about three months, and then I began to officially enter the job, but again, there will be no specific tasks, mainly to learn the modules that have been programmed by my predecessors, study the algorithm or design intent, and then get familiar with the working environment, that is, various configuration libraries or something.

Under normal circumstances, it takes about half a year to take over some simple modules, and then it is often checked uncomfortably.

So as a programmer who has just started your job, don't think that the tasks assigned to you are boring and useless, in fact, they are mainly used to learn, learn some experience, and avoid making some low-level mistakes in future work.

It is also worth mentioning that newcomers must not think too highly of themselves, no matter how powerful you are, you are just a newcomer, those who have been working for some years have been in the industry for so long, no matter how bad they are, they must still have some ability, so it is very important to have a good relationship with them.

Another thing that may be off-topic, when you first joined the work, try to be modest, even if you are really a genius, you have to look up to you, if Bole is just about to take a closer look at Maxima, but the horse suddenly kicked Bole down, I estimate that this horse is almost over in this life.

Get ready! Your work is about to face a myriad of knowledge and pressures waiting for you to master and rush to the project! Of course, hold on, and you will have a sense of accomplishment after the project is officially launched.

I don't know if you know anything about programmers, but it seems to be a very high-level job, most of which are engaged in the IT industry. In other words, IT is full of mystery, and all kinds of systems can be developed under the keyboard of programmers. However, those programmers also have a hard time at work, especially when they are just starting out.

So, what do programmers do when they first start working?

When I was in college, I majored in computer science, and after graduation, I worked in software testing in an Internet company, and many of my classmates engaged in development after graduation, becoming what everyone calls "programming apes". However, programmers are not so easy to do, although they have learned relevant knowledge in school, but they are only scratching the surface, and it is not enough to really become a programmer with only those knowledge in school.

At that time, there was a male classmate in the class who came out for an internship before graduation, and everyone knew that he was like an ignorant teenager who didn't understand anything when he first came out of work. So, most of his time is spent studying, learning various development languages and databases, he will go to work earlier than all his colleagues, use the morning to learn a little more knowledge, and in the evening after work all his colleagues go home, only he is still studying in the company.

How to say it, it is still difficult to work when you first come out, and the leader will assign you many tasks, but never ask you if you can do it, just look at the results you develop. So, in order to complete the task, they have to use their free time to learn those complex things. So-called programmers are sometimes not as easy as everyone thinks, especially at the beginning of the job, everything is very difficult, because the work tasks are complex and arduous, and they have to spend most of their time learning professional knowledge instead of doing boring things.

All in all, no matter what industry is not so easy to do, especially the programmer industry, when they first come out of work, they don't know anything, so they have to spend most of their time learning professional knowledge, only then can they complete their work tasks.

Hey, it's good that I can have a company to ask me now, after the cold winter of the Internet, now the recruitment requirements of enterprises are high, and the internship positions want to be left for school recruitment, and I haven't found a company after looking for a month, which is difficult.

One percent of the time is spent writing bugs, and the rest of the time is fixing bugs

Because I like it, I do it, because I live, because I want to contribute my own strength to the world.