3 ms·
What's horrible about running your own code?
by applecore 12y ago
What's horrible about running your own code?
- sliverstorm 12y agoI think he is saying in a round about way his code always works just right on the first compile, so he never even needs to run it before releasing it.
- Rapzid 12y agoI think he's saying he works on the code for long periods of time before worrying about how running it works out. Then he just tweaks the bits that are off and goes about his business.
- codygman 12y agoThat's exactly how I work with Haskell.
- semi-extrinsic 12y agoFunny, that's exactly how I work with Fortran (2008). And I have Syntastic in Vim nag me every time I save if I made a mistake that the compiler catches. A great advantage over C/C++ is that even on 30 000+ LoC projects split into many files, compiling from clean takes less than 30 seconds. "implicit none", of course.
- imanaccount247 12y agoNope, what Rapzid said. My code very rarely compiles first try, but when it does I have a strong amount of certainty that it will work. So I only have to run it a few times a day to check on the output, rather than every single time I compile it. Nobody said anything about releasing it without running it.
- deleted 12y ago[deleted]
- imanaccount247 12y agoNothing. What is horrible is being forced to run it constantly every single time you make a tiny change to see if you messed it up or not. I don't need to do that when I am using haskell, I just have my repl session autmatically :reload when I save a file and it tells me if I broke anything.