Timeline for How to effectively work with teammates whose fixes to bugs cause more bugs? [closed]
Current License: CC BY-SA 4.0
28 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jun 15, 2020 at 22:03 | review | Reopen votes | |||
| Jul 24, 2020 at 6:13 | |||||
| Jun 15, 2020 at 22:00 | history | removed from network questions | Thomas Owens♦ | ||
| Jun 15, 2020 at 21:59 | history | closed |
gnat Greg Burghardt Martin Maat Thomas Owens♦ |
Not suitable for this site | |
| Jun 15, 2020 at 17:25 | comment | added | Davor Ždralo | @Hans-MartinMosner - oh this is absolutelly a software engineering issue. Sloppy, un-reviewed code that doesn't follow best practices is not something for HR to fix. | |
| Jun 15, 2020 at 11:05 | comment | added | SJuan76 | A thing to consider is the root cause of those "hard to solve" bugs, "edge cases" and the like... Perhaps the design of the code could be improved so that code blocks are less complicated and easier to test? I have had to maintain code where every "fix" felt like dancing on a minefield. Of course, it is up to you and your team to asses if this aspect can be improved. | |
| Jun 15, 2020 at 10:30 | comment | added | Voo | @Jovash If you yourself are also a junior developer one thing I would consider is if you really want to work at a company where you don't have any opportunity to learn from experienced programmers. Sure you can learn about things like good development practices, devops and so on yourself too, but it really helps to have people who can mentor you and lead by example. | |
| Jun 14, 2020 at 23:44 | comment | added | Filip Milovanović | You might also want to try pair programming (not the whole time, but, say, 2-3 hours a day, few days a week) - have a discussion on that as a team; this will give you the chance to learn things from each other (and make no mistake, it is going to be a two-way street), and sort of bring up the base level of the "skill landscape" for the whole team. It will also let you work on communication skills and other aspects of being a team. | |
| Jun 14, 2020 at 22:12 | comment | added | historystamp | I'd suggest hiring a consult to give a seminar on basic software development strategies. | |
| Jun 14, 2020 at 22:07 | history | edited | Robert Harvey | CC BY-SA 4.0 |
deleted 614 characters in body
|
| Jun 14, 2020 at 19:40 | history | edited | Jovash | CC BY-SA 4.0 |
added 612 characters in body
|
| Jun 14, 2020 at 19:26 | vote | accept | Jovash | ||
| S Jun 14, 2020 at 18:57 | history | suggested | user142543 | CC BY-SA 4.0 |
I found a few bits hard to read. I've attempted to improve SPAG.
|
| Jun 14, 2020 at 18:39 | answer | added | n_b | timeline score: 5 | |
| Jun 14, 2020 at 16:17 | review | Suggested edits | |||
| S Jun 14, 2020 at 18:57 | |||||
| Jun 14, 2020 at 14:35 | history | became hot network question | |||
| Jun 14, 2020 at 4:47 | comment | added | Hans-Martin Mosner | @Jovash your comment and the answers already given show that the question has a significant SE aspect where I mainly saw the workplace/interpersonal aspect, so feel free to ignore my comment :-) | |
| Jun 14, 2020 at 0:11 | answer | added | gnasher729 | timeline score: 13 | |
| Jun 14, 2020 at 0:03 | comment | added | candied_orange | I'm going to argue against closing this question because there are solutions to this issue that fall under the umbrella of self organizing teams. | |
| Jun 13, 2020 at 23:57 | answer | added | candied_orange | timeline score: 30 | |
| Jun 13, 2020 at 23:52 | comment | added | Greg Burghardt | This would be appropriate for workplace.stackexchange.com, if that helps. | |
| Jun 13, 2020 at 22:59 | answer | added | Arseni Mourzenko | timeline score: 65 | |
| Jun 13, 2020 at 22:57 | comment | added | Steve | It seems to me to be an appropriate question of development method: how to handle developer peers of differing competence on a shared project. | |
| Jun 13, 2020 at 22:56 | comment | added | Erik Eidt | Those answers are pretty old, so might not reflect current reality here, I don't know. This site has changed focus several times over the years, meanwhile other sites have come about. | |
| Jun 13, 2020 at 22:17 | comment | added | Jovash | OK, I accept the rebuke. Though I don't understand how it is any more of a workplace problem than say, softwareengineering.stackexchange.com/questions/154733/… or softwareengineering.stackexchange.com/questions/162709/… | |
| Jun 13, 2020 at 22:17 | review | Close votes | |||
| S Jun 15, 2020 at 22:03 | |||||
| Jun 13, 2020 at 22:07 | comment | added | Hans-Martin Mosner | This isn't a software engineering problem, although it appears in the context of creating software. We don't know you or your colleagues, your company, your culture. How do you think we should come up with a solution to this workplace problem? If you don't have senior developer who can coach your colleagues, you may need to step in and provide guidance, possibly in the form of pair programming which is probably the least intrusive way to nudge them towards better solutions. | |
| Jun 13, 2020 at 21:48 | review | First posts | |||
| S Jun 15, 2020 at 22:03 | |||||
| Jun 13, 2020 at 21:47 | history | asked | Jovash | CC BY-SA 4.0 |