duykhoa12t

Before I start working on a project, I spend a couple of minutes to read and understand the logic of the current code base related to the change. By doing this, it naturally reminds me about the language syntax, the framework, the project convention, and the team's best practice. If you do it regularly, you will feel it more natural. Most of the modern languages' projects are easy to identified the scope of changes. Don't pay too much attention to the languages syntax, but rather to the logic.

Same to me. I store the note folder to a private gitlab repo, and write a bashscript function to commit and push the note.

How Google works https://www.howgoogleworks.net/

Those ideas and principles of building a successful Google, from making great product, build the great culture and hiring the smart creative people.

Did she mean daily rate? I wonder if a junior ask for this rate, of course the company has no chance to afford a senior dev.

I read from https://robots.thoughtbot.com/.

I totally agree with you. We tried, but things aren't expected

I think you have no trouble with typing, because you care too much for your code quality, it makes you slow. However, you are doing good thing for other people - who will work on your project and for yourself.

Checkout Rack (https://github.com/rack/rack) and Hanami (https://github.com/hanami/hanami).

I myself learn a lot from these projects. The code is clean, with good tests and documents.

Thanks for your answer. I am thinking about this. I just wonder like beside your career, we still consider about family, house... If we want to move around the side role, how can we move to the next step of our career. Or you think we don't need to think about going to next level, but explore the skills set is more valuable?

Good news. hehe. Could you share me how do you update the new technique, or you are using the same techniques you've learned several years ago. Sorry if I used a heavy word. But I saw myself out of date too quickly, and I don't think I can catchup the trend in the next few years. But I really want to do web development, or should I move to the next step as many people - to be a manager?

OK, that's good thought, hehe. I am forcing myself to improve a lot, not for this current job, but to catch up with the community. I am not sure I can continue doing it after 30, cause too many things to learn and gonna burn out myself.

you're right. But the problem with 30's developer is lack of opportunity to learn. Ok, for the current job, you know very well about system, architect. But you know, we're focusing to much about the current technique, the current system, and we limit ourself in learning new thing, and our learning curse is much slower than younger developers also.