Hardest Part in Programming

For me the hardest part is when you find that your data structures are incapable of modeling the problem and you have to fix them somehow, usually by introducing some workaround. At once you had a clean structure and now it is full of hacks.

class fart extends butt implements shit

>>2
That's gross, stop that.

>>2
haha, anus :DD

I write programs in small cycles of two phases, one in which entropy is increased, and one in which it is contained.
I find that it is very hard that the initial design will fit as the program develops, so perhaps rather than polishing that initial design until it's pristine it's best to leave things in a "good enough" state so that they do their job, but you also won't feel too bad about deleting them later on.

The solution is simple. Don't fix the problem. Keep the clean structure.

if by ``clean'' you mean lacking in features, sure
keep your software stale and featureless, while the competition adds more and more stuff, with occasional bugs, but the pros outweigh the cons and then your project becomes abandoned due to its lack of usefulness

>>2
fart is a subtype of butt which can be used the same way as shit? that makes no sense

>>8
Just like OOP.

>>9
OOP is often a square peg in a round hole, but disregard that. this makes no sense when judged by the OOP design principles. to be fair, so does most OOP in practice as opposed to OOP in books

hardest part is getting dubs and making others check them

>>8
Exactly and it's disgusting.