i personally have been reorganising the whole structure in my code to fit an imperative programming model and it breaks down pretty nice for the most part... there is a few parts of my code that still use nip codes but i could think of reasonable names for them
nip1 is bloated as fuck, and i reject the numbering system, it's dumb, i think that it should be explained via short names, 1, 2, at most 3 words to express what a thing does
this makes it alot easier for people to understand and a lot easier to architect as a programmer