Was there an entry on how you are all hyper-sensitive and narcissistic and therefore prone take wide-sweeping generalizations personal? 'Cause there should be...
You've sort of muddled the comparison, due to the differences in addressing schemes.
Typing in "example" and being redirected to http://www.example.com/ is more like dialing 555-555-5555 and the country code being inferred, so you actually call 1-555-555-5555 (in the US, since I'm an insensitive clod). You might have meant to call China, but seriously, you probably didn't.
Further still, what IE is doing is essentially connecting you to your preferred operator (Debbie?) whenever "the number you dialed is no longer in service."
As a soon-to-be-graduating software engineering student, I would say that finding our own solution to this problem was always a useful exercise in every pair/group I've been in. And the solutions were ALL different, depending on the needs of the group.
You teach Java, stick to that. If you include more tooling in your class than just an IDE, you run the risk of coupling the tools and the language in the minds of your students, which will in turn make it difficult for them to transition into a job where the tooling is significantly different.
You'll also expand your job description to be tech support for whatever tool you choose, and you'll have to accept whatever problems and problem-generated excuses that tool generates. If you are tool-agnostic, you can be more of a hard-ass when an assignment is late or incomplete.
How many articles have there been ridiculing someone from some company or government agency that lost some data? OP did say it was for work, afterall. If he worked for me, I'd give him a raise for caring.
Maybe we're not afraid of the 'average thief' anymore, we just don't want pretentious slashdotters talking shit about how that would have never happened to them because they have X software on Y OS on Z hardware bla bla bla. And since we do all talk shit, maybe we're the people to ask for a solution.
my original comment was about the inappropriate use of the word baseband.
...the sending and receiving sides of the ADSL signal are modulated above baseband...
My argument here is that the ASDL signals are sent at a frequency higher than the voice traffic, not the baseband, since ADSL does not have a baseband. The use of the word "baseband" implies that ADSL data is analog, and it is not. It is digital. Yes, it's a nit-picky argument, but I clarified that the reason for this is because the original article (if you can call it that) was a rant about people using technically incorrect terminology.
OK, now you're referring to the IEEE 802.3 medium naming convention, which differentiates between "baseband" and "broadband," "baseband" meaning only one signal is sent at a time, whereas "broadband" means channelization is used to send multiple signals at once. ADSL over phonelines would therefore be "broadband," since there is definitely channelization going on, making the use of the term "baseband" still inappropriate.
The use of the word "baseband" is entirely inappropriate. Baseband refers to the frequency range of the original analog signal prior to modulation. It is only applicable when modulating an analog signal, such as upshifting an audio signal. ADSL is digital, so there is no "baseband." What you are referring to is the voice channel.
Lest we forget, we were originally discussing the incorrect usage of technical terms.
ADSL takes digital signals and modulates them into an analog signal. This analog signal is what is sent across the wires. This signal happens to be sent at a frequency much higher than voice traffic, as mentioned above, so that the two traffic flows can be split and handled separately. So there is, in fact, an AD converter, as well as DA.
The phrase "ADSL is solely digital" is not technically incorrect either, it's just digital traffic that is keyed with analog signals. For example, with FSK (Frequency Shift Keying), which is used in military radios to transmit digital data over radiotelephone ("walkie talkie") frequencies, one frequency is used to encode a '0' and a different frequency is used to encode a '1'. The signals sent are sinusoidal (analog) waves, but the data sent is still purely digital.
We've had this on the Austin (that's in Texas) area toll roads for a year or two now.
I'm a fan. I always hated having to slow down and sit in a queue at the toll plazas, but I don't use the tolls enough to warrant the whole EZTag/TXTag thing. Now with this I can keep on clipping along, get to where I'm going quickly, and mail in a couple bucks at the end of the month.
When the tolls first came to the area, there were all sorts of whinings and complainings going around, and I'm sure they'll end up here too. Let me short-circuit the whole mess. If you don't like toll-roads, don't use them. There is always (by law, at least in Texas) an alternate route. Also, only the people that use them pay for them, so you can't whine about "your tax dollars," they aren't being used.
You're only going to be summing from 0 to 99, so your answer would be short by 100. You need the condition in your for loop to be less-than/equal to, not just less than.
Remember, big ego != (actually good || worth keeping around || worth paying || worth having to deal with)
Agreed. Let's also keep in mind that "uber badass programmers" are a dime a dozen these days. Great developers are hard to find. You know, the ones that actually understand what all (other than coding) goes into making a quality product.
In addition to its distinctive pink color, a unique attribute of the Keyboard for Blondes are the "fun" sayings on 64 of the keys, such as "Oops!" on the Delete key, "The Big One: 'I Need My Space' Key" on the spacebar, or "Yes! I want it!" on the Enter key. A number of the keys also act as special texting shortcuts, such as "OMG" on the O key, "LOL" on the L key, and "XOXO" on the X key.
Deploying Red Hat Linux to all of your servers is free. Absolutely free, no cost. Access to their repos and support costs money. Repos provide an easy and convenient way to upgrade stuff, but you can always get the source and build the updates manually, or build your own repos from the source and link all of your boxes to that repo, etc.
This is not an argument that Red Hat is not in fact a commercial organization, but their approach is drastically different from Microsoft. With Microsoft, software is a product, and support and updates are free (since updates can be seen as an admission of "oops, we did that wrong.) With Red Hat, software is a service, since it grows and changes constantly. You can get a certain snapshot for free in the form of a blessed release.
From a development standpoint, Red Hat's model makes more sense, because the cost of initial development pales in comparison to the cost of managing software.
At the real heart of the issue, there really is no standard for numbering, official or market. Some companies release number after number with little or no dot releases (anyone remember AOL?). Some don't even have numbers, just one main chunk of code that is patched and upgraded via the interwebz. Others use dot releases to mark patches or minor improvements and use major revisions to mark a significant change. This seems to be the de facto standard, if there is one.
Barring some sort of IEEE standard, the best we can hope for is companies/organizations that publish a roadmap that let's us all know what will constitute the next major release (much like Firefox, Fedora, etc).
My advice to the OP would be this, if your costumers are technical in nature, be straight up. If this is a piece of consumer software, drop the versioning altogether and call it Super Awesome Product Xtreme.
I think you guys forgot the part where you swear not to tell anyone what's involved in the induction ceremony. I strongly suggest you turn in your sashes now.
My wife also runs Fedora (8) on her laptop. I turned it into a dual-boot XP-Fedora box awhile back, and at first she never touched the Fedora side. Over time, it shifted, and now she's in Fedora 99% of the time (Windows only to update the ol' iPod). She also is in a no way a developer, and still knows little about the CLI and how to use it, but hey, it's a start.
Slashdot Mirror
Dear God there MUST be video of this.
FreeCol is pretty fun.
My OS is increasingly becoming just Firefox.
Was there an entry on how you are all hyper-sensitive and narcissistic and therefore prone take wide-sweeping generalizations personal? 'Cause there should be...
You've sort of muddled the comparison, due to the differences in addressing schemes.
Typing in "example" and being redirected to http://www.example.com/ is more like dialing 555-555-5555 and the country code being inferred, so you actually call 1-555-555-5555 (in the US, since I'm an insensitive clod). You might have meant to call China, but seriously, you probably didn't.
Further still, what IE is doing is essentially connecting you to your preferred operator (Debbie?) whenever "the number you dialed is no longer in service."
As a soon-to-be-graduating software engineering student, I would say that finding our own solution to this problem was always a useful exercise in every pair/group I've been in. And the solutions were ALL different, depending on the needs of the group.
You teach Java, stick to that. If you include more tooling in your class than just an IDE, you run the risk of coupling the tools and the language in the minds of your students, which will in turn make it difficult for them to transition into a job where the tooling is significantly different.
You'll also expand your job description to be tech support for whatever tool you choose, and you'll have to accept whatever problems and problem-generated excuses that tool generates. If you are tool-agnostic, you can be more of a hard-ass when an assignment is late or incomplete.
How many articles have there been ridiculing someone from some company or government agency that lost some data? OP did say it was for work, afterall. If he worked for me, I'd give him a raise for caring.
Maybe we're not afraid of the 'average thief' anymore, we just don't want pretentious slashdotters talking shit about how that would have never happened to them because they have X software on Y OS on Z hardware bla bla bla. And since we do all talk shit, maybe we're the people to ask for a solution.
or maybe not.
Fundamentals of Logic Design - Roth. Designed for a self-paced course taught at the University of Texas at Austin, so actually geared toward your needs. http://www.amazon.com/Fundamentals-Logic-Design-C-Roth/dp/0495073083/ref=sr_1_1?ie=UTF8&s=books&qid=1247594924&sr=8-1
...the sending and receiving sides of the ADSL signal are modulated above baseband...
My argument here is that the ASDL signals are sent at a frequency higher than the voice traffic, not the baseband, since ADSL does not have a baseband. The use of the word "baseband" implies that ADSL data is analog, and it is not. It is digital. Yes, it's a nit-picky argument, but I clarified that the reason for this is because the original article (if you can call it that) was a rant about people using technically incorrect terminology.
10BASE-T is BASEband on the wire
OK, now you're referring to the IEEE 802.3 medium naming convention, which differentiates between "baseband" and "broadband," "baseband" meaning only one signal is sent at a time, whereas "broadband" means channelization is used to send multiple signals at once. ADSL over phonelines would therefore be "broadband," since there is definitely channelization going on, making the use of the term "baseband" still inappropriate.
The use of the word "baseband" is entirely inappropriate. Baseband refers to the frequency range of the original analog signal prior to modulation. It is only applicable when modulating an analog signal, such as upshifting an audio signal. ADSL is digital, so there is no "baseband." What you are referring to is the voice channel.
Lest we forget, we were originally discussing the incorrect usage of technical terms.
To go one step further with the explanation:
ADSL takes digital signals and modulates them into an analog signal. This analog signal is what is sent across the wires. This signal happens to be sent at a frequency much higher than voice traffic, as mentioned above, so that the two traffic flows can be split and handled separately. So there is, in fact, an AD converter, as well as DA.
The phrase "ADSL is solely digital" is not technically incorrect either, it's just digital traffic that is keyed with analog signals. For example, with FSK (Frequency Shift Keying), which is used in military radios to transmit digital data over radiotelephone ("walkie talkie") frequencies, one frequency is used to encode a '0' and a different frequency is used to encode a '1'. The signals sent are sinusoidal (analog) waves, but the data sent is still purely digital.
That's what SHE said!
If you're looking to hire an artist, ask for a portfolio. If you're looking for a coder, give them a few challenges during their technical interview.
Either way, seems an interview and some knowledge of the person's work will expose their skills and deficiencies, who cares what they call themselves?
We've had this on the Austin (that's in Texas) area toll roads for a year or two now. I'm a fan. I always hated having to slow down and sit in a queue at the toll plazas, but I don't use the tolls enough to warrant the whole EZTag/TXTag thing. Now with this I can keep on clipping along, get to where I'm going quickly, and mail in a couple bucks at the end of the month.
When the tolls first came to the area, there were all sorts of whinings and complainings going around, and I'm sure they'll end up here too. Let me short-circuit the whole mess. If you don't like toll-roads, don't use them. There is always (by law, at least in Texas) an alternate route. Also, only the people that use them pay for them, so you can't whine about "your tax dollars," they aren't being used.
Yep, that's pretty much it.
You're only going to be summing from 0 to 99, so your answer would be short by 100. You need the condition in your for loop to be less-than/equal to, not just less than.
I would make the condition of the for loop i <= 100 and take out the sum++ line.
Remember, big ego != (actually good || worth keeping around || worth paying || worth having to deal with)
Agreed. Let's also keep in mind that "uber badass programmers" are a dime a dozen these days. Great developers are hard to find. You know, the ones that actually understand what all (other than coding) goes into making a quality product.
Deploying Red Hat Linux to all of your servers is free. Absolutely free, no cost. Access to their repos and support costs money. Repos provide an easy and convenient way to upgrade stuff, but you can always get the source and build the updates manually, or build your own repos from the source and link all of your boxes to that repo, etc.
This is not an argument that Red Hat is not in fact a commercial organization, but their approach is drastically different from Microsoft. With Microsoft, software is a product, and support and updates are free (since updates can be seen as an admission of "oops, we did that wrong.) With Red Hat, software is a service, since it grows and changes constantly. You can get a certain snapshot for free in the form of a blessed release.
From a development standpoint, Red Hat's model makes more sense, because the cost of initial development pales in comparison to the cost of managing software.
At the real heart of the issue, there really is no standard for numbering, official or market. Some companies release number after number with little or no dot releases (anyone remember AOL?). Some don't even have numbers, just one main chunk of code that is patched and upgraded via the interwebz. Others use dot releases to mark patches or minor improvements and use major revisions to mark a significant change. This seems to be the de facto standard, if there is one.
Barring some sort of IEEE standard, the best we can hope for is companies/organizations that publish a roadmap that let's us all know what will constitute the next major release (much like Firefox, Fedora, etc).
My advice to the OP would be this, if your costumers are technical in nature, be straight up. If this is a piece of consumer software, drop the versioning altogether and call it Super Awesome Product Xtreme.
Translation: You worry about all of that geeky stuff, we'll handle the real world.
Honestly, I expect a little better from the slashdot crowd. If the engineer's opinion is worthless here, where is it valued?
The lower 50% of american workers pay NO income tax. They pay payroll and social security and that's it, they are exempt from the federal income tax.
Pretty sure that payroll tax is income tax.
I think you guys forgot the part where you swear not to tell anyone what's involved in the induction ceremony. I strongly suggest you turn in your sashes now.
My wife also runs Fedora (8) on her laptop. I turned it into a dual-boot XP-Fedora box awhile back, and at first she never touched the Fedora side. Over time, it shifted, and now she's in Fedora 99% of the time (Windows only to update the ol' iPod). She also is in a no way a developer, and still knows little about the CLI and how to use it, but hey, it's a start.