The one thing that I always found unpleasant when moving between languages was the keywords... so, I picked up a C book, migrated to C++, then Java, picked up PHP along the way. Everything was fairly similar with keywords and syntax, and then perl threw a monkey wrench into the mix. I've never looked at python, are there similarities there or are the perl gurus guiding us through their path of enlightenment?
A farmer who works a farm owned by someone else. The owner provides the land, seed, and tools exchange for part of the crops and goods produced on the farm.
Unfortunately there is little land left to start you rown business (read: software company). Perhaps you'll get a garden sooner or later, but in the end the chances are against becoming the next Microsoft plantation.
Might make a better team than JSP and Java. Check this out. Zend and Sun are working together on a java specification request that will interwork the easy development of PHP as a web front end to the powerful business logic systems that java provides.
Sure you can do SOAP server with PHP, but that's not as good as having a SOAP server with Java (or any other sort of server) and slapping a PHP web interface on top of it. I can't wait until it's ready.
Did anyone else think that this article had a dark undertone of government and corporerations looking to lock down information in the name of security. I mean, some of this information is important and may have benefits to the general public.
The scariest line is that they wanted to burn his research. Flash backs of 1984 flashed in my mind.
Tons of stuff confuses the public, and if organizations like the RIAA can control the definition of terms (MP3 = piracy), than they could help disuade people from pirating (or sharing if that's your angle) music.
I think it comes down to the R&D organization size. I know many large enterprise companies do something like this:
- Market Requirements document authored by the business team, outlines what exactly the market demands to satisfy the customers
- Technical Product Requirements authored by a systems engineer or lead developer who knows all aspects of the entire product, and specifies the feature areas and general product information to satisfy the market requirements
- Software or Feature requirements/architecture: usually authored by a systems engineer or architect (not necessarily the guy who writes code) on how those general feature areas work (GUI functionality, discrete features, etc). In theory you should be able to take these specific requirements and hand them to ANY developer with proper coding skills and they should turn it into exactly what is needed.
I wouldn't expect a developer to get involve at all in the first, a little in the second, and key on the third to say if it is doable or not in the time frame for the project. And of course the product manager (who understands the market) is a required reviewer of all three.
The product manager should state the high level features that the market is demanding. It is then up to the development community, and more specifically a systems engineer or lead developer, to translate those marketing requirements into technical requirements. Customers want to do task A, so that means we need GUI X, and server component Y to let them do A.
The person who actually sits down and writes the code for X and Y doesn't really need to know a lot about A, or be an expert in the market for A, as long as the requirements have been fully specified for X and Y.
Yes, the planning phase of a project should identify the business case that the product will play in and the potential for revenue that the product will generate.
If you dominate the market or have a monopoly, you can pretty much cram whatever you want down the throat of your customers.
Back in the 80s, AT&T decided what phone features you got, they were the market so they could do whatever they want. Today Cisco has some leeway in that area, but there are still other vendors who have some nice innovations that Cisco will then adopt as well. Or Cisco will drive the market and other vendors will reproduce their features, or improve upon them. Such is the glory of competition.
Slashdot Mirror
Yeah! What do they think this is, some sort of end user license agreement?!
True that, and Bill O'Reilly is the pit-bull used to attack opinions that waver from the FoxNews marching tune!
RedHat didn't purchase Ximian?
The one thing that I always found unpleasant when moving between languages was the keywords... so, I picked up a C book, migrated to C++, then Java, picked up PHP along the way. Everything was fairly similar with keywords and syntax, and then perl threw a monkey wrench into the mix. I've never looked at python, are there similarities there or are the perl gurus guiding us through their path of enlightenment?
Do any open source projects get audited for ISO 9001 compliance? They have a quality certification that many [enterprise] customers desire.
I know at work ISO audits are both fun and exciting! (must contain laughter)
What happened to consumer privacy?! Sounds like an RIAA tactic to me!
A farmer who works a farm owned by someone else. The owner provides the land, seed, and tools exchange for part of the crops and goods produced on the farm.
Unfortunately there is little land left to start you rown business (read: software company). Perhaps you'll get a garden sooner or later, but in the end the chances are against becoming the next Microsoft plantation.
Damn, need to find some better metaphors here!
but let's just cut to the chase: Linux wins. SCO might give IBM a bloody nose, but they're not gonna knock that giant down.
That's the point of the project, so a Java object looks like a php object to PHP.
I think it'd just be PHP -> Java middle tier and elminate the web service.
Might make a better team than JSP and Java. Check this out. Zend and Sun are working together on a java specification request that will interwork the easy development of PHP as a web front end to the powerful business logic systems that java provides. Sure you can do SOAP server with PHP, but that's not as good as having a SOAP server with Java (or any other sort of server) and slapping a PHP web interface on top of it. I can't wait until it's ready.
Whoops, you're right
Did anyone else think that this article had a dark undertone of government and corporerations looking to lock down information in the name of security. I mean, some of this information is important and may have benefits to the general public.
The scariest line is that they wanted to burn his research. Flash backs of 1984 flashed in my mind.
In the background, he plays the Beastie Boys.
He's got the right to party!
Tons of stuff confuses the public, and if organizations like the RIAA can control the definition of terms (MP3 = piracy), than they could help disuade people from pirating (or sharing if that's your angle) music.
2 attempts to subscribe ba@cyberangels to a gay magazine;
The trolls strike again!
Why not 8 or 9? Certainly there must be some performance increases in 8 or 9!
Either way, RedHat still won.. 255 to 254, YEAH!!!!
I know we like to challenge all these Amazon patents that come down the pipe citing tons of prior art and how ridiculous the patent sounds...
This patent sounds like a strategic business move though and something that nobody else is doing...
of our large R&D development community is using Netscape, mostly because these people are using mostly Solaris or some are using Red Hat (7.3/8/9).
The other half is ALL IE, Outlook, Exchange.
That's what they all say..
I think it comes down to the R&D organization size. I know many large enterprise companies do something like this:
- Market Requirements document authored by the business team, outlines what exactly the market demands to satisfy the customers
- Technical Product Requirements authored by a systems engineer or lead developer who knows all aspects of the entire product, and specifies the feature areas and general product information to satisfy the market requirements
- Software or Feature requirements/architecture: usually authored by a systems engineer or architect (not necessarily the guy who writes code) on how those general feature areas work (GUI functionality, discrete features, etc). In theory you should be able to take these specific requirements and hand them to ANY developer with proper coding skills and they should turn it into exactly what is needed.
Depending on the organization size, the requirements for a product usually take a few levels:
- Market requirements
- General Technical Product Requirements
- Feature Requirements
I wouldn't expect a developer to get involve at all in the first, a little in the second, and key on the third to say if it is doable or not in the time frame for the project. And of course the product manager (who understands the market) is a required reviewer of all three.
The product manager should state the high level features that the market is demanding. It is then up to the development community, and more specifically a systems engineer or lead developer, to translate those marketing requirements into technical requirements. Customers want to do task A, so that means we need GUI X, and server component Y to let them do A.
The person who actually sits down and writes the code for X and Y doesn't really need to know a lot about A, or be an expert in the market for A, as long as the requirements have been fully specified for X and Y.
Yes, the planning phase of a project should identify the business case that the product will play in and the potential for revenue that the product will generate.
If you dominate the market or have a monopoly, you can pretty much cram whatever you want down the throat of your customers.
Back in the 80s, AT&T decided what phone features you got, they were the market so they could do whatever they want. Today Cisco has some leeway in that area, but there are still other vendors who have some nice innovations that Cisco will then adopt as well. Or Cisco will drive the market and other vendors will reproduce their features, or improve upon them. Such is the glory of competition.
(and analysts, project mgr's etc..)
Those are the people that should provide input into the project as the key source for market direction.