New answers tagged

0

A small team is often more likely to ignore design elements that contribute to maintainability and scalability, i.e. SOLID design principles: Single responsibility Open/closed (extensibility) Liskov Substitution (Implementations with the same interface should never give different results) Interface segregation Dependency inversion. High level modules ...


0

So my question is if it really so important to have such experience, since I saw many posts that some members of big team just do some dirty job and do not see the whole picture? Teamwork is important but the size of the team doesn't really matter. With this in mind I would say that you work in a larger team than you are making out. This is because you don'...


3

There are things to do differently in a large team. For example, if you are a team of two, you won’t have many merge conflicts (which are a pain), so if you let things go a bit little harm is done. If you’re in a team of 15, if the team doesn’t handle pull requests immediately, you can get into a pretty bad mess. Anything you do affects 14 other people, not ...


6

Depending on what types of jobs you are looking for, working in a large team is not necessarily important. However, there are elements of development that either do not make sense, or do not really show up, until there is a large enough project, or a large enough group of developers working on something. One example can be dealing with source control and ...


8

An interviewer referring to your experience as "child programming" is insulting and unprofessional to say the least. That's not even a grey area. You've probably dodged a bullet with that one. As for your actual question: Yes, experience working on large teams is important, but it depends on the position you're going for. Most companies require ...


Top 50 recent answers are included