Switched the family off of Telus last year (land line and cells) after being told to politely screw off by Telus staff over questions about over billing and rate plan changes.
They tried to get my 16 year old daughter to sign a new three year contract before they would look at her broken phone. Yes, the plan was in our name.
The upped the rates on our phones twice without any notification.
The wouldn't come to repair faulty wiring hanging from the pole outside our house (Shaw fixed it).
The best part of getting off Telus was that I didn't have to listen their staff complain to me about their hangovers and crappy jobs.
Without a doubt the worst company I have ever had to deal with in my entire life. I can't figure out if the management hates their staff or their customers more.
Frameworks such as RoR which do not provide datamodelers the flexibility to design a model the way they'd like to are by their nature limited. Sure, it many cases it's possible to work around these limitations but that's no reason not to point them out. It is certainly one of the reasons it's not caught on more broadly in enterprise environments where database performance is often paramount to rapid development.
You're not serious are you? RoR provides incremental changes, testing, rollback, data transformation, syncronization of code with data elements, automatic performance metrics, and reporting out of the box. RoR and other progessive , testable, verifiable frameworks already live inside banks, trading houses, insurance companies, large internet service providers, telecoms and (dare I say it) large database vendors. Rails is just one framework that supports this type of disciplined developement which includes databases as part of the stack.
It's a big bad world out there, but it's not that scarey.
Oh crap, I have to test my app.
Oh crap, I have to think about my domain.
Oh crap, I have to fulfill requirements from the dba first.
Dude, autoincrmenting primary keys in a databases? Geez, I wonder why ever frickin' database on the planet supports it. I guess we are all morons.
A 4 month delay on rolling out their new OS? KDE has been delayed more than that. Let's not even talk about Vista - wow they really nailed that. Missed what opportunity - it's not like the competition is expected to hit any home runs over the next year.
There's more important stories around Apple that people should be concerned about - supply chain management, native Intel support for Office coming late, or the potential competition from a open gPhone. Time weighing heavy on the subbies hands?
I don't think this is technology question. If you look at well researched info like the Chaos report the majority of technology projects fails, regardless of the technology. To blame RoR (or PHP, Java,.NET, etc) for their problems is missing the point. There are a lot of bad smells here and it has little to do with technology.
They have integration problems, fighting fires for existing systems (Hello???), and don't seem to have a clear technology selection approach. Of course, this particular shop will be more successful with PHP because they know it best and the demands of their business (business complexity, transactionality, infrastructure, etc) are will suited to this.
I've seen plenty of blanket criticisms like "it's consistent with other RoR criticism" leveled against plenty of technologies for years. I have one ex-client whose business is currently in severe peril since their PHP infrastructure is crumbling. Does this mean PHP is bad? Hardly. Does this mean the vendor that is providing the technology has poor development, testing, and support practices. Probably.
I've seen lots of PHP, Ruby, Python, Java,.NET, C++, Smalltalk, etc, etc, etc projects fail. What it means is that software development is difficult.
I've got to agree. In two years he could have rewritten this in Fortran on MVS. This has nothing to do with techonology. Obviously he's not comfortable with Ruby - it not be the right language for him since it's full on OOP. Complaining about integration problems because two systems are written in different languages indicates that their systems are tightly coupled. As Homer Simposon would say "Doh!".
Probably sticking with PHP in their shop is a good idea in their case and they would have gotten in over their heads with . The second rule of techonology problems is "No matter how it looks at first, it's always a people problem."
Slashdot Mirror
How about asking the question: "Is it good for business to fund applied and theoretical research and development?"
Easy call in my mind.
Switched the family off of Telus last year (land line and cells) after being told to politely screw off by Telus staff over questions about over billing and rate plan changes. They tried to get my 16 year old daughter to sign a new three year contract before they would look at her broken phone. Yes, the plan was in our name. The upped the rates on our phones twice without any notification. The wouldn't come to repair faulty wiring hanging from the pole outside our house (Shaw fixed it). The best part of getting off Telus was that I didn't have to listen their staff complain to me about their hangovers and crappy jobs. Without a doubt the worst company I have ever had to deal with in my entire life. I can't figure out if the management hates their staff or their customers more.
Frameworks such as RoR which do not provide datamodelers the flexibility to design a model the way they'd like to are by their nature limited. Sure, it many cases it's possible to work around these limitations but that's no reason not to point them out. It is certainly one of the reasons it's not caught on more broadly in enterprise environments where database performance is often paramount to rapid development. You're not serious are you? RoR provides incremental changes, testing, rollback, data transformation, syncronization of code with data elements, automatic performance metrics, and reporting out of the box. RoR and other progessive , testable, verifiable frameworks already live inside banks, trading houses, insurance companies, large internet service providers, telecoms and (dare I say it) large database vendors. Rails is just one framework that supports this type of disciplined developement which includes databases as part of the stack.
It's a big bad world out there, but it's not that scarey.
Oh crap, I have to test my app. Oh crap, I have to think about my domain. Oh crap, I have to fulfill requirements from the dba first. Dude, autoincrmenting primary keys in a databases? Geez, I wonder why ever frickin' database on the planet supports it. I guess we are all morons.
They have $20 billion in cash.
A 4 month delay on rolling out their new OS? KDE has been delayed more than that. Let's not even talk about Vista - wow they really nailed that. Missed what opportunity - it's not like the competition is expected to hit any home runs over the next year. There's more important stories around Apple that people should be concerned about - supply chain management, native Intel support for Office coming late, or the potential competition from a open gPhone. Time weighing heavy on the subbies hands?
Do you think Derek could have written his new site from scratch in two months if he didn't have two huge messes behind him?
I don't think this is technology question. If you look at well researched info like the Chaos report the majority of technology projects fails, regardless of the technology. To blame RoR (or PHP, Java, .NET, etc) for their problems is missing the point. There are a lot of bad smells here and it has little to do with technology.
They have integration problems, fighting fires for existing systems (Hello???), and don't seem to have a clear technology selection approach. Of course, this particular shop will be more successful with PHP because they know it best and the demands of their business (business complexity, transactionality, infrastructure, etc) are will suited to this.
I've seen plenty of blanket criticisms like "it's consistent with other RoR criticism" leveled against plenty of technologies for years. I have one ex-client whose business is currently in severe peril since their PHP infrastructure is crumbling. Does this mean PHP is bad? Hardly. Does this mean the vendor that is providing the technology has poor development, testing, and support practices. Probably.
I've seen lots of PHP, Ruby, Python, Java, .NET, C++, Smalltalk, etc, etc, etc projects fail. What it means is that software development is difficult.
I've got to agree. In two years he could have rewritten this in Fortran on MVS. This has nothing to do with techonology. Obviously he's not comfortable with Ruby - it not be the right language for him since it's full on OOP. Complaining about integration problems because two systems are written in different languages indicates that their systems are tightly coupled. As Homer Simposon would say "Doh!". Probably sticking with PHP in their shop is a good idea in their case and they would have gotten in over their heads with . The second rule of techonology problems is "No matter how it looks at first, it's always a people problem."