Discussion in 'Business & Enterprise Computing' started by elvis, Jul 1, 2008.
I wrote the requirements, and they have changed - pray that i do not alter them further.
DONE is agreed team definition of when a requested piece of work is actually completed, nothing to do with specification or fitness to objective of delivery. Just completeness of task within the team.
I used to think Done was when I'd be proud of what was delivered...
But hey, I went 30+ years of my life thinking mediocre meant it was fucken trash.
But if the requests are vague, Done becomes subjective.
Nope... done is within the team, it is documentation, testing that it works and doesn't regress, filling in the fucken Jira ticket appropriately, getting peer review of code prior to push... yadda yadda
Fit for purpose is subjective and should be decided outside the team, as the team have already decided that their delivery is fit for purpose and is not part of DONE other than conforming to any prerequisites in the specification of the task, provided that has been meet the task can still be DONE and not fit for purpose because product owner / architect didn't specify the complete story, that is not part of DONE.
SCRUM only identifies the definition of DONE as the agreement of the the individuals within the team, a contract to do specific tasks against a request within the sprint, by the team members, most of these deliverables are procedural for every task completed. This stuff is everyday stuff and is just a check list to maintain consistency in documentation, automated testing and coding standards... manglement usually add project management objectives like cost tracking and ticket system updates.
1. why do "businesses/startups" get upset when you start debt collection against them and issue a lean on em when they own money?
2. then get bent out of shape when you explain trading insolvent means they are personally liable and that swanky director title they have has fucked em and bankruptcy means they will loss personally as the shelf company can't save them?
1. Because it's a waste of everybody's time, so fuck you?
2. Because they know you can't do shit until late September, so fuck you?
2. Courts are open buddy.
Good luck raising with court proceedings being public knowledge.
LOL - auditing my ssh keys last nite, I still have production access and repo access to projects and companies I haven't worked for from 8 years ago. Is it still called hacking if you have the keys to the front door but don't live there any more?
I also have AWS root cert for 3 companies I no longer work for... because its so hard to issue individual ssh keys, we'll just give the root key to everyone, even contractors.
Unauthorised access to a computer system, and its a crime. Once you put your key in the lock and turned it you stepped over the line. Yes its pisspoor security on their part, but still.
do they still work? or are you just assuming they've never been changed?
What if the door is open (Aka Direct Object Access)?
Well I know 3 will never be changed because they are AWS root certificates, account root certificates cannot be changed. The oldest one is to a self hosted system and I have emailed them today to let them know that the SSH key I have is still active, see if the AFP arrest me for hacking, since logs will show just a simple login/logout.
Trespassing is trespassing, regardless of whether the front door was open or not.
I'm not an AWS guru, but I thought you can create a new key, and then disable/delete the old.
Seems a glaring security hole if there's a credential that can never be changed.
(either way, damn colossally negligently stupid to be sharing creds around, and not taking advantage of their IAM system)
Dumbasses will do dumbass shit.
What If I'm standing out side, Looking in?
Do you do that a lot?
Yes, but the nice policeman said if I put my pants back on, he'd leave me alone.
How could he tell you weren't wearing pants under your furry costume?
bottom half was different colour fur.