|
Abhinav S wrote: So Yoda does get angry.
No no no!
"Angry Yoda does get."
FTFY 
"State acheived after eating too many chocolate-covered coconut bars - bountiful"
Chris C-B
|
|
|
|
|
Pete O'Hanlon wrote: "Pretend you're a principal consultant at a consulting firm and you want to demonstrate the value and sophistication that your firm can bring to the table. Please make a data access layer proposal that would help support this goal."
Ali's Thinking
"bring to the table" ... ... maybe food or a meal?
"data" ... ... ... ... that's tricky, they must mean the menu?
"value" ... ... ... ... well to bring value I guess I need to include diamonds somewhere and maybe gold
"sophistication" ... ... I must include a classy drink like Cinzano or Babycham!
Okay, my answer is,
"I will bring to the table a gold and diamond encrusted menu, listing a choice of sweet sickly alcoholic drinks."
I think that should get me an A++! 
"State acheived after eating too many chocolate-covered coconut bars - bountiful"
Chris C-B
|
|
|
|
|
|
I found this exact text on another site - the person who posted it has an account which is 7 years old. You'd have thought he/she'd be beyond this drivel by now.
My guess is it's an interview/job app question, though most principal consultants (in one of the "big" firms) I've worked with have degrees in an "-ology" in anything other than technology and could barely tie their shoelaces together from an IT point of view.
Alberto Brandolini: The amount of energy necessary to refute bullshit is an order of magnitude bigger than to produce it.
|
|
|
|
|
I can only find it on one other site - posted at about the same time as the question was posted here.
|
|
|
|
|
I'll pretend you're an ignorant school child that is not only to lazy to do the assignment yourself but also so uncreative to even put the question in your own words. You have a long road ahead of you.
As I grow older I've found that pleasing everyone is impossible but pissing everyone off is a piece of cake.
|
|
|
|
|
|
I'm organising some documents and I've realised I have a new pet peeve: putting "Final" in a document name to indicate that it's the final version.
In itself this isn't awful. What's awful is:
document.docx
document - final.docx
document - final - DG-comments.docx
document - FINAL.docx
So which one's the final one?
This is why documents need source control...
[Edit: Just found:" Copy of Copy of document FINAL.docx". We have a winner!]
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: So which one's the final one?
The one that's left when I've finished with the delete key...
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Precisely!
cheers
Chris Maunder
|
|
|
|
|
"Final?! Did you say 'final'? Nothing is final until we decide it is!"
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
Put them into the repository, you'll get versioning for free.
|
|
|
|
|
Before my PM fell in love with Sharepoint (and to be fair, it is easier for non-technical users) we versioned all our office/etc documents with the same tool we used for source control. Diffing was basically a no-go at that time; but we did have proper version history.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
We went through the same thing - but if you save them as HTML documents (which I know has downsides) then you can diff.
|
|
|
|
|
If you accept all changes first you can Diff in Word (since 2007 in a side by side multi-pane view like many code diff tools). The main limitation there (from an integration standpoint at least) is that except for delivered versions of documents we almost always have tracked changes in ours. The frustrating part is that Word keeps the date/time of each change, but has no option to only show changes newer than a specific date. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Also - anyone emailing around a doc to multiple people for their updates - thus we have 20 new branches of "Business Plan (Draft) v1.2.docx" to merge back together...
|
|
|
|
|
Haha... I used to have to run around fetching signatures on pointless documents while the more senior programmers were implementing whatever they wanted.
I would sort my list of signers by their job title (most important people last). I would fetch signatures from configuration management, software test, test engineering, QA (yes, we had 3 versions of testing), document control, the engineering head, the vp of ... blah blah blah.
Anyway, all these people were above me. So the lower ones, who gave me revisions up front... I would implement the revision, bring it back, and then head to the next. Wouldn't you know it, by the time I get to the top, the lower guy is scowling at me because he has to sign it for the umpteenth time, and the only revisions he cared about (his) are gone. I say I'm just doing my job and if he don't sign I'll have to go to the higher ups. 
I didn't have many friends there. 
|
|
|
|
|
You're doing it wrong - the only signature that counts is the client's!
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
No version control problems - give them a Wiki.
Let them fight it out amongst themselves.
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Do you really want to let a marketing schmuck edit a wiki?
Software Zen: delete this;
|
|
|
|
|
Give them credit, if a marketing schmuck can run the most powerful tech company in the world into the ground there's no limit to what they can do!
Back on topic, make a shared Google doc and let the drones fight amongst themselves.
|
|
|
|
|
Well, I know this much ~
The final é in finalé is the finalé of finalé.
|
|
|
|
|
At my current work place, we have databases named like below on the same instance of SQL Server
1. Database1
2. Database1 New
3. Database1 Current
4. Database1 Recent
5. Database1 Latest
6. Database1 Real
For some reason, no one wants to delete any of them.
|
|
|
|
|
I make them put their initial after the database version, then I know who the owner is. I'm also in the habit of taking DB off line on the dev and UAT servers, if no one screams in a month I can delete them.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Almost as bad as putting "new" to indicate that this is a new version.
modified 20-Oct-19 21:02pm.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
