Skip to main content
8 events
when toggle format what by license comment
Jan 14 at 10:18 history edited Ewan CC BY-SA 4.0
added 234 characters in body
Jan 14 at 9:53 comment added gnasher729 Readable code is readable because it does exactly what needs doing, no stupid detours wasting time, so it tends to be more efficient from the start. And it is much easier to improve performance if you start with readable code. Instead of answering “what the hell is this code doing, and how do I do it faster”, you only need to answer the second question.
Jul 6, 2021 at 19:55 comment added candied_orange @imaky you sound fine to me and you're singing my song. Performance is a business decision.
Jul 6, 2021 at 14:30 comment added Ewan 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?
Jul 6, 2021 at 4:39 comment added Imaky 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
Jul 6, 2021 at 3:37 comment added candied_orange 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.
Jul 6, 2021 at 1:36 comment added Imaky 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!
Jul 5, 2021 at 18:35 history answered Ewan CC BY-SA 4.0