-  [WT]  [Home] [Manage]

[Return]
Posting mode: Reply
Name
Email
Subject   (reply to 3)
Message
Captcha
File
Embed   Help
Password  (for post and file deletion)
  • Supported file types are: 7Z, GIF, JPG, PDF, PNG, RAR, TXT, XZ, ZIP
  • Maximum file size allowed is 10240 KB.
  • Images greater than 200x200 pixels will be thumbnailed.
  • Currently 112 unique user posts. View catalog

  • Blotter updated: 2012-05-14 Show/Hide Show All

File 128694641066.jpg - (59.56KB , 450x450 , 2007_000190.jpg ) Thumbnail displayed, click image for full size.
3 No. 3
So when you're getting ready to start a project, what do you do? Do you just sit down and start cranking out code, or do you take some time to plan things out? Some prefer one way, some prefer the other. What do you prefer and why? Discuss!
>> No. 4
the third principle of the UNIX philosophy:
Build a prototype as soon as possible.
>> No. 5
http://en.wikipedia.org/wiki/Scrum_%28development%29

cranking out code works great when you're working on something that can be done in a couple days but anything larger would require some planning.
>> No. 6
The Unix Philosophy and the Scrum Development Method don't seem to be too far at odds with each other. By acknowledging that user requirements can change, and having regular (seemingly short) iteration periods, developers are forced to go for the simplest, fastest, most reasonably effective solution. Likewise, the Unix Philosophy doesn't preclude working out algorithms and data structures, it just encourages getting up and running as fast as possible so that tinkering and refining can be done.
>> No. 18
I alternate. I start by cranking out some code, then plan, then implement or change, or just delete the code. On and off.


Delete post []
Password  
Report post
Reason  




Inter*Chan Imageboard Top List