From junior to senior
I'm a young developer. This is the third year since I started to work. During the last year, I was always asking myself what's the difference between the undergraduate, the junior, and the senior developer? In the latest one to one meeting with my manager, I found kind of the difference. The undergraduate developers learn new things. The junior learn how to do things well. And the senior focus on valuable things.
When I was at university, I need to take lots of courses, do projects, and pass exams. There's no denying that I study hard, but in fact, I have no idea about the project I did is useful or not in reality. I don't understand the true meanings of "composition over inheritance" that I wrote in the exams. It looks like if you get higher notes than your classmate, you do a better job. But definitely not. The undergraduate education follows a rule of the more the better. You get higher notes because you implement an extra function in your project. However it's really a bad design which makes the app difficult to use. While your classmate uses a design pattern to make the project more scalable, but it's not what your professor looking for. Because of the lack of feedback, I don't know what's good and what's bad, I can't improve my skill.
When I started to work in a company, the first lesson I learned is that there's no more one-shot project. The code you add to the project may be touched again after one month, one year or even ten years later. So your code must fellows some standards and has good quality. I have improved my code quality from the feedback of the code review. I have learned how to make a trade-off by discussing the different solutions with my colleagues. As a junior, I try my best to deliver each feature assigned to my with good quality, but I never think about why I need to implement this function, what's the value of it.
In the last one to one meeting, my manager told me he is preparing a big feature for our team to work for the next four months. He explained a bit about the context of this feature. In the end, he said that he needed to do some study on the feasibility and the cost of the feature to see if it's worthy to do like that. I realized when I was working on each small feature, bug fix, or assigned tasks, my manager was thinking about the evolution of the project. Among the different directions, what's the most valuable one.
Search from various English teachers...
Corrections · 1
1
From junior to senior
I'm a young developer. This is the third year since I started to work. (better: it's been three years since I started working/this is my third year of working) During theOver the last year, I was always I've been asking myself what's the difference is between the undergraduate, the junior, and the senior developer? In the latest one-to-one meeting with my manager, I kind of found kind of the difference. The undergraduate developers learn new things. The juniors learn how to do things well. And the seniors focus on valuable things.
When I was at university, I need had to take lots of courses, do projects, and pass exams. There's no denying that I study hard, but in fact, I have no idea aboutwhether the project I did is useful or not in reality. I don't understand the true meanings of "composition over inheritance" that I wrote in the exams. It looks like if you get higher notesgrades/marks than your classmates, you do a better job. But definitely not (better: that's definitely not the case). The undergraduate education follows a rule of 'the more the better'. You get higher notesgrades/marks because you implement an extra function in your project. However it's really a bad design which makes the app difficult to use. While your classmate uses a design pattern to make the project more scalable, but it's not what your professor is looking for. Because of the lack of feedback, I don't know what's good and what's bad, so I can't improve my skill.
When I started to work in (better: for) a company, the first lesson I learned is that there's no more one-shot project. The code you add to the project may be touched again after one month, one year or even ten years later. So your code must fellows follow some standards and has have/be of good quality. I have improved my code quality from the feedback of the code review. I have learned how to make a trade-off by discussing the different solutions with my colleagues. As a junior, I try my best to deliver each feature assigned to my me with good quality (I think 'to a good standard' or just 'well' would sound more natural here), but I never think about why I need to implement this function, or what what's the value of it is.
In the (better: our) last one-to-one meeting, my manager told me he is preparing a big feature for our team to work on for the next four months. He explained a bit about the context of this feature. In the end, he said that he needed to do some study (better: research) on the feasibility and the cost of the feature to see if it's worthy to do worth doing it like that. I realized when I was working on each small feature, bug fix, or assigned tasks, my manager was thinking about the evolution of the project. Among (better: Of) the different directions, what's the most valuable one which one was the most valuable.
Want to progress faster?
Join this learning community and try out free exercises!
Don’t miss out on the opportunity to learn a language from the comfort of your own home. Browse our selection of experienced language tutors and enroll in your first lesson now!
Start Learning Today
