Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Solid advice. Pretty much what I was looking for. Thanks. Commented Aug 30, 2015 at 6:43
  • 3
    If it's 4K lines of C, avoid writing more than 4K lines of Java. Commented Aug 30, 2015 at 10:12
  • 1
    @gnasher729 I would expect a 5 : 1 ratio when porting c to a high level programming language, 800 lines of Java (The stdlib is huge, use it) Commented Aug 30, 2015 at 13:12
  • 1
    @Caridorc: If there are standard-library-routines to do a big part of your work instead of having to write it from scratch where none were used before, that's reasonable. Though the shoe is on the other foot (and will pinch abominably), if that's not the case and something maps badly to Java or it's standard library. Which gets more likely the less standard and more optimized the original is. Commented Aug 30, 2015 at 15:01
  • 2
    Essential reading, in case you have missed either book in your education so far: Working Effectively with Legacy Code by Michael Feathers, and Refactoring by Martin Fowler. Commented Aug 30, 2015 at 15:48