Tag Info

Hot answers tagged

12

Your concerns are extremely valid. Especially the first two points about Team A not having the time to add features or fix bugs that impact Team B. I've seen this happen at my own job quite a few times. This might be a good idea if: It is known that Team A will be working on the projects that require new features in the database, while Team B's goal is ...


5

When releasing a new version of a program is it better to include the full changelog since the beginning of the project or just the part since the last release? Neither. Only provide the relevant, bigger changes that an end user is going to care about. No one cares about the fact that you refactored class Foo so that it can be re-used a bit more ...


3

When I go through the code for an already developed application, I can see that there are some bugs These small bugs should be found during dev testing and after dev testing developer should also run the application to make sure it works as expected before passing it to QA so right there already something is not going very well. I inform the QA team ...


1

A lot of it is about communication skills. You should also know that being skeptical about new tools is common in software industry. More on this later. First: Your Mindset You are not selling so don't feel like it. You are kindly presenting a solution to a common problem so be confident. (Actually if you were marketing a product, you would also be ...


1

Yes, you should. Software quality is the responsibility of everyone on the project. Ok, let me backpedal immediately... you should actually open the bug yourself, if that's what your manager says you should do (after checking to make sure it isn't already reported). Having a wall between the two groups is counter-productive, in my opinion, because it ...


1

I can only tell you what I do. First, if you see a bug then it's "your fault" and you should enter it into the tracker, write a test case proving the bug, fix it, and submit the fix. If the QA teams sees a but then it's "their fault" and should be entered in the tracker with steps to reproduce. Now it's not really about fault, it's more about long term ...


1

I worked for a number of high-profile corporations. It was always gladly accepted if a person opens a bug when [s]he discovers a bug. No matter who that person is, and whose responsibility that bug might be. If somebody could be offended by having a bug filed against their code, these people act utterly unprofessionally. A developer should be as egoless as ...



Only top voted, non community-wiki answers of a minimum length are eligible