How to learn software design
-
OK, I will admit that I don't know much about it, though I definitely got the impression that Brooks himself thought it was, at least through the first several releases. My understanding is that it was delivered almost two years late, initially didn't provide most of the promised features, and had very serious problems with persistent bugs that kept reappearing long after he left the project himself. While later versions and derivative systems were fairly successful, the original release was a serious blow to IBM's reputation on the level of Windows ME or worse - or so I have always heard, perhaps I was wrong about that.
-
@cartman82 none of this shite. Except for the last one.
-
@ScienceCat said in How to learn software design:
Did you think about something specific when writing that or could otherwise give a recommendation? I tend to choose poorly in these cases and would probably end up trying to reimplement something much too complex...
You should pick a small utility library or framework in a language/area of your interest. I've mostly done front end/webby stuff in PHP and JS, so you really should disregard everything I say.
If you do feel like doing web stuff in PHP, then take a look at the Codeigniter web framework. This is only useful if you do decide to web stuff seriously, though. And don't try to do whole thing in one go
If you do JS, lodash is something you'll want to look at
-
@boomzilla said in How to learn software design:
And if your experience teaches you nothing else, it will be that six months ago you was an idiot.
-
@Jaloopa said in How to learn software design:
it gave me god insight into what the pattern could do.
Holy shit, you gained omniscience?
Edit:
d
Blog++ | The Six Months Rule