you share a workstation when you pair prog. you don't share when u r reading mail, playing unreal etc, dpoing spike work to get a proposed idea fleshed out. and if you are in the right sort of projects and work spaces, PP is fun and productive. IMOit is very hard to do pairing for more than 2 hours at a time cos it is actually harder on yr brain - you can't goof off mentally for ten minutes when things get tough.
i spect the device can tell parents when their teenage sons are abusing themselves - vibration detection, administers electric shock (at parental discretion of course). oof.
more seriously - maybe there is a "protecting us from them" piece. let's not forget that we (the people who are not the parents of yr children) might like to know where they were when our houses were burgled, cars ripped and burnt etc. cos don't forget the little darlin's sometimes do that too. now i would not mind if a court mandated that little Sydney needs to be tracked and Sidney Senior is on point...
hey !! my father in law was in this film. he was one of the burly popeye-type hauling the HUGE clock into position on one of the ships. does not make _me_ famous, of course, but does not make me less so:)
>you're still supporting Celine Dion's retirement fund.
yeah but at least it means she might retire sooner which would be a good thing.
worked for an outfit that didn't pay staff on time
on
Loki Aftermath Looks Bad
·
· Score: 2, Interesting
in the late 80s early 90s in the UK. the excuse was always that BACS (Bank Automated Clearing System) had "failed" - yeah, right. they would usually pay late - and usually a few days up to a couple weeks late, and often after some maintenance revenue came in, just coincidentally. one of our people took particular exception to this and checked her rights (this is late 80s UK remember) - apparently they could pay you up a month late and not get any flak for it legally. o'course it turned out that making waves about it got you put to the back of the queue next month, so no one ever did that twice. of course the irony of the thing was we were an accounting software company with BACS payroll modules - we knew exactly that BACS is like a rock, and so was the software...sympathies for those folks.
...looking at the article thinking "that number of light years looks too small - i mean a year - how big can that be? ah - i'll stick a few zeroes on the end - yeah, that's done it!!"
it is the zeno/xeno's arrow denial position - everytime you halve the distance to the "proof" - but you never fill in the gaps completely for the people who want the gaps to exist.
the AOP thing is a good design solution for a highly decoupled kind-of miasma of objects when nothing happens and then events do? where there is less of a logical use-case type of path, and state is more critical than state transitions.
but then, if you had that sort of a system, there are a number of patterns that would do most of what you want - does AOP look like the retrofitting an event paradigm onto a more workflow type collaboration of objects?
can you suggest a way to overcome this problem thru abstraction? seems to me that if we can still get some value out of an aspect approach without heresy, that is still a better world?
first time i read the article i thought - dontcha identify yr concerns when you do your use case analysis and see the verb "log" cropping up and then factor out all that function into a class responsible for logging? IWC, i did not really see the value. then when i re-read and looked at the code examples i thought - if you develop for concerns, maybe there is more extensibility in the source because it is concern-aware? would that give you more refactoring elbow-room during the lifetime of the system?
Slashdot Mirror
you share a workstation when you pair prog. you don't share when u r reading mail, playing unreal etc, dpoing spike work to get a proposed idea fleshed out. and if you are in the right sort of projects and work spaces, PP is fun and productive. IMOit is very hard to do pairing for more than 2 hours at a time cos it is actually harder on yr brain - you can't goof off mentally for ten minutes when things get tough.
i spect the device can tell parents when their teenage sons are abusing themselves - vibration detection, administers electric shock (at parental discretion of course). oof.
more seriously - maybe there is a "protecting us from them" piece. let's not forget that we (the people who are not the parents of yr children) might like to know where they were when our houses were burgled, cars ripped and burnt etc. cos don't forget the little darlin's sometimes do that too. now i would not mind if a court mandated that little Sydney needs to be tracked and Sidney Senior is on point...
bet it would be no smoking anyway. and you would have to keep yr seat belt on at all times, which would kinda kill the fun of weightlessness.
hey !! my father in law was in this film. he was one of the burly popeye-type hauling the HUGE clock into position on one of the ships. does not make _me_ famous, of course, but does not make me less so :)
>you're still supporting Celine Dion's retirement fund.
yeah but at least it means she might retire sooner which would be a good thing.
in the late 80s early 90s in the UK. the excuse was always that BACS (Bank Automated Clearing System) had "failed" - yeah, right. they would usually pay late - and usually a few days up to a couple weeks late, and often after some maintenance revenue came in, just coincidentally. one of our people took particular exception to this and checked her rights (this is late 80s UK remember) - apparently they could pay you up a month late and not get any flak for it legally. o'course it turned out that making waves about it got you put to the back of the queue next month, so no one ever did that twice. of course the irony of the thing was we were an accounting software company with BACS payroll modules - we knew exactly that BACS is like a rock, and so was the software...sympathies for those folks.
...looking at the article thinking "that number of light years looks too small - i mean a year - how big can that be? ah - i'll stick a few zeroes on the end - yeah, that's done it!!"
it is the zeno/xeno's arrow denial position - everytime you halve the distance to the "proof" - but you never fill in the gaps completely for the people who want the gaps to exist.
the AOP thing is a good design solution for a highly decoupled kind-of miasma of objects when nothing happens and then events do? where there is less of a logical use-case type of path, and state is more critical than state transitions.
but then, if you had that sort of a system, there are a number of patterns that would do most of what you want - does AOP look like the retrofitting an event paradigm onto a more workflow type collaboration of objects?
can you suggest a way to overcome this problem thru abstraction? seems to me that if we can still get some value out of an aspect approach without heresy, that is still a better world?
first time i read the article i thought - dontcha identify yr concerns when you do your use case analysis and see the verb "log" cropping up and then factor out all that function into a class responsible for logging? IWC, i did not really see the value. then when i re-read and looked at the code examples i thought - if you develop for concerns, maybe there is more extensibility in the source because it is concern-aware? would that give you more refactoring elbow-room during the lifetime of the system?
>It was, in many ways, an inventory of what he had just gained by beating the Saxons and taking their lands.
which is just what poor old harold's ancestors (danes, not saxons) had themselves done a not-many years earlier what goes around etc...