The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Hell, I keep having to open up IE because Firefox won't let me go to sites that have "bad" certificates, and doesn't even give me the option of going anyway. (We're not allowed to loosen up security here, but at least IE will just warn me before letting me go.)
We won't sit down. We won't shut up. We won't go quietly away.
No, it's their current security settings. It's the default ones.
Yeah - I can certainly wade into the security settings, work out which zone I want to fiddle with, try and work out exactly what domain I need to whitelist (extra fun because downloads often come from a subdomain and you can't wildcard add domains) and then iterate through all of that.
Or I can just use a browser that lets me get some work done.
...but the garbage I've had to look into and fix, well, it's just amazing.
Lack of abstraction (makes testing a total PITA)
Lack of encapsulation (would be nice to be able to load up the configuration values without hitting a serer that I don't connect to in testing)
Absolutely convoluted code for getting something to run on a separate thread (even before Task.Run this was basically a 5 liner, not the 100+ lines of drivel I'm wading through.)
How many times do I need to xpath the config file to get the same value in the same loop???
Let's instantiate variables and never use them!
Let's add debugging that inspects the .NET stack. And not disable it in a release build.
Let's load an XSLT transform from a file every time we need to transform something.
And maybe XSLT isn't the most efficient?
And let's put in comments about "not too pricey performance-wise" for stupid-arsed things and totally ignore the glaring inefficiencies elsewhere.
Let's use bool? as a 3 state variable instead of a readable enum.
And the list goes on.
I am getting sorely disappointed in the code I've had to work with. I have yet to see something decently implemented in this job. It's pretty clear to me that if I were the Trump of the software engineering world, I would cull 90% of them and relegate them to captaining garbage scows.
There is a whole lot between knowing what Marc knows and not knowing a damn thing about programming. Unfortunately, it seems people who know nothing about programming still end up programming somehow
How would you react if someone built your house, you pay good money, and your front door could always be opened from the outside (even though it seems to have a lock)? You'd be furious, sue your contractor and find a new door. You'd probably not trust the rest of the house anymore either (check your walls, foundation, windows, etc.). I think that's roughly the equivalent of SQL injection. Yet only one is common practice