SHARE BEST PRACTICES

version control and programming socks

>>62309880
courtesy reach-around when plowing a cute trap

>>62309880
Push node modules to repo

cumming inside

Tabs over spaces.

>>62309880

Saving often and doing backups

>>62309880

Write tests for everything that can theoretically break. If you don't write them before the implementation or directly afterwards, you'll never write the test.

Having a glass of water and keeping hydrated.

>>62309880
If you need to execute some functions which require lots of RAM, then use this trick: First cause an infinite recursion loop for a stackoverflow error, catch the error and then execute your function in the catch block. Than you can be sure that you always have RAM available.

    private void fillRAM() { fillRAM(); }

    public void expensiveFunction() {
        try {
            fillRAM();
        }
        catch (StackOverflowError e){
            expensiveFunctionImpl();
        }
    }

>>62312205
thx dude, was dealing with that right now

>>62312205
This seems strange and a hack. What is the mechanism for this to actually work

File: 1503332460597.jpg (80KB, 463x372px) Image search: [Google]

80KB, 463x372px

>>62312205
Genius

Securely erase all your porn.

>>62312205
can expensiveFunctionImpl() dump the entire contents of memory to disk then upload to server?

I have a text file in which I note all notable changes I make to my system (eg editing advanced options or the registry on Wangblows or Linux config files).

File: boys-who-dress-like-girls-make-the-best-programmers.jpg (47KB, 408x341px) Image search: [Google]

47KB, 408x341px

I respect anyone that comments thoroughly what their code is doing and what they intended for it to do. I don't care if it doubles your file size. I wanna see green.

>>62312356
yes it can. Actually, that's what Chrome does to use so much RAM

>>62312550
fantastic, assuming this only works on windows?

>>62312575
No, you can use this on every OS. Have fun!

>>62312638
thx fammo, i actually use a similar technique for debugging PIC micro firmware
you just declare an array, with 1 byte length, you can then access any part of the memory, byte 2 of memory is array[1] etc, i just write everything to a serial port and I can see everything.. what is overflowing etc. arm is so much better