tag:blogger.com,1999:blog-1383695822029623916.post61366088294503905..comments2024-03-28T00:20:38.908-04:00Comments on Chris Wong's Development Blog: Programming at the speed of thoughtChristopher Wonghttp://www.blogger.com/profile/16941177380839071164noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1383695822029623916.post-84759078891035926372012-02-14T18:15:30.365-05:002012-02-14T18:15:30.365-05:00Oh man I feel your pain. I'm in a very 'e...Oh man I feel your pain. I'm in a very 'enterprisey' project right now, and about one and a half years ago I read about JRebel, downloaded the evaluation version and plugged it straight into the enterprise project. My God what a difference it made in my productivity - much less server restarts (didn't eliminate them completely) which saw me churn through my own list of bugs/Emanuelhttp://www.ultraq.net.nz/noreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-50447293573134420902012-02-14T12:28:38.853-05:002012-02-14T12:28:38.853-05:00Hi,
I'm always wondering why people are tired...Hi,<br /><br />I'm always wondering why people are tired of restarting their app/container/server/whatever. Just write tests and stop testing with your mouse/browser. That's what ruins your productivity !<br /><br />Browser testing during development should be used only to test the JSP/JSF code which reloads instantly since JSP is JSP. Of course, if you use GWT, no one can help you...<br waddlehttps://www.blogger.com/profile/09869559469299459929noreply@blogger.com