Comment by uticus
1 year ago
> make a copy and slightly modify it
In addition to not breaking existing code, also has added benefit of boosting personal contribution metrics in eyes of management. Oh and it's really easy to revert things - all I have to do is find the latest copy and delete it. It'll work great, promise.
I mean…when you have a pile of spaghetti, there is only so much you can do.
Ask for more staff, reorganize the team into a set of multiple teams, and hire more middle management! Win win for the manager.
Add tests to the function as it exists today. Submit. Add new functionality, make sure tests still pass. Done. Updating a function here and there shouldn't require more staff.
3 replies →
Add some meat sauce and more spaghetti :)
Spaghetti piles are where you can do the most... if you're brave enough and have agency to do so.
Immutable functions! I guess that’s one way of doing functional programming /s
Reminds me of https://www.unison-lang.org/docs/the-big-idea/
In a (very real) sense, git is an immutable data structure of immutable snapshots of code.
You can do commit squashing in git, right? I know HG history editing wa much more of a pain than it seems to be in git.
1 reply →
pfft, that's just symbol versioning