preface

If I can’t be the best Java engineer, I’ll be the best front-end engineer among Java engineers. Some time ago, I silently fed myself this bowl of chicken soup for the soul… I am not a very good Java engineer. Even though I have worked for eight years, I still feel there is a big gap between myself and the top engineers. However, I have one advantage, that is, I am optimistic and stubborn about learning, and I will often suggest myself to move forward, even if I can’t do anything. Three years after I started working, I realized one thing: I am not particularly smart and savvy, and I am slow in understanding technology. Even if I often stay up late, I cannot solve some very simple problems in my work. A girl once said to me: If you are not very lucky, please try very hard. This is my motto in life. If you want to keep motivating yourself, you need one. So I set a motto for myself from then on: if I can’t be the boss, I’ll be the boss’s heel. I’ve been doing this for years, learning from others, summarizing others, and finally turning into my own.


The front-end is the future of the back-end

Before I get to the cause, I want to talk about the front end from the perspective of a long-time Java programmer

I’ve always been in awe of the front end, because it brings the most intuitive design to life, with a lot of beautiful and rich effects just from some CSS and JS code. In the past, engineers did not know the front and back ends at all. They could copy and paste the back end Java and copy and paste the front end JQuery directly, so they could make pages and data. After the bootstrap came out, more front-end ideas and changes were brought about. Angular, React, and Vue ushered in a new revolution. The author of layUI had to face the reality and shut down the official website to open source, which became a memory of the era of JQuery. I was disappointed and depressed for a while. I have never written CSS seriously since I became a Java programmer. If I can copy it, I will never write it by hand. If I can achieve it, I will never understand it very well. Even though the front and back end were separated, I still kept an open mind to learn vUE after it appeared, believing that it was a required course for back-end programmers. If I gave up abruptly, I would lose my competitiveness. But my CSS, the past eight years still stay in the primary stage, never improved. Until recently, I was fed up with the arrogance of some front-end engineers for work reasons.


What causes

In small and medium-sized Internet companies, the front end often bears greater responsibility than the back end. At least the two companies I have worked in are all one or two front ends and a large number of back ends, which is destined to have a special position in such companies. It’s not the first time I’ve been frustrated by a few grumpy front-end engineers at work since the front end became self-contained. Whether it’s drawing pages or interfacing interface, there’s a sense of superiority everywhere. I almost thought I was interfacing with an American, not a Chinese. At a regular meeting last week, due to gradually heavy work tasks and great pressure on the front end, the supervisor proposed to let me, the back end, undertake a small part of the tasks on the front end. As a result, the front end suddenly exploded, thinking that it would pose a threat to his work value. “He can’t even draw a page in a day,” “He will write a front-end engineering mess we have to clean up after,” and so on, the neck of the tantrum gave me a big shock. I don’t like to bring my emotions to work, but that doesn’t mean I don’t have any. Especially to say that I can’t draw a page in a day is an insult! Can I stand it? I put up with it, because I won’t. As the saying goes, people live a breath, the tree live a skin, I have never stopped learning these years, I asked you to learn Java you can learn? You can’t be tired! But you asked me to learn front-end I must be easier than you learn Java. So I had this tone in my mouth and said that I wanted to make a breakthrough in CSS, so I made a plan right away.


Learning methods

It’s not CSS that’s hard for Java programmers to master right away, it’s Java, you heard it right, because there’s so much to learn in Java that it’s hard for you to succeed in a technology you don’t care about. It’s simply a matter of energy. But Java programmers also have their own ways to quickly learn CSS. Here are some of the lessons I learned this week:

1) Only master the most basic syntax, such as width, height, margin, padding, color, border, etc. Some partial syntax may be useful, but it is not worth your time to learn it in depth. 2) Start with layout, especially flex syntax. I can say that the most useful flex syntax for Java programmers is flex syntax. It works on both PC and mobile devices, so I recommend learning flex syntax. Here are some screenshots of my Flex notes, but you can also jot down key points like I did, because Java programmers tend to forget these things and can watch them over and over again to form a permanent memory.

3) Master a few uses of Photoshop, mainly used to calculate spacing or width and height elements, and use straws to obtain color parameters. At the beginning of learning, it is the most convenient and practical choice to directly put the screenshot of a website into Photoshop and directly refer to others’ values and color matching;

Calculate spacing:Take the background color:

4) learn F12 debugging, mainly used to refer to the style of the website and platform, many can be used for reuse, and can learn a lot of CSS style writing.

5), the best and fastest way to learn CSS is still to imitate, find a website, imitate a page inside CSS copy, this way can not only quickly enter the state, but also learn a lot of things, the most important, can directly make the effect you will be very motivated.


My achievements

I did a quick study of the above methods, especially the Flex syntax, and then went straight to the front page of the nuggets and started copying. In the weekend holiday time, with this tone, from 8 o ‘clock in the evening, until more than 4 o ‘clock in the morning, finally completed my first serious study of CSS in eight years. Many front-end saw might make fun of me, a simple home page should spend so much time to complete, but I feel very happy, I think I’m starting at this time, real understanding of how a picture with full page, also more sure his future direction: to do the most severe front-end engineer in Java engineer.


Afterword.

The original intention of sharing this article is to hope that those Java programmers or other programmers like me who have hesitated can find themselves, a little bit of breakthrough themselves, not afraid of learning bad, afraid of you do not learn ah. I copy write nuggets page and style files will be shared, partners can follow the reference, interested can also try to copy write down the home page or other pages, every line of CSS is my hand. Link: pan.baidu.com/s/1QQkwcpNU… After I will spend time to learn and accumulate while writing a background management system, pure page does not contain the kind of business functions, because I do not like to contain miscellaneous miscellaneous eight content, like clean shelf, business I go to write. There will also be a version that includes Vue and elementPLUS, and most importantly, I will write the documentation for you to learn, and I will explain the implementation step by step through the article, and take you step by step to achieve the effect. Interested in small partners can pay attention to me in advance oh ~



I focus on sharing the fun and experience in my work. If you think there is any help, please click a like or save it