Timeline for Simplicity-efficiency tradeoff
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| May 30, 2014 at 14:26 | comment | added | Karl Bielefeldt | Agreed, to a point. If I'm on a C# team, but I want to write all my code in F# without getting consensus from my team, that's a problem. Frankly, on the other hand, if someone still doesn't understand a feature like LINQ that was introduced to their bread-and-butter language six years ago, they're not doing their job. That's why I suspect the problem isn't so much LINQ itself, as messily-written or inappropriately-applied LINQ. | |
| May 30, 2014 at 7:55 | comment | added | Giorgio | "My second draft still requires basic understanding of functional programming...": You pointed out an important aspect: readability also depends on how familiar other team members are with a given technology or programming style. A different programming style (even one that is widely recognized as superior) will likely be rejected or considered too complex by a team that is not familiar with it. The goal of managers is to get a uniform code style that everybody understands (keep a high truck number), using the best possible solution is not the highest priority. | |
| May 29, 2014 at 23:00 | comment | added | JeffO | A think the code review idea is great and makes me wonder if better procedures & communication were in place with this team the OP would have learned about this issue sooner. | |
| May 29, 2014 at 21:43 | vote | accept | Tawfik Khalifeh | ||
| May 29, 2014 at 21:43 | comment | added | Tawfik Khalifeh | really inspiring, just for the info, I'm not showing off, I'm solving a problem at hand->naturally, thanks for your answer, really helpful | |
| May 29, 2014 at 21:40 | history | answered | Karl Bielefeldt | CC BY-SA 3.0 |