Upgrades are not a big concern for many customers (especially larger customers). Usually by the time customers are ready to upgrade, it is simply cheaper to purchase entirely new hardware.
I read that in a report several years ago and didn't beleive it myself. Then I started a small IT business (with a partner) and have completed several server redeployments. After the third time doing this, I remembered the old article. I tried to find it, but couldn't find the exact one again. At any rate, since then, we've been taking this into account when purchasing new hardware. Then I read this today, and it reminded me again about this.
The price/performance ratio of new machines increases so much, that it just doesn't make sense to upgrade older hardware in terms of the performance or cost.
The site is using akamai to distribute it's content, so they shouldn't really be worried about "Managing traffic could also be a good way to ensure that the site stays working in the closing days of the election campaign".
Thats fine, until Firefox (or whatever) is the most popular browser, and the virus/adware/whatever - writers start targeting it.
Just because IE appears to be the most buggy (and it might very well be) does not mean it is. The fact that it happens to be the most "popular" (it's the default browser on 90% of desktops) means it is going to be the most attacked.
I am the senior software engineer for a small Canadian development company. I manage the design and development of a set of Web Applications.
We've been running Linux-based web servers, and developing on Linux for the past several years. Last year we completed a sort of research project; reimplementing our flagship web application using ASP.NET. We managed to completely replicate functionality which had taken us approximately 850 hours to implement using OSS technology in less than 150 hours of work. Granted, we had an established design to work with, so the comparison is not totally un-biased.
Since then, we have completely switched over to ASP.NET technology. The productivity gains alone have completely negated any initial purchase or migration costs. In this respect, we continue to see gains on a daily basis.
On the support front, comparing MS to Open Source is fruitless. Signing up as a MS Partner (~ $300 USD) provides developers with copies and licenses to use (almost) every current MS software product. It also gives developers access to MS development support. You just can't compare that with the OSS alternative.
Reducing binary and runtime memory consumption is a great idea, but it's usually going to involve some design tradeoffs. This may mean the product will run slower, or have a slower, less responsive UI.
Pax Warrior is not really a game as such, but an "interactive multimedia documentary". It is marketted as, and plays like an interactive Social Studies game. Users (students) are presented with a first-person interaction taking them through the experiences and decisions faced by a UN Commander on a peace keeping mission to Rwanda.
Pax Warrior is very interesting in that, like many games, it presents users with choices that must be made, and consequences that arise from those decisions. In this case, the choices and consequences are very closely modelled on what actually happended in Rwanda.
And yes, for those who are wondering, it has a fixed ending. It's a pretty emotionally connected, moving one at that.
Wrong. The x86 series of processors has long been used in consumer products. Why? To paraphrase Intel Inside (A documentary written on the early days of Intel), the world is overflowing with engineers capable of programming and developing using the x86 platform. Not only that, but there is a proliferation of tools available for developing with x86.
Read the article; the Full Disclosure Post indicates that this malicious code (and some other malicious code that allows DoS) was intentionaly added into the program, and is most likely a Feature and not a Bug.
I have the MX700 and it absolutely rules. The back/forward buttons are great and the rechargeable batteries last *forever*. It even runs under RH8. The size and shape of the mouse take some getting use to though. And lefties need not apply.
The point I am trying to make is that IMHO, it is more important to build friendship first. Being a friend in the sense that I meant it means knowing a little about them and, as I said, being "comfortable approaching them" with issues. I think that building a basic understanding of the people you work with will enable better communication with them. And I think that communication is more important than trust in terms of teamwork.
I said I "do not always trust them". That means that I trust them 99% of the time, but since I know a little about them, I know when they are working on the boundaries of what they know/can do and I should offer help (in the case of coworkers) or check over what they are doing (in the case of subordinates).
Now I also happen to be in the fairly unique position of having been an "actual friend" with one of the people I work with (we went to University together), so that probably significantly affects how I look at things.
Teambuilding was easy, bring the team together and do exercises in trust, recognizing diversity, and discovering your teammate's backgrounds. So I am asking the Slashdot community, what have you found to be effective in building a better team other than exercises in teamwork?"
Hmmm...sounds like someone has been taking all those Dilbert cartoons seriously...;)
OK, jokes aside, sure you trust each other, but are you friends with one another? There is a very important distinction and I've found that friendship is far most important than trust. I don't always trust that my co-workers (and subordinates) will do things "correctly" or even their best. But for the most part they are also my friends and I feel comfortable approaching them if there is a problem or just some task to work on.
How about doing something friends might be more inclined to do rather than team building exercises? Go mountain biking, paint-balling, rock climbing or hiking together.
There are also things you can do at work. We play Frisbee, Starcraft, or just hang out at lunch. It's not only fun and relaxing, but it builds up the relationships between everyone.
I went to the same event in Edmonton AB and noticed the same thing with the CDs they handed out there.
On a completely different note, they sure didn't make it easy to use the software. Before you could even begin installing anything off the CD you had to download and install updates from the MS site. Then you had to install reboot and configure a Remote Debugging software package simply to allow for another piece of software to install correctly. Once that other piece was installed (I can't even remember what it was off hand), you had to reconfigure and then uninstall the remote debugging toolkit. Then you could actually begin by inserting CD#1. 8 CDs (and I can't even count how many reboots) later VS.NET was finally up-and-running.
Now it's just a matter of configuring it and figuring out how the whole thing works...
Most CS majors have done this at one time or another. Last term I learned LISP, PROLOG, Matlab programming and assembler for a digital project. At the same time I was doing a course in C/C++ and teaching a Java Programming Seminar/Lab.
The most important thing I can suggest is lots of review as often as possible. Someone above suggested implementing the programs from one language in the other languages you are learning. That's a pretty good suggestion, but I'd suggest a slight modification:
Implement the basic techniques of each language in the other language(s). Things like making/assigning variables, looping, file access, etc.
I don't know a lot about the Visual Basic.NET material, but if you know your basic C++, then you shouldn't really have any problems. If you know Java, then all the better, because some of the Java techniques/principles can be applied to the C# aspect of.NET.
I used this book as a secondary reference for a Database course a couple of years ago, and then later for a reference on developing an online MessageBoard using PHP.
The book is pretty good, but tends to gloss over some of the more technical issues of PHP. In addition, the book tries to cover so much that there are a few parts that are missing some of the more complex details. For example, the section on PHP Session Management was a little too brief for my liking, and ended up being supplemented with material from http://www.php.net
These were are fairly minor issues and the only really *serious* issue I had with the book was the section on MySQL installation. It made the installation look so simple and straightforward, when in fact it was not. I attempted installing MySQL on several different boxes under both Mandrake and Redhat. In the end, the MySQL server was installed on a secondary machine under FreeBSD, where it installed without a hitch.
Actually, it kinda sounds bad. More diverse document formats means more formats to support.
A single "universal" document format would seem to be better. That way any company/OSS project could make a product that can use the format and compete for market share.
Slashdot Mirror
Upgrades are not a big concern for many customers (especially larger customers). Usually by the time customers are ready to upgrade, it is simply cheaper to purchase entirely new hardware.
I read that in a report several years ago and didn't beleive it myself. Then I started a small IT business (with a partner) and have completed several server redeployments. After the third time doing this, I remembered the old article. I tried to find it, but couldn't find the exact one again. At any rate, since then, we've been taking this into account when purchasing new hardware. Then I read this today, and it reminded me again about this.
The price/performance ratio of new machines increases so much, that it just doesn't make sense to upgrade older hardware in terms of the performance or cost.
The site is using akamai to distribute it's content, so they shouldn't really be worried about "Managing traffic could also be a good way to ensure that the site stays working in the closing days of the election campaign".
Works from Edmonton, Alberta, Canada too. The Netcraft report only says it is being blocked from London, Sydney, and Amsterdam.
Thats fine, until Firefox (or whatever) is the most popular browser, and the virus/adware/whatever - writers start targeting it.
Just because IE appears to be the most buggy (and it might very well be) does not mean it is. The fact that it happens to be the most "popular" (it's the default browser on 90% of desktops) means it is going to be the most attacked.
I completely agree on the TCO issue.
I am the senior software engineer for a small Canadian development company. I manage the design and development of a set of Web Applications.
We've been running Linux-based web servers, and developing on Linux for the past several years. Last year we completed a sort of research project; reimplementing our flagship web application using ASP.NET. We managed to completely replicate functionality which had taken us approximately 850 hours to implement using OSS technology in less than 150 hours of work. Granted, we had an established design to work with, so the comparison is not totally un-biased.
Since then, we have completely switched over to ASP.NET technology. The productivity gains alone have completely negated any initial purchase or migration costs. In this respect, we continue to see gains on a daily basis.
On the support front, comparing MS to Open Source is fruitless. Signing up as a MS Partner (~ $300 USD) provides developers with copies and licenses to use (almost) every current MS software product. It also gives developers access to MS development support. You just can't compare that with the OSS alternative.
Reducing binary and runtime memory consumption is a great idea, but it's usually going to involve some design tradeoffs. This may mean the product will run slower, or have a slower, less responsive UI.
Computer storage is cheap. My time is not.
http://www.paxwarrior.com
Pax Warrior is not really a game as such, but an "interactive multimedia documentary". It is marketted as, and plays like an interactive Social Studies game. Users (students) are presented with a first-person interaction taking them through the experiences and decisions faced by a UN Commander on a peace keeping mission to Rwanda.
Pax Warrior is very interesting in that, like many games, it presents users with choices that must be made, and consequences that arise from those decisions. In this case, the choices and consequences are very closely modelled on what actually happended in Rwanda.
And yes, for those who are wondering, it has a fixed ending. It's a pretty emotionally connected, moving one at that.
Wrong. The x86 series of processors has long been used in consumer products. Why? To paraphrase Intel Inside (A documentary written on the early days of Intel), the world is overflowing with engineers capable of programming and developing using the x86 platform. Not only that, but there is a proliferation of tools available for developing with x86.
Here is *exactly* what you need :i nde x.html
http://www4.tomshardware.com/network/20031016/
According to the review, it is a "802.11b Hotspot router aimed at the wireless-with-your-latte Mom 'n Pop store-owner. Includes receipt printer"
Read the article; the Full Disclosure Post indicates that this malicious code (and some other malicious code that allows DoS) was intentionaly added into the program, and is most likely a Feature and not a Bug.
Will they even get anything from her? She's a minor and not legally bound to fullfill contracts.
I have the MX700 and it absolutely rules. The back/forward buttons are great and the rechargeable batteries last *forever*. It even runs under RH8. The size and shape of the mouse take some getting use to though. And lefties need not apply.
You're totally mis-interpreting what I said.
The point I am trying to make is that IMHO, it is more important to build friendship first. Being a friend in the sense that I meant it means knowing a little about them and, as I said, being "comfortable approaching them" with issues. I think that building a basic understanding of the people you work with will enable better communication with them. And I think that communication is more important than trust in terms of teamwork.
I said I "do not always trust them". That means that I trust them 99% of the time, but since I know a little about them, I know when they are working on the boundaries of what they know/can do and I should offer help (in the case of coworkers) or check over what they are doing (in the case of subordinates).
Now I also happen to be in the fairly unique position of having been an "actual friend" with one of the people I work with (we went to University together), so that probably significantly affects how I look at things.
Teambuilding was easy, bring the team together and do exercises in trust, recognizing diversity, and discovering your teammate's backgrounds. So I am asking the Slashdot community, what have you found to be effective in building a better team other than exercises in teamwork?"
;)
Hmmm...sounds like someone has been taking all those Dilbert cartoons seriously...
OK, jokes aside, sure you trust each other, but are you friends with one another? There is a very important distinction and I've found that friendship is far most important than trust. I don't always trust that my co-workers (and subordinates) will do things "correctly" or even their best. But for the most part they are also my friends and I feel comfortable approaching them if there is a problem or just some task to work on.
How about doing something friends might be more inclined to do rather than team building exercises? Go mountain biking, paint-balling, rock climbing or hiking together.
There are also things you can do at work. We play Frisbee, Starcraft, or just hang out at lunch. It's not only fun and relaxing, but it builds up the relationships between everyone.
I went to the same event in Edmonton AB and noticed the same thing with the CDs they handed out there.
On a completely different note, they sure didn't make it easy to use the software. Before you could even begin installing anything off the CD you had to download and install updates from the MS site. Then you had to install reboot and configure a Remote Debugging software package simply to allow for another piece of software to install correctly. Once that other piece was installed (I can't even remember what it was off hand), you had to reconfigure and then uninstall the remote debugging toolkit. Then you could actually begin by inserting CD#1. 8 CDs (and I can't even count how many reboots) later VS.NET was finally up-and-running.
Now it's just a matter of configuring it and figuring out how the whole thing works...
Well it's a good thing Slashdot doesn't get many hits, because they're using MySQL.
http://slashdot.org/faq/tech.shtml#te050
"Wherever you go...there you are"
That's a little different. The costs and prices listed there are for a support service they provide for the Operating System.
If you want to fit it into a "standard resume", add it into the Volunteer Work section of your resume.
"I am so smart...S M R T..."
Most CS majors have done this at one time or another. Last term I learned LISP, PROLOG, Matlab programming and assembler for a digital project. At the same time I was doing a course in C/C++ and teaching a Java Programming Seminar/Lab.
.NET material, but if you know your basic C++, then you shouldn't really have any problems. If you know Java, then all the better, because some of the Java techniques/principles can be applied to the C# aspect of .NET.
The most important thing I can suggest is lots of review as often as possible. Someone above suggested implementing the programs from one language in the other languages you are learning. That's a pretty good suggestion, but I'd suggest a slight modification:
Implement the basic techniques of each language in the other language(s). Things like making/assigning variables, looping, file access, etc.
I don't know a lot about the Visual Basic
Good Luck!
The book is pretty good, but tends to gloss over some of the more technical issues of PHP. In addition, the book tries to cover so much that there are a few parts that are missing some of the more complex details. For example, the section on PHP Session Management was a little too brief for my liking, and ended up being supplemented with material from http://www.php.net
These were are fairly minor issues and the only really *serious* issue I had with the book was the section on MySQL installation. It made the installation look so simple and straightforward, when in fact it was not. I attempted installing MySQL on several different boxes under both Mandrake and Redhat. In the end, the MySQL server was installed on a secondary machine under FreeBSD, where it installed without a hitch.
Imagine the internet with several different, and constantly evolving HTML formats to support.
Actually, it kinda sounds bad. More diverse document formats means more formats to support.
A single "universal" document format would seem to be better. That way any company/OSS project could make a product that can use the format and compete for market share.
sorry, but no.
--nathan