The tip of the iceberg
Having mentioned earlier about technical specifications I realized that I’d like to discuss it deeper. Though at first, I’ll present a general description of how a software development team works.
I’d like to note two major points: everything is based on my personal experience, and there is no way to grasp an entire range of possible situations in great detail. Let me explain the latter: nowadays companies, developing software, vary in their sizes and spheres so that it can be a start-up with 2 software engineers, it can be a bank with a thousand employees or it can be a giant corporation consisting of one hundred thousand employees. As you might have heard software development itself falls into different specializations, though a well-known frontend/backend dichotomy is not comprehensive, for instance, it doesn’t cover the following: driver development, embedded development, Windows-based game development, and so on. Plenty of programming languages and frameworks are out of the current discussion scope because I want to focus on how processes are organized rather than coding here. Let’s also close our eyes on other roles in a team that can also accidentally write code: DevOps, QA engineers, etc. Last but not least: personality traits of a team leader as well as other team members, on one team a team leader, has read a book about Scrum and now they groom their backlog every day and have all sorts of meetings, in another place everyone has decided that Scrum is too complicated, so their team leader tries to split tasks themselves, finally in one more place a whole IT department consists of two people who work as they can without time or intention to read books about how it’d be perfect.
So, in future posts, I’ll tell you about different roles involved in software development, and how the processes can be organized, little by little, I'll come to examples of successful and unsuccessful cases from my personal experience. Finally, after all the introduction we’ll come back to the technical specifications. Stay tuned!
#job #IT #General #Introduction
Having mentioned earlier about technical specifications I realized that I’d like to discuss it deeper. Though at first, I’ll present a general description of how a software development team works.
I’d like to note two major points: everything is based on my personal experience, and there is no way to grasp an entire range of possible situations in great detail. Let me explain the latter: nowadays companies, developing software, vary in their sizes and spheres so that it can be a start-up with 2 software engineers, it can be a bank with a thousand employees or it can be a giant corporation consisting of one hundred thousand employees. As you might have heard software development itself falls into different specializations, though a well-known frontend/backend dichotomy is not comprehensive, for instance, it doesn’t cover the following: driver development, embedded development, Windows-based game development, and so on. Plenty of programming languages and frameworks are out of the current discussion scope because I want to focus on how processes are organized rather than coding here. Let’s also close our eyes on other roles in a team that can also accidentally write code: DevOps, QA engineers, etc. Last but not least: personality traits of a team leader as well as other team members, on one team a team leader, has read a book about Scrum and now they groom their backlog every day and have all sorts of meetings, in another place everyone has decided that Scrum is too complicated, so their team leader tries to split tasks themselves, finally in one more place a whole IT department consists of two people who work as they can without time or intention to read books about how it’d be perfect.
So, in future posts, I’ll tell you about different roles involved in software development, and how the processes can be organized, little by little, I'll come to examples of successful and unsuccessful cases from my personal experience. Finally, after all the introduction we’ll come back to the technical specifications. Stay tuned!
#job #IT #General #Introduction