Life is about trade-offs.

Thinking of things as black boxes makes it easier to bring someone to the point where they can be productive, and makes development far easier.

Knowing what is inside the box allows you to solve obscure problems when they arise.

The vast majority of the time, thinking in terms of black boxes saves you time and energy. I agree that it can be worth it to learn how the box works a bit, though, because when it goes wrong it can be very useful to know that. But the payoff doesn't come that frequently, and often isn't all that large. Besides as long as someone on your team knows, and you know who to delegate to when confused, the effect isn't all that different from actually knowing it yourself. (Except that the other person gets the credit. Also ignore this if you don't work in a team.)

Perhaps what I'm saying is that while in an ideal world we would all know everything about every topic, in the real one we can't expect to. So learn what you can, make black boxes of many things, and fill in some of your ignorance as time and opportunity present themselves. But accept that there will be ignorance.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.