It shouldn't matter how long ago the original programmer left the organisation, SOMEONE should be responsible for that codehttps://twitter.com/jxxf/status/1219009311676030976 …
Show this thread
I'm going to use this decent thread as a platform for my own views Hey, fools, CODE IS LIABILITY, SOMEONE NEEDS TO OWN IThttps://twitter.com/jxxf/status/1219009308438024200 …
As of today, we have about eighteen years to go until the Y2038 problem occurs.
But the Y2038 problem will be giving us headaches long, long before 2038 arrives.
I'd like to tell you a story about this.
Show this thread
-
-
-
Someone is responsible for this code having no tests. It's not the person who left the companyhttps://twitter.com/jxxf/status/1219009313164943362 …
Show this thread -
All code is a liability. Code that nobody owns, nobody knows how it works, how to build it, what to do when it goes wrong, is a massive liability and a time bomb
Show this thread -
There is code that you own and you don't know you own it. There's code you know you own and you've never once looked at it. Get a spelunking task up on the board
Show this thread -
I mean, it might be nothing. But it might be you need to drop everything else and spend six months applying ten years of cumulative shirked security fixes. Until you look you don't know
Show this thread -
When I inherit code, I schedule time to investigate it. You always inherit bugs, tickets, incomplete work, unknown unknowns. If nothing else, people ease off when they know something isn't going to be their responsibility anymore
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.