Actually, I would be interested in seeing you pick that paragraph apart point by point, showing each error. Blocking the use of modified code on a device has proved contentious. As has the wrapping up of open code into SaaS offerings which avoid the necessity of distributing the source code.
If you spend an awful lot of time grinding in the NOC you eventually become a level-something 'Network Architect' with no direct reports but with the ability to tell everyone what to do.
Taking a few management tips from in-game, perhaps?
Putting aside for one moment any shortcomings in their infrastructure, those posts area text-book example of how to communicate status clearly and concisely to customers.
That's nice for it. The question is how liquid are those assets and how much cash can it actually get its hands on at short notice. As banks in Britain have noticed, assets just ain't worth what they were.
English and American chocolate is very different for historical reasons.
Historically, making milk chocolate was beset by one problem: getting fresh milk to the plant. Before refrigeration and railways it was nigh on impossible. The two countries had different approaches: in the UK sugar was added to the milk as a preservative, in the U.S, the milk was essentially allowed to sour.
By the time refrigeration arrived, the nations' tastes were set. The U.S continues to make much of its chocolate with soured milk, while the UK has very sweet milk chocolate.
So when as an Englander I first tasted a Hershey bar the overwhelming impression was of off-milk or vomit. This was, ummm... offputting.
I've never yet found a single solitary use for Automator, but back in the 90s I used to build Hypercards that did all sorts of things, mainly automated text processing taxing quark documents and turning them into rudimentary HTML. It was soooo easy.
The worst thing you can do is take it as a personal sleight, that won't make you feel good about yourself or make your company/coworkers feel good about you. And it's funny how you end up working with people again in the future.
So take it calmy and be utterly professional about it, treat it like an exercise and learn from it to start building leaving-staff policies for the It department of the firm you are about to join.
To start with write a document with a work plan for the remaining four weeks:
Set out all of projects that are close to completion and which you feel need to be completed before you leave if your current company isn't going to have difficulties completing.
Set out the bits of knowledge you want to document.
Send that to your boss together with a description of the minimum system access you will need for each task, and possible workarounds if that access isn't available.
As your boss to decide whether he/she would like any of this work done.
If the answer is yes, you will have started a constructive conversation on what needs doing and how you can do it. If the answer is no, you can become a prolific Slashdot poster with a clear conscience and start planning out the initial elements of your new job.
If you really believe this then I suspect that you have not been subjected to a "religion" firsthand.
And if you really believe that it is impossible to distinguish between the level of coercion leveled on a member of say the UK Church of England and say Scientology hen I suspect that you have not been subjected to a cult firsthand.
Sounds like the main problem was the settings set up by your IT guys. I think it is reasonable for an enterprise system to not let the end user over-ride centrally-imposed constraints, no?
"Absolutely, we would be delighted to provide you with this high-value ad-hoc access system. In order to protect our valuable operational infrastructure this will require the installation of a separate datawarehouse. Provisioning this system will cost $X, the monthly charge for maintenance of the system, the population of the datawarehouse and the provision of secure access will cost $Y"
The advantage of this approach:
1. It makes you look helpful and willing to accomodate your customers 2. It makes it clear what some of the issues are 3. If you set the values of $X and $Y at the correct values you can generate significant additional revenue for your business 4. If you set the values of $X and $Y just a little higher, the answer equates to "No".
I came here to say that the oldest running code was probably the DNA that codes for .
Do you need a religion to say that this code was written rather than generated? I think we are treading a thin semantic line here. I'd argue that you could easily say the code sequence was 'written' through a process of random chance and natural selection.
If an infinite number of monkeys armed with keyboards will eventually write the complete works of Shakespeare, it still gets written, even though the process is random.
Slashdot Mirror
Actually, I would be interested in seeing you pick that paragraph apart point by point, showing each error. Blocking the use of modified code on a device has proved contentious. As has the wrapping up of open code into SaaS offerings which avoid the necessity of distributing the source code.
Is Gal Civ 2 entirely written in Python, then?
If you spend an awful lot of time grinding in the NOC you eventually become a level-something 'Network Architect' with no direct reports but with the ability to tell everyone what to do.
Taking a few management tips from in-game, perhaps?
... this is, for the powers that be.
... keep 'em peeled.
Agreed,
Putting aside for one moment any shortcomings in their infrastructure, those posts area text-book example of how to communicate status clearly and concisely to customers.
The salient part is unless I have to. You are basically setting out the same position as all other Web developers.
That's nice for it. The question is how liquid are those assets and how much cash can it actually get its hands on at short notice. As banks in Britain have noticed, assets just ain't worth what they were.
English and American chocolate is very different for historical reasons.
Historically, making milk chocolate was beset by one problem: getting fresh milk to the plant. Before refrigeration and railways it was nigh on impossible. The two countries had different approaches: in the UK sugar was added to the milk as a preservative, in the U.S, the milk was essentially allowed to sour.
By the time refrigeration arrived, the nations' tastes were set. The U.S continues to make much of its chocolate with soured milk, while the UK has very sweet milk chocolate.
So when as an Englander I first tasted a Hershey bar the overwhelming impression was of off-milk or vomit. This was, ummm... offputting.
But it is just what people are used to.
Even better. I have a Ford Focus and two toddlers who tend to leave half eaten apple cores on the back seats.
Musn't post on too little sleep, that should have said "This is what we call a PR gimmick".
Alton Towers gets free publicity in the papers, a debate ensues, no-one actually gets their PDAs removed. Nothing to see here, move along please.
I've never yet found a single solitary use for Automator, but back in the 90s I used to build Hypercards that did all sorts of things, mainly automated text processing taxing quark documents and turning them into rudimentary HTML. It was soooo easy.
quit yer hitching!
The worst thing you can do is take it as a personal sleight, that won't make you feel good about yourself or make your company/coworkers feel good about you. And it's funny how you end up working with people again in the future.
So take it calmy and be utterly professional about it, treat it like an exercise and learn from it to start building leaving-staff policies for the It department of the firm you are about to join.
To start with write a document with a work plan for the remaining four weeks:
Set out all of projects that are close to completion and which you feel need to be completed before you leave if your current company isn't going to have difficulties completing.
Set out the bits of knowledge you want to document.
Send that to your boss together with a description of the minimum system access you will need for each task, and possible workarounds if that access isn't available.
As your boss to decide whether he/she would like any of this work done.
If the answer is yes, you will have started a constructive conversation on what needs doing and how you can do it. If the answer is no, you can become a prolific Slashdot poster with a clear conscience and start planning out the initial elements of your new job.
And if you really believe that it is impossible to distinguish between the level of coercion leveled on a member of say the UK Church of England and say Scientology hen I suspect that you have not been subjected to a cult firsthand.
Serious point here, exactly how is WiMax toio complex, or rather, why can't the poster set it up?
I think the author's interpretation of 'community edited' is perfectly reasonable. As you say, he wrote it and asked others to edit it.
Sounds like the main problem was the settings set up by your IT guys. I think it is reasonable for an enterprise system to not let the end user over-ride centrally-imposed constraints, no?
The version available for Macs around 1990 was damn useful. Wouldn't touch it with a barge-pole now.
Precisely. If this had appeared in 'another place' I would already be reaching for the 'bury as spam' or 'bury because this is lame' options.
"Absolutely, we would be delighted to provide you with this high-value ad-hoc access system. In order to protect our valuable operational infrastructure this will require the installation of a separate datawarehouse. Provisioning this system will cost $X, the monthly charge for maintenance of the system, the population of the datawarehouse and the provision of secure access will cost $Y"
The advantage of this approach:
1. It makes you look helpful and willing to accomodate your customers
2. It makes it clear what some of the issues are
3. If you set the values of $X and $Y at the correct values you can generate significant additional revenue for your business
4. If you set the values of $X and $Y just a little higher, the answer equates to "No".
Win-Win.
...and the findings suggest that, actually - no-one does.
I came here to say that the oldest running code was probably the DNA that codes for .
Do you need a religion to say that this code was written rather than generated? I think we are treading a thin semantic line here. I'd argue that you could easily say the code sequence was 'written' through a process of random chance and natural selection.
If an infinite number of monkeys armed with keyboards will eventually write the complete works of Shakespeare, it still gets written, even though the process is random.