3 lines of code shouldn't take all day • Hacker News Board

Re: 3 lines of code shouldn't take all day

#211

Post by nijave » Fri, Dec 17, 2021, 7:43 PM UTC

gfodor wrote: post #26

dan353hehe wrote: post #5

Agree with this so much. One of the main things that I try to do is ensure that the turn around time between testing and writing code is as short as possible. As an example I inherited a codebase about 2 years ago that would take 15 minutes to run the test suite. It was painful. It was just long enough that it would waste an entire day just trying to implement a simple feature. The project was behind schedule and no…

Another much under-utilized way to speed up test suites: delete tests

Also just deleting dead code and tests that go along with it

Tend to get a boost in application boot/startup time, too

Re: 3 lines of code shouldn't take all day

#212

Post by jmnicolas » Sat, Dec 18, 2021, 7:27 AM UTC

throwawayboise wrote: post #186

jmnicolas wrote: post #43

Earlier quoted context omitted.

Your example is valid for beginners but once you're getting experience you don't code like that anymore. After 13+ years of C#, on simple projects I can code for a couple hours without compiling and get the pleasant surprise that my code work the first time I run it. And I'm certainly not a genius, I'm a 1X programmer.

I have been coding for over 30 years and I can barely write one function without at least making some typos if not logical errors. I would never code for a couple of hours without compiling/testing.

You're not using an IDE? Sometimes I joke that I just press CTRL+Space and Visual Studio does the coding for me (and this was before Github Copilot!).

Re: 3 lines of code shouldn't take all day

#213

Post by CRConrad » Thu, Dec 30, 2021, 10:33 AM UTC

tomrod wrote: post #204

bipson wrote: post #71

Earlier quoted context omitted.

Came here to say this. I even see the mindset spreading to other activities, like writing an abstract, paper, proposal or preparing slides: I regularly (more often than not) see students using their supervisors as "CI-chain", submitting iterations with lots of stupid errors, half-baked sentences, unclean structure... because they learned to hit CTRL-b and see what comes back. Of course there are reasons to talk about…

What does CTRL-b map to? Paste?

"Build"?