Exactly. Does anybody remember seeing a movie called the Cube?
Wow. Just wow. What a cool concept. Not going to spoil it for those that haven't seen it, but who would have imagined that a single set. Yes. A single set could be used to produce a compelling, edge of your seat movie plot, and on the budget of an oily rag and a used stick of gum.
Contrast this with its sequel. Cube 2 - hypercube! High budget, and loads of crap.
I really thought pitch black was an awesome movie, even if loosely based on the Asimov novel Nightfall. Unfortunately, the sequel didn't measure up to the first movie, but it was entertaining nonetheless.
Call me a die hard old school kinda guy, but I miss *good* science fiction. As in science fiction that contains plausible science, and good social commentary, not this whole fantasy style Avatar kind of science fiction movie.
When spoken in the context of Flash, then yes, it makes perfect sense to not have those pesky 'shared objects' aka cookies on your machine.
However, with the advent of Flex (now Flashbuilder to confuse and confound more), there are many applications out there that legitimately store information on the client.
There has been a large mention of games already, but to that mix, I would add business software. There are many RIA's out there that manage data and distribution using Flex, and hence, pull a large amount of information from servers. Yes, sure, you could reload the data every time that you navigate away from a particular flash harness page, or you could store data within the shared object and not need to spend the vendor's bandwidth, nor stuff the client's pipe with information that was just sent a few minutes ago.
With the introduction of P2P channels in Flex 4, this opens up a whole range of possibilities to send data to a cluster of peers on a destination network, rather than clogging up outgoing pipes with information. There are a range of business cases for this technology.
That said, however, there is a need to curb the wild west attitude to data storage. There should be an option to default allow/deny/question whether Shared Objects should be allowed. Currently it is auto accept up to 100kb which falls outside of many legitimate applications anyway. Most importantly, there should be an option to always allow shared objects from a particular website.
We can't let the abuse of a technology proclude us from legitimate use when there are perfectly valid and reasonable strategies to manage and distinguish between positive and negative use cases.
At my current company we allow for "just because" time. This can be up to 10% of a developer's time, but even that number is flexible. At the end of someone's "just because" time, the business provides constructive (read constructive) feedback as to whether that time was useful, and why/why not.
We combat burnout, and we allow for each developer to get some gun slinging time, which is very important for creativity. At the end, they get feedback as to whether it was useful or not WITHOUT persecution, which hones their instincts in.
In my experience in corporate and small business software development, Agile vs Non-Agile is actually quite irrelevant. As long as there is a process in place, that is being adhered to and is the right horse for the right course, it works and works quite well.
The problem is that in a lot of 2 bit organisations, unskilled Development Managers come along and cobble together a frankenstein process, and/or don't enforce it during the execution. What was once an Agile PROCESS, now becomes an AD-HOC MESS.
When things go wrong, human nature tends to find the first handy scapegoat, so the methodology gets the blame, when really the problem exists between the keyboard and the chair.
I have the feeling that back in the 19th Century (in the US anyway) people like that would be having an abrupt and Frank discussion with Mr. Colt. Especially in the wild west.;)
Damn straight it's about seat overflow. I flew from LA to Sydney (15 hr flight) next to a rather stout Polish tire salesman. He couldn't even fit into the damn seat! He lifted the arm rest, took over half of my seat, and I would up crunched against a couple next to me.
When I found out, I complained to the QANTAS stewardess, and she said that I could move seats later. Quite hard on a full plane.
you know how uncomfortable it is having a seat rest firmly wedged in your back for 15 hours?
Sorry people of carriage, but if your caboose cannot fit into the seat to the point where you need to lift your armrest, you simply need to buy another god damned seat.
Slashdot Mirror
Exactly. Does anybody remember seeing a movie called the Cube?
Wow. Just wow. What a cool concept. Not going to spoil it for those that haven't seen it, but who would have imagined that a single set. Yes. A single set could be used to produce a compelling, edge of your seat movie plot, and on the budget of an oily rag and a used stick of gum.
Contrast this with its sequel. Cube 2 - hypercube! High budget, and loads of crap.
I really thought pitch black was an awesome movie, even if loosely based on the Asimov novel Nightfall. Unfortunately, the sequel didn't measure up to the first movie, but it was entertaining nonetheless.
Call me a die hard old school kinda guy, but I miss *good* science fiction. As in science fiction that contains plausible science, and good social commentary, not this whole fantasy style Avatar kind of science fiction movie.
Surely I don't stand alone.
Bubba... is that you?
When spoken in the context of Flash, then yes, it makes perfect sense to not have those pesky 'shared objects' aka cookies on your machine.
However, with the advent of Flex (now Flashbuilder to confuse and confound more), there are many applications out there that legitimately store information on the client.
There has been a large mention of games already, but to that mix, I would add business software. There are many RIA's out there that manage data and distribution using Flex, and hence, pull a large amount of information from servers. Yes, sure, you could reload the data every time that you navigate away from a particular flash harness page, or you could store data within the shared object and not need to spend the vendor's bandwidth, nor stuff the client's pipe with information that was just sent a few minutes ago.
With the introduction of P2P channels in Flex 4, this opens up a whole range of possibilities to send data to a cluster of peers on a destination network, rather than clogging up outgoing pipes with information. There are a range of business cases for this technology.
That said, however, there is a need to curb the wild west attitude to data storage. There should be an option to default allow/deny/question whether Shared Objects should be allowed. Currently it is auto accept up to 100kb which falls outside of many legitimate applications anyway. Most importantly, there should be an option to always allow shared objects from a particular website.
We can't let the abuse of a technology proclude us from legitimate use when there are perfectly valid and reasonable strategies to manage and distinguish between positive and negative use cases.
On thy way brother Eli, and take ye horse and cart with ye!
Maybe I should apply for not producing corn. I haven't been doing that for many many years.
So I guess the term gas, grass or ass nobody rides for free will have a redundant term in it then?
Can you hear me now?!?
Can you hear me now?!?
Can you hear me now?!?
And come on! It's BadAnalogyGuy!!! The analogy is as advertised.
That's beyond his cranial capacity.
There's so much back scratching going on here that these guys must sleep on their stomach. I'm sick to mine.
Come on guys, stop teasing the Luxembourgian.
You are so spot on with burnout.
At my current company we allow for "just because" time. This can be up to 10% of a developer's time, but even that number is flexible. At the end of someone's "just because" time, the business provides constructive (read constructive) feedback as to whether that time was useful, and why/why not.
We combat burnout, and we allow for each developer to get some gun slinging time, which is very important for creativity. At the end, they get feedback as to whether it was useful or not WITHOUT persecution, which hones their instincts in.
Somewhere somebody is always a fool. The trick is to have a fool tolerant system. e.g. foolproof.
In my experience in corporate and small business software development, Agile vs Non-Agile is actually quite irrelevant. As long as there is a process in place, that is being adhered to and is the right horse for the right course, it works and works quite well.
The problem is that in a lot of 2 bit organisations, unskilled Development Managers come along and cobble together a frankenstein process, and/or don't enforce it during the execution. What was once an Agile PROCESS, now becomes an AD-HOC MESS.
When things go wrong, human nature tends to find the first handy scapegoat, so the methodology gets the blame, when really the problem exists between the keyboard and the chair.
I have the feeling that back in the 19th Century (in the US anyway) people like that would be having an abrupt and Frank discussion with Mr. Colt. Especially in the wild west. ;)
He made it himself. He wouldn't trust anyone else to get the spelling right.
Better than McLovin.
That's all well and good, but what fraction of a car is that?
Christopher Reeve. Next question?
Damn straight it's about seat overflow. I flew from LA to Sydney (15 hr flight) next to a rather stout Polish tire salesman. He couldn't even fit into the damn seat! He lifted the arm rest, took over half of my seat, and I would up crunched against a couple next to me.
When I found out, I complained to the QANTAS stewardess, and she said that I could move seats later. Quite hard on a full plane.
you know how uncomfortable it is having a seat rest firmly wedged in your back for 15 hours?
Sorry people of carriage, but if your caboose cannot fit into the seat to the point where you need to lift your armrest, you simply need to buy another god damned seat.
And car analogies are just so 2000!
We won't mention Robodan, Circuitmas, and Kwanza.
Week? Month more like it. Back to your corner!
The van must drive pretty darn slowly. Have you ever run in flippers?!? I guess the other option was an impromptu face plant on google maps.
They just chose that name to increase page ranking of search results!