>not making your code as cryptic as possible so it can't

>>62111242
https://github.com/Droogans/unmaintainable-code

>obfuscating code

does your day entirely consist of JUSTing up as much as possible of other men's lives?

>>62111242
>if it's leaked
>open source

File: 1503706703568.jpg (2KB, 125x125px) Image search: [Google]

2KB, 125x125px

>>62111556
>purposefully leaking your code

>>62111242
> not open sourcing your code
> not documenting your code as clear as possible
> not working with a community to improve your code

Pleb

>>62111533
Obfuscating code often has the effect of reducing the binary size, since "my_lovely_variable" becomes "7a" or whatever. I always do it as a final build step.

File: 1502553992740.png (19KB, 500x590px) Image search: [Google]

19KB, 500x590px

>>62111585
>leaking your code
>creating vulnerabilities within your code
>letting jamal have his way with your code (cuck)

I'm not impressed

>>62111242
What the hell kind of code are you writing that's so sensitive to getting leaked?

Most of the time proprietary software code leaks fuck all happens because nobody cares about what some nerds wrote to make the program run. Hell, most people don't even know what programming is. So even when doing closed source software there's no reason to be paranoid about others seeing your code.

And companies often get the source code for the software they buy anyway, under an NDA.

>>62111613
This is bait

File: 1492205170746.png (206KB, 800x800px) Image search: [Google]

206KB, 800x800px

>>62111632
My magnum opus of course, I'm an artist. A painter wouldn't put his painting on display before it is finished.

>>62111678
>a painter shits on his painting so that nobody will enjoy it before it's time

>>62111632
Have you even held a job in the software industry?

File: 129916409e7229efaceeafde4f0ff1c6.png (202KB, 706x673px) Image search: [Google]

202KB, 706x673px

>>62111701
True artists are rarely appreciated within their lifespans.

File: Kekuna.png (26KB, 572x496px) Image search: [Google]

26KB, 572x496px

>>62111723
>literally a head emptier than an airhead has

>>62111678
>code artisan

>>62111242
Wayy ahead of you OP, I found a good tool:
https://github.com/thegrimprogrammer/escript

>>62111277
One of the funniest things I've read all year.

>>62111704
I do. If my company's product was leaked today nothing would happen. The special sauce is already patented and therefore fully disclosed, the source code is just an implementation that could be trivially reimplemented by a competitor should they decide to risk a patent infringement suit.

I get it, some companies do rely on trade secrets that would be revealed by a code leak, but that's a tiny, tiny minority of all software written today. The risks of proprietary source code being released is way overblown. In fact there would be a lot of benefits to even proprietary software being delivered with full source code since the customer then can freely extend it, even if they can't redistribute any of the changes as they would be able to with free software.

>>62111242

>cognitive dissonance

>>62115042
/thread

>>62111242

>not writing software and removing the comments before uploading it and keeping the commented copies hidden on a .rar file on a zip disk only accessible from an parallel port external zip drive

File: 7e7.jpg (62KB, 600x516px) Image search: [Google]

62KB, 600x516px

>>62116194
>.rar

>>62116194
>Not rewriting the program each time you need to use it

>>62116194
>not not writing software and using already made proprietary software

>>62111242
my code is always cryptic and unreadable but unintentionally

>>62111277
One of my C++ teachers in uni purposedly told us to make our code well commented and neat so they can correct them easier and we could get better grades; but that in real life we just make our code unmaintanable so only the guy who wrote it (us) could be called back to repair it, and get lifetime job