I agree to a point when you've reached a senior level. Jr to Mid level programmers should be slowly building up their skills in this area before being given full admin access - many companies I've worked for limit the admin privileges to installing software for Jrs, Software and Settings for Mids (minus disabling critical software like Virus protection), and Srs have full access to their local box.
As a side note - no support person can handle all the situations needed in the programming environment. That being said, you should still consult your support personnel before making any modification your not completely sure of - it's only common courtesy if they're the ones having to reinstall everything because you f'ed your machine up. If you do all your own installing then you're probably competent enough to handle it.
I haven't personally used Confluence, but we use JIRA to store documents related to the tasks and it works pretty well. You can't search the attached documents, but typically if there is a doc associated with a task that isn't too much of a problem. And if you are only going to have a few people submitting bugs/tasks you can't beat the functionality for the price....
Just a side note: the LHC uses to separate beams that collide at 4 points along a single tunnel. Which is required since they're using proton-proton or larger nuclei (particularly lead) in the experiments. The Tevatron uses proton-antiproton allowing them to use the same beam equipment. Unfortunately, the cost of creating antilead nuclei is too high right now, so they opted for 2 beams instead.
Ok here goes:
Should science undergraduates be taught Fortran? Yes
Should it be the FIRST language, NO, not any more
So much of science, especially physics, is done on computers now - as both a software engineer and someone transitioning into Physics I ran into many people that had severe problems learning FORTRAN and applying it to problems. I really feel science students should have a couple of general courses in programming in C before moving on to other languages or even programming classes specific to their science. Here's the reasoning: A) Science students need to learn programming basics away from the pressure of also learning within their science field at the same time - if your learning the science at the same time, the actual basic programming concepts get lost and muddied with the science being learned.
B) It can allow a science major to learn the concepts of programming in a general purpose language without muddying it with a lot of OS specific, library specific, attitude specific usage (aside from the compiler use)
C) There is a C compiler on almost every system you will most likely use in your lifetime as a scientist
D) C has enough structure to be "readable", but doesn't have so many constraints that it has problems being fast
E) C syntax is the basis for many other programming languages including Python and Java (both of which are heavily used in science as well)
and finally if a science major has a good understanding of programming concepts they can know what to look for when they're learning a new language (whatever it might be) - they will know that they have to learn the syntax for control structures in the new language (for, while, if, etc) as well know they'll have to find out more esoteric language specific concepts like how do I create functions and libraries? How do I use them?
ALL THAT being said, yes FORTRAN is a critical language to know with the sciences, because of the availability of libraries. HOWEVER, many of those libraries are now available in other languages and/or can be called from a different language via an abstraction (a concept that would be taught in a more general computing course)
Aside from minor glitches in installation on my older boxes (and I later found that the problems were caused by failing hardware), I have had very few problems with getting just about anything to work on my Linux boxes. The only other time you should have any problems (if you know what you're doing) is when the hardware you're using is REALLY new.
I have to agree with you on one point: Trying to sell linux as the next hot think on the stock market was a joke. And yes anyone who even remotely understood the limitations of the open source model would know you shouldn't bank on distros to make the big bucks. Where there is a little bit of money is in the value added market: services and products that run on linux that help produce revenue. The model is not good for big corporations who need earnings "NOW!" it is for the medium and small businesses and individuals who are just looking at providing a good product at a reasonable price (slow growth/low profits)
I definitely agree. In addition I think this article on CNN is going to be an interesting trend (Even though I'm a big proponent of open source, corporations want support and an established standard. Products like this give a good start for the migration....) hopefully we'll start to see ports of our favorite games soon 8)
Here's the link:
http://www.cnn.com/2002/TECH/ptech/04/02/office.li nux.idg/index.html
They're just offering value added software (productivity tools) that other companies charge for already. Truly there is no free lunch, if you want something that's good to endure you need to support it. MandrakeSoft is just doing it through a different model (an interesting one at that). In their latest Newletter they mentioned "We believe it is more beneficial to offer new features to Club members than it is to remove services from others." They don't plan on charging for things they were already offering for free, they're just offering perks to those who would like to support them monetarily.
Slashdot Mirror
I agree to a point when you've reached a senior level. Jr to Mid level programmers should be slowly building up their skills in this area before being given full admin access - many companies I've worked for limit the admin privileges to installing software for Jrs, Software and Settings for Mids (minus disabling critical software like Virus protection), and Srs have full access to their local box.
As a side note - no support person can handle all the situations needed in the programming environment. That being said, you should still consult your support personnel before making any modification your not completely sure of - it's only common courtesy if they're the ones having to reinstall everything because you f'ed your machine up. If you do all your own installing then you're probably competent enough to handle it.
The whole point is to make sure the implementation can't be broken BEFORE they distribute it and have to recall/replace/handle frivolous lawsuits/etc.
I haven't personally used Confluence, but we use JIRA to store documents related to the tasks and it works pretty well. You can't search the attached documents, but typically if there is a doc associated with a task that isn't too much of a problem. And if you are only going to have a few people submitting bugs/tasks you can't beat the functionality for the price....
Recent article on BBC seems to confirm rocket hypothesis. Why do people go to the UFO hypothesis so fast?
The surest sign that there is intelligent life in the universe is that they haven't come here.
Just a side note: the LHC uses to separate beams that collide at 4 points along a single tunnel. Which is required since they're using proton-proton or larger nuclei (particularly lead) in the experiments. The Tevatron uses proton-antiproton allowing them to use the same beam equipment. Unfortunately, the cost of creating antilead nuclei is too high right now, so they opted for 2 beams instead.
Ok here goes:
Should science undergraduates be taught Fortran? Yes
Should it be the FIRST language, NO, not any more
So much of science, especially physics, is done on computers now - as both a software engineer and someone transitioning into Physics I ran into many people that had severe problems learning FORTRAN and applying it to problems. I really feel science students should have a couple of general courses in programming in C before moving on to other languages or even programming classes specific to their science. Here's the reasoning:
A) Science students need to learn programming basics away from the pressure of also learning within their science field at the same time - if your learning the science at the same time, the actual basic programming concepts get lost and muddied with the science being learned.
B) It can allow a science major to learn the concepts of programming in a general purpose language without muddying it with a lot of OS specific, library specific, attitude specific usage (aside from the compiler use)
C) There is a C compiler on almost every system you will most likely use in your lifetime as a scientist
D) C has enough structure to be "readable", but doesn't have so many constraints that it has problems being fast
E) C syntax is the basis for many other programming languages including Python and Java (both of which are heavily used in science as well)
and finally if a science major has a good understanding of programming concepts they can know what to look for when they're learning a new language (whatever it might be) - they will know that they have to learn the syntax for control structures in the new language (for, while, if, etc) as well know they'll have to find out more esoteric language specific concepts like how do I create functions and libraries? How do I use them?
ALL THAT being said, yes FORTRAN is a critical language to know with the sciences, because of the availability of libraries. HOWEVER, many of those libraries are now available in other languages and/or can be called from a different language via an abstraction (a concept that would be taught in a more general computing course)
Aside from minor glitches in installation on my older boxes (and I later found that the problems were caused by failing hardware), I have had very few problems with getting just about anything to work on my Linux boxes. The only other time you should have any problems (if you know what you're doing) is when the hardware you're using is REALLY new.
I have to agree with you on one point: Trying to sell linux as the next hot think on the stock market was a joke. And yes anyone who even remotely understood the limitations of the open source model would know you shouldn't bank on distros to make the big bucks. Where there is a little bit of money is in the value added market: services and products that run on linux that help produce revenue. The model is not good for big corporations who need earnings "NOW!" it is for the medium and small businesses and individuals who are just looking at providing a good product at a reasonable price (slow growth/low profits)
I definitely agree. In addition I think this article on CNN is going to be an interesting trend (Even though I'm a big proponent of open source, corporations want support and an established standard. Products like this give a good start for the migration....) hopefully we'll start to see ports of our favorite games soon 8) Here's the link: http://www.cnn.com/2002/TECH/ptech/04/02/office.li nux.idg/index.html
They're just offering value added software (productivity tools) that other companies charge for already. Truly there is no free lunch, if you want something that's good to endure you need to support it. MandrakeSoft is just doing it through a different model (an interesting one at that). In their latest Newletter they mentioned "We believe it is more beneficial to offer new features to Club members than it is to remove services from others." They don't plan on charging for things they were already offering for free, they're just offering perks to those who would like to support them monetarily.