[Addendum] In a similar vein, if you spend the bulk of the day waiting on a JDK compile on your secondary workstation, don't fuck around with rm in the bin directory where the JDK gets installed.
Let's just say that you should generally make decisions on how to clean up your memory before you're 300,000 lines deep into your project. Updating all of that code to use smart pointers is a bitch.
[Addendum] In a similar vein, if you spend the bulk of the day waiting on a JDK compile on your secondary workstation, don't fuck around with rm in the bin directory where the JDK gets installed.
[Addendum] In a similar vein, if you spend the bulk of the day waiting on a JDK compile on your secondary workstation, don't fuck around with rm in the bin directory where the JDK gets installed.
Previous Entry
*Poke*
Next Entry
The Hardcore Development Box
Advertisement
Latest Entries
A Few Farewells
14900 views
Code Reuse In Actual Practice
16840 views
Source-Level Debugging For Epoch Programs
5319 views
Using Poison to Reverse Engineer Code
4002 views
Using Poison to Reverse Engineer Code
372891 views
Debugging Information Success
3215 views
Debugging Information Success
6043 views
Debugging Epoch Programs
3489 views
Debugging Epoch Programs
7812 views
Epoch 64-bit compiler progress
2898 views
Advertisement
Ann the joys of C++.
But, pray tell, of what use is the JDK except as a target for rm!