Re:Ask HN: What is your best advice for a developer to write...
by pklausler on Wednesday June 29, 2016 @02:58PM
(#12003808)
You can write buggy code in any language, and good code in any language. If Ruby's what you have to use, write good Ruby code. If the only reason you're not able to use something better is that you don't know anything better, then fix that when you can.
Re:Ask HN: What is your best advice for a developer to write...
by tunesmith on Wednesday June 29, 2016 @03:27PM
(#12004093)
You probably are not sloppy, because you are worried about being sloppy. The sloppy programmers are the ones that don't care about being sloppy. If you're conscientious, you have a huge leg up on a lot of other programmers.
Re:Ask HN: What is your best advice for a developer to write...
by mhurron on Wednesday June 29, 2016 @03:44PM
(#12004235)
Since 'sloppy' is going to be defined differently by basically everyone, this isn't true.
That someone is worried about being sloppy really only lets you assume they don't write code they consider sloppy.
Re:Ask HN: What is your best advice for a developer to write...
by afarrell on Thursday June 30, 2016 @03:07AM
(#12007027)
Not even that. They could believe that they are in a job where they are expected to move at a pace that implies sloppy code.
Of course, that will actually mean they move much more slowly due to bug fixes, but a junior dev in an environment without a good senior dev can easily fall to the "quick and dirty" fallacy.
Re:Ask HN: What is your best advice for a developer to write...
by lojack on Wednesday June 29, 2016 @03:16PM
(#12003968)
How exactly do the first five points put Ruby out of the picture? Sure, it isn't statically typed and allows mutable data, but I don't see how any of the remaining points couldn't apply.
Also, your first three points puts Ruby pretty much out of the picture.
EDIT: Mentioned Ruby because that's what I am working on right now, after Java and Scala