Timeline for Boss and Boss's Boss have differing philosophies on code, I'm caught in crossfire
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 18, 2018 at 17:23 | comment | added | Stian | @Erik well, I'd put whatever that goes ping pong between B and BB in a standard. No need to standardize that which doesn't create problems. | |
| Apr 18, 2018 at 15:12 | comment | added | Erik | You might want to expand on everything you should put in the document, then. The coding standard guidelines I've seen are all about how to layout code and sometimes a bit about naming things, not about how to solve the actual technical problems. | |
| Apr 18, 2018 at 15:10 | comment | added | Stian | @Erik how so? If both provide input and agree on it, there should be no problem with either style or substance? | |
| Apr 18, 2018 at 15:07 | comment | added | Erik | This only works if the problem is purely one of style, not of substance. | |
| Apr 18, 2018 at 6:07 | comment | added | Stian | @Nij hah =D Well, if you have witnessed the power of bureaucracy when it is working in your favor, it is hard not to be a disciple. | |
| Apr 18, 2018 at 5:54 | comment | added | user53718 | -1. Didn't mention documentation often enough... | |
| Apr 18, 2018 at 5:39 | history | answered | Stian | CC BY-SA 3.0 |