|
|
By Yashima, on February 16th, 2005
or: Why milestones are good for you
I find making project schedules and estimates an absolute pain. Neither painless schedules a la Joel, our internal “process” nor any tools I found so far, make this easier. Why? I am not sure, but I think one thing I am missing is some basic theory how . . . → Read More: Milestone: Lessons learned
By Yashima, on February 15th, 2005
This morning I posted how I had come to the conclusion that findability might play a role in design. Since Uli questionned my argument, I’ll try to elaborate a bit on the thought.
Continue reading Naming your code
By Yashima, on February 15th, 2005
So I am still wondering, are the white dots dirt, planes or stars? Look at the exif data and tell me if it is possible to photograph stars with those settings at that time.
Maybe I was just influenced by being in the planetarium shortly before taking that picture. Which was taken . . . → Read More: Star Clouds
By Yashima, on February 15th, 2005
In my newly formed opinion, a piece of code deserves to be in its own class if you ever took time to find that particular piece because you could not remember in what class it was included.
(Oh yes that’s learning by making mistakes.)
By Yashima, on February 15th, 2005
Sometimes to avoid a decision I decide to make something “configurable” ;-)
What this ultimately achieves is, that of the two choices (or more) that I have, I can now choose at any time, except I don’t! I arbitrarily choose one, because I “could” always choose the other for the next run. Arbitrarily chosen . . . → Read More: Decisions
|
|
Recent Comments