My 88-year-old (at the time, she's 94 now) grandmother actually broke her hip when she slipped on a banana peel near a bus stop. We teased her about it for weeks after her speedy and complete recovery after a hip replacement.
As a developer who's tried a number of keyboards, I can vouch for the "chiclet" keyboard being the best available keyboard on the market, bar none (the wired desktop version, that is).
Without the midichlorian story device, Vader would have continued to be as powerful after his battle with Obi-Wan as he was before it. Since the midichlorians in his bloodstream provided his link to the Force, once he became "more machine...than man" he could no longer control it as he once did, thus weakening him to the point where he was defeatable.
When there is no network available, I recommend putting the phone back in your pocket and enjoying the view and the company of others. How's that for a sweet solution?
His main point is that "simple" does not necessarily equal "fewer features." Similarly, "more features" does not necessarily equal "more complex." Simplicity in the user interface IS a feature. Simplicity is achieved partially by matching the program model to the user model, which in software is almost always the right thing to do. To use his example, I don't expect to have to wade through 10+ options for powering off my computer. I should be able to push the button and it's off (this is the user model). Too many input choices for what is essentially a single output is a real pain in the butt. This is the program model not matching the user model, which pretty much defines a complex user interface. Add features but keep the UI simple. That's the whole point.
Our Church of Emacs is very open minded, we discuss both how best to worship our Saviour among the True Believers, and also welcome preachers of false religions like The Church of Bill Gates, Discordia, and vi to our church, where we can test their silly misconceptions against out pure and strong faith . Most of the information in this page is from these discussions. Please don't misuse our sacred place to discuss joke religions like Scientology, Kibology, or BoB.
Agile doesn't mean no documentation. It means less documentation, sure. It doesn't mean no analysis, it doesn't mean no audits - it means that these things should be done when they make sense and in ways that make sense. Having this sort of requirement from the customer means that it should be done. There's no reason that agile development methods shouldn't be used. For the most part, agile development methods are best practices anyway. This means EXTENSIVE unit testing (written BEFORE the implementation classes), EXTENSIVE interaction with the customer, and documentation that actually matches the implementation (remember, if documentation and code don't match up, they're both wrong). Said documentation can be extensive as well.
Part of agile (to me, at least) is taking away the tedium of development - automating the build and deployment, especially. Having a automated, documented, and repeatable build process seems like it would pass any audit. This also lets you analyze the health of your projects more easily too. It all comes together with Agile...
The point here is that a different implementation language would better serve the needs of the desired process. If they're trying to move to an Agile model, which it sounds like they are, then Java using Spring and Hibernate will assist in that process. Spring especially is designed to make best practices more easily attainable. Following best practices makes the code more maintainable. IMO, maintainable code equates to fewer bugs & happier developers that can spend more time understanding the problem domain. This seems to be what they're going for.
Even if this transition does take a year or more, they're already losing money because of their current process. The technologies mentioned are built around a better process, so using them will at the very least help them change their mindset. I'm not saying that C++ can't be used in such an environment, but it seems that it'd be that much more difficult - especially since their code base seems to need rewriting anyway.
"Paradigm" and "synergy" both have very specific meanings and are quite useful when used correctly. Padding sentences with them is unforgivable, but when used properly they convey a very clear idea in a single word that would otherwise require an entire sentence. Writing these words off whole cloth marks you as unprofessional and somewhat uneducated.
The more people that develop buggy, slow, insecure, non-upgradeable & unmaintainable "applications" in Office, the more people will realize they shouldn't have paid their cousin to develop an app just because he could write a web page. This translates into dollars for me and my team, who have cleaned up such a mess on more than one occasion. Unfortunately, the price tag for this tends to be rather high, especially when compared to "pay me $500 and I'll do it" that he's getting from his brother-in-law (who inevitably divorces and leaves the business high and dry).
So, good luck with all that. Send me an email when you realize you've coded yourself into a corner because you run into a security problem or you're out of resources because Outlook is hogging them all...guess I'll see you on The Daily WTF sometime soon.
Oh, Windows more featureful than OS X? "Ajax isn't a competitor to OLE?" Nice try. And you call yourself an open source "zealot." Whatever.
Was said professor also the one who discovered the Pentium bug, by chance? This is not a smartass remark, as you would recognize if you had this professor...
Re:Thats the whole point of the "puzzler"
on
Java Puzzlers
·
· Score: 1
One generally uses Java for its excellent OO-ness, not because they want to use primitives...
I haven't had experience with integrating PHP into an "enterprise" situation personally, but I'll refer you to Zend's Enterprise PHP page for various reasons why PHP is indeed ready for the enterprise.
The link you provided took over a minute to load. Any enterprise that relies on PHP for its enterprise solution is a doomed enterprise, at least IT-wise.
Slashdot Mirror
My 88-year-old (at the time, she's 94 now) grandmother actually broke her hip when she slipped on a banana peel near a bus stop. We teased her about it for weeks after her speedy and complete recovery after a hip replacement.
Without governance your IT department is screwed. IT is a service and must be treated as such - just like calling a lawyer.
As a developer who's tried a number of keyboards, I can vouch for the "chiclet" keyboard being the best available keyboard on the market, bar none (the wired desktop version, that is).
Without the midichlorian story device, Vader would have continued to be as powerful after his battle with Obi-Wan as he was before it. Since the midichlorians in his bloodstream provided his link to the Force, once he became "more machine...than man" he could no longer control it as he once did, thus weakening him to the point where he was defeatable.
The time has come for you to either change your organization or change your organization. (credit to Scott Ambler)
How did Dumbledore's painting know of the plan to take Harry off Private Drive, in order to counsel Snape?
That was Dumbledore himself, plotting book seven with Snape.
PS It's Privet.
Is there a cellphone that does this? Sign me up!!!
Beer at home: $1. Beer at a club: $7. Perhaps it's *you* missing the reason bars make so much money.
When there is no network available, I recommend putting the phone back in your pocket and enjoying the view and the company of others. How's that for a sweet solution?
This album came out LAST week.
And exactly what software comes with that Asus?
His main point is that "simple" does not necessarily equal "fewer features." Similarly, "more features" does not necessarily equal "more complex." Simplicity in the user interface IS a feature. Simplicity is achieved partially by matching the program model to the user model, which in software is almost always the right thing to do. To use his example, I don't expect to have to wade through 10+ options for powering off my computer. I should be able to push the button and it's off (this is the user model). Too many input choices for what is essentially a single output is a real pain in the butt. This is the program model not matching the user model, which pretty much defines a complex user interface. Add features but keep the UI simple. That's the whole point.
> There's no "religion issue".
Gonna have to disagree with your police work there:
http://www.dina.kvl.dk/~abraham/religion/
Our Church of Emacs is very open minded, we discuss both how best to worship our Saviour among the True Believers, and also welcome preachers of false religions like The Church of Bill Gates, Discordia, and vi to our church, where we can test their silly misconceptions against out pure and strong faith . Most of the information in this page is from these discussions. Please don't misuse our sacred place to discuss joke religions like Scientology, Kibology, or BoB.
You should check out Spring's MVC as well. While you're at it, Spring might help with other areas of your code, like coupling and testability.
You know you can disable scriptlets in the container, right?
Agile doesn't mean no documentation. It means less documentation, sure. It doesn't mean no analysis, it doesn't mean no audits - it means that these things should be done when they make sense and in ways that make sense. Having this sort of requirement from the customer means that it should be done. There's no reason that agile development methods shouldn't be used. For the most part, agile development methods are best practices anyway. This means EXTENSIVE unit testing (written BEFORE the implementation classes), EXTENSIVE interaction with the customer, and documentation that actually matches the implementation (remember, if documentation and code don't match up, they're both wrong). Said documentation can be extensive as well.
Part of agile (to me, at least) is taking away the tedium of development - automating the build and deployment, especially. Having a automated, documented, and repeatable build process seems like it would pass any audit. This also lets you analyze the health of your projects more easily too. It all comes together with Agile...
The point here is that a different implementation language would better serve the needs of the desired process. If they're trying to move to an Agile model, which it sounds like they are, then Java using Spring and Hibernate will assist in that process. Spring especially is designed to make best practices more easily attainable. Following best practices makes the code more maintainable. IMO, maintainable code equates to fewer bugs & happier developers that can spend more time understanding the problem domain. This seems to be what they're going for.
Even if this transition does take a year or more, they're already losing money because of their current process. The technologies mentioned are built around a better process, so using them will at the very least help them change their mindset. I'm not saying that C++ can't be used in such an environment, but it seems that it'd be that much more difficult - especially since their code base seems to need rewriting anyway.
Coleman
"Paradigm" and "synergy" both have very specific meanings and are quite useful when used correctly. Padding sentences with them is unforgivable, but when used properly they convey a very clear idea in a single word that would otherwise require an entire sentence. Writing these words off whole cloth marks you as unprofessional and somewhat uneducated.
Anything declared as "Enterprise" that runs on the JET database engine meets the definition of a "bad" product.
The more people that develop buggy, slow, insecure, non-upgradeable & unmaintainable "applications" in Office, the more people will realize they shouldn't have paid their cousin to develop an app just because he could write a web page. This translates into dollars for me and my team, who have cleaned up such a mess on more than one occasion. Unfortunately, the price tag for this tends to be rather high, especially when compared to "pay me $500 and I'll do it" that he's getting from his brother-in-law (who inevitably divorces and leaves the business high and dry).
So, good luck with all that. Send me an email when you realize you've coded yourself into a corner because you run into a security problem or you're out of resources because Outlook is hogging them all...guess I'll see you on The Daily WTF sometime soon.
Oh, Windows more featureful than OS X? "Ajax isn't a competitor to OLE?" Nice try. And you call yourself an open source "zealot." Whatever.
PWNED.
Was said professor also the one who discovered the Pentium bug, by chance? This is not a smartass remark, as you would recognize if you had this professor...
One generally uses Java for its excellent OO-ness, not because they want to use primitives...
The link you provided took over a minute to load. Any enterprise that relies on PHP for its enterprise solution is a doomed enterprise, at least IT-wise.