The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
constantly ignores industry standard UI design principles
Are the design principles specific to your industry or design in general? I ask because if your program's UI is 20 years old, maybe updating things to be easier to use isn't a bad thing.
I agree with Sander that you should try talking with the BA. Explain why the design needs to be consistent and if there are industry specific standards to follow, those as well. At the same time, be open to suggestions that might improve usage. Maybe some of the "new and better" ideas might improve things for the end users... would it be an improvement to get rid of wasted clicks even if they are 'standard'?
That said, a lot of the CompSci people I've worked with (myself included) are terrible at UI. We don't always think about how things should work the same as 'normal' people do. It wasn't until I spent a few years with actual trained usability experts that I started to change my approach to something akin to 'If you have to think about it then it probably isn't a good UI.'
I don't have much advice other than don't hire people without industry experience - something I learned in the .com boom days.
Academia doesn't teach proper software development, and because academia is sort of antithetical in nature to putting practice over theory it probably never will.
People get lost in the Right Way(TM) to design things that often isn't the right way at all when the real world collides with it, but they get stuck in this idea of "it must fit the model" and i've found that the higher the degree in Compsci the more likely this sort of thing comes from them.
I'm sorry to say but uni as much as it educates, puts blinders on people, and those blinders only get undone through actual experience.
If you want to save this hire, be patient with them, correct them, and hope to hell they are responsive to criticism and can update their work accordingly.
Otherwise, it's time to look for a different UI person. Just my $0.02
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?"
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.
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!
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.
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.
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 !!
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?
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.
, 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.