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*

7
  • 3
    If you can't find any references to consistency as a good practice, you haven't searched hard enough. The great majority of advisers will tell you that consistency across a code base is very important, often more important than the specific way you resolve a particular decision. Commented Mar 12, 2015 at 8:06
  • 1
    Your question is more specific than the title implies. Things that are true about applications might not be as true for software in general. For example when using micro-services architecture implementing services in different languages and technologies is not unreasonable. Commented Mar 12, 2015 at 11:23
  • @Den: I don't have experience with micro-services but my impression is that a piece of software is much easier to work with if it is developed in a single technology. That way you only need one profile in your team, not several developers mastering different skills. Commented Mar 13, 2015 at 8:47
  • @IgnacioSolerGarcia - correct, it is beneficial to employer, but not to employees (unless they are happy to stop learning). Commented Mar 13, 2015 at 9:12
  • @Den: honestly, I don't think work is the place to learn. I really think that it is wrong to learn while you work as you will make lots of errors in production code. What if your mechanic was learning while he was fixing your car? (And charging like a senior mechanic) Commented Mar 13, 2015 at 9:19