Am I doing non-UI threading right?
-
@Arantor Everything that's worth knowing, and what I don't know, must therefore be a waste of time
:tro:But ok, I see now what you mean.
@dcon said in Am I doing non-UI threading right?:
Don't forget, they're typically the boss's insert any family relationship too.
Or from the same college class
... 
-
@Applied-Mediocrity said in Am I doing non-UI threading right?:
@dcon said in Am I doing non-UI threading right?:
Don't forget, they're typically the boss's insert any
familyrelationship too.Or from the same college class
... Oh right. Fixed (here, not in the original)
-
@dkf said in Am I doing non-UI threading right?:
@Zenith said in Am I doing non-UI threading right?:
So no I don't want their grubby mitts anywhere near code too brillant for their microbrains.
I remember a friend complaining about that. His solution was to make the code even more brilliant, such that you'd need an advanced degree in mathematics to understand what it did and why it was so screaming fast. I know it involved moving something to do with non-standard fourier transforms onto a GPU so that they could be used to do automatic image registration in real time despite the distortions in the equipment acquiring the images, but it definitely was above my knowledge level...
The upshot was his code caused everyone who interacted with it to go "How the hell does that even work?!"
Wavelets man
-
@Captain said in Am I doing non-UI threading right?:
@dkf said in Am I doing non-UI threading right?:
@Zenith said in Am I doing non-UI threading right?:
So no I don't want their grubby mitts anywhere near code too brillant for their microbrains.
I remember a friend complaining about that. His solution was to make the code even more brilliant, such that you'd need an advanced degree in mathematics to understand what it did and why it was so screaming fast. I know it involved moving something to do with non-standard fourier transforms onto a GPU so that they could be used to do automatic image registration in real time despite the distortions in the equipment acquiring the images, but it definitely was above my knowledge level...
The upshot was his code caused everyone who interacted with it to go "How the hell does that even work?!"
Wavelets man
So name your FFT and related something halfway sensical.
Oh, okay - this was the same thing? I blew out stack on the first read. That's pretty weird...
-
@Arantor said in Am I doing non-UI threading right?:
@Applied-Mediocrity that's the thing - this kind are always self taught. They just hit a point where they figure they know some definition of 'everything' and stop learning, to the point where they glass-ceiling themselves.
I've yet to meet anyone who studied CS at a university fall into the same trap. They fall into other, different traps.
Just get to know my cow-orkers.
-
@Zenith said in Am I doing non-UI threading right?:
code too brillant for their microbrains
Decades ago, I had to deal with such a person. Honestly, he was a genius, only person I ever met who could hand write Pentium Assembler and keep track of the pipelines and caches in his head.... but oh so dangerous. My role at the company was to find the smallest possible box that he could be put in where his talents provided value and keep him away from the rest of the code base to protect the teams.
Write code for the reader. If you are willing to hire and pay someone (even at H1B levels) then it is a failure to have code that they can not understand.
-
@TheCPUWizard Writing code an H1B can understand is like writing a book a dog can read.
-
@Zenith Scratch-and-sniff? Makes sense.
-
So in case anybody wanted to know, apparently you can detect context (website vs application) with
System.Web.Hosting.HostedEnvironment.IsHosted. That cleared up alot of problems with access. It's also old enough (dating back to .NET 2.0) that I should've known better
-
@Zenith Threads are such assholes. They also don't seem to carry over user handles. So the server has been running as a service account, impersonating the browser user, right up to the point there it creates a thread and forgets that it's not the service account. Passing a stupid
System.Security.Principal.WindowsIdentityhandle into the thread resolved that but come on.
-
@Zenith said in Am I doing non-UI threading right?:
@Zenith Threads are such assholes. They also don't seem to carry over user handles. So the server has been running as a service account, impersonating the browser user, right up to the point there it creates a thread and forgets that it's not the service account. Passing a stupid
System.Security.Principal.WindowsIdentityhandle into the thread resolved that but come on.Just have your Thread factory be able to selectively copy context objects from the caller, as write-thru or read-only as indicated, and be able to dispose them. Yeesh. It's not sprocket finance.
-
@Gribnit You're sprocket finance
-
@Zenith said in Am I doing non-UI threading right?:
@Gribnit You're sprocket finance
Sprockets aren't even that expensive.
-
@dkf said in Am I doing non-UI threading right?:
@Zenith said in Am I doing non-UI threading right?:
@Gribnit You're sprocket finance
Sprockets aren't even that expensive.That's what makes financing them so complicated. It's all margins, and the margins are so small. So it's very difficult to account for them without blowing your margins on accounting.
