surf dtoid with 
Rising (10+)
People you follow
send message
follow
followers
I am such a huge fan of anal nitpicking. Here we have broken links, poor spacing and bbcode issues I wouldn't have thought to complain about. kudos sir.
You are being very generous, there is so much shit that needs fixing. So much shit I could fix myself. Not looking for work, but I mean, I would fix this shit if you paid me Niero, 3 years of practical programming experience here.
also
Seriously, lets take care of repairs before we move on to improvements.
well said.
also
Seriously, lets take care of repairs before we move on to improvements.
well said.
@Manasteel88
I'm... not sure how sarcastic that is. As a web developer, things like this really do get under my skin. I'm pretty OCD about my own creations, but this is different. They added the "your blogs" tab semi-recently and it has never worked. That's not "oh no, it's off a pixel", it's "did you ever click it?"
I've had my own share of janky alignment issues, but the cblog's spacing wasn't messed up before. At some point, changes were made and then it became bad. If it's using a wordpress-style include for posts list and individual display, It should be the same either way because it's in the same template.
@Lenigod
I know this is missing some things, but I can't remember all of them, and I didn't want to list any issue I couldn't reproduce in a couple browsers.
I'm... not sure how sarcastic that is. As a web developer, things like this really do get under my skin. I'm pretty OCD about my own creations, but this is different. They added the "your blogs" tab semi-recently and it has never worked. That's not "oh no, it's off a pixel", it's "did you ever click it?"
I've had my own share of janky alignment issues, but the cblog's spacing wasn't messed up before. At some point, changes were made and then it became bad. If it's using a wordpress-style include for posts list and individual display, It should be the same either way because it's in the same template.
@Lenigod
I know this is missing some things, but I can't remember all of them, and I didn't want to list any issue I couldn't reproduce in a couple browsers.
@trev
Here is what I feel like every time I find something broken
I think it's due in part to me working in a similar field, that not only do I find 'broken' things easier, but many times I realize it is the result of rushed or un-tested code.
Here is what I feel like every time I find something broken
I think it's due in part to me working in a similar field, that not only do I find 'broken' things easier, but many times I realize it is the result of rushed or un-tested code.
not really a whole lot of sarcasm, only a small pinch of it. Mostly referring to pic 1 and 2 as things that aren't really necessary improvements, but do annoy me. I had completely forgotten about that broken color thing and it's the best place to start in repairs.
Totally with you on like all of these things, even the minor ones. A nice, polished looking site looks good. I'd like to have one of those.
I'm really glad Niero put out a call for these blogs. I feel like people have been holding this stuff in for a long time.
Anyway, a lot of good suggestions here. Thanks!
Anyway, a lot of good suggestions here. Thanks!
Thanks for the suggestions. Just to let you know we've been working on a Elephant 2.0 which will solve many, many of these issues.
Like mentioned before, the system we're on was untested and was made very quickly to keep up with the community growing, to some degree we're happy that we took the "do it" path, but we're kind of sad that we've had so many issues due to that.
Also, please bear in mind that we're all capable engineers with lots of experience (some of us wrote books about it, have open source projects, worked for bigger companies, etc). The issue here is that we've had years and years of legacy code which we're taking out of the new version of Elephant.
So be patient. You'll love the new improvements.
Like mentioned before, the system we're on was untested and was made very quickly to keep up with the community growing, to some degree we're happy that we took the "do it" path, but we're kind of sad that we've had so many issues due to that.
Also, please bear in mind that we're all capable engineers with lots of experience (some of us wrote books about it, have open source projects, worked for bigger companies, etc). The issue here is that we've had years and years of legacy code which we're taking out of the new version of Elephant.
So be patient. You'll love the new improvements.
@kurior
I'm trying to think of the right way to express this, so take it with a grain of salt. I'm not questioning the abilities of your or the other people that work on it, but the mentality with which it is applied. Since it's what I do, I can only look at it through that lens of a developer. Dtoid seems to go through phases; a hot, new idea comes up, is plugged, gets mostly implemented, and is then just sort of dropped, never to be mentioned again.
The youtube thing is a perfect example of what I'm trying to say. I have a google doc of videos I wanted to add to posts that hasn't been edited for 45 days, which means it's been at least that long since I gave up looking for fun videos for FNF posts and it was created well before that. So video support was pulled out, and I wouldn't have done that until the new thing was ready. Similarly, between beta.destructoid going away and the potential future fixing of any of the things listed here, Flixist was created. I was getting "Assertion Failed: Bad TK" when I tried to embed a video, but an entire new site was set up. That's not what I would do, so when I see it with developer-vision, I end up in wtfrudointown.
This comment is going on too long, I think. In a nutshell (ah, help, I'm trapped), it's not that I mind the "do it" path, it's that from the outside the path seems things don' get fully done. If the new software is going to fix things, great, but don't backtrack on it. Put it in place and do it until it works.
I'm trying to think of the right way to express this, so take it with a grain of salt. I'm not questioning the abilities of your or the other people that work on it, but the mentality with which it is applied. Since it's what I do, I can only look at it through that lens of a developer. Dtoid seems to go through phases; a hot, new idea comes up, is plugged, gets mostly implemented, and is then just sort of dropped, never to be mentioned again.
The youtube thing is a perfect example of what I'm trying to say. I have a google doc of videos I wanted to add to posts that hasn't been edited for 45 days, which means it's been at least that long since I gave up looking for fun videos for FNF posts and it was created well before that. So video support was pulled out, and I wouldn't have done that until the new thing was ready. Similarly, between beta.destructoid going away and the potential future fixing of any of the things listed here, Flixist was created. I was getting "Assertion Failed: Bad TK" when I tried to embed a video, but an entire new site was set up. That's not what I would do, so when I see it with developer-vision, I end up in wtfrudointown.
This comment is going on too long, I think. In a nutshell (ah, help, I'm trapped), it's not that I mind the "do it" path, it's that from the outside the path seems things don' get fully done. If the new software is going to fix things, great, but don't backtrack on it. Put it in place and do it until it works.
