Skip to main content
Software Engineering

Return to Answer

fix punctuation, fix awkward prose ("known to be known")
Source Link
Alex D
Alex D
  • 1.3k
  • 9
  • 14

Depends..

As with everything, itsit's about context:

It's Good when:

  • Framework or library is too heavy, and you only require limited functionality. Rolling your own extremely light-weight version that suitessuits your requirement is a better approach.
  • When you want to understand and learn something complex, rolling youyour own makes sense.
  • You have something different to offer, something others' implementations do not have. May beMaybe a new twist, new feature etc.

It's Bad when:

  • Functionality already exists and is known to be stable and well known (popular).
  • Your version adds nothing new.
  • Your version introduces bugs or constraintslimitations (e.g. your version is not thread-safe).
  • Your version is missing features.
  • Your version has worse documentation.
  • Your version is lacking unit tests compared to what it is replacing.

Depends..

As with everything, its about context:

It's Good when:

  • Framework or library is too heavy, and you only require limited functionality. Rolling your own extremely light-weight version that suites your requirement is a better approach.
  • When you want to understand and learn something complex, rolling you own makes sense.
  • You have something different to offer, something others' implementations do not have. May be a new twist, new feature etc.

It's Bad when:

  • Functionality already exists and is known to be stable and well known (popular).
  • Your version adds nothing new.
  • Your version introduces bugs or constraints (e.g. your version is not thread-safe).
  • Your version is missing features.
  • Your version has worse documentation.
  • Your version is lacking unit tests compared to what it is replacing.

Depends..

As with everything, it's about context:

It's Good when:

  • Framework or library is too heavy, and you only require limited functionality. Rolling your own extremely light-weight version that suits your requirement is a better approach.
  • When you want to understand and learn something complex, rolling your own makes sense.
  • You have something different to offer, something others' implementations do not have. Maybe a new twist, new feature etc.

It's Bad when:

  • Functionality already exists and is stable and well known (popular).
  • Your version adds nothing new.
  • Your version introduces bugs or limitations (e.g. your version is not thread-safe).
  • Your version is missing features.
  • Your version has worse documentation.
  • Your version is lacking unit tests compared to what it is replacing.
added the missing apostrophes
Source Link
I don't use this profile anymo
I don't use this profile anymo
  • 328
  • 1
  • 3
  • 14

Depends..

As with everything, its about context:

ItsIt's Good when:

  • Framework or library is too heavy, and you only require limited functionality. Rolling your own extremely light-weight version that suites your requirement is a better approach.
  • When you want to understand and learn something complex, rolling you own makes sense.
  • You have something different to offer, something othersothers' implementations do not have. May be a new twist, new feature etc.

ItsIt's Bad when:

  • Functionality already exists and is known to be stable and well known (popular).
  • Your version adds nothing new.
  • Your version introduces bugs or constraints (e.g. your version is not thread-safe).
  • Your version is missing features.
  • Your version has worse documentation.
  • Your version is lacking unit tests compared to what it is replacing.

Depends..

As with everything, its about context:

Its Good when:

  • Framework or library is too heavy, and you only require limited functionality. Rolling your own extremely light-weight version that suites your requirement is a better approach.
  • When you want to understand and learn something complex, rolling you own makes sense.
  • You have something different to offer, something others implementations do not have. May be a new twist, new feature etc.

Its Bad when:

  • Functionality already exists and is known to be stable and well known (popular).
  • Your version adds nothing new.
  • Your version introduces bugs or constraints (e.g. your version is not thread-safe).
  • Your version is missing features.
  • Your version has worse documentation.
  • Your version is lacking unit tests compared to what it is replacing.

Depends..

As with everything, its about context:

It's Good when:

  • Framework or library is too heavy, and you only require limited functionality. Rolling your own extremely light-weight version that suites your requirement is a better approach.
  • When you want to understand and learn something complex, rolling you own makes sense.
  • You have something different to offer, something others' implementations do not have. May be a new twist, new feature etc.

It's Bad when:

  • Functionality already exists and is known to be stable and well known (popular).
  • Your version adds nothing new.
  • Your version introduces bugs or constraints (e.g. your version is not thread-safe).
  • Your version is missing features.
  • Your version has worse documentation.
  • Your version is lacking unit tests compared to what it is replacing.
Added documentation point
Source Link
edit approved Dec 18, 2014 at 21:00
JDiMatteo
edit approved Dec 18, 2014 at 21:00
JDiMatteo
  • 375
  • 2
  • 15

Depends..

As with everything, its about context:

Its Good when:

  • Framework or library is too heavy, and you only require limited functionality. Rolling your own extremely light-weight version that suites your requirement is a better approach.
  • When you want to understand and learn something complex, rolling you own makes sense.
  • You have something different to offer, something others implementations do not have. May be a new twist, new feature etc.

Its Bad when:

  • Functionality already exists and is known to be stable and well known (popular).
  • Your version adds nothing new.
  • Your version introduces bugs or constraints (e.g. your version is not thread-safe).
  • Your version is missing features.
  • Your version has worse documentation.
  • Your version is lacking unit tests compared to what it is replacing.

Depends..

As with everything, its about context:

Its Good when:

  • Framework or library is too heavy, and you only require limited functionality. Rolling your own extremely light-weight version that suites your requirement is a better approach.
  • When you want to understand and learn something complex, rolling you own makes sense.
  • You have something different to offer, something others implementations do not have. May be a new twist, new feature etc.

Its Bad when:

  • Functionality already exists and is known to be stable and well known (popular).
  • Your version adds nothing new.
  • Your version introduces bugs or constraints.
  • Your version is missing features.

Depends..

As with everything, its about context:

Its Good when:

  • Framework or library is too heavy, and you only require limited functionality. Rolling your own extremely light-weight version that suites your requirement is a better approach.
  • When you want to understand and learn something complex, rolling you own makes sense.
  • You have something different to offer, something others implementations do not have. May be a new twist, new feature etc.

Its Bad when:

  • Functionality already exists and is known to be stable and well known (popular).
  • Your version adds nothing new.
  • Your version introduces bugs or constraints (e.g. your version is not thread-safe).
  • Your version is missing features.
  • Your version has worse documentation.
  • Your version is lacking unit tests compared to what it is replacing.
Post Made Community Wiki by JSON
Source Link
Darknight
Darknight
  • 12.2k
  • 1
  • 41
  • 58