[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.
🎉 Celebrating 25 Years of GameDev.net! 🎉
Not many can claim 25 years on the Internet! Join us in celebrating this milestone. Learn more about our history, and thank you for being a part of our community!
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
14589 views
Code Reuse In Actual Practice
16467 views
Source-Level Debugging For Epoch Programs
4990 views
Using Poison to Reverse Engineer Code
154274 views
Using Poison to Reverse Engineer Code
3627 views
Debugging Information Success
2923 views
Debugging Information Success
5465 views
Debugging Epoch Programs
3136 views
Debugging Epoch Programs
7445 views
Epoch 64-bit compiler progress
2630 views
Advertisement
Ann the joys of C++.
But, pray tell, of what use is the JDK except as a target for rm!