Timeline for ASP.NET Projects using too much .NET Boilerplate Libraries / Code
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 9, 2021 at 10:19 | comment | added | BreakingGnus | This Answer does not feel 'opinionated' to me. But learning someone else's solution will almost always be helpful. We learn general principles by first encountering particular instances. If you use common ideas, for example Optimistic Concurrency, people can Google that. Who knows, they might learn something. | |
| Sep 6, 2017 at 7:51 | comment | added | JacquesB | @B1313: I don't dispute your particular framework is amazing, bug-free, documented and easy to learn. But you ask the question in general, and most teams consist of average developers (by definition) and does not have a "ninja rockstar" developer like you. And from a management perspective, over-reliance on a single elite developer is a major risk. | |
| Sep 6, 2017 at 7:40 | history | edited | JacquesB | CC BY-SA 3.0 |
added 1 character in body
|
| Sep 6, 2017 at 2:17 | comment | added | G.T.D. | Your answer could be vastly improved by removing the editorializing and opinionated remarks. Oh and in response to your comment, I am not sure why it takes a month to document any code especially a small framework. My colleagues actually agreed with me on having less M$ software generally means less bloatware / broken code w/ updates. P.S. My framework has been working fine for approx. 2.5 years now (in production) and I can teach it to someone in an hour...try doing that with Entity or Identity...oh yeah, you need "books, or tutorial[s]" for those. | |
| Sep 3, 2017 at 10:54 | history | edited | JacquesB | CC BY-SA 3.0 |
added 24 characters in body
|
| Sep 3, 2017 at 10:42 | history | answered | JacquesB | CC BY-SA 3.0 |