1. Put Your own Communication Satellites into space. 2. Purchase a fleet of container ships and load up with servers and satcom gear. 3. ??? 4. Profit!!!
If you are fulfulling the responsibility of an Architect, you better damn well understand the following:
1. Networking - in particular how many simultaneous connections can be handled by a given machine, network device, and throughput of same. This has implications when designing systems - particularly high performance systems (multiple threads, multiple users, and large data transfers). What are the various strengths and limitations of various protocols (http, h323, IP, UDP etc) considered. What are the network security implications of the design?
2. File Systems and Storage - how many inodes does a given filesystem partition contain, will the app outstrip local disk usage so a NAS or Storage Area Network is required?
3. Databases and Directories (LDAP) - how much overhead does oracle require vs PostGre vs MySql etc and what are the tradeoffs with regard to performance and cost, what is appropriate to store in a DB versus a directory, and can you extend the directory as needed or does the vendor(s) own the key attribute tree? etc..
4. Hardware - when will a workstation suffice, when do you need a server, when do you need an array of servers, when do you need a high performance computing cluster or super computer and what is the difference (in cost, energy consumption, and performance)? Will you need to include backup and restoration gear, laboratory and testing gear, and development gear in your plans?
5. Tools - what are the tradeoffs for various proprietary tools, and FOSS tools? What are the best tools for the job? What does your teams know how to use efficiently? Will the cost of retraining be worth the benefits of a different approach?
6. Project Management - you have to keep the PMs straight, particularly if they did not come out of the development side.
7. Finance - you have to be able to justify the costs associated with your decisions and understand how they impact the overall business case (can we afford to do X)?
This list just scratches the surface - these are areas that I have seen architects and system developers fall down on the job - too many times. Attempting to grok systems architecture is a life long learning experience.
There are some things that work well as a server side application, and there are other things that work better on the client side.
If you need multiple people to access the same data, or you need to be able to access the data remotely - then software as a service is a good choice (and you can own the servers yourself - serving yourself, as it were - if you are concerned about your data being in other's hands. Of course you'll need to manage the system yourself then).
If you need stability and performance - then client side applications fit the bill (you will need to manage upgrades, backups and data syncronization as required).
If you need absolute security - then don't put it on the network at all.
Risk is involved in all of those decisions - balancing it out to get the right mix is your best bet.
I'm a musician, have played in bands, have done recording of various types (multitrack, reel2reel mastering, digital) and have known a number of audiophiles (and enjoyed their systems) over the years.
This argument is similar to the debate years ago surrounding speaker cables. I wanted to get to the bottom of it, so I set up a test. I could not detect a difference between using expensive 'monster' cable and cheap lamp cable for the same set of speakers (although it is true that the potential for induction/crosstalk increases in the non-shielded cable - a smart deployment of the wire, seperated from power and crossing at right angles when needed, decreases the likelyhood of interference - and doesn't cost an arm and a leg).
Similarly, with a high quality headset (high and low frequencies beyond 'standard' headsets) - I can't tell the difference between a CD and a MP3 of the same song played through my system. Taking a step farther still, the sound is certainly better for that particular music than was possible via Cassette Tape or over the FM radio back in the day.
Short of hearing a live performance of the song - MP3 is as good as it gets - and certainly audio equivalent to CD when uncompressed. The argument from the article is a fallacy as far as I am concerned. Now it may be possible that someone with extraordinary hearing could detect details between CD and MP3 formats - maybe. But I am not one of those people.
I get the feeling from my own experience that these folks may be manipulating the outcome inside their mind. The human mind is capable of filling in the blesks - jhst as yiu rahd tneje wouhs tkat are sjwlhed incorrectly - by filling in the corrections in your mind. This is no different that what could be happening in your mind with the so-called differences allegedly heard between the different formats. This is certainly as valid a theory as that put forward in the article (that MP3 compression is heard differently than CD quality by the brain - and thus could effect our emotional experience of the music). Both signals are translated to an analog signal that powers the speakers in any case - and going back to my tried and true old recordings - I can't hear a difference. (Read this to learn more about mp3 compression and psychoacoustics)
I will say this - the quality of recordings has gone down - and not because of MP3s. I know this because my old albums and remasters of old albums are better on average than the new stuff that is coming out today - on CD or not doesn't matter. I hear a lot of rookie mistakes - particularly clipping/overdriving of recording levels - that are not present in the older recordings. That is not to say there aren't any good recordings today - they just seem to be few and far between.
please show me the Linux distro that has longer support, desktop or server than Microsoft?
Your argument is a fallacy because it does not take into account the simple fact that Linux can be modified (I have source code going back to 1.4 kernel and everything inbetween), and MS Windows can not.
PS. Check out the Microsoft EULA. You will see similar verbiage. When was the last time someone went after Microsoft for shoddy software, and won? Zero - that is how many.
Business puts all their eggs in the Microsoft basket today - and that is no different than doing so with OSS for all intents and purposes.
The big problem I see with no "owners" of software is that ensuring you had "the real deal" would be difficult, because there's nobody to go after for "shoddy" software.
Actually you have no recourse anyway because the copyright owner (in the case of GPL'd software) has provided no such assurances; from the GPL -
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
The model I've seen spring up as a result is for a third party vendor to provide support. I wouldn't hold my breath in an attempt to get copyright holders (many of which are hobbiests) to cough up a warranty. The main reason, aside from stability, that a business is going to go for OSS is to save money. Cheap does not come without a price, however.
This is why I am a firm believer that you should either hold a computer science degree from an institution that provides a well rounded background so you understand these issues, or you come from another discipline and show that you understand those issues. Hiring should be geared to identify those candidates.
Too many people with little interest or skills in computers and system development ended up overflowing the market place for programmers during the dot-com era. They were only in it for the money - and had no interest in the work - and it showed.
Unfortunately most businesses have a very short term view - and focus on the stock price - at the peril of their good name (if they had one to begin with). For decades it has been common knowledge that programmers are not interchangeable, yet business continues to operate as if we are - in pursuit of a quick profit fix, at the expense of quality and customer satisfaction.
The need to shake out the riff-raff from the job market is long overdue. We end up cleaning up behind them anyway - we might as well get paid for it.
Remember -- the really powerful aspect of this phone is that Apple can push OS/software updates to the phone.
This means that you won't have to throw away your iPhone 1.0 because the interface and underlying applications can be modified as they get more experience/perfect more services. I am sure they will partner with other companies to do this (Cisco VPN anyone?).
I can see a bluetooth portable keyboard for data input (foldable into a small bundle that fits in your bag) for those of us that write alot while out on the town - sipping a latte and writing the next installment of your travelogue or great American novel(tm).
Use a CMS (A cheap linux server made from an old machine, running Zope/Plone would do) to store your files that need to be shared. Failing that - use your trusty USB device to sneaker net your files around the office.
The main reason I print anything at work is to share it in a meeting. At home I don't print anything myself - my wife and kids like to print origami sheets, artwork for the fridge, and the occaisional file copy of some transaction. Again, we probably shouldn't let the printer manufacturers get away with this; vote with your dollars and avoid printers that have such designs.
At that point I think I would dig down and figure out how it measures it. It has to be one of only a few methods for such a problem (weight, volume/level, electrical conductance etc.). Once I figure out what it was I would jerry rig the system to show allways full.
Failing that, given the low cost of these machines I think I would buy one that doesn't prevent you from printing in that situation.
This is not a big problem - for a big company. A Big company could easily license the IP from their competitors to build the 'perfect' phone.
Of course, that elimenates all the little guys from competing because they can't afford to license the technology.
On the other hand, companies prefer to purposefully 'differentiate' their products so the customer is presented with a choice - which the company is banking on. You will probably never see the 'perfect' phone, as a result. It is the nature of the beast.
Any underground bunker has to deal with this - shifting earth over the course of years causes cracks through which water can, and will enter. Most bunkers are equipped with pumps as well as ventilation systems to move water and air in/out.
Obviously this bunker was abandoned after the time capsules were interred there. A real bunker takes constant maintenance to keep it fit for service.
After the Russians detonated that 50MT bomb, everyone said 'why bother', and abandoned the bunker mentality.
I've not run into that problem -- I haven't downloaded anything that large. The source for Cyberduck should be available since it is open source (I think?) - might be worth taking a look to see how they are handling memory allocation/deallocation.
When I got my Macbook I found some of the OSX apps deficient.
I ditched and replaced the following apps:
Safari --> replaced with Mac version of Firefox.
Terminal Emulator --> replaced with iTerm -- tabbed shell terminals and various niceties.
Writer (or whatever it was called) --> replaced with Emacs for development and NeoOffice for writing+ (spreadsheets, basic DB,
Sticky Notes --> replaced with 'Stick-Em-Up!' more full featured sticky notes - allows categorization of notes.
Finder --> replaced with QuickSilver.
I did keep the following apps - which I think work best from my perspective:
iTunes, Garage Band, iDVD, iMovie HD, iPhoto, Address Book, iCal, Dictionary, and the Unix development tools from the add-on CD.
Finally, I added a few other things that I wanted:
Python 2.5.1 (upgraded default python - which was way out of date), iGTD (project management), MiNews (news aggregator), CyberDuck (FTP/SFTP client - equivalent to WSFTP on Windows), TeamSpeex (TeamSpeak compatible client), and Text Wrangler (a text editor that can manipulate and read various text types - e.g. UTF8, and highlight code for a plethora of languages)
Slashdot Mirror
1. Put Your own Communication Satellites into space.
2. Purchase a fleet of container ships and load up with servers and satcom gear.
3. ???
4. Profit!!!
If you are fulfulling the responsibility of an Architect, you better damn well understand the following:
1. Networking - in particular how many simultaneous connections can be handled by a given machine, network device, and throughput of same. This has implications when designing systems - particularly high performance systems (multiple threads, multiple users, and large data transfers). What are the various strengths and limitations of various protocols (http, h323, IP, UDP etc) considered. What are the network security implications of the design?
2. File Systems and Storage - how many inodes does a given filesystem partition contain, will the app outstrip local disk usage so a NAS or Storage Area Network is required?
3. Databases and Directories (LDAP) - how much overhead does oracle require vs PostGre vs MySql etc and what are the tradeoffs with regard to performance and cost, what is appropriate to store in a DB versus a directory, and can you extend the directory as needed or does the vendor(s) own the key attribute tree? etc..
4. Hardware - when will a workstation suffice, when do you need a server, when do you need an array of servers, when do you need a high performance computing cluster or super computer and what is the difference (in cost, energy consumption, and performance)? Will you need to include backup and restoration gear, laboratory and testing gear, and development gear in your plans?
5. Tools - what are the tradeoffs for various proprietary tools, and FOSS tools? What are the best tools for the job? What does your teams know how to use efficiently? Will the cost of retraining be worth the benefits of a different approach?
6. Project Management - you have to keep the PMs straight, particularly if they did not come out of the development side.
7. Finance - you have to be able to justify the costs associated with your decisions and understand how they impact the overall business case (can we afford to do X)?
This list just scratches the surface - these are areas that I have seen architects and system developers fall down on the job - too many times. Attempting to grok systems architecture is a life long learning experience.
There are some things that work well as a server side application, and there are other things that work better on the client side.
If you need multiple people to access the same data, or you need to be able to access the data remotely - then software as a service is a good choice (and you can own the servers yourself - serving yourself, as it were - if you are concerned about your data being in other's hands. Of course you'll need to manage the system yourself then).
If you need stability and performance - then client side applications fit the bill (you will need to manage upgrades, backups and data syncronization as required).
If you need absolute security - then don't put it on the network at all.
Risk is involved in all of those decisions - balancing it out to get the right mix is your best bet.
Sounds like the perfect vacation destination to me.
(Anyone who's spent two weeks in a car with their family - really needing a vacation from their 'vacation' will understand where I am coming from.)
That's just what they want you to think...
Gives 'Blue Screen of Death' a new meaning...
Correction - the foxes have always been in charge of the henhouses. The henhouses are just a lot bigger, and the foxes are a lot smarter.
Have you contacted the company about this billing problem to resolve it? You shouldn't just let it go.
I'm a musician, have played in bands, have done recording of various types (multitrack, reel2reel mastering, digital) and have known a number of audiophiles (and enjoyed their systems) over the years.
This argument is similar to the debate years ago surrounding speaker cables. I wanted to get to the bottom of it, so I set up a test. I could not detect a difference between using expensive 'monster' cable and cheap lamp cable for the same set of speakers (although it is true that the potential for induction/crosstalk increases in the non-shielded cable - a smart deployment of the wire, seperated from power and crossing at right angles when needed, decreases the likelyhood of interference - and doesn't cost an arm and a leg).
Similarly, with a high quality headset (high and low frequencies beyond 'standard' headsets) - I can't tell the difference between a CD and a MP3 of the same song played through my system. Taking a step farther still, the sound is certainly better for that particular music than was possible via Cassette Tape or over the FM radio back in the day.
Short of hearing a live performance of the song - MP3 is as good as it gets - and certainly audio equivalent to CD when uncompressed. The argument from the article is a fallacy as far as I am concerned. Now it may be possible that someone with extraordinary hearing could detect details between CD and MP3 formats - maybe. But I am not one of those people.
I get the feeling from my own experience that these folks may be manipulating the outcome inside their mind. The human mind is capable of filling in the blesks - jhst as yiu rahd tneje wouhs tkat are sjwlhed incorrectly - by filling in the corrections in your mind. This is no different that what could be happening in your mind with the so-called differences allegedly heard between the different formats. This is certainly as valid a theory as that put forward in the article (that MP3 compression is heard differently than CD quality by the brain - and thus could effect our emotional experience of the music). Both signals are translated to an analog signal that powers the speakers in any case - and going back to my tried and true old recordings - I can't hear a difference. (Read this to learn more about mp3 compression and psychoacoustics)
I will say this - the quality of recordings has gone down - and not because of MP3s. I know this because my old albums and remasters of old albums are better on average than the new stuff that is coming out today - on CD or not doesn't matter. I hear a lot of rookie mistakes - particularly clipping/overdriving of recording levels - that are not present in the older recordings. That is not to say there aren't any good recordings today - they just seem to be few and far between.
This is much to do about nothing IMHO.
Your argument is a fallacy because it does not take into account the simple fact that Linux can be modified (I have source code going back to 1.4 kernel and everything inbetween), and MS Windows can not.
You can even pay someone to maintain your linux systems...
PS. Check out the Microsoft EULA. You will see similar verbiage. When was the last time someone went after Microsoft for shoddy software, and won? Zero - that is how many.
Business puts all their eggs in the Microsoft basket today - and that is no different than doing so with OSS for all intents and purposes.
Actually you have no recourse anyway because the copyright owner (in the case of GPL'd software) has provided no such assurances; from the GPL -
The model I've seen spring up as a result is for a third party vendor to provide support. I wouldn't hold my breath in an attempt to get copyright holders (many of which are hobbiests) to cough up a warranty. The main reason, aside from stability, that a business is going to go for OSS is to save money. Cheap does not come without a price, however.
That religion is the worship of 3D visual goodness, and programming in general.
Ohm addme padme hum - keep the foo counters turning.
I encounter this every day in my job.
This is why I am a firm believer that you should either hold a computer science degree from an institution that provides a well rounded background so you understand these issues, or you come from another discipline and show that you understand those issues. Hiring should be geared to identify those candidates.
Too many people with little interest or skills in computers and system development ended up overflowing the market place for programmers during the dot-com era. They were only in it for the money - and had no interest in the work - and it showed.
Unfortunately most businesses have a very short term view - and focus on the stock price - at the peril of their good name (if they had one to begin with). For decades it has been common knowledge that programmers are not interchangeable, yet business continues to operate as if we are - in pursuit of a quick profit fix, at the expense of quality and customer satisfaction.
The need to shake out the riff-raff from the job market is long overdue. We end up cleaning up behind them anyway - we might as well get paid for it.
Sometimes the reach exceeds the grasp.
Reed mor bukks!
I got you all beat - my watch is more powerful than the first computer I owned - back in the early '80s...a TI58 programable calculator.
Remember -- the really powerful aspect of this phone is that Apple can push OS/software updates to the phone.
This means that you won't have to throw away your iPhone 1.0 because the interface and underlying applications can be modified as they get more experience/perfect more services. I am sure they will partner with other companies to do this (Cisco VPN anyone?).
I can see a bluetooth portable keyboard for data input (foldable into a small bundle that fits in your bag) for those of us that write alot while out on the town - sipping a latte and writing the next installment of your travelogue or great American novel(tm).
In that case, time for the paperless office!
Use a CMS (A cheap linux server made from an old machine, running Zope/Plone would do) to store your files that need to be shared. Failing that - use your trusty USB device to sneaker net your files around the office.
The main reason I print anything at work is to share it in a meeting. At home I don't print anything myself - my wife and kids like to print origami sheets, artwork for the fridge, and the occaisional file copy of some transaction. Again, we probably shouldn't let the printer manufacturers get away with this; vote with your dollars and avoid printers that have such designs.
At that point I think I would dig down and figure out how it measures it. It has to be one of only a few methods for such a problem (weight, volume/level, electrical conductance etc.). Once I figure out what it was I would jerry rig the system to show allways full.
Failing that, given the low cost of these machines I think I would buy one that doesn't prevent you from printing in that situation.
I don't change the ink until I don't see ink coming out on the page. How hard can that be?
This is not a big problem - for a big company. A Big company could easily license the IP from their competitors to build the 'perfect' phone.
Of course, that elimenates all the little guys from competing because they can't afford to license the technology.
On the other hand, companies prefer to purposefully 'differentiate' their products so the customer is presented with a choice - which the company is banking on. You will probably never see the 'perfect' phone, as a result. It is the nature of the beast.
So - it doesn't work fine the rest of the time? Doesn't sound like a gleaming endorsement of this technique.
Any underground bunker has to deal with this - shifting earth over the course of years causes cracks through which water can, and will enter. Most bunkers are equipped with pumps as well as ventilation systems to move water and air in/out.
Obviously this bunker was abandoned after the time capsules were interred there. A real bunker takes constant maintenance to keep it fit for service.
After the Russians detonated that 50MT bomb, everyone said 'why bother', and abandoned the bunker mentality.
I've not run into that problem -- I haven't downloaded anything that large. The source for Cyberduck should be available since it is open source (I think?) - might be worth taking a look to see how they are handling memory allocation/deallocation.
When I got my Macbook I found some of the OSX apps deficient.
I ditched and replaced the following apps:
Safari --> replaced with Mac version of Firefox.
Terminal Emulator --> replaced with iTerm -- tabbed shell terminals and various niceties.
Writer (or whatever it was called) --> replaced with Emacs for development and NeoOffice for writing+ (spreadsheets, basic DB,
Sticky Notes --> replaced with 'Stick-Em-Up!' more full featured sticky notes - allows categorization of notes.
Finder --> replaced with QuickSilver.
I did keep the following apps - which I think work best from my perspective:
iTunes, Garage Band, iDVD, iMovie HD, iPhoto, Address Book, iCal, Dictionary, and the Unix development tools from the add-on CD.
Finally, I added a few other things that I wanted:
Python 2.5.1 (upgraded default python - which was way out of date), iGTD (project management), MiNews (news aggregator), CyberDuck (FTP/SFTP client - equivalent to WSFTP on Windows), TeamSpeex (TeamSpeak compatible client), and Text Wrangler (a text editor that can manipulate and read various text types - e.g. UTF8, and highlight code for a plethora of languages)