We can talk about this for a long time. In short, treat each line responsibly. Fourthly, responsibility. No one will really check your code, or rather, understand how it works. All your mistakes will pop up during testing or in production. You need to take the initiative in solving problems. Somewhere you will have to immerse yourself in the business process, correspond with other people, hold meetings.
Regardless of the difficulties. So, how the process goes. The main bosnia and herzegovina whatsapp fan person in the team - the product owner - sets a business task that will bring profit to the product. The system analyst works out the task: thinks over the process in the system, draws up requirements, writes documentation. Then the task is given to the tech lead, and he gives it to you.
No one will tell you how to solve it, you only have a requirement for how it should work. Almost always you need to learn a new library. I will throw in some examples of tasks: - Make authorization using a jwt token. - Accept a request via http, save it to the database, make an xml of a certain format from it and send it to mq.
You are expected to produce results
-
- Posts: 506
- Joined: Sat Dec 28, 2024 3:24 am