three days mostly lost!
Sep. 20th, 2007 03:41 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
juan_gandhiYes, I am a fan of IntelliJ. Still. But last week a "method breakpoint" somehow penetrated my code. How the fuck did I know it makes the code 30 times slower? I spent interesting time looking for the causes of possible network delays; I found stupid bugs in java.text classes (made by one of my colleagues); I bugged unsuccessfully my colleagues.
Until I discovered in a mail thread that METHOD BREAKPOINTS DRASTICALLY SLOW INTELLIJ.
Drastically is the word. Imaging you have bugs to fix, and you cannot even run the server, for 3 days in a row.
Until I discovered in a mail thread that METHOD BREAKPOINTS DRASTICALLY SLOW INTELLIJ.
Drastically is the word. Imaging you have bugs to fix, and you cannot even run the server, for 3 days in a row.
no subject
Date: 2007-09-21 09:52 pm (UTC)Debugging is only good when you have a rather small piece of code that behaves strangely right before your eyes, or for getting stack trace / program state from crash dumps.
IMHO, of course.
no subject
Date: 2007-09-21 11:16 pm (UTC)In my case, I spent two days figuring out how to run it from cl.
In general, there's a better way: unittesting. But in our team we are just starting having really using it. Unfortunately.