Why wouldn't ebay just 'escrow' all feedback... give notification to the seller that the buyer had posted feedback, but not make it visible until they had also posted. Give X days for each, and if they refuse to leave any, call it 'neutral'.
Seems mostly fair to me... surely they thought of it, though, and for some reason decided one-sided feedback was better?
I haven't used mod_fcgid, but I am definitely going to look into it now. Thanks for the tip. Right now we are using mongrel clusters & mod_proxy_balancer, which does a pretty good job. Proper scripts make it easy to update & start/stop, and I haven't had manually to kill any dead mongrels in a long time (at least 6 months). Better queries and caching is totally the key. Zed had a really interesting writeup, or maybe he was talking about it on someone's podcast, but he talked about using Nginx and some crazy caching schemes to make a better type of dynamic partial caching thing. It sounded interesting, but I haven't been able to find anything else on it. I'm currently doing caching with partials with a cron script to periodically remove the old caches, plus scripts to automatically remove the cache when it detects something change in that area. Also, we use javascripts to pull some small non-critical areas that need to update independently.
The threading thing has been covered in a lot of places. Do a google and read about it... it's really not that big of an issue. For the super heavy tasks, we use DRb. It works very well. The administrative part of things is easily covered with capistrano or with custom scripts. I use the same pattern when I deploy and update sites... I'd hate to think a simple update process is too much work for a developer, but I guess some people are just extremely lazy. That brings me to this idea that Rails is hard to scale. I can't imagine being as lazy as a lot of the "developers" i hear that claim without any real knowledge that Rails is hard to scale.
Here's exactly where the naysayers come from. They watch the screencasts that show a functioning blog being created in 5 minutes and give it a half-assed try. They create something functional, then run into problems deploying. Then they get a little bit of traffic and their crap crashes because they thought they could get away with, say, using scaffolding in a production environment. There are a lot of flashy things in Rails that make it easy to use, but those things aren't really efficient. So, once they get past the shiny parts, they don't get into the actual optimization and they give up. To be a good Rails developer, one has to balance the two and not expect everything to be automatic.
I've noticed that a lot of the crappy Rails developers have gone back to their previous languages. I wondered when it would happen, but there seems to be a pretty big shift... I think that as this happens, we're going to get more trolls that couldn't make it posting about how much (they think) rails sucks.
I'm a full-time rails dev, have been for the last 2 years. The interwebs are big, lots of room (and money) to go around, so I'm not sure why people feel the need to bash rails so much. Seems like a waste of energy.
Exactly right. I don't even preview my layouts in IE until I am sure that they are safe for the standards-compliant browsers, then I implement all of the stupid IE hacks all in one sweep at the end. It takes maybe 5 minutes because the majority of the hacks are predictable.
I'm as pissed about IE still being crap as the next guy, but we have to deal with reality here. It is easy to piss and moan about how shitty IE is, but the fact is, it STILL has huge marketshare and will be around for awhile. 90% of the visitors to my sites are on IE 6 or 7, which is way out of line with the rest of the internet. It doesn't ruin my day to know that when I'm finished with a site or modification that I have to check it in IE, but it does annoy me.
If you have no real-life experience, you will join the legions of other just-out-of-college programmers that have no practical skills or real knowledge. The answer is to write programs RIGHT NOW that you think are important, fun, useful, marketable, etc. Join another project if you want, but whatever you do, it needs to be something you can be passionate about. The more experience you have with real products that people use, the better./self-taught programmer with college education. The self-taught was worth 10x the formal education.
About your point #6, not only is it easier, but it is easier to add onto later. When you use SQL to create objects, you have to go back to whatever line of code you used to do your insert command and adjust the fields. In Rails, you just run a migration to add a field to the table, then modify your form to add that extra field.
And, I think you're pretty much right on about his other "points." The slashdot summary of his post is entirely misleading and total flamebait--and not written by him. I think the guy is just inexperienced and crawled back to PHP out of a lack of wanting to change his mindset. He does in the end give Rails some credit for introducing him to a logical MVC structure, and I doubt he meant to flame Rails. He just happened to make mostly subjective and uninformed points to justify going back to what he already knew... I'm guessing he named his post "7 reasons..." before actually counting the reasons. Blogging is teh hard:p
That's exactly what just happened to me. I left on good terms, stayed on their payroll as an hourly 'consultant' and 2 years later am going back for a much better position.
Okay, that's just idiotic rambling from one who obviously has no Agile experience. Agile programming means planning for things to change, as we ALL know they do. It means designing with flexibility in mind--knowing that when plans, features, behavior, etc., needs to change, you've structured the program in a way that makes it easy to do so. It doesn't mean 'not having a plan' or free-form programming with no structure discipline, but it sure is easy to write off the entire idea by portraying it so:rolls eyes:
If idiots here can't punch all the way through a fucking card, do you really expect them to be able to stay within the lines with an "X"? We have a lot of R-Tards here, I don't know if you've noticed that or not. Let's take the braindeadest of fucks, who have proven that they can't figure out a physical paper ballot and put them in front of a poorly designed computer that probably wasn't calibrated properly by the idiot poll workers.
I agree 100%. The scaffolding should be used to get a feel for how quickly developing *anything* on Rails can be. For newbies or J2ee migrants, the short videos on the Locomotive and rubyonrails.com site shows how scaffolding can be built, modified, etc. There's no way I'd put scaffolding into any site that others will see. It's quick, dirty, and easy. Use and extend it, but don't rely on it!
Coming from J2ee-land, Rails has been really easy to pick up, and very easy to maintain--so far. If you visit the #rubyonrails irc.freenode.net, it's very active, and there are a ton of Java guys who want to see what RoR is all about. My biggest problem was figuring out the project structure and then figuring out the standards. Parenthesis, semicolon line endings, and block brackets not being required really turned me off at first. It felt sloppy and just weird.
I think the biggest advantage is that all of the add-ons we were using are included in RoR. Log4j and hibernate, for example, can be hell to set up and maintain. With RoR, the logger is built in, and its migrations are just hibernate-ish enough to get the functionallity I wanted out of it. The pieces you need are there, and they are easy to use. For us OS X guys, Locomotive makes it ridiculously easy to start out also. I don't know about setting up a RoR app in a production environment... From what I've read there looks like a lot of initial configuration, but I had my share of difficulties with Tomcat also.
Since we're still developing the app, I don't know how easy it will be in the future to maintain. I worry about Ruby updates and how they'll interact with old code. WHat happens when deployed in totally different environments? The API is total suck, and there really isn't a ton of information like there is on J2ee. I want to know the best practices and common ways of doing things, but all I find are blogs and random articles that don't really get into detail. The Programming Ruby and Agile Web Development with Rails books are great, but they don't get into these other areas.
an ellipses (...) in the subject, you don't have to repeat your subject in the body of your message. See how much better my message flows than yours?;-)
I think an effective use of a placebo is when addicts of some types of drugs continue going to methadone clinics, even after the physical addiction is gone... Even if the dosage is so small it doesn't matter, or even if the dosage is a placebo by that time, it makes them feel better to go.
I think it's also one reason why some people feel the need to have a disorder of some kind. It's something like what a hypochondriac feels, but different. I'm not a doctor, but from my understanding, hypochondriacs make themselves sick and need to feel sick, whereas someone who feels the need to have a disorder of some kind needs the attention, or the feeling they get from treatment. I guess it's more like fight club.
err, well... I sortof have to take credit for the original mistake. my t key sticks sometimes. *whoops*
It got accepted, and I read through it again, then emailed the editor on duty (daddypants) before it went out to you non-subscribers... I hoped it'd be fixed in time.
Well as long as you people keep on continuing with this elitist attitude, instead of being inclusive and offering viable alternatives, you'll continue to lose elections to people you think are as stupid as Bush.
If Bush voters are so stupid, then your party of intellectual superiority should have had no problem convincing them of your agenda.
I would bet that there are quite a few of us web designers that use DreamWeaver in "Code View" instead of WYSIWYG.
Those who are tied completely to the WYSIWYG view are fooling themselves. DW will absolutely rape your code, and it takes a ton of work to make it compliant after it's taken over.
For DW's site management, tag completion, and upload ease, DW can be a pretty useful tool.
DW is buggy, does lock up, and does require updates/patches... But then again, if someone uses DW, they probably use Windows too*, so they should be used to lock-ups and patching.
That's basically what I do. Design the whole site in Photoshop/Fireworks, slice it up, put it into dreamweaver. From there, get it looking right, then chop the file into whatever includes it will need to become, usually a header and footer.
I don't understand why you'd want to use Dreamweaver's templates in the first place. One change to a template and you have to save, update, then upload your entire site... it doesn't make much sense. Of course, it could be more advanced now--I used it for all of a week before I realized that including a file is way simpler.
I agree completely... I've used H&R for the last 4 years. They always find things I wouldn't have, and if you consistantly go to the same person, it builds up a decent relationship. Definitely makes tax time less sucky.
I don't even know what it costs to go there... I just take my stuff, and if there's a refund I have their charge come out of it.
Not enough proof that global warming exists, and there's less proof that we're to blame. Anyone have stats on how much pollution released from a single eruption vs pollution caused by industrialized countries?
Slashdot Mirror
Area51/Rampart here. Surrounded by other M:TG and Warcraft sites.
Why wouldn't ebay just 'escrow' all feedback... give notification to the seller that the buyer had posted feedback, but not make it visible until they had also posted. Give X days for each, and if they refuse to leave any, call it 'neutral'. Seems mostly fair to me... surely they thought of it, though, and for some reason decided one-sided feedback was better?
I haven't used mod_fcgid, but I am definitely going to look into it now. Thanks for the tip. Right now we are using mongrel clusters & mod_proxy_balancer, which does a pretty good job. Proper scripts make it easy to update & start/stop, and I haven't had manually to kill any dead mongrels in a long time (at least 6 months). Better queries and caching is totally the key. Zed had a really interesting writeup, or maybe he was talking about it on someone's podcast, but he talked about using Nginx and some crazy caching schemes to make a better type of dynamic partial caching thing. It sounded interesting, but I haven't been able to find anything else on it. I'm currently doing caching with partials with a cron script to periodically remove the old caches, plus scripts to automatically remove the cache when it detects something change in that area. Also, we use javascripts to pull some small non-critical areas that need to update independently.
The threading thing has been covered in a lot of places. Do a google and read about it... it's really not that big of an issue. For the super heavy tasks, we use DRb. It works very well. The administrative part of things is easily covered with capistrano or with custom scripts. I use the same pattern when I deploy and update sites... I'd hate to think a simple update process is too much work for a developer, but I guess some people are just extremely lazy. That brings me to this idea that Rails is hard to scale. I can't imagine being as lazy as a lot of the "developers" i hear that claim without any real knowledge that Rails is hard to scale.
/Just the opinion of a full-time rails developer.
Here's exactly where the naysayers come from. They watch the screencasts that show a functioning blog being created in 5 minutes and give it a half-assed try. They create something functional, then run into problems deploying. Then they get a little bit of traffic and their crap crashes because they thought they could get away with, say, using scaffolding in a production environment. There are a lot of flashy things in Rails that make it easy to use, but those things aren't really efficient. So, once they get past the shiny parts, they don't get into the actual optimization and they give up. To be a good Rails developer, one has to balance the two and not expect everything to be automatic.
I've noticed that a lot of the crappy Rails developers have gone back to their previous languages. I wondered when it would happen, but there seems to be a pretty big shift... I think that as this happens, we're going to get more trolls that couldn't make it posting about how much (they think) rails sucks.
I'm a full-time rails dev, have been for the last 2 years. The interwebs are big, lots of room (and money) to go around, so I'm not sure why people feel the need to bash rails so much. Seems like a waste of energy.
Exactly right. I don't even preview my layouts in IE until I am sure that they are safe for the standards-compliant browsers, then I implement all of the stupid IE hacks all in one sweep at the end. It takes maybe 5 minutes because the majority of the hacks are predictable.
I'm as pissed about IE still being crap as the next guy, but we have to deal with reality here. It is easy to piss and moan about how shitty IE is, but the fact is, it STILL has huge marketshare and will be around for awhile. 90% of the visitors to my sites are on IE 6 or 7, which is way out of line with the rest of the internet. It doesn't ruin my day to know that when I'm finished with a site or modification that I have to check it in IE, but it does annoy me.
If you have no real-life experience, you will join the legions of other just-out-of-college programmers that have no practical skills or real knowledge. The answer is to write programs RIGHT NOW that you think are important, fun, useful, marketable, etc. Join another project if you want, but whatever you do, it needs to be something you can be passionate about. The more experience you have with real products that people use, the better. /self-taught programmer with college education. The self-taught was worth 10x the formal education.
About your point #6, not only is it easier, but it is easier to add onto later. When you use SQL to create objects, you have to go back to whatever line of code you used to do your insert command and adjust the fields. In Rails, you just run a migration to add a field to the table, then modify your form to add that extra field.
:p
And, I think you're pretty much right on about his other "points." The slashdot summary of his post is entirely misleading and total flamebait--and not written by him. I think the guy is just inexperienced and crawled back to PHP out of a lack of wanting to change his mindset. He does in the end give Rails some credit for introducing him to a logical MVC structure, and I doubt he meant to flame Rails. He just happened to make mostly subjective and uninformed points to justify going back to what he already knew... I'm guessing he named his post "7 reasons..." before actually counting the reasons. Blogging is teh hard
That's exactly what just happened to me. I left on good terms, stayed on their payroll as an hourly 'consultant' and 2 years later am going back for a much better position.
Okay, that's just idiotic rambling from one who obviously has no Agile experience. Agile programming means planning for things to change, as we ALL know they do. It means designing with flexibility in mind--knowing that when plans, features, behavior, etc., needs to change, you've structured the program in a way that makes it easy to do so. It doesn't mean 'not having a plan' or free-form programming with no structure discipline, but it sure is easy to write off the entire idea by portraying it so :rolls eyes:
http://www.youtube.com/watch?v=bQjR9EOwHuw is what I meant
If idiots here can't punch all the way through a fucking card, do you really expect them to be able to stay within the lines with an "X"? We have a lot of R-Tards here, I don't know if you've noticed that or not. Let's take the braindeadest of fucks, who have proven that they can't figure out a physical paper ballot and put them in front of a poorly designed computer that probably wasn't calibrated properly by the idiot poll workers.
Google suggest is a simple one.
I agree 100%. The scaffolding should be used to get a feel for how quickly developing *anything* on Rails can be. For newbies or J2ee migrants, the short videos on the Locomotive and rubyonrails.com site shows how scaffolding can be built, modified, etc. There's no way I'd put scaffolding into any site that others will see. It's quick, dirty, and easy. Use and extend it, but don't rely on it!
Coming from J2ee-land, Rails has been really easy to pick up, and very easy to maintain--so far. If you visit the #rubyonrails irc.freenode.net, it's very active, and there are a ton of Java guys who want to see what RoR is all about. My biggest problem was figuring out the project structure and then figuring out the standards. Parenthesis, semicolon line endings, and block brackets not being required really turned me off at first. It felt sloppy and just weird.
I think the biggest advantage is that all of the add-ons we were using are included in RoR. Log4j and hibernate, for example, can be hell to set up and maintain. With RoR, the logger is built in, and its migrations are just hibernate-ish enough to get the functionallity I wanted out of it. The pieces you need are there, and they are easy to use. For us OS X guys, Locomotive makes it ridiculously easy to start out also. I don't know about setting up a RoR app in a production environment... From what I've read there looks like a lot of initial configuration, but I had my share of difficulties with Tomcat also.
Since we're still developing the app, I don't know how easy it will be in the future to maintain. I worry about Ruby updates and how they'll interact with old code. WHat happens when deployed in totally different environments? The API is total suck, and there really isn't a ton of information like there is on J2ee. I want to know the best practices and common ways of doing things, but all I find are blogs and random articles that don't really get into detail. The Programming Ruby and Agile Web Development with Rails books are great, but they don't get into these other areas.
Especially if you paint it yellow.
damn, poo, you got me again :)
an ellipses (...) in the subject, you don't have to repeat your subject in the body of your message. See how much better my message flows than yours? ;-)
I think an effective use of a placebo is when addicts of some types of drugs continue going to methadone clinics, even after the physical addiction is gone... Even if the dosage is so small it doesn't matter, or even if the dosage is a placebo by that time, it makes them feel better to go.
I think it's also one reason why some people feel the need to have a disorder of some kind. It's something like what a hypochondriac feels, but different. I'm not a doctor, but from my understanding, hypochondriacs make themselves sick and need to feel sick, whereas someone who feels the need to have a disorder of some kind needs the attention, or the feeling they get from treatment. I guess it's more like fight club.
err, well... I sortof have to take credit for the original mistake. my t key sticks sometimes. *whoops*
It got accepted, and I read through it again, then emailed the editor on duty (daddypants) before it went out to you non-subscribers... I hoped it'd be fixed in time.
Well as long as you people keep on continuing with this elitist attitude, instead of being inclusive and offering viable alternatives, you'll continue to lose elections to people you think are as stupid as Bush.
If Bush voters are so stupid, then your party of intellectual superiority should have had no problem convincing them of your agenda.
I would bet that there are quite a few of us web designers that use DreamWeaver in "Code View" instead of WYSIWYG.
Those who are tied completely to the WYSIWYG view are fooling themselves. DW will absolutely rape your code, and it takes a ton of work to make it compliant after it's taken over.
For DW's site management, tag completion, and upload ease, DW can be a pretty useful tool.
DW is buggy, does lock up, and does require updates/patches... But then again, if someone uses DW, they probably use Windows too*, so they should be used to lock-ups and patching.
I'm a DW user on OS X.
That's basically what I do. Design the whole site in Photoshop/Fireworks, slice it up, put it into dreamweaver. From there, get it looking right, then chop the file into whatever includes it will need to become, usually a header and footer.
I don't understand why you'd want to use Dreamweaver's templates in the first place. One change to a template and you have to save, update, then upload your entire site... it doesn't make much sense. Of course, it could be more advanced now--I used it for all of a week before I realized that including a file is way simpler.
I agree completely... I've used H&R for the last 4 years. They always find things I wouldn't have, and if you consistantly go to the same person, it builds up a decent relationship. Definitely makes tax time less sucky.
I don't even know what it costs to go there... I just take my stuff, and if there's a refund I have their charge come out of it.
This last summer was the 12th coldest summer in a hundred years, here in Nebraska. (http://www.journalstar.com/articles/2004/09/23/lo cal/10055198.txt)
Not enough proof that global warming exists, and there's less proof that we're to blame. Anyone have stats on how much pollution released from a single eruption vs pollution caused by industrialized countries?
"John Kerry voted for George Bush's War"
makes us right-wingers chuckle, and the lefties cringe.