So if I do not share any songs and I continuously download all of the songs on thier 'hitlist', they could not come after me? But if I share songs that I have paid for, they will (or it is a possibility) come after me?
That seems very strange, but then again....nevermind. I guess that is the point.
Punch seems to be one of the better ones out there, but that doesn't mean too much. It does have the 90 day refund policy and 30 days (I think) of free telephone support, but I didn't seriously start using it for a month or two after I bought it. I would have used the free telephone support had I started using it earlier, b/c I have had some very strange problems...mostly due to the ceiling height being 9 feet. Also, the roof has been giving me trouble, especially for the wrap-around porch and a first floor room that needs its own roof. I do have to say that I am not a pro at using the software, so I 'could' be doing something wrong!
In my case, I have given up on the outside of the house. As for inside, it has been very usefull to be able to 'walk-through' the design. I like the fact that I can put plants in the yard and when I do the walk-through, I can see what it will look like through the windows! The software definitely needs some work, but it is worth the money just to be able to get a preview of what the inside will look like!
That recipe is all wrong!! You don't use 1/2 pint!! Order a full pint, drink about the first 1/4, and then continue with the other ingredients. Thats how a car bomb should be done.
If you are out on the town and feeling a bit sluggish, do one (or two or three...) of these and you will be on track to be the life of the party!
(Tastes like chocolate milk!!)
First of all, the term 'Software Engineer' IS abused, and that is in part due to the fact that there is no perfect or universally accepted method out there to engineer software.
As for Computer Science versus Computer Engineer curriculum... the two programs should overlap a little. At my school, people in Comp Sci had to take a few circuits and low level language classes, and the Comp E people had to take a few basic java, algorithm, and possibly, a design class.
Using my school as a basis again, if I were to choose someone to design a piece of hardware and write an interface for it, I would choose someone from Comp Engineering. If I were to choose someone to design and implement some kind of application, then I would choose someone from Comp Sci. One is not better than the other because they are two different things. When I was switching majors, I decided to go with Comp Sci because I wanted to design software. I was a Junior in Math Sci when I switched, so I have the math part covered.
Now, I wouldn't officially call a Computer Science graduate a Software Engineer, but I would definitely not consider a Computer Engineer a Software Engineer. Both have the same ability to take on the role of a 'programmer', but at the higher level is where the two seperate.
I consider a 'programmer' to be someone who went to a tech school.
At the school I went to, it basically boils down to: Computer Science: Software (memory management, theory, design)
Computer Engineering: Hardware (circuits, lower level languages, hardware design)
on what level you are coding on. If a person is involved in designing the software (data flow, class responsibilities, cohesion, coupling etc etc) then I would consider him/her to be an engineer.
If the person is given a detailed framework of the class design and how everything should fit together, then I would consider him/her a programmer.
To me, the title 'engineer' is a very loose term and is associated with a person who is involved in the design process of a project.
Slashdot Mirror
From my experience, someone who boasts to be a 'star' programmer usually is not one. I'm just saying...
That seems very strange, but then again....nevermind. I guess that is the point.
In my case, I have given up on the outside of the house. As for inside, it has been very usefull to be able to 'walk-through' the design. I like the fact that I can put plants in the yard and when I do the walk-through, I can see what it will look like through the windows! The software definitely needs some work, but it is worth the money just to be able to get a preview of what the inside will look like!
That recipe is all wrong!! You don't use 1/2 pint!! Order a full pint, drink about the first 1/4, and then continue with the other ingredients. Thats how a car bomb should be done.
If you are out on the town and feeling a bit sluggish, do one (or two or three...) of these and you will be on track to be the life of the party! (Tastes like chocolate milk!!)
As for Computer Science versus Computer Engineer curriculum... the two programs should overlap a little. At my school, people in Comp Sci had to take a few circuits and low level language classes, and the Comp E people had to take a few basic java, algorithm, and possibly, a design class.
Using my school as a basis again, if I were to choose someone to design a piece of hardware and write an interface for it, I would choose someone from Comp Engineering. If I were to choose someone to design and implement some kind of application, then I would choose someone from Comp Sci. One is not better than the other because they are two different things. When I was switching majors, I decided to go with Comp Sci because I wanted to design software. I was a Junior in Math Sci when I switched, so I have the math part covered.
Now, I wouldn't officially call a Computer Science graduate a Software Engineer, but I would definitely not consider a Computer Engineer a Software Engineer. Both have the same ability to take on the role of a 'programmer', but at the higher level is where the two seperate.
I consider a 'programmer' to be someone who went to a tech school.
At the school I went to, it basically boils down to: Computer Science: Software (memory management, theory, design) Computer Engineering: Hardware (circuits, lower level languages, hardware design)
on what level you are coding on. If a person is involved in designing the software (data flow, class responsibilities, cohesion, coupling etc etc) then I would consider him/her to be an engineer. If the person is given a detailed framework of the class design and how everything should fit together, then I would consider him/her a programmer. To me, the title 'engineer' is a very loose term and is associated with a person who is involved in the design process of a project.