Slashdot Mirror

← Back to Domains

Domain: c2.com

Stories and comments across the archive that link to c2.com.

Comments · 1,108

  1. Refactoring and Extreme Programming by Anonymous Coward · · Score: 2 · on Refactoring: Improving the Design of Existing Code

    I think a lot of people underestimate the importance of refactoring code. It's put to good use (as I can attest from experience) in the Extreme Programming software development methodology. (If you haven't heard of this, check it out. It seems kind of radical, but it works very well in practice if applied appropriately.)

  2. XP by Stu+Charlton · · Score: 1 · on Ask Slashdot: On Good Software Design Processes

    Try Extreme Programming ... a very light process that encourages coding, testing, refactoring and communication. Suited mainly to object-oriented apps (i.e. user level vs. system level).

  3. Extreme Programming by Anonymous Coward · · Score: 1 · on Ask Slashdot: On Good Software Design Processes

    This sounds like the philosophy exposed by Kent Beck and his XP crew.

    The basic philosophy of XP is to write code until you have something that works. Write a unit test for it. Listen to what the users think of it. Then write it again. Refactor mercilessly.

    It's a good philosophy, partly because it cuts out all the crap about up front design and UML and allows the shape of the code to take shape naturally. At the same time, the refactoring ensures that the project doesn't become a mess of unfinished prototypes, and the tests ensure that everything works when you refactor (or at least tell you when you broke something.)

    here and here.

  4. Check out Extreme Programming by CaptainCaveman · · Score: 1 · on Ask Slashdot: On Good Software Design Processes
    A relatively new approach to software development is "Extreme Programming", which I've been toying with quite a bit lately.

    Extreme Programming is a sort of minimalist approach to software development, but that doesn't mean it requires no discipline.

    At the heart of Extreme Programming are the following practices (from Wiki):

    1. Coding. At the end of the day, if the program doesn't run and make money for the client, you haven't done anything.
    2. Testing. You have to know when you're done. The tests tell you this. If you're smart, you'll write them first so you'll know the instant you're done. Otherwise, you're stuck thinking you maybe might be done, but knowing you're probably not, but you're not sure how close you are.
    3. Listening. You have to learn what the problem is in the first place, then you have to learn what numbers to put in the tests. You probably won't know this yourself, so you have to get good at listening to clients- users, managers, and business people.
    4. Refactoring. You have to take what your program tells you about how it wants to be structured and feed it back into the program. Otherwise, you'll sink under the weight of your own guesses.

    For some great resources related to Extreme Programming, visit Ron Jeffries' website.
  5. Open Source Business Patterns by pcburns · · Score: 1 · on New ESR paper: The Magic Cauldron

    I just realised how much ESRs business models are like Patterns
    All he has to do is change the format a bit and they'll fit right in at WikiWikiWeb

  6. Open Source Business Patterns by pcburns · · Score: 1 · on New ESR paper: The Magic Cauldron

    I just realised how much ESRs business models are like Patterns
    All he has to do is change the format a bit and they'll fit right in at WikiWikiWeb

  7. Some usability suggestions by Anonymous Coward · · Score: 1 · on Slashdot Tweaks
    I really like the thematic tags, but why don't you
    separate them from the points. I mean, there will always
    be some posts that are good but unclassifyable.

    --Anonymous Moderator

    PS: Rob!! here are some features that would really help this site's
    usability.

    • HTML validation, link validation, spell checking, and grammar checking.
    • More source releases, especially in the customization areas of the code. Its time to simplify/
      refactor Slashdot's source code.
    • More permanency. Maybe you could archive only highly read and high-scoring posts/articles.
  8. You all just don't get it... by kip3f · · Score: 1 · on Y2K and Nuclear Weapons

    This is a big problem. If there is a loss of power for more then 3 days, there WILL be meltdowns. The problem is that so much is dependent on power, railroads, oil. The big one, of course, is power. If there are major power outages, it will severely harm all other industries. Not scared yet? checkout

    this site.

    --
    Man is most nearly himself when he achieves the seriousness of a child at play.