|
I couldn't agree more. Just yesterday I was looking at some code by our newest hire and I had to correct several things they did because that was the way they were taught in school. I had to tell them that was fine for small, assignment projects but for larger scale, real world projects those are definitely not the right ways to things.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
A company BA you're likely stuck with. A contractor (you didn't hire) you can shuffle aside.
The whole MVVM mentality totally divorces the (BA's) view from the physical and logical data models and any performance considerations.
Share your models. If you don't have any, start making them (Visio). Then design and code.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it.
― Confucian Analects: Rules of Confucius about his food
modified 23-Jan-20 11:00am.
|
|
|
|
|
Matt Bond wrote: I have 2 business analysts (BA's)
Not advice, but a reminder that you can't spell "analyst" without "anal"...
|
|
|
|
|
I really hate to say this, but what you need is to have regular meetings about design.
Sometimes, meetings do actually serve a good purpose.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Write a design guide, put a "printed" date on each page of [x] years before the new BA started, give it to the dog to sleep on for a few nights, then refer to it whenever he gives you work. Just point out it's non-conformant. When he asks why no-one's produced it before, just say it's so internalised that it's second nature to everyone. But must be adhered to.
|
|
|
|
|
Find your cousin James, and ask him to terminate the 2nd BA with extreme prejudice.
Software Zen: delete this;
|
|
|
|
|
I am trying to use Robocopy switches.
I have a drive that is mapped as \\sr\archive
I have a local drive s:\AZ\A
this code is the normal command :
Robocopy \\sr\archive s:\AZ\A /MIR /FFT /Z /XA:H /W:5
Except I need to have a way to keep things up to date.
Do I put something in Task Scheduler, or can I use the /mot:5
switch and will it just keep Robocopy in memory that way?
how can I robocopy 7 paths which have a file name over 300 character ?
|
|
|
|
|
If you remove all the folders on the source it'll not only work, but be much faster too.
better yet, try FORMAT - can't think of it right now but there's a switch that'll make it work.
after many otherwise intelligent sounding suggestions that achieved nothing the nice folks at Technet said the only solution was to low level format my hard disk then reinstall my signature. Sadly, this still didn't fix the issue!
|
|
|
|
|
"/C" always did it for me...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
I strongly suggest that you look up exactly what the FORMAT command does, followed by this link: Cambridge English Dictionary[^]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Ask the people who created it: robocopy | Microsoft Docs[^] and certainly don't ask it where the page expressly asks you not to, in red writing ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I have always used xcopy with the /d for anything with a newer date than the target.
xcopy src: tar: /c/h/e/r/y/d
YMMV Some like Robocopy, I have found it to not have something I want. I have used it in some instances where xcopy just won't work though.
To err is human to really mess up you need a computer
|
|
|
|
|
rnbergren wrote: I have always used xcopy with the /d for anything with a newer date than the target.
If that's the goal, then this is how I've always used robocopy:
robocopy source target /MIR /R:0
Even though my backup set is measured in terabytes, the above only copies what's actually changed at the source (and deletes what's been removed), and only takes a few minutes. That's been reliable for me and that's what I've been using for nearly a decade.
|
|
|
|
|
thanks dandy72, it works and about the longpath name ?
|
|
|
|
|
Good question.
Long path names are either handled correctly already by robocopy, or I've just been very lucky and have never encountered them. Must be the first one, because when it comes to this sort of thing, luck is rarely on my side.
Quick Google search says robocopy supports long paths.
|
|
|
|
|
I saw this link before posting and it didn't help me with a long path over 300 C, so I am posting here
..the program that I mentioned before solved the problem, but can you apply the solution in the link you shared? maybe I have a technical problem which prevents me from applying it !!
|
|
|
|
|
SenioritaNaomi wrote: can you apply the solution in the link you shared?
I'm not sure I understand. The only link I provided was to a StackExchange discussion that mentions robocopy should support long paths out of the box, and before that, a sample of how I use the command myself.
This article shows various ways to enable NTFS long paths in Windows 10, but looking at the registry on two of my systems (one of which is my NAS, which is what I use robocopy against), it looks like I don't have it explicitly enabled...so I'm not sure if it's necessary. OTOH, my "NAS" is running Windows 7, so it can't be a "recent version of Windows 10"-only feature.
I realize this will come across as a lame suggestion, but is there any chance you can organize your folder structure so it doesn't run so deep? My NAS is essentially my archive of all my documents, music, source code, CD/DVD ISOs, installers, etc...and--unless robocopy is failing silently--I've somehow managed to avoid running into the path limit, and this is the "live archive" I've been using for 10+ years. In fact it's unlikely to be the case, because now that I think of it, even the last time I moved my entire set of files from an 8TB drive to a 10TB drive, I compared the total amount of data on the original disk with the target, and I got a match (down to the byte), so I know nothing got left behind because the path was too long.
Another thought (again, rather lame): Is your drive formatted as NTFS?
[Edit]
I see in another response in this thread that you've found a solution using another tool - good to know. I honestly don't know at this point what to suggest might be wrong with robocopy.
|
|
|
|
|
yes, I found a solution to my problem, A GUI tool called gs richcopy 360 , and thanks for you for trying to help me, but what does this comment mean "what to suggest might be wrong with robocopy." ? 
|
|
|
|
|
SenioritaNaomi wrote: , but what does this comment mean "what to suggest might be wrong with robocopy." ?
I simply meant to say I don't know why robocopy isn't working in the expected way in your case. Because if the discussion at the link I had provided is accurate, then robocopy should already support long paths and it should "just work". But clearly it doesn't, at least in your particular situation.
|
|
|
|
|
/MOT:5 will keep it running and it will check for changes every 5 minutes and copy any changes to the destination.
/MON:5 will keep it running and it will check for "n" or more changes and will copy any changes when "n"is reached.
Either switch will keep robocopy running until you Ctrl+C to end it.
and for the problem of long path name , it can be solved easily by robocopy alternatives like securecopy quest and gsrichcopy360 .
|
|
|
|
|
Thanks ELENASTEFAN , it works, and I m doing good with the program you mentioned gsrichcopy 360 for the problem of a long pathname and also it solves the issue of copying the updated files only.
|
|
|
|
|
My optimizing compiler for regex works. I think. I still have lots of testing to do.
What a bear that was. It took me days, even.
I'll have to produce an article, since despite this being for mere regex, it is actually a flippin' optimizing compiler which is pretty cool.
My inner bit twiddler is glowing right now.
Update: Aaand perf testing says i'm not doing near enough yet.
Real programmers use butterflies
modified 23-Jan-20 9:00am.
|
|
|
|
|
honey the codewitch wrote: Aaand perf testing says i'm not doing near enough yet.
Perf testing will always say that. 
|
|
|
|
|
Yeah, at least it's forcing me to write statistics gathering code for it though.
This is turning out to be quite the little monster. I'm surprised at how compact the code is given everything it does at this point. It has stayed pretty small.
Real programmers use butterflies
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
