11

Reinvent the wheel workaround: Rename the wheel.

Since you cannot reinvent it, because it already exists and it's working, just call it "rolling circular object" and get away with it.

Why in hell I should call packages "namespaces"?
A package can contain a lot of things actually. It's visual, you can create an icon for it.

Namespace? is that even a word?

Next time I rent an apartment, I'll ask if they have a FuckSpace instead of a bedroom.

"Well, it's a small studio, there is only a ShitSpace and an Open EatAndFuckSpace"

Will do.

Comments
  • 5
    Fuck space is everywhere if you're not a boring prude 😏
  • 3
    Pre-existing function does 90% of what I need.

    Should I?

    A) Tack three more parameters on with default values.

    B) Make a copy of the function and tack a word onto its name describing my specific use... and then tack three more parameters on.
  • 1
    uh!
    I had the same problem when I invented the human male body and designed a small tube to eliminate waste liquid.
    Later I thought the same "tube" idea was useful also for fucking.
    What to do?
    A) use the same tube for both? a bit messy.
    B) create two similar tubes? one named "penis", flexible and soft, the other "cock", always hard and straight?

    Not sure my personal solution was the best one, but it worked. more or less.

    It got complicated with the external interface.
  • 1
    Uhm. I like the rant.

    But namespace and package are not equal. Whut da fuh?
  • 0
    @IntrusionCM yes probably I was carried away by the rant. But trying to approach C# with a java perspective, probably it's the first reaction...I'd like to dive deep into the differences
  • 1
    @willcandy Javas packages / namespaces are... shitty.

    It's one of the things where Java really sucks. :/

    Forget Java namespaces / packages when approaching C#. It's a different kind of thing ;)
  • 0
    @HiFiWiFiSciFi B, because A may break something, as if you needed to add those extra passables, you're clearly using them for something that's been newly added. Update the rest of the codebase (or at least just test it) against the new function, and if nothing breaks due to the changes, THEN merge into A.
Add Comment