tag:blogger.com,1999:blog-6950833531562942289.post5527725930573016883..comments2024-03-25T03:36:48.099-07:00Comments on C0DE517E: Kill your darlingsDEADC0DEhttp://www.blogger.com/profile/01477408942876127202noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6950833531562942289.post-9970023608314687622008-02-09T14:02:00.000-08:002008-02-09T14:02:00.000-08:00I had the same problem. I don't like to start writ...I had the same problem. I don't like to start writing without having th complete knowledge of the problem, and of all the known solutions etc. My advice is, read a bit of stuff, then start a quick prototype, choose a prototyping language so you won't use that code in the final C++ product anyways (to avoid the prototry resign pattern). Hopefully the prototype will show you early problems in the design you was thinking of, and so you can think more, do another proto etc... This does not save you entirely from having a bad design in the end, you have always to iterate, but at least a first exploratory phase helps you choose the right direction. I think it's an art, and in art discipline does help, but still you don't have to be too rigid, so I won't give "my" list of steps to perform (also because I don't have any).DEADC0DEhttps://www.blogger.com/profile/01477408942876127202noreply@blogger.comtag:blogger.com,1999:blog-6950833531562942289.post-11166396961006444882008-02-09T04:29:00.000-08:002008-02-09T04:29:00.000-08:00That was a good read, and some much needed advice....That was a good read, and some much needed advice. Nowadays, I find increasingly difficult to start a project, worrying about the "big picture" and "overall design" and spend too much time thinking about it before even writing a single piece of code. <BR/><BR/>It is difficult to guage how much planning to put in, just the right amount.Anonymousnoreply@blogger.com