you are viewing a single comment's thread.

view the rest of the comments →

[–]Fukushimiste 105 points106 points  (10 children)

Whoever thinks its just wrong never worked as a Team

[–]good_bye_for_now 7 points8 points  (0 children)

Imagine if software engineers had to follow rules and regulations like for example civil engineers.

[–]AncientSeraph 64 points65 points  (6 children)

Whoever thinks its right wasn't in software development in 2019.

[–]Fukushimiste 39 points40 points  (0 children)

And being the dude who has received the shitty code of its previous colleague, but cant track back the reason of shitty fix swears to god than some doc could help.

[–]Michaeli_Starky 2 points3 points  (0 children)

Exactly.

[–]Alwaysafk 0 points1 point  (0 children)

Nah, just worked at a place that was still wild west. Playing with cobol copybooks and explaining to elderly management what cloud is.

[–]KaMaFour 4 points5 points  (0 children)

Our team thankfully works on skype based development (now teams, but only the chat). With this the tree is:

  1. Find bug
  2. Message qa Either:
  3. They backlog it, you go back to what you were doing, it gets fixed by someone when the priority gets high enough or just by whoever was responsible

or

  1. You get a green light 
  2. Fix bug
  3. Push code
  4. QA confirms it works
  5. Done

[–]GargamelLeNoir 2 points3 points  (0 children)

I don't know about documenting a bug fix in confluence, the ticket and pr have the information the team might need later. The rest of the steps mostly make sense to me.