News for hackers. Stuff that matters.

A comment on Keeping a plaintext “did” file. Parent comment

Re:Keeping a plaintext “did” file by Tade0 on Monday July 16, 2018 @08:17AM (#17540669)
I would do the same if I weren't afraid of coming off as passive-aggressive given that I voiced my opinions in the past but received a reply in the vein of: "We're aware that this old code is really bad, but with our constrained resources we need to prioritize keeping this boat afloat.".
[ Parent | on HN ]
Re:Keeping a plaintext “did” file by noxToken on Monday July 16, 2018 @09:27AM (#17541076)
I keep mine locally. I have the PlainTasks[0] package installed for Sublime Text. It's a plaintext file with a bit of TODO functionality baked in. When I find something, I note the commit, the line (or block), and why I want to fix it. I try to slightly estimate high enough that I could throw some fixes in for the sprint.

[0]: https://github.com/aziz/PlainTasks

[ Parent | on HN ]
Re:Keeping a plaintext “did” file by contravariant on Monday July 16, 2018 @09:49AM (#17541204)
At some point you do need to stop baling water and actually plug the hole though.
[ Parent | on HN ]
Re:Keeping a plaintext “did” file by corey_moncure on Monday July 16, 2018 @11:35AM (#17542106)
Nah. The bridge crew all have executive lifeboats. No biggie if the ship goes down.
[ Parent | on HN ]
Re:Keeping a plaintext “did” file by sillyquiet on Monday July 16, 2018 @02:38PM (#17543779)
To completely and hyperbolically torture this metaphor, as long as you whip the galley slaves to row fast enough so that you can jump to safety on "Short Term Stock Gain" Island, you'll be fine.
[ Parent | on HN ]
Re:Keeping a plaintext “did” file by JustSomeNobody on Monday July 16, 2018 @10:37AM (#17541579)
They should teach this at MBA school. But they don't.
[ Parent | on HN ]