Makes sense from a pure dollars and cents perspective... if one person is cheaper than the other, go with the cheaper one. Incidentally, how much money are YOU costing your company?
"Well thought-out", eh? Hmmm... that's an interesting approach. Can you recommend a framework I can use to evaluate this "well thought-out" methodology or a consulting firm which can provide mentoring specialists?
If you're not with us, you're against us, and that didn't sound "with us" enough for me. The air force will be preparing your neighborhood for a Haliburton contract in five minutes.
Or they just stay because the've finally realized every employer is pretty much the same (and if you move too many times, you'll find that employers stop calling you back). Sort of a version of price fixing.
Get a court to agree that I should tell you, and I will.
Which is more than reasonable on the part of the service provider (my hat goes off to you for having the courage to stand firm on this point). Without true anonymity, free speech is an illusion. Of course, FUD will see to it that we'll never have anything remotely resembling anonymity - mention Freenet on Slashdot and watch the avalanche of "I'd never support Freenet - it can be used to spread CP!" Apple will win.
And COBOL-based electronic application programs that cut you off at 30 characters and disallow lower-case are better? At least on the paper applications, there was a margin to write in.
I always wondered about that myself. Before I got the job I have now, I used to "daydream online" from time to time by visiting a certain travel website and putting together/pricing different dream vacations. The job I have now? You guessed it - I now work for that travel website. And I'll tell you something - the last $#(@% thing I want to see when I get home is that web site that has kept me up until 3 AM more than once...
I think their first target will be the Dallas Cowboys cheerleaders. They got an anonymous tip that one or more of them would be harmed in the changing room.
I can tell you from experience that you have to abuse your mod points (e.g. get meta-moderated down) through about 16 "mod point cycles" before they stop giving them to you. You don't have to tell him to stop, they'll stop him.
which will work their way towards the nearest appropriate location based on their key.
Ahhh - but I'm the MPAA, remember? Why would I connect my hostile node into the rest of the Freenet dark net at all? I'm just sitting there with my "honeypot", if you will, waiting for connection attempts, logging request that pops into my modded node.
Random people who don't know each other exchanging noderefs over IRC provides what advantage over the prior Freenet implementation, exactly?
In fact, this can only be seen as a disadvantage. Say I'm the MPAA and people are using Freenet to trade movies (actually if that were the case I could just let them to die of old age waiting for the download to complete, but pretend for a minute). I download freenet's source code, modify the source a bit, go on #movietraders and publish my noderef. Now, since it's IRC, I know who (by nickname) saw that noderef published. I keep track of what they try to download from my modded node, subpeona their IP addresses, and sue them.
The "public" freenet worked, at least in theory, because the seed nodes were fairly globally accessible. The dark net will only work if you actually know somebody running a freenet node (and know he won't sell you out to the RIAA/MPAA/FBI/Chinese authorities/Diebold, etc.) In the grand scheme of things, I don't know that many people... and I've never talked about freenet with any of them.
What is WebWorks, BTW? I've been hearing about it more and more lately - when I Google it, I get this, which looks like a proprietary desktop publishing system to me... is that what you're referring to? Is it really worth looking into and paying licenses for, when Struts, Tapestry and Spring are all open source?
Your college education will be of marginal vaule to you as a programmer.... You won't necessarily be a good programmer just because you made good grades either.
You could be right - in the end, he'll probably end up settling for a lowly CTO or CIO position.
There is no way (nada, zip, nothing) that any trusted platform could ever stop Linux from running.
Except, of course, "protect" the boot sector from modification (and no more booting from disk or CD, either), which is exactly what they'll do. And, of course, to tie off any loose ends, circumvention will be a jailable offense.
And then an anonymous coward says, "Well, you should have said no", so you hunt him down, tie his hands behind his back like Kevin Spacey did to that fat guy he made eat the spaghetti sauce in "Seven", and force him to implement a fully SOAP and BPEL compliant Web Service-based SOA solution. In Lisp. Using Notepad. On Windows 3.1. In a shared cubicle.
They seem to have little idea of what *our* (the engineers) workflow/work process is.
This would work well if the programmer just sat down with the user, with no fixed delivery date, and they started working towards a common goal. This is similar to what you're doing with Excel and Word - you have no project manager, no "budgeted hours", no "chief architect", no "technical lead", and no "requirements design meetings". Just a problem to be solved as efficiently as it can be solved.
Unfortunately, for the programmer, you're not allowed to talk to the users (or, at least, I never have been). Talking to the end-users (actually, there are no users - they're "stakeholders". You'll never meet them.) is for the Birkenstock-wearing, ponytailed, hybrid-driving "usability engineers" the author is so slobberingly excited about. Programmers just get 1500-page "requirements documents", all written in Microsoft Word over a six-month period of review meetings. The less actual information, the better. From those specifications, the programmers are expected to fill out an Excel spreadsheet listing the "tasks" they must complete to fulfill "requirements" with such descriptions as "6.G.9.d.z. The freemulator frooble must goblify the cooblestocken whenever the user selects the remulize option". No asking the "stakeholders" what that actually means - they're far too busy to talk to you. The programmer must then randomly compile a list of "tasks" and a completely wild guess as to how long each task might take. You can estimate any amount of time for any given task and add as many tasks as you like, as long as the total time you estimate adds up to the target date that the stakeholders made up out of the air without consulting you. Once the task list is complete, the whole list is handed over to a project manager who "manages" each task. He does so using sophisticated project management techniques he learned in a one-hour training seminar such as: requiring all programmers to attend a weekly two-hour status meeting where he solemnly reads the list of tasks, one by one, and says, "what percent complete are you on this task?", and "you're falling behind on these tasks. Can we offload some of these to somebody else?". Tasks can never be added or deleted once they project manager "finalizes" his Excel spreadsheet.
At the same time, the stakeholders will change their minds daily. They'll randomly remove one of the 20,000 requirements (the one you spent the last three months coding for) from the requirements list and announce that they've "flexed the scope" to meet a new "compressed delivery date" (which is next Friday).
Slowly but surely, in spite of all the obstacles that have been placed in your way in the name of improving "Product Design" efficiency, you (the programmer) will finally start to understand what it is the users might actually want and what this thing actually does. Unfortunately, about the time you see exactly what needs to be done and the best, most flexible way to do it, the "two months past code complete" date will be hit. Then you will enter "crunch time". The weekly two-hour meetings will change to daily three-hour meetings. One of the agenda items on each meeting will be to discuss how to improve programmer productivity. To make up for the lost time spent in these meetings, you'll be required to work on the weekends. Fifty new programmers will be added to the effort to "help". You'll spend 10 hours of your 16 hour day getting them up to speed. At this point, you do whatever the hell it takes to get this monkey off your back.
Then, at the end of the year, after months and months of 80+ hour work weeks, a failing liver from your increased alcohol consumption (it's the only way you can actually manage to fall asleep) and a divorce since your wife and kids can't remember your first name or what you look like, the users complain about the stinking pile of poo that you finally were able to produce in spite of the "efficiency experts" driving the process. You see, you nee
Well, don't forget - what he actually wrote was "Please free me - we are oppressed here in the Chinese mainland!" It was the outbound censorship gateway that changed his post to reflect a more, ahem, "appropriate" tone.
I got further than you. I stopped at, "If you're interested in cameras, pick up a copy of this book and see if it's the kind of book you're interested in. Then check to see if there's anything close to what you're interested in. If there's nothing in there that you're interested in, or close to something that you might be interested in being interested in, you'll probably not be interested by this book." An insight like that just can't be topped, so there seemed no point in reading further.
imagine a world where playing in your back yard, watching TV at 3 pm, or going to school will all expose a child to _______
Fill in the blank with: religion (Christinanity if you're a Muslim or Islam if you're a Christian), high-fat foods, sharp objects, political viewpoints (Republican if you're a Democrat, Democrat if you're a Republican), homosexuality, interracial marriage, etc. etc. all of which somebody out there will insist that their children will be "harmed" by exposure to. Do we need laws against those, too?
Slashdot Mirror
Makes sense from a pure dollars and cents perspective... if one person is cheaper than the other, go with the cheaper one. Incidentally, how much money are YOU costing your company?
"Well thought-out", eh? Hmmm... that's an interesting approach. Can you recommend a framework I can use to evaluate this "well thought-out" methodology or a consulting firm which can provide mentoring specialists?
That's probably true... but it still takes more training and education and general intelligence than every other job in the corporation.
If you're not with us, you're against us, and that didn't sound "with us" enough for me. The air force will be preparing your neighborhood for a Haliburton contract in five minutes.
...you hope.
Yes, good idea. If there's one thing you can count on child pornographers to do, it's to obey the letter of the law.
HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA - oh, wait, you're serious? What society do YOU live in?
but the want to actually act on that attraction is not socially normalHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA - oh, wait, you're serious...
Or they just stay because the've finally realized every employer is pretty much the same (and if you move too many times, you'll find that employers stop calling you back). Sort of a version of price fixing.
Which is more than reasonable on the part of the service provider (my hat goes off to you for having the courage to stand firm on this point). Without true anonymity, free speech is an illusion. Of course, FUD will see to it that we'll never have anything remotely resembling anonymity - mention Freenet on Slashdot and watch the avalanche of "I'd never support Freenet - it can be used to spread CP!" Apple will win.
And COBOL-based electronic application programs that cut you off at 30 characters and disallow lower-case are better? At least on the paper applications, there was a margin to write in.
I always wondered about that myself. Before I got the job I have now, I used to "daydream online" from time to time by visiting a certain travel website and putting together/pricing different dream vacations. The job I have now? You guessed it - I now work for that travel website. And I'll tell you something - the last $#(@% thing I want to see when I get home is that web site that has kept me up until 3 AM more than once...
I think their first target will be the Dallas Cowboys cheerleaders. They got an anonymous tip that one or more of them would be harmed in the changing room.
I can tell you from experience that you have to abuse your mod points (e.g. get meta-moderated down) through about 16 "mod point cycles" before they stop giving them to you. You don't have to tell him to stop, they'll stop him.
I tried that approach, but my wife was opposed to it.
Ahhh - but I'm the MPAA, remember? Why would I connect my hostile node into the rest of the Freenet dark net at all? I'm just sitting there with my "honeypot", if you will, waiting for connection attempts, logging request that pops into my modded node.
In fact, this can only be seen as a disadvantage. Say I'm the MPAA and people are using Freenet to trade movies (actually if that were the case I could just let them to die of old age waiting for the download to complete, but pretend for a minute). I download freenet's source code, modify the source a bit, go on #movietraders and publish my noderef. Now, since it's IRC, I know who (by nickname) saw that noderef published. I keep track of what they try to download from my modded node, subpeona their IP addresses, and sue them.
The "public" freenet worked, at least in theory, because the seed nodes were fairly globally accessible. The dark net will only work if you actually know somebody running a freenet node (and know he won't sell you out to the RIAA/MPAA/FBI/Chinese authorities/Diebold, etc.) In the grand scheme of things, I don't know that many people... and I've never talked about freenet with any of them.
What is WebWorks, BTW? I've been hearing about it more and more lately - when I Google it, I get this, which looks like a proprietary desktop publishing system to me... is that what you're referring to? Is it really worth looking into and paying licenses for, when Struts, Tapestry and Spring are all open source?
You could be right - in the end, he'll probably end up settling for a lowly CTO or CIO position.
Except, of course, "protect" the boot sector from modification (and no more booting from disk or CD, either), which is exactly what they'll do. And, of course, to tie off any loose ends, circumvention will be a jailable offense.
And then an anonymous coward says, "Well, you should have said no", so you hunt him down, tie his hands behind his back like Kevin Spacey did to that fat guy he made eat the spaghetti sauce in "Seven", and force him to implement a fully SOAP and BPEL compliant Web Service-based SOA solution. In Lisp. Using Notepad. On Windows 3.1. In a shared cubicle.
This would work well if the programmer just sat down with the user, with no fixed delivery date, and they started working towards a common goal. This is similar to what you're doing with Excel and Word - you have no project manager, no "budgeted hours", no "chief architect", no "technical lead", and no "requirements design meetings". Just a problem to be solved as efficiently as it can be solved.
Unfortunately, for the programmer, you're not allowed to talk to the users (or, at least, I never have been). Talking to the end-users (actually, there are no users - they're "stakeholders". You'll never meet them.) is for the Birkenstock-wearing, ponytailed, hybrid-driving "usability engineers" the author is so slobberingly excited about. Programmers just get 1500-page "requirements documents", all written in Microsoft Word over a six-month period of review meetings. The less actual information, the better. From those specifications, the programmers are expected to fill out an Excel spreadsheet listing the "tasks" they must complete to fulfill "requirements" with such descriptions as "6.G.9.d.z. The freemulator frooble must goblify the cooblestocken whenever the user selects the remulize option". No asking the "stakeholders" what that actually means - they're far too busy to talk to you. The programmer must then randomly compile a list of "tasks" and a completely wild guess as to how long each task might take. You can estimate any amount of time for any given task and add as many tasks as you like, as long as the total time you estimate adds up to the target date that the stakeholders made up out of the air without consulting you. Once the task list is complete, the whole list is handed over to a project manager who "manages" each task. He does so using sophisticated project management techniques he learned in a one-hour training seminar such as: requiring all programmers to attend a weekly two-hour status meeting where he solemnly reads the list of tasks, one by one, and says, "what percent complete are you on this task?", and "you're falling behind on these tasks. Can we offload some of these to somebody else?". Tasks can never be added or deleted once they project manager "finalizes" his Excel spreadsheet.
At the same time, the stakeholders will change their minds daily. They'll randomly remove one of the 20,000 requirements (the one you spent the last three months coding for) from the requirements list and announce that they've "flexed the scope" to meet a new "compressed delivery date" (which is next Friday).
Slowly but surely, in spite of all the obstacles that have been placed in your way in the name of improving "Product Design" efficiency, you (the programmer) will finally start to understand what it is the users might actually want and what this thing actually does. Unfortunately, about the time you see exactly what needs to be done and the best, most flexible way to do it, the "two months past code complete" date will be hit. Then you will enter "crunch time". The weekly two-hour meetings will change to daily three-hour meetings. One of the agenda items on each meeting will be to discuss how to improve programmer productivity. To make up for the lost time spent in these meetings, you'll be required to work on the weekends. Fifty new programmers will be added to the effort to "help". You'll spend 10 hours of your 16 hour day getting them up to speed. At this point, you do whatever the hell it takes to get this monkey off your back.
Then, at the end of the year, after months and months of 80+ hour work weeks, a failing liver from your increased alcohol consumption (it's the only way you can actually manage to fall asleep) and a divorce since your wife and kids can't remember your first name or what you look like, the users complain about the stinking pile of poo that you finally were able to produce in spite of the "efficiency experts" driving the process. You see, you nee
Well, don't forget - what he actually wrote was "Please free me - we are oppressed here in the Chinese mainland!" It was the outbound censorship gateway that changed his post to reflect a more, ahem, "appropriate" tone.
I got further than you. I stopped at, "If you're interested in cameras, pick up a copy of this book and see if it's the kind of book you're interested in. Then check to see if there's anything close to what you're interested in. If there's nothing in there that you're interested in, or close to something that you might be interested in being interested in, you'll probably not be interested by this book." An insight like that just can't be topped, so there seemed no point in reading further.
Fill in the blank with: religion (Christinanity if you're a Muslim or Islam if you're a Christian), high-fat foods, sharp objects, political viewpoints (Republican if you're a Democrat, Democrat if you're a Republican), homosexuality, interracial marriage, etc. etc. all of which somebody out there will insist that their children will be "harmed" by exposure to. Do we need laws against those, too?
You mispeled "over your head".