I call bullshit. Federally backed low interest loans may in fact allow more people to go to school and increasing demand for education and allowing schools to charge more and provide more.
That said, I don't think the limiting factor on the cost of higher education is how much money the federal government is giving out. In fact, less than half of students get any form of loan at all, let alone federal. The average loan? 5K. With tuiton running 25K \ year some places, it just isn't all getting paid for by the government.
That, and people aren't that dumb. We do get ourselves into more debt than we can handle, but who is really going to put themselves into 450K of debt for a college education in the states? You'd see tons of people going overseas and others not going to school. The demand would be low enough the universities would have to lower prices.
-----
Oh, and both of these guys dropped out of college as well and did quite well for themselves on their own.
I tend to go visit Tom's when I'm looking to purchase new hardware. Do I really care if a review comes out a week later than the other sites? Hell no. I won't be reading it for a month anyway.
I hope they are able to pull this off without losing readership. I think they can cede the first review of a product and go for providing the best review. That's strong marketting.
I'm still not seeing a real need for Generics. They complicate the language by giving us more syntax to learn while providing very little.
If we're supposed to have a collection of rocks, what the heck would paper be doing in there? More often than not, reasonable coding should prevent this.
The key place where this might make sense is when you're producing an API for external consumption. There, it might be nice to say that the collection being thrown back at the user is all of one type or another.
The links are fine, but a Wiki is essentially a web page that people can log in to and edit relatively easily. Often they are used as a commons for sharing information or ideas.
Everyone is ripping against this like it's the worse thing since moldy sliced bread. Sounds like they have a small number of extra shifts and a large number of nurses who want to work them.
They could give out the extra shifts randomly or to the nurse who a manager thinks is particularly cute in that uniform. They could queue everyone up and let everyone have a turn.
Instead, they get the people who need the work the most actually working and those who are just looking for bigger money to spend at the mall will likely drop out at high wage levels. In a sense, this is a very fair way to sort out who needs the work. It's unfortunate that the nurses earn less this way, but they aren't having their wages forcibly cut, they are bidding.
Further, last I checked there was generally a shortage of nurses, rather than a surplus. I figure the hardships this introduces would less than tragic for most.
What would I think about this for my profession? Hmm... extra pay for overtime would sure be a nice thing. Oh, the overtime is optional? That's nice too. I'm not really jealous of the nurses here, and I think this is moderately slimy behavior, but there really have been worse developments in the course of human history.
So... If I'm a developer and I sell my product for $50 it's perfectly appropriate for the one purchaser of my product to "share" it with the rest of the world. Everyone else gets it for free?
Let's look at a book and examine the word "sharing". A book seems to be the right place to discuss this in light of copyright. Now, if I share a book with you, probably only one of us can be reading it at time. Either you have it or I have it.
This is very differant from sharing software by posting keys up on a warez site. In that case, I can use the software, you can use the software, and 1000 other people can use it simultaneously. That doesn't sound like sharing. You didn't give anything up so that someone else could gain.
Working out a reasonable way to share software is tricky. Some commercial software has floating licenses that will do the trick to some extent, but that's not a complete solution.
If you get something for free, that you should have paid for, that's either a gift or theft. If nobody gave something up willingly, then I'm thinking this smells like theft.
Is Piracy a good term? Eh, I don't really care. You could call it theft if you'd like.
Speaking of which. Microsoft has a point about GPLed stuff. God bless Apache and their BSD style licensing. Now I just need to get around to donating something to them.
The key would be to target the rocks to logical places - or have the satallite we actually send put itself in a good place. Either a relatively stable point in a solar system or plop it down on a dead rock like our moon.
That's the interesting part of the paper. Discussing where the good places are, so we would have an idea of where to go looking for messages that have been sent to us.
This book seems like a good one for all developers to read. I'm honestly only about half way though it, but I've skimmed the whole thing.
The big thing that jumps out at me is that he promotes how cool CruiseControl is for automating builds, but uses cron for his release builds. Generally, I would want to use the same tool to create my continuous integration, nightly and production release builds. I was under the impression that there were ways to make that happen in CruiseControl.
disclaimer: I help write a product that does do this, so maybe I'm just projecting biases.
The section on diagnostics also looks quite interesting, but I'm not that far yet.
Yes! Bikes get trashed. If you're buying a bike for school, buy a cheap one. One, it won't be touched if properly locked. Two, if it is, you can buy another 3 for the price of nice bike.
I had more stuff stolen from me in high school than I did in university (25K students). Freshman year, we did have our room "broken" into to. Yeah, you should lock the door at night. We hardly woke up in time for the door to close. A bit later, my roomate discovered that his CDs had left. Had to be someone on our floor.
My big advice is get a PC instead of a laptop if possible. You wouldn't leave $2000 in cash sitting out your desk, don't bring a laptop. For taking notes, a pen and paper are great. Personally I find that if I write something long hand, I remember it - going back over it is extra. For really hard classes, I would sometimes type up my notes afterwards, that was a great way to quickly go back over everything.
Here are the roomates me and my friends had freshman year:
Business student, who joined a Christian Frat. Stoner who was never in the room Slob who was a decent guy Annoying sorority girl who was an "ambassador" for the football team. Nice girl who partied a bit much.
Most of these people were really decent folks or were not around enough to cause anyone problems. Don't stress the roomate until you have to worry about 'em.
Sure, when he finds the bugs in your code through a peer review, you can add the test cases to first expose the problem then prove that you've corrected it.
The other major advantage of code reviews is that you know someone else is going to look at your code soon. You're less likely to try to slip something trashy that works through.
What is capitalism, as opposed to companies that are owned by a number of people which try to make money? You can argue that money has too great a role in the US politocal structure, but that would be a flaw in the political system, not in capitalism.
You make lots of big claims and back those up only with other big claims. How does any of this hold up?
Even in ClearCase you need a nuetral place that does builds, runs tests against those builds and emails people when those tests fail.
There's a very good reason why Cruise Control, Anthill Pro and others support ClearCase. While it does support multiple individual development (a feature you don't need to spend ClearCase sized money on) it doesn't do the testing part of continuous integration. And it definately isn't an automated build server.
If you're not testing, you're not doing continuous integration. If your automated build server doesn't handle the tagging of the source control for milestone builds, your only doing continuous integration and leaving your QA and release management teams blowing in the wind.
Sure the lava lamp is gimmicky and stupid, but the important part is that it provides quick feedback when the build "breaks". This is what we want from continuous integration. We want to be building a lot and TESTING the crap out of those builds. And we want that all to be happening automatically on a clean server.
When one fails, we suspect that there's a bug or someone forgot to check something in. Generally, it's good to find this out quickly. The advantage of the lamp is that you notice the lamp changing where you might not notice yet another email. That said, I have a "Failed Builds Notification" folder in my email, and when that has something in it, I pay attention. A spammer who can spoof his way in there deserves my attention:)
It's not about keeping the red lamp off. It's about noticing when the red lamp is on.
Ah, a nice thing to do here is have your tool check the repository log for who checked in since the last time the build worked, then email those developers and say "Hey idiot, you or someone else on this list broke the build. Here's the error."
The glowing red light is a gag, but something like CruiseControl or Anthill or BuildForge will go a long way.
Google has a list of tools that will help automate builds and manage them. I help write one of them, but won't be that shameless in the plug.
Overall, I think it's good to have some sort of tool that automates your builds and emails you when they brake. Continuous integration is a good part of it for developers, but this also gets into release management, communication between teams, and such.
Slashdot Mirror
I call bullshit. Federally backed low interest loans may in fact allow more people to go to school and increasing demand for education and allowing schools to charge more and provide more.
That said, I don't think the limiting factor on the cost of higher education is how much money the federal government is giving out. In fact, less than half of students get any form of loan at all, let alone federal. The average loan? 5K. With tuiton running 25K \ year some places, it just isn't all getting paid for by the government.
That, and people aren't that dumb. We do get ourselves into more debt than we can handle, but who is really going to put themselves into 450K of debt for a college education in the states? You'd see tons of people going overseas and others not going to school. The demand would be low enough the universities would have to lower prices.
-----
Oh, and both of these guys dropped out of college as well and did quite well for themselves on their own.
Wow, I was super unlcear in my complaint. My complaint was that making a collection type safe is mostly a waste of time. sorry about that.
Why couldn't his name have been Bob? Then I could have had a nice joke about blaming Eve.
Yeah. I think that job sucks more than the rest.
I tend to go visit Tom's when I'm looking to purchase new hardware. Do I really care if a review comes out a week later than the other sites? Hell no. I won't be reading it for a month anyway.
I hope they are able to pull this off without losing readership. I think they can cede the first review of a product and go for providing the best review. That's strong marketting.
I'm still not seeing a real need for Generics. They complicate the language by giving us more syntax to learn while providing very little.
If we're supposed to have a collection of rocks, what the heck would paper be doing in there? More often than not, reasonable coding should prevent this.
The key place where this might make sense is when you're producing an API for external consumption. There, it might be nice to say that the collection being thrown back at the user is all of one type or another.
The links are fine, but a Wiki is essentially a web page that people can log in to and edit relatively easily. Often they are used as a commons for sharing information or ideas.
He also seems intent on drastically changing the nature of a corporation - that might not be doable.
Everyone is ripping against this like it's the worse thing since moldy sliced bread. Sounds like they have a small number of extra shifts and a large number of nurses who want to work them.
They could give out the extra shifts randomly or to the nurse who a manager thinks is particularly cute in that uniform. They could queue everyone up and let everyone have a turn.
Instead, they get the people who need the work the most actually working and those who are just looking for bigger money to spend at the mall will likely drop out at high wage levels. In a sense, this is a very fair way to sort out who needs the work. It's unfortunate that the nurses earn less this way, but they aren't having their wages forcibly cut, they are bidding.
Further, last I checked there was generally a shortage of nurses, rather than a surplus. I figure the hardships this introduces would less than tragic for most.
What would I think about this for my profession? Hmm... extra pay for overtime would sure be a nice thing. Oh, the overtime is optional? That's nice too. I'm not really jealous of the nurses here, and I think this is moderately slimy behavior, but there really have been worse developments in the course of human history.
So... If I'm a developer and I sell my product for $50 it's perfectly appropriate for the one purchaser of my product to "share" it with the rest of the world. Everyone else gets it for free?
Let's look at a book and examine the word "sharing". A book seems to be the right place to discuss this in light of copyright. Now, if I share a book with you, probably only one of us can be reading it at time. Either you have it or I have it.
This is very differant from sharing software by posting keys up on a warez site. In that case, I can use the software, you can use the software, and 1000 other people can use it simultaneously. That doesn't sound like sharing. You didn't give anything up so that someone else could gain.
Working out a reasonable way to share software is tricky. Some commercial software has floating licenses that will do the trick to some extent, but that's not a complete solution.
If you get something for free, that you should have paid for, that's either a gift or theft. If nobody gave something up willingly, then I'm thinking this smells like theft.
Is Piracy a good term? Eh, I don't really care. You could call it theft if you'd like.
Speaking of which. Microsoft has a point about GPLed stuff. God bless Apache and their BSD style licensing. Now I just need to get around to donating something to them.
So restricting the age of selling alchohol (which implies checking id) can be challenged constitutionally?
The key would be to target the rocks to logical places - or have the satallite we actually send put itself in a good place. Either a relatively stable point in a solar system or plop it down on a dead rock like our moon.
That's the interesting part of the paper. Discussing where the good places are, so we would have an idea of where to go looking for messages that have been sent to us.
Cool, do you have CruiseControl manage the release builds as well or something else?
Most of the setups I've seen are running CppUnit or similar with Make for builds and tests. Another option is OpenMake
Making that happen repeatedly on a controled server is the domain of Anthill, CruiseControl and a handful of for money tools.
This book seems like a good one for all developers to read. I'm honestly only about half way though it, but I've skimmed the whole thing.
The big thing that jumps out at me is that he promotes how cool CruiseControl is for automating builds, but uses cron for his release builds. Generally, I would want to use the same tool to create my continuous integration, nightly and production release builds. I was under the impression that there were ways to make that happen in CruiseControl.
disclaimer: I help write a product that does do this, so maybe I'm just projecting biases.
The section on diagnostics also looks quite interesting, but I'm not that far yet.
Yes! Bikes get trashed. If you're buying a bike for school, buy a cheap one. One, it won't be touched if properly locked. Two, if it is, you can buy another 3 for the price of nice bike.
I had more stuff stolen from me in high school than I did in university (25K students). Freshman year, we did have our room "broken" into to. Yeah, you should lock the door at night. We hardly woke up in time for the door to close. A bit later, my roomate discovered that his CDs had left. Had to be someone on our floor.
My big advice is get a PC instead of a laptop if possible. You wouldn't leave $2000 in cash sitting out your desk, don't bring a laptop. For taking notes, a pen and paper are great. Personally I find that if I write something long hand, I remember it - going back over it is extra. For really hard classes, I would sometimes type up my notes afterwards, that was a great way to quickly go back over everything.
Here are the roomates me and my friends had freshman year:
Business student, who joined a Christian Frat.
Stoner who was never in the room
Slob who was a decent guy
Annoying sorority girl who was an "ambassador" for the football team.
Nice girl who partied a bit much.
Most of these people were really decent folks or were not around enough to cause anyone problems. Don't stress the roomate until you have to worry about 'em.
Sure, when he finds the bugs in your code through a peer review, you can add the test cases to first expose the problem then prove that you've corrected it.
The other major advantage of code reviews is that you know someone else is going to look at your code soon. You're less likely to try to slip something trashy that works through.
What is capitalism, as opposed to companies that are owned by a number of people which try to make money? You can argue that money has too great a role in the US politocal structure, but that would be a flaw in the political system, not in capitalism.
You make lots of big claims and back those up only with other big claims. How does any of this hold up?
Even in ClearCase you need a nuetral place that does builds, runs tests against those builds and emails people when those tests fail.
There's a very good reason why Cruise Control, Anthill Pro and others support ClearCase. While it does support multiple individual development (a feature you don't need to spend ClearCase sized money on) it doesn't do the testing part of continuous integration. And it definately isn't an automated build server.
If you're not testing, you're not doing continuous integration. If your automated build server doesn't handle the tagging of the source control for milestone builds, your only doing continuous integration and leaving your QA and release management teams blowing in the wind.
Sure the lava lamp is gimmicky and stupid, but the important part is that it provides quick feedback when the build "breaks". This is what we want from continuous integration. We want to be building a lot and TESTING the crap out of those builds. And we want that all to be happening automatically on a clean server.
:)
When one fails, we suspect that there's a bug or someone forgot to check something in. Generally, it's good to find this out quickly. The advantage of the lamp is that you notice the lamp changing where you might not notice yet another email. That said, I have a "Failed Builds Notification" folder in my email, and when that has something in it, I pay attention. A spammer who can spoof his way in there deserves my attention
It's not about keeping the red lamp off. It's about noticing when the red lamp is on.
Ah, a nice thing to do here is have your tool check the repository log for who checked in since the last time the build worked, then email those developers and say "Hey idiot, you or someone else on this list broke the build. Here's the error."
The glowing red light is a gag, but something like CruiseControl or Anthill or BuildForge will go a long way.
Disclaimer: I work for one of the above.
You're right. Clearly your grammar skills are superior to mine. Congratulations.
Google has a list of tools that will help automate builds and manage them. I help write one of them, but won't be that shameless in the plug.
Overall, I think it's good to have some sort of tool that automates your builds and emails you when they brake. Continuous integration is a good part of it for developers, but this also gets into release management, communication between teams, and such.