The Vogons would be proud
-
Our new manager is putting all kinds of documents and procedures in place. Standard Operating Procedures, Forms for Change Requests, etc. I guess some of it's good, if it's not overdone and starts to get in the way of getting work done. I'm used to working for smaller companies with a more 'flexible' process ;)
Don't say i didn't warn you, a change request to change text on a button from "Save" to "Submit" will now be taking 4 months to get from development to production. On a positive note, you will still be getting your pay check. :laugh:
"Coming soon"
-
Don't say i didn't warn you, a change request to change text on a button from "Save" to "Submit" will now be taking 4 months to get from development to production. On a positive note, you will still be getting your pay check. :laugh:
"Coming soon"
-
Our new manager is putting all kinds of documents and procedures in place. Standard Operating Procedures, Forms for Change Requests, etc. I guess some of it's good, if it's not overdone and starts to get in the way of getting work done. I'm used to working for smaller companies with a more 'flexible' process ;)
Jacquers wrote:
starts to get in the way of getting work done.
Exactly. Your manager is a noob.
It's much easier to enjoy the favor of both friend and foe, and not give a damn who's who. -- Lon Milo DuQuette
-
Don't say i didn't warn you, a change request to change text on a button from "Save" to "Submit" will now be taking 4 months to get from development to production. On a positive note, you will still be getting your pay check. :laugh:
"Coming soon"
No it won't. It will never get done, as it will not get high enough priority to be ever phased in into a sprint. And the testing process afterwards including adapting all automated test cases for ranorex and other tools will cause so many working hours that it will be labelled as "too expensive" and then it will be dropped. In 5 years from now, users will still not know, that "Save" actually sends data to a server :doh:
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
-
Don't say i didn't warn you, a change request to change text on a button from "Save" to "Submit" will now be taking 4 months to get from development to production. On a positive note, you will still be getting your pay check. :laugh:
"Coming soon"
That reminds me of when I advised my boss to turn down a contract writing some medical software because it had to go through an FDA approval process or some such (it has been years - i think that's the agency though) Anyway, turnaround time on releases/updates in that scenario is just too much. We'd have to have endlessly tested before every revision to even hope to break even and we didn't have the infrastructure for it - i'd have wanted at least one dedicated tester on staff to do that.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
-
Our new manager is putting all kinds of documents and procedures in place. Standard Operating Procedures, Forms for Change Requests, etc. I guess some of it's good, if it's not overdone and starts to get in the way of getting work done. I'm used to working for smaller companies with a more 'flexible' process ;)
Jacquers wrote:
Our new manager is putting all kinds of documents and procedures in place.
Ah yes, "paperwork" that nobody cares about and nobody will ever read, most likely so that a checkbox can be checked for the auditors when they come to verify some ISO or similar compliance that some other paper-pushing bureaucrats wrote in some dark windowless government office to justify their own existence. Bah. Humbug. SDLC. X|
Latest Articles:
Abusing Extension Methods, Null Continuation, and Null Coalescence Operators -
That reminds me of when I advised my boss to turn down a contract writing some medical software because it had to go through an FDA approval process or some such (it has been years - i think that's the agency though) Anyway, turnaround time on releases/updates in that scenario is just too much. We'd have to have endlessly tested before every revision to even hope to break even and we didn't have the infrastructure for it - i'd have wanted at least one dedicated tester on staff to do that.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
actually it can be a winner. I encountred this at a manufacturing company. firstly the FDA will let some other body do the approval, say state (or if it's overseas the home country govt.) after that they show up for their own inspection, maybe leave a few notes, requests (for info - not changes), and once that is done they approve you. every 3 years or so they come back for an inspection - as long as nothing has changed, as long as documentation is in place, they re-approve.
honey the codewitch wrote:
turnaround time on releases/updates in that scenario is just too much
so that means you don't update or change anything, really just don't change a thing - only fix what is broken (and document that to the volume of an encyclopedia.) doesn't matter if your system runs on RSTS/E on a PDP 11/23, doesn't matter if the cooling system is a monkey pedaling a stationary bicycle, you change nothing, you upgrade nothing, just write (literally, on paper using a pen, on to SOP forms which also never change) a daily ream of logs and the renewals keep coming. 2 or 3 FDA folks roll up, show them you've done the required, let them walk around and flip through a few binders of logs, let them feed the monkey a bag of [very clean] peanuts, get the other monkey CEO to take them out for lunch - that's it.
after many stupid answers the nice folks at Technet said the only solution is to reinstall my signature. What a surprise!
-
Our new manager is putting all kinds of documents and procedures in place. Standard Operating Procedures, Forms for Change Requests, etc. I guess some of it's good, if it's not overdone and starts to get in the way of getting work done. I'm used to working for smaller companies with a more 'flexible' process ;)
So... whose grandmother has been eaten by the Ravenous Bugblatter Beast of Traal? :omg: :)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
Our new manager is putting all kinds of documents and procedures in place. Standard Operating Procedures, Forms for Change Requests, etc. I guess some of it's good, if it's not overdone and starts to get in the way of getting work done. I'm used to working for smaller companies with a more 'flexible' process ;)
You want the form for a change request? Do you have the form for approval to receive a change request? You'd first need to get the form for the form for approval, of course. Why, it's forms all the way down!
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
Our new manager is putting all kinds of documents and procedures in place. Standard Operating Procedures, Forms for Change Requests, etc. I guess some of it's good, if it's not overdone and starts to get in the way of getting work done. I'm used to working for smaller companies with a more 'flexible' process ;)
-
actually it can be a winner. I encountred this at a manufacturing company. firstly the FDA will let some other body do the approval, say state (or if it's overseas the home country govt.) after that they show up for their own inspection, maybe leave a few notes, requests (for info - not changes), and once that is done they approve you. every 3 years or so they come back for an inspection - as long as nothing has changed, as long as documentation is in place, they re-approve.
honey the codewitch wrote:
turnaround time on releases/updates in that scenario is just too much
so that means you don't update or change anything, really just don't change a thing - only fix what is broken (and document that to the volume of an encyclopedia.) doesn't matter if your system runs on RSTS/E on a PDP 11/23, doesn't matter if the cooling system is a monkey pedaling a stationary bicycle, you change nothing, you upgrade nothing, just write (literally, on paper using a pen, on to SOP forms which also never change) a daily ream of logs and the renewals keep coming. 2 or 3 FDA folks roll up, show them you've done the required, let them walk around and flip through a few binders of logs, let them feed the monkey a bag of [very clean] peanuts, get the other monkey CEO to take them out for lunch - that's it.
after many stupid answers the nice folks at Technet said the only solution is to reinstall my signature. What a surprise!
all those docs. still glad i punted. :laugh:
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
-
Don't say i didn't warn you, a change request to change text on a button from "Save" to "Submit" will now be taking 4 months to get from development to production. On a positive note, you will still be getting your pay check. :laugh:
"Coming soon"
devenv.exe wrote:
a change request to change text on a button from "Save" to "Submit" will now be taking 4 months to get from development to production
You might as well go the whole hog, and change the text to "I bloody give in!"
I wanna be a eunuchs developer! Pass me a bread knife!
-
actually it can be a winner. I encountred this at a manufacturing company. firstly the FDA will let some other body do the approval, say state (or if it's overseas the home country govt.) after that they show up for their own inspection, maybe leave a few notes, requests (for info - not changes), and once that is done they approve you. every 3 years or so they come back for an inspection - as long as nothing has changed, as long as documentation is in place, they re-approve.
honey the codewitch wrote:
turnaround time on releases/updates in that scenario is just too much
so that means you don't update or change anything, really just don't change a thing - only fix what is broken (and document that to the volume of an encyclopedia.) doesn't matter if your system runs on RSTS/E on a PDP 11/23, doesn't matter if the cooling system is a monkey pedaling a stationary bicycle, you change nothing, you upgrade nothing, just write (literally, on paper using a pen, on to SOP forms which also never change) a daily ream of logs and the renewals keep coming. 2 or 3 FDA folks roll up, show them you've done the required, let them walk around and flip through a few binders of logs, let them feed the monkey a bag of [very clean] peanuts, get the other monkey CEO to take them out for lunch - that's it.
after many stupid answers the nice folks at Technet said the only solution is to reinstall my signature. What a surprise!
lopatir wrote:
your system runs on RSTS/E
On a side note, back in the dawn of time, my work responsibility was to configure and run UETP1 on RSTS/E machines as final QA. Since the system disk would get wiped, the System Name, which is printed in the header of every message, was of no real import. Until of course one enterprising QA person realized the length of that field could be completely filled with the text : PARITY ERROR Hilarity followed :-) as the tech vainly tried to find the problem. 1User Environment Test Package
But I never wave bye bye
-
You want the form for a change request? Do you have the form for approval to receive a change request? You'd first need to get the form for the form for approval, of course. Why, it's forms all the way down!
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Reminds me of something I learned the hard way in my first job.
NEVER use the last requisition in the book for anything other than another requisition book!
Cheers, Peter
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
