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*

6
  • 1
    I'm more confortable with the idea that readability is superior to performance in a normal context (not a cpu-intensive or realtime processing). Currently with 1 developer hour we can pay a t4g.small instance for one fully month. Also, we do stress tests to check if aws instances grows as expected without degrading the costumer experience. But thanks for your comment! Commented Jul 6, 2021 at 1:36
  • It's nice when you can have both but given a choice between readable code and performant code I'll take readable every time. Why? Because making readable as performant as needed is easy. Making performant code as readable as needed is not. Commented Jul 6, 2021 at 3:37
  • At the end, we work in a business, and 1 hour of developing is more cheap than 1 hour of hardware. Crafting readable code is cheaper than adding more processing nodes. Is a economic decision.... Sorry if I'm talking weird, but english is not my native language. In spanish, this sounds better :P Commented Jul 6, 2021 at 4:39
  • the equation for hardware costs can change quickly as you scale and performance is a tricky thing. If you have finished code and a competitor that runs faster, smoother more cheaply. which is the best? Commented Jul 6, 2021 at 14:30
  • 1
    @imaky you sound fine to me and you're singing my song. Performance is a business decision. Commented Jul 6, 2021 at 19:55