- When a developer proposes with beaming pride to trim error stack-trace to a few lines, to reduce logging footprint. ðŸ˜ðŸ˜ðŸ˜ðŸ˜ðŸ˜
- When a Tech Lead does not show technical inclination to learn things. ðŸ˜
- When a Tech Lead takes boasts of attempting to fix memory leak in enterprise java application by uploading code/memory-dump to third-party site thus breaching corporate security policy. ðŸ˜
- When a Manager/Management is callous about blatant breach in security practices and does not take mitigation/containment plans. ðŸ˜ðŸ˜ðŸ˜
- When a Program Manager has no clue about the Product Roadmap and doesn't care about the big-picture. ðŸ˜
- When a Program Manager has no clue about the Program Roadmap and doesn't care about the big-picture. ðŸ˜
- When a Product/Program Manager attempts to steal the credits of the technical work done by developer(s). ðŸ˜
- When Project teams crave for individual credits over working together with other stakeholders to achieve the big organisational vision. ðŸ˜ðŸ˜
- When the Management is focused in vendetta politics instead of working towards the program milestones. ðŸ˜ðŸ˜ðŸ˜ðŸ˜ðŸ˜
- When developers partake in management politics of cannibalism for quick wins instead of long term team harmony and learning together. ðŸ˜ðŸ˜
Got even nastier things to share? Don't hesitate to dump your thoughts over comments and maybe feel a little lighter. Cheers!
