You can't create quality software without planning before coding. Ditto for not testing after coding. This isn't rocket science, yet too many "professionals" think all they need to do is code.
The waterfall model isn't a management process, it's basic common sense. It's not about attending meetings and getting signatures, it's about knowing what to code before you code it, then verifying that that is what you coded. The classic waterfall took too long because you had to plan Z before you started coding A, but with an iterated waterfall (which is still a waterfall, duh) you only need to plan A before you code A.
Not at all true. Homeschoolers have quite active social lives. Most of the myths of homeschooling were invented by the media in an effort to portray them as the other. "Look at those people who are not like us!" In fact, homeschoolers have networks because parents cannot do everything alone at the dining room table. Homeschoolers will be interacting with all the other homeschoolers in the area, will be going on frequent group field trips, etc. And they join soccer and baseball teams just like everyone else.
Unless your parents were total helicopters, you did an awful lot of socializing outside of the school. What did you do after school, on weekends, on vacations? Surely your parents didn't lock you up in your room! Homeschoolers get this same socialization, plus their homeschooling networks.
The waterfall method is still the best development model. Uou have to analyze, then plan, then code, then test, then maintain. The steps need to be in order and you can't skip any of them. Unfortunately waterfall doesn't fit into the real world of software development because you can't freeze your requirements for so long a time. But cyclic models are a good second place, because they are essentially iterated waterfall models. When you boil all the trendy stuff out of Agile, you're basically left with a generic iterated waterfall, which is why it works. The trendy crap is just so you can sell the idea to management.
I updated yesterday. Pulled down the sources and built world and kernel. All during this my system remained usable. I didn't have to upgrade any ports. After build I dropped into single user mode, installed, then rebooted. When I was back up, I noticed no differences... and that is a *good* thing! All operating systems should be like this (although with varying degrees of hands-on-ness).
It doesn't matter what the law says or what I agreed to, the FSF still says they will use their team of lawyers to enforce their particular interpretation of their license. It's not about who is right or wrong, it's about who has the biggest lawyers.
If you go back to the beginning of the thread, you'll find out I was talking about my monitor. So far there are no wireless monitors. I have a 27" flatscreen, so downgrading to a 15" or even 17" laptop display is exceedingly subpar.
No, the people can limit the government. But it takes an informed people willing to get off their butts and stop it. Yeah it's difficult, maybe even impossible, but it's still worth attempting.
There were still people here arguing that certain crisises could only be met giving the executive branch more powers. But regardless, I don't trust either Obama with those powers either. Actually, sometimes the nice guys are the worst to give them too, because people are more willing to let him slide.
If you have a system that depends on the right guy being in power, you have a broken system. We must never give more powers to the right guys than we would trust to the wrong guys.
GPL libraries are the prime example where one developer's restrictions are applied to other another developer's code. The FSF claims that linkage equals derivation.
Static linkage actually distributes the code, so copyright covers it in the distribution department, but dynamic linkage does not distribute the code. Derivation is not dependency, nor is it referencing. Also, deriving classes in C++ is a wholly different concept than deriving from copyrighted works. I can write write applications that link to a library without even having the library source code anywhere on the development system, and distribute the resulting program separate and distinct from the library.
I've got a dock for my Thinkpad, and it's awesome. I would hesitate to buy any laptop in the future that did not have some sort of docking station or port extender. And no, a USB hub is **NOT** a port extender!
I can dock and undock my laptop in two seconds, without any ratsnest of cords snaking over my desktop, no cords getting lost behind the desk while I'm away, etc.
Freedom means I can act freely, so long as I do not act to block the freedom of others to do the same. There's nothing wrong with the reciprocality of the GPL, but the nature of software development is that it gets mixed, so reciprocality requirements on your own code end up being requirements placed on other people's code.
Remember all you folks who argued for greater presidential powers: Every power you gave Bush is a power Obama now has. And ditto for you Obama fans who will be arguing the same in the next few years for your guy. Eventually there will be someone you don't like in office. There's a very good reason for limiting the power of government: malchiks and nitwits frequently find their way into office.
If a GPL developer takes a BSD driver, then fixes a bug, the BSD developer cannot subsequently fix that bug. Because the GPL fix is "open" it is impossible to do a clean room implementation of the fix. Either you convince the GPL developer to license his fix back to you under a different license, or you have to implement a *different* solution.
Just because a BSD developer whines does not mean he wants to sue you in court. GPL developers don't understand this, because their whole worldview is based on controlling the behavior of other people. Freedom is not about controlling other people!
Re:At the risk of sounding like a freebsd fanboi
on
FreeBSD 7.1 Released
·
· Score: 1
A friend of mine used to have the following bumper sticker: "If you love something, set it free. If it doesn't come back to you, hunt it down and kill it!"
Ironically enough, I spotted a slight variation on it on the bumper of a GPL fanboy: "If you write love software, set it Free. If no one contributes back, hunt them down and sue the shit out of them!"
"Foreign" filesystem support in the kernel will always be spotty. But don't blame FreeBSD for this, as the situation is the same from the other direction. Linux support for UFS is spotty as well.
That doesn't eliminate the suck however. I've got an external USB drive that I want to use with FreeBSD, Linux, Windows *and* OSX, and the only usable common filesystem between them is the horrendous FAT32. I'm probably going to end up using NTFS because as least there's non-kernel fuse drivers for it.
They shouldn't focus on the desktop to the exclusion of everything else, like some linux distros do, but neither should they ignore it. I'm using FreeBSD as my primary desktop, and it works great. Yeah, it does take a big of configuration, but it's well worth it. It's on the level of Slackware or Arch.
If you only have one good idea in your lifetime, and it happens to occur while attending university, and it just so happens that your professor used it, too bad. But if you're such a freaking genius, then I'm sure you'll have many good ideas over your lifetime. Don't worry about the one that didn't get patented and ensconced within a platoon of lawyers.
I was really really hoping for a mid-line system that didn't have a freaking built-in monitor! I've already got a 27" flatpanel which I'm not about to throw away for an iMac.
We need a bailout! Classify piano roll makers as financial institutions and give them a piece of the TARP pie! If we let these jobs die we will never see them again! Bailout, bailout, bailout!!!
The crash in a nutshell: Moral hazard. The US Federal Government created a moral hazard with guarantees against private risk. There's no downside if the government won't let you fail, so why be safe and when you can be daring? And so financial markets made overly risky investments. Worthless securities became valuable commodities.
This isn't a failure of capitalism, but a failure of government tinkering. The common claim that Bush/Greenspan/etc were laissez faire is a laughable assertion. Fannie, Freddie and the Fed are quasi-government institutions, and NOT private organizations operating in a free market. The market is not perfect by any stretch of the imagination, but that does not imply that government fiddling about can do better.
When faced with collapsing financial markets, the question to ask is not what government can do, but what the government can undo.
If I understand correctly, the GPL license of the QT toolkit requires all derivative works to be distributed under the same terms, i.e. the GPL.
You understand wrong. Qt is released with several exceptions to the GPL, allowing you to use any Free Software license, not just the GPL. No, you can't write a proprietary app without buying a license, but you are not limited to just the GPL.
Slashdot Mirror
You can't create quality software without planning before coding. Ditto for not testing after coding. This isn't rocket science, yet too many "professionals" think all they need to do is code.
The waterfall model isn't a management process, it's basic common sense. It's not about attending meetings and getting signatures, it's about knowing what to code before you code it, then verifying that that is what you coded. The classic waterfall took too long because you had to plan Z before you started coding A, but with an iterated waterfall (which is still a waterfall, duh) you only need to plan A before you code A.
Not at all true. Homeschoolers have quite active social lives. Most of the myths of homeschooling were invented by the media in an effort to portray them as the other. "Look at those people who are not like us!" In fact, homeschoolers have networks because parents cannot do everything alone at the dining room table. Homeschoolers will be interacting with all the other homeschoolers in the area, will be going on frequent group field trips, etc. And they join soccer and baseball teams just like everyone else.
Unless your parents were total helicopters, you did an awful lot of socializing outside of the school. What did you do after school, on weekends, on vacations? Surely your parents didn't lock you up in your room! Homeschoolers get this same socialization, plus their homeschooling networks.
The waterfall method is still the best development model. Uou have to analyze, then plan, then code, then test, then maintain. The steps need to be in order and you can't skip any of them. Unfortunately waterfall doesn't fit into the real world of software development because you can't freeze your requirements for so long a time. But cyclic models are a good second place, because they are essentially iterated waterfall models. When you boil all the trendy stuff out of Agile, you're basically left with a generic iterated waterfall, which is why it works. The trendy crap is just so you can sell the idea to management.
FreeBSD: Unlike Linux, we won't send the cops around to make sure you're using the officially approved operating system!
I updated yesterday. Pulled down the sources and built world and kernel. All during this my system remained usable. I didn't have to upgrade any ports. After build I dropped into single user mode, installed, then rebooted. When I was back up, I noticed no differences... and that is a *good* thing! All operating systems should be like this (although with varying degrees of hands-on-ness).
It doesn't matter what the law says or what I agreed to, the FSF still says they will use their team of lawyers to enforce their particular interpretation of their license. It's not about who is right or wrong, it's about who has the biggest lawyers.
GPL: license to sue.
If you go back to the beginning of the thread, you'll find out I was talking about my monitor. So far there are no wireless monitors. I have a 27" flatscreen, so downgrading to a 15" or even 17" laptop display is exceedingly subpar.
If that happens without intercession by SCOTUS, it will be a first in US history.
No, the people can limit the government. But it takes an informed people willing to get off their butts and stop it. Yeah it's difficult, maybe even impossible, but it's still worth attempting.
There were still people here arguing that certain crisises could only be met giving the executive branch more powers. But regardless, I don't trust either Obama with those powers either. Actually, sometimes the nice guys are the worst to give them too, because people are more willing to let him slide.
If you have a system that depends on the right guy being in power, you have a broken system. We must never give more powers to the right guys than we would trust to the wrong guys.
GPL libraries are the prime example where one developer's restrictions are applied to other another developer's code. The FSF claims that linkage equals derivation.
Static linkage actually distributes the code, so copyright covers it in the distribution department, but dynamic linkage does not distribute the code. Derivation is not dependency, nor is it referencing. Also, deriving classes in C++ is a wholly different concept than deriving from copyrighted works. I can write write applications that link to a library without even having the library source code anywhere on the development system, and distribute the resulting program separate and distinct from the library.
Yes it does, but how well does UDF work for harddrives?
You can buy decent 27" monitors for $200? Where?!?!
I've got a dock for my Thinkpad, and it's awesome. I would hesitate to buy any laptop in the future that did not have some sort of docking station or port extender. And no, a USB hub is **NOT** a port extender!
I can dock and undock my laptop in two seconds, without any ratsnest of cords snaking over my desktop, no cords getting lost behind the desk while I'm away, etc.
Freedom means I can act freely, so long as I do not act to block the freedom of others to do the same. There's nothing wrong with the reciprocality of the GPL, but the nature of software development is that it gets mixed, so reciprocality requirements on your own code end up being requirements placed on other people's code.
Remember all you folks who argued for greater presidential powers: Every power you gave Bush is a power Obama now has. And ditto for you Obama fans who will be arguing the same in the next few years for your guy. Eventually there will be someone you don't like in office. There's a very good reason for limiting the power of government: malchiks and nitwits frequently find their way into office.
If a GPL developer takes a BSD driver, then fixes a bug, the BSD developer cannot subsequently fix that bug. Because the GPL fix is "open" it is impossible to do a clean room implementation of the fix. Either you convince the GPL developer to license his fix back to you under a different license, or you have to implement a *different* solution.
Just because a BSD developer whines does not mean he wants to sue you in court. GPL developers don't understand this, because their whole worldview is based on controlling the behavior of other people. Freedom is not about controlling other people!
A friend of mine used to have the following bumper sticker: "If you love something, set it free. If it doesn't come back to you, hunt it down and kill it!"
Ironically enough, I spotted a slight variation on it on the bumper of a GPL fanboy: "If you write love software, set it Free. If no one contributes back, hunt them down and sue the shit out of them!"
"Foreign" filesystem support in the kernel will always be spotty. But don't blame FreeBSD for this, as the situation is the same from the other direction. Linux support for UFS is spotty as well.
That doesn't eliminate the suck however. I've got an external USB drive that I want to use with FreeBSD, Linux, Windows *and* OSX, and the only usable common filesystem between them is the horrendous FAT32. I'm probably going to end up using NTFS because as least there's non-kernel fuse drivers for it.
They shouldn't focus on the desktop to the exclusion of everything else, like some linux distros do, but neither should they ignore it. I'm using FreeBSD as my primary desktop, and it works great. Yeah, it does take a big of configuration, but it's well worth it. It's on the level of Slackware or Arch.
If you only have one good idea in your lifetime, and it happens to occur while attending university, and it just so happens that your professor used it, too bad. But if you're such a freaking genius, then I'm sure you'll have many good ideas over your lifetime. Don't worry about the one that didn't get patented and ensconced within a platoon of lawyers.
p.s. Ideas can't be "stolen".
I was really really hoping for a mid-line system that didn't have a freaking built-in monitor! I've already got a 27" flatpanel which I'm not about to throw away for an iMac.
We need a bailout! Classify piano roll makers as financial institutions and give them a piece of the TARP pie! If we let these jobs die we will never see them again! Bailout, bailout, bailout!!!
The crash in a nutshell: Moral hazard. The US Federal Government created a moral hazard with guarantees against private risk. There's no downside if the government won't let you fail, so why be safe and when you can be daring? And so financial markets made overly risky investments. Worthless securities became valuable commodities.
This isn't a failure of capitalism, but a failure of government tinkering. The common claim that Bush/Greenspan/etc were laissez faire is a laughable assertion. Fannie, Freddie and the Fed are quasi-government institutions, and NOT private organizations operating in a free market. The market is not perfect by any stretch of the imagination, but that does not imply that government fiddling about can do better.
When faced with collapsing financial markets, the question to ask is not what government can do, but what the government can undo.
You understand wrong. Qt is released with several exceptions to the GPL, allowing you to use any Free Software license, not just the GPL. No, you can't write a proprietary app without buying a license, but you are not limited to just the GPL.
http://www.linuxjournal.com/article/6366