This is an article about my thoughts on .NET internship development after 3 weeks of employment

This is an article of reflections on .NET internship development after 3 weeks of employment

Tucao

Let’s start with a bit of rant!

The first thing I complain about is the issue of overtime pay. The company pays a lot of overtime pay, but I am in the probation period (3 months) and I don’t get overtime pay. However, my team leader in the company likes to work overtime and always asks me if I can work overtime. , people who know a little bit about human nature will work overtime together. Although the company stipulates that you get off work at 17:30, you basically start leaving at 18:00, and then you usually leave at 8:00 for overtime work, so if you don’t work overtime, you actually work 8 and a half hours a day, and if you work overtime It was 10 hours, and then it was the end of the year. I had been here for three weeks and only experienced a one-week weekend.

After complaining about working overtime, it’s time for company projects. Company projects are divided into old projects and new projects. I spent one week learning new projects, one week learning old projects, and in the third week I started writing business code. The old project is .NET Web Form. It’s really a headache. Basically, maintenance is carried out on the old code. The new project is also based on the .NET MVC project framework. It is not a cross-platform Core, but it is barely better than the old project.

Then there is the business code. Basically adding, modifying, querying, and deleting are all stored procedures! After graduating from college, I was used to EF’s linq+lamda expressions when writing projects. It was really annoying for me to write stored procedures. If I had to use stored procedures for business, there was no way, but my team leader seemed to be a fan of stored procedures. , everything is written using stored procedures. There is a lot of logic in the stored procedure, and I am not very good at writing, so it is easy to fail to complete the task on time, and then be dissed.

Then there is the problem of task arrangement. Basically, I don’t have time to fish, and the assigned tasks are very full. And when I am doing the task, this task is still completed, and other tasks come, and then the team leader tells me how to get there. After finishing it, I can’t remember it, and then I will be dissed.

Summary

The treatment is pretty good.

There are many tasks and it is easy to be dissed.

Stored procedures are a headache, and I miss lambda expressions.

Sure enough, there are no programmers who don’t work overtime