4 ms·

Consulting php.net isn't an issue. I've been programming PHP for years and the language is so inconsistent I wouldn't be surprised if even the developers check

by vito 17y ago

Consulting php.net isn't an issue. I've been programming PHP for years and the language is so inconsistent I wouldn't be surprised if even the developers check their documentation every so often. But, please, don't code for speed, code for quality. I can't tell you how many cesspools I've seen as a result of "rapid development". Namely, Lighthouse and github are some of the buggiest and unstable applications I've ever used. They're still great applications, but dammit, when every new ticket goes to a milestone that expired years ago (Lighthouse) and I currently have "-1" unread messages (github), I can't help but be annoyed. Lighthouse more than github.

apsurd 17y ago
Thanks, I was considering if someone were to say "don't worry about being fast". Since I like sports, I made it a point to say "quick", because in sports being fast could mean messing up and being sloppy, whereas "quick" has a much more positive connotation. I do NOT value making sloppy code, rather I'm just hoping I can learn from guys much better than me, and how they work smarter. Thanks for the comment.
pjhyett 17y ago
We spent months building GitHub's issue system and had a lengthy beta period. No one experienced the bug you're referring to until the feature went public. Shit happens, you fix it and move on.
- vito 17y ago
  Don't get me wrong, I love github, but it seems like every bug on sites I use exists on a site that was developed with Rails or some other framework that advertises rapid development. I'm not accusing you of incompetence, but out of every site I go to it's the one that's most often got some feature disabled because it was too buggy, unplanned, or what have you. Granted, it's also the one with the most new features popping up. Yes, shit happens, but there's a pretty strong correlation between agile development and bugginess, whether it's the mentality it encourages or some other factor.

by vito 17y ago

apsurd 17y ago

Thanks, I was considering if someone were to say "don't worry about being fast". Since I like sports, I made it a point to say "quick", because in sports being fast could mean messing up and being sloppy, whereas "quick" has a much more positive connotation. I do NOT value making sloppy code, rather I'm just hoping I can learn from guys much better than me, and how they work smarter. Thanks for the comment.

pjhyett 17y ago

We spent months building GitHub's issue system and had a lengthy beta period. No one experienced the bug you're referring to until the feature went public. Shit happens, you fix it and move on.

vito 17y ago
Don't get me wrong, I love github, but it seems like every bug on sites I use exists on a site that was developed with Rails or some other framework that advertises rapid development. I'm not accusing you of incompetence, but out of every site I go to it's the one that's most often got some feature disabled because it was too buggy, unplanned, or what have you. Granted, it's also the one with the most new features popping up. Yes, shit happens, but there's a pretty strong correlation between agile development and bugginess, whether it's the mentality it encourages or some other factor.