5 ms·

When I was younger I always assumed all the tracking had value. After a decade of working, it’s all a facade. And all these people are constantly trying to be m

When I was younger I always assumed all the tracking had value. After a decade of working, it’s all a facade. And all these people are constantly trying to be managers which explodes the amount of documentation

A4ET8a8uTh0 4y ago
Some tracking has value. Last year I did some testing. Its results were recorded for posterity. A year later, for god only knows what reason, production environment differed slightly from testing environment a tiny little bit. Records allowed for a relatively quick follow up with vendor and resolution. But it goes back.. how do you know something will be important?
- Kamq 4y ago
  Can I ask how people found it a year later? Everything always ends up on a confluence dumping ground, and I have trouble finding pages I wrote after any sort of significant period of time, much less finding things other people wrote.
  - A4ET8a8uTh0 4y ago
    To be honest, I think it is my history with the vendor. I know them to be flaky so I keep anal documentation of minute changes one version to the next. It is genuinely just an excel spreadsheet, but there is a focus on changes they introduce along with dates since I was burned before. The issue was fairly unique and actually tested for and the list of implemented defect fixes in testing env. was listed on our end ( and maybe for once the fact we don't use confluence helped ), which helped to narrow it down on the vendor's side ( I am not sure what they use internally ) and it certainly helped that there were only two related projects for that specific move for the date the issue occurred. FWIW, it is possible that I am just still relatively new to this ( 3 years for the testing part ) so all the issues we experience don't all blend together yet. edit: Apologies, as I re-read it, my response feels fairly generic, but I am not sure I can discuss more details.
    - Kamq 4y ago
      Ahh, I see. I think I can see the value in tracking kept by a person for themselves to troubleshoot things in the future. But I can't imagine that's the kind of tracking greatpostman had in mind, and it's definitely not the kind of tracking that most managers I've worked with try to produce.
      - A4ET8a8uTh0 4y ago
        Its my bad. As I re-read parent, I think you are right. It does not really apply. I would delete my comment, but it is too late at this point.

A4ET8a8uTh0 4y ago

Some tracking has value. Last year I did some testing. Its results were recorded for posterity. A year later, for god only knows what reason, production environment differed slightly from testing environment a tiny little bit. Records allowed for a relatively quick follow up with vendor and resolution. But it goes back.. how do you know something will be important?

Kamq 4y ago
Can I ask how people found it a year later? Everything always ends up on a confluence dumping ground, and I have trouble finding pages I wrote after any sort of significant period of time, much less finding things other people wrote.
- A4ET8a8uTh0 4y ago
  To be honest, I think it is my history with the vendor. I know them to be flaky so I keep anal documentation of minute changes one version to the next. It is genuinely just an excel spreadsheet, but there is a focus on changes they introduce along with dates since I was burned before. The issue was fairly unique and actually tested for and the list of implemented defect fixes in testing env. was listed on our end ( and maybe for once the fact we don't use confluence helped ), which helped to narrow it down on the vendor's side ( I am not sure what they use internally ) and it certainly helped that there were only two related projects for that specific move for the date the issue occurred. FWIW, it is possible that I am just still relatively new to this ( 3 years for the testing part ) so all the issues we experience don't all blend together yet. edit: Apologies, as I re-read it, my response feels fairly generic, but I am not sure I can discuss more details.
  - Kamq 4y ago
    Ahh, I see. I think I can see the value in tracking kept by a person for themselves to troubleshoot things in the future. But I can't imagine that's the kind of tracking greatpostman had in mind, and it's definitely not the kind of tracking that most managers I've worked with try to produce.
    - A4ET8a8uTh0 4y ago
      Its my bad. As I re-read parent, I think you are right. It does not really apply. I would delete my comment, but it is too late at this point.