Re^2: Project Structure Revisited

++ however there were a lot of out of work PhDs around when I was a kid in rural New Mexico; the proximity of the Sandia and Los Alamos National labs. LSD was $4 a tab, at most, because some of the unemployed were chemists.

Expertise can't always overcome personal choices or quirks. An expert with an inconvenient personality tick or unusually strong ethics will have a much harder time finding work. One easy example: Deciding against working for the US government as a conscientious position can cut a huge swath right through the available jobs. Hell, your very expertise can count against you if you're engaged in a field that is highly regulated or political. People who know exactly what they are doing can be a burden or even a legal liability in those situations.

(I'm pro-expertise and highly pro-work, I just has to calls 'em like I sees 'em.)

Comment on Re^2: Project Structure Revisited

Replies are listed 'Best First'.
Re^3: Project Structure Revisited by Xiong (Hermit) on Aug 17, 2010 at 13:21 UTC
Your Mother++ # for taking a shot at a small part of the underlying task in CB earlier. I'm reckless enough to throw many hours into reading dense tomes, most of which I know in advance (based on prior experience in kind) will prove but tangential to my immediate needs; I'm flush enough to throw dollars away on books that I'll read twice, store for five years, and then give away. Somewhere, I know, will be the book that speaks directly to my needs and which I will thumb over to destruction. I may as well take oko1's advice and wave cash in the air, if that's what it takes to shake the fruit from the tree. So, I'll offer first to the Monastery the US$100 contract to produce a recommended reading list on the topic of project file and folder management. Any Monk is welcome to submit a two- or three-line bid showing you understand what I seek. If the bid is accepted, I'll PayPal in advance, in full. I propose fulfillment in a month but I'm flexible. If the bid is rejected, I'll explain why unless you expressly request I not. The work-for-hire: the reading list; becomes my property and I will publish it here under the same terms as PerlMonks itself. We don't need the conch anymore. We know who ought to say things.... It's time some people knew they've got to keep quiet and leave deciding things to the rest of us.	[reply] [d/l]
Re^4: Project Structure Revisited by scorpio17 (Canon) on Aug 17, 2010 at 20:23 UTC
Okay, I'll throw my name into the hat. After all, $100 buys a lot of hot wings. Try these: http://www.scmpatterns.com/book/pattern-summary.html http://www.cmcrossroads.com/cgi-bin/cmwiki/view/CM/ And/or google for "software configuration management (scm)." Maybe that helps?	[reply]
Re^5: Project Structure Revisited by Xiong (Hermit) on Aug 17, 2010 at 22:54 UTC
Sorry. Fascinating links but they go to a higher level of abstraction than I generally feel I can indulge; also, they relate to another topic, which is some superset of version control. So far as VCS goes, I'm using Git and pushing public to GitHub. I follow, broadly, the branching strategy clearly outlined by Vincent Driessen. I lack skill with this toolset; but I'm learning; and feel very comfortable with it. You do have the right general idea, which is Here are some pointers not Here is some data nor worse, You're a fool for asking. Upvoted and, if you stop by SF, a slice and a Coke. Feste: Misprison in the highest degree. Lady, cucullus non facit monachum. That's as much to say as, I wear not motley in my brain....	[reply] [d/l]