Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

3 lines of code shouldn't take all day

devtails.xyz

Post reply on HN
Print view View original

11–20 of 213 posts

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

#11

Post by kyruzic »

How I wish a single line code change only took a 15 second build.

The java app I work on regularly takes 3 minutes for a single line change. Then you just need to pray that jrebel will work today and actually hot reload your change. Otherwise you have another 8 or so minutes of redploying weblogic.

Of course the ideas suggested in this can help, but when you need to run an integration test which also takes minutes to run you realize that 3 lines of code isn't bad for a days work.

One day soon I will never touch Java again.

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

#12

Post by faraaz98 »

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…

How much time did removing docker shave off?

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

#13

Post by xmprt »

tayo42 wrote: post #9

I see this is about game development, but in the web/server world idk how anyone ever thinks its acceptable to make development impossible on your local laptop/computer. Everyone time I do a code review I need to ensure they didn't break local development. It blows my mind that I need to do it, like they think its ok to build and deploy for every little test. When I first joined I spent so much time just getting it t…

I think this is why I love green field projects so much. More than being able to work on my own code and design from scratch, I appreciate the fact that no one has messed up how testable and runnable the code is from a developer machine.

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

#14

Post by senectus1 »

For all the issues I have with Elon Musk, I really like his design philosophy.

Step 1 Make it less dumb

Step 2 Delete a part of the process

If you're not adding step in 10% of the time, you're not deleting enough

Step 3 Simplify or Optimize

Step 4 Go Faster

Step 5 Automate

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

#15

Post by suzzer99 »

kyruzic wrote: post #11

How I wish a single line code change only took a 15 second build. The java app I work on regularly takes 3 minutes for a single line change. Then you just need to pray that jrebel will work today and actually hot reload your change. Otherwise you have another 8 or so minutes of redploying weblogic. Of course the ideas suggested in this can help, but when you need to run an integration test which also takes minutes to…

Going from Weblogic 10 minute reboots to Node 5 second reboots made development so much more productive and fun for me.

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

#17

Post by suzzer99 »

substructure wrote: post #10

AWS CloudFormation had one of the worst user stories related to iteration time a few years ago. The lack of feedback between the writing of the yaml file and validation of the structure/type/format was frustratingly slow. I would pay good money for better tooling in the Infrastructure as Code(IaC) space. Waiting for the resources to update, fail with cryptic error messages, then slowly rollback only to then fail the…

Getting anything new working in CloudFormation is a great way to kill a day.

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

#19

Post by idiocrat »

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…

For some reason not many people like the "maintenance" type of work.
Post reply on HN