4 ms·
> So in a sense I am not strictly practicing my approach Developing in an IDE that compiles almost continuously is about as far from the development philosophy
by slunk 5y ago
> So in a sense I am not strictly practicing my approach
Developing in an IDE that compiles almost continuously is about as far from the development philosophy you're advocating for here as one could get :P
- lmilcin 5y agoThat doesn't make any sense. This isn't about throwing away tools for some idealized goal. It is about using the tools that are available to achieve best results without making you reliant on the tools to the point you don't know what your program is going to do without compiling and running. IDE helps catch a lot of stupid simple mistakes and that helps save time. Why would that be bad?
- slunk 5y agoI don't think using an IDE to catch lots of stupid simple mistakes is bad. It's how I prefer to work. > It looks really strange to me to observe other developers constantly compiling and running their code just to see if it works. It kinda looks as if they did not exactly understand what they are doing because if they did, they would be confident the implementation works. Explain to me how this statement doesn't apply to your use of an IDE, but the other engineers you've observed don't understand what they're doing.
- deleted 5y ago[deleted]
- lmilcin 5y agoIf you can't read that sentence with comprehension none of my explanations are going to help.
- h_anna_h 5y agoThey did read that sentence with comprehension. It is you who can't connect the lines. Your IDE already does typechecking and finds other issues for you. Basically the only thing that you are missing is the ability to run and test your program.
- 59nadir 5y agoIt's legitimately surprising that you would double down here instead of realize that your tooling is recompiling your code and showing you the result continuously, making your workflow essentially the same as the people you seem to feel so superior to.