It actually throws off peoples scholorships mightily. I know of two people who had to transfer back to their native state schools after getting caught up in the "cheating scandal" of this fall.
I work for a military contractor. Every project that we've worked on, we've ALWAYS given the military the source we use. What is th econflict with OSS?
They can write something that will be able work without IE. It may take them time and money, but this monopolist has plenty of money...and as much time as anyone else. Make them ship a stripped down version by date X, or open their OS code under the LGPL or BSD license. Or break the company in two at that point. Either one serves the consumer nicely.
Re:Why are people still using a 30 year old langua
on
C
·
· Score: 1
It seems that Dennis Ritchie was so besotted with A and B...
Actually, the precursor to B was BCPL, not A. B is C's precursor.
I don't think that this would be that bad for the company. It would cost them tons, but they would then have a well-documented product that was cleaner on the interface side. Better for them too!
I wouldn't listen to this and get disheartended. I go to the other Tech...(Georgia Tech)...and I see jobs in all the major cities for many different skills, even C++...:).
Skills of all sort are still needed, but companies can't afford the worthless jackoffs they hired so many of in the dot-com boom.
I would try for unpaid internships before I would go for open source. I would have to say that 80% of being sucessful at work is more about motivation and drive than actual practice in the discipline. Try talking a company into letting you work 20 hours a week for a couple months, being basically the monkey boy on project. You will work with a team, people outside of an academic mindset, and even a real code base. But you have to act like a real employee, actively seeking out tasks and being the epitome of professionalism.
Then after that internship is done, you will have work experience that shows you and the rest of the world how much you want to work in this field. If you value open source, try for an open source company, but I wouldn't limit myself to that.
Anyway, don't you need a license from Sony to develop software for the dreamcast? If you don't have one, how is wrong to restrict access to a tool that's only purpose is do development, even if its academic.
bzzt...WRONG!. You can't be prohibited from downloading software you wrote to a piece of hardware that you own, as long as you don't circumvent any encryption to do so. That is the use the guy has for the dreamcast.
Check out savannah...here. Download the software its run on. Put that on your computer. Then you have the project on your own server. That's the idea of free software.
This will be fairly useful in warehouse situations. Maybe on an assembly line: you can work on your task, and if computer assistance is needed, just flip the screen down and look up a part number or whatever. These still aren't the best for long-term computing sessions.
One of the professors here at Georgia Tech, Thad Starner, has been making (and selling, to a limited degree) something like this for years. Glad to see it hit the consumer market.
You do share with patents. In 17 years. If we shorten the time to say, 5 years, or even 7, then R&D can rcoup their discovery, and the world can actually use the knowledge the patent gives us.
(And have you ever noticed that when one channel goes to ads, all the other major networks seem to do so as well? I suspect they designed it that way so even though you may switch away, someone else on another channel will switch and see the ad that you missed.)
Things meant to be aired on TV have alloted breaks in them at certain times. This allows pretty simple commercial playback automation. You will notice this if you ever rent a made for TV movie from the video store. Here is a paper on this timing: http://www.bm.ust.hk/~econ/paper/zhoubreak.pdf
True, there are more children waiting to be adopted than people wanting to adopt. There are not a surplus of babies however. The surplus is in kids who are already past the infant stage therefore are less desireable to parents wanting to adopt.
Think polymorphic interfaces
on
Modular Robots
·
· Score: 1
I can see a wonderfully simple interfacing among the robotic parts. I would really like to see these controlled with embedded java to allow you to say go(NW,1000 * FT); to treads, feet or wheels, and the robot goes 1000 ft northwest. The possibilites are endless for a large amount of sophistication internal to the modules, while keeping a simple interface.
Could someone provide a nice bit of Karma Whoreing and point to a resource about how this works?
From the people who seem to know how this works, it seems like.Net and #Unsafe are compile time "sandboxes" if you will. If your intermeadiate code violates the principles of the sandbox, its marked unsafe. All unmanaged pointers would have to go in unsafe then I am guessing.
Implementation gotachas are the big deal here. If the.Net security manager, say, checks the header of a downloaded program this could be a security hole (headers can be modified). If it rescans the code/binary to make sure it matches security paramaters there is no problem with this.
Old idea, new opportunity. Use the links to teach kids about the things that they can do to improve their community. Use the international interconnectivity to have the children learn about the different changes that are needed all around the world.
A NYC kid will be totally surprised when a kid from India is trying to better toilet facilities in his neighborhood. A kid in Djibouti will be surprised that the kid in London doesn't know everyone on his block.
The international network, and the knowledge that someone is watching their projects will both make it easier for the kids to persist and to get aid in their endeavors.
This is an excellent idea. When I am actually DOING something that I need to learn how to do, this is how I learn to do it. I would love to see a book do this. It would be just like weeks of experience, but read out of a book.
Think Like a Programmer: Wrapping your mind around code and other computer conundrums
This book teaches a non-programmer with no experience what sorts of questions to think in terms of when trying to write software. It shows how to think of things in a modular, abstracted way. It also shows how to make simple data structures. I am imagine it as a companion to a nutshell book for a intro CS course or a person trying to learn on their own.
Concise Sexy C
A book that impresses tons of C idioms that make code smaller, simpler to read, self-documenting, and usually faster. From ugly to elegant. Gives good questions to ask yourself to pare down code to a more simple, elegant form.
Developing Beauty-Sense
How to gain the experiences necessary in a craft to tell what's "beautiful" in that sphere of creation. How to watch a pratictioner of the field to tell what is beautiful in your design and what is an ugly hack. That is the stage where you know that you really have a skill down to the point where you are respectable, or at least on the road to being so. This book could be on a paticular skill, or general. Either way I would kill for it.
Coding Standards: The Good, The Bad, The Ugly
Have you ever spent days going through "updating code documention" after a project because there was too much to change while you went along? Have you ever just plain ignored the standard becuase it didn't tell anyone anything important? Have you ever seen standards where there were often 3 times as many MANDATED boilerplate lines of comments above functions as there were lines of code in the function? Have you ever seen standards for Java and C++ written by C programmers with no understanding of OO principles? This book is for you. It goes over what adds to programmer productivity and what takes away. It shows how to write tools to make documentation of functions and classes painless. It shows how to use existing tools like "indent" to also help documentation efforts. There are special sections near the end that have full bodied examples of good, bad and ugly coding standards from the real world. In these sections there is commentary about why these standards are bad or good, and what goals they are trying to accomplish. Bomus material on explaining the implications of a coding standard to your boss.
Re:Has he talked about Rod Brooks?
on
Arguing A.I.
·
· Score: 1
Well you might think that anything that discards robotics doesn't have a viable prospect for "real intellegence." I think that you are wrong there. I think things like learning chat-bots that read IRC channels have a chance at learning quite a bit about the world. But they would be like a aboriginal savage brought into the world if they tried to function in another domain. But then again, so would you if all you did was learn from IRC channels and then tried to walk down mainstreet USA.
Slashdot Mirror
It actually throws off peoples scholorships mightily. I know of two people who had to transfer back to their native state schools after getting caught up in the "cheating scandal" of this fall.
I work for a military contractor. Every project that we've worked on, we've ALWAYS given the military the source we use. What is th econflict with OSS?
They can write something that will be able work without IE. It may take them time and money, but this monopolist has plenty of money...and as much time as anyone else. Make them ship a stripped down version by date X, or open their OS code under the LGPL or BSD license. Or break the company in two at that point. Either one serves the consumer nicely.
It seems that Dennis Ritchie was so besotted with A and B...
Actually, the precursor to B was BCPL, not A. B is C's precursor.
I don't think that this would be that bad for the company. It would cost them tons, but they would then have a well-documented product that was cleaner on the interface side. Better for them too!
I wouldn't listen to this and get disheartended. I go to the other Tech...(Georgia Tech)...and I see jobs in all the major cities for many different skills, even C++...:).
Skills of all sort are still needed, but companies can't afford the worthless jackoffs they hired so many of in the dot-com boom.
I would try for unpaid internships before I would go for open source. I would have to say that 80% of being sucessful at work is more about motivation and drive than actual practice in the discipline. Try talking a company into letting you work 20 hours a week for a couple months, being basically the monkey boy on project. You will work with a team, people outside of an academic mindset, and even a real code base. But you have to act like a real employee, actively seeking out tasks and being the epitome of professionalism.
Then after that internship is done, you will have work experience that shows you and the rest of the world how much you want to work in this field. If you value open source, try for an open source company, but I wouldn't limit myself to that.
Yes, you can emulate games. Its prefectly legal to emulate games that you own.
But it can make back the stockholder's money. And that's probbably why the guy is doing it.
Anyway, don't you need a license from Sony to develop software for the dreamcast? If you don't have one, how is wrong to restrict access to a tool that's only purpose is do development, even if its academic.
bzzt...WRONG!. You can't be prohibited from downloading software you wrote to a piece of hardware that you own, as long as you don't circumvent any encryption to do so. That is the use the guy has for the dreamcast.
Check out savannah...here. Download the software its run on. Put that on your computer. Then you have the project on your own server. That's the idea of free software.
....certain that they are going to point out "why" they can't remove IE stuff from windows.
The much harder side is for the examiner for the states to show why they can.
This will be fairly useful in warehouse situations. Maybe on an assembly line: you can work on your task, and if computer assistance is needed, just flip the screen down and look up a part number or whatever. These still aren't the best for long-term computing sessions.
One of the professors here at Georgia Tech, Thad Starner, has been making (and selling, to a limited degree) something like this for years. Glad to see it hit the consumer market.
This rule applies to Trademark law. Not Patent Law. Different areas with different rules.
You do share with patents. In 17 years. If we shorten the time to say, 5 years, or even 7, then R&D can rcoup their discovery, and the world can actually use the knowledge the patent gives us.
He didnt' say abolish all patents and copyrights. Only software and business ones.
(And have you ever noticed that when one channel goes to ads, all the other major networks seem to do so as well? I suspect they designed it that way so even though you may switch away, someone else on another channel will switch and see the ad that you missed.)
Things meant to be aired on TV have alloted breaks in them at certain times. This allows pretty simple commercial playback automation. You will notice this if you ever rent a made for TV movie from the video store. Here is a paper on this timing: http://www.bm.ust.hk/~econ/paper/zhoubreak.pdf
True, there are more children waiting to be adopted than people wanting to adopt. There are not a surplus of babies however. The surplus is in kids who are already past the infant stage therefore are less desireable to parents wanting to adopt.
I can see a wonderfully simple interfacing among the robotic parts. I would really like to see these controlled with embedded java to allow you to say go(NW,1000 * FT); to treads, feet or wheels, and the robot goes 1000 ft northwest. The possibilites are endless for a large amount of sophistication internal to the modules, while keeping a simple interface.
Is a book that I am sure you can find on amazon. It talks about exactly what you want in ANY boss. Works especially well for coders.
Please make sure you look at things from your coders perspective, and keeped them sheltered from but aware of customers and upper management concerns.
Root the horrible developers out (possibly by requiring people to get advance degrees if they don't have them). They really do make work a drag.
....(at least being "safe" might be good for programs knocked up at home)....
Is this really an issue? Since sperm is bigger than virii, any condom that is non-pourous enough to stop sperm should be safe.
Could someone provide a nice bit of Karma Whoreing and point to a resource about how this works?
.Net and #Unsafe are compile time "sandboxes" if you will. If your intermeadiate code violates the principles of the sandbox, its marked unsafe. All unmanaged pointers would have to go in unsafe then I am guessing.
.Net security manager, say, checks the header of a downloaded program this could be a security hole (headers can be modified). If it rescans the code/binary to make sure it matches security paramaters there is no problem with this.
From the people who seem to know how this works, it seems like
Implementation gotachas are the big deal here. If the
Old idea, new opportunity. Use the links to teach kids about the things that they can do to improve their community. Use the international interconnectivity to have the children learn about the different changes that are needed all around the world.
A NYC kid will be totally surprised when a kid from India is trying to better toilet facilities in his neighborhood. A kid in Djibouti will be surprised that the kid in London doesn't know everyone on his block.
The international network, and the knowledge that someone is watching their projects will both make it easier for the kids to persist and to get aid in their endeavors.
This is an excellent idea. When I am actually DOING something that I need to learn how to do, this is how I learn to do it. I would love to see a book do this. It would be just like weeks of experience, but read out of a book.
Think Like a Programmer: Wrapping your mind around code and other computer conundrums
This book teaches a non-programmer with no experience what sorts of questions to think in terms of when trying to write software. It shows how to think of things in a modular, abstracted way. It also shows how to make simple data structures. I am imagine it as a companion to a nutshell book for a intro CS course or a person trying to learn on their own.
Concise Sexy C
A book that impresses tons of C idioms that make code smaller, simpler to read, self-documenting, and usually faster. From ugly to elegant. Gives good questions to ask yourself to pare down code to a more simple, elegant form.
Developing Beauty-Sense
How to gain the experiences necessary in a craft to tell what's "beautiful" in that sphere of creation. How to watch a pratictioner of the field to tell what is beautiful in your design and what is an ugly hack. That is the stage where you know that you really have a skill down to the point where you are respectable, or at least on the road to being so. This book could be on a paticular skill, or general. Either way I would kill for it.
Coding Standards: The Good, The Bad, The Ugly
Have you ever spent days going through "updating code documention" after a project because there was too much to change while you went along? Have you ever just plain ignored the standard becuase it didn't tell anyone anything important? Have you ever seen standards where there were often 3 times as many MANDATED boilerplate lines of comments above functions as there were lines of code in the function? Have you ever seen standards for Java and C++ written by C programmers with no understanding of OO principles? This book is for you. It goes over what adds to programmer productivity and what takes away. It shows how to write tools to make documentation of functions and classes painless. It shows how to use existing tools like "indent" to also help documentation efforts. There are special sections near the end that have full bodied examples of good, bad and ugly coding standards from the real world. In these sections there is commentary about why these standards are bad or good, and what goals they are trying to accomplish. Bomus material on explaining the implications of a coding standard to your boss.
Well you might think that anything that discards robotics doesn't have a viable prospect for "real intellegence." I think that you are wrong there. I think things like learning chat-bots that read IRC channels have a chance at learning quite a bit about the world. But they would be like a aboriginal savage brought into the world if they tried to function in another domain. But then again, so would you if all you did was learn from IRC channels and then tried to walk down mainstreet USA.