Become a fan of Slashdot on Facebook


Forgot your password?
Slashdot Deals: Deal of the Day - Pay What You Want for the Learn to Code Bundle, includes AngularJS, Python, HTML5, Ruby, and more. ×

Submission + - Seeking Distilled Software Engineering Experience ( 1

knapper_tech writes: "I'm a 26-year-old web programmer self-trained in nice MVC based frameworks, including Yii and Django, with their ORM's, well-packaged extensions, database agnosticism and all that other high-minded stuff thrust into a professional track of imperative PHP and MySQL. As usual, believing in high-minded concepts is never quite as informative as witnessing the cascading bugs in haphazardly maintained, undocumented code that never seems to go away and stay with the customer. In addition I get a lot of blown projects by would-be developers in the door. In the spirit of reuse, what are some really good pieces of literature for one to hone their use of the force? I'm not so much asking for logical proofs of why a certain pattern is always better than another, but moreso examples of, "This was the code, this was the fallout, and this was how to decouple it and hook it in properly." I'll be able to pick up the core concepts on my own reading. What I can't duplicate economically (time being priceless) is time spent in the industry. What of course would be most informative is what practices you as a coder hope to find when expecting my code to have a useful lifetime in a code base."
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Seeking Distilled Software Engineering Experience

Comments Filter:
  • Good goals. Keep in mind that unless there are special circumstances, if you're programming for hire, the code doesn't belong to you but to the [person/company/employer] paying for it to be developed. I'll assume that you've already worried about all the legal niceties.

    I have a library of code that I keep with me as I make my around the extensive customer site. At this point there are two thing that every item in my library is required to have: documentation and unit test. For the most part, class d

You cannot have a science without measurement. -- R. W. Hamming