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.
Recently I've been looking at radiation meters. They all seem to begin by describing different common types of radiation -- Alpha, Beta, Gamma, X-rays -- yet when you read the specifications, none detect Alpha and few detect Beta. (I need an Alpha detector.)
I imagine someone might also begin a car ad with something along the lines of "Mercedes Benz traces it's roots to 1883 and has been synonymous with high-quality European automobiles for more than a century, this Yugo is also a European automobile..."
Just as an aside - I used to purchase the Kodak Easy-Share cameras in the (what is now called) super telephoto class - really bridges between SLR's and point-an-shoot. When Kodak was going bankrupt I upgraded to the latest and greatest, a Z990 (30x Schneider lens that is just amazing). I got it for $150, new, just after they announced bankruptcy and stores were dumping inventory. Not long after, you would have to pay full list $300 to get one in new condition, sometimes more. One other thing I loved about this series is that it used four AA batteries. Easy to keep spares; cheap, too, even for the best NiMH slow discharge. I've gotten over 200 shots one set and it wasn't used up. Alas, I dwell,
Finally, the point:
Well - they were in bad financial shape and licensed their name to some China based company and now called PixPro. They are now, basically, junk.
I think quality sucks because we still buy the things.
For example, these cheap 2 in 1 Chopper from Kmart[^], they're actually terrible quality, but they're so useful that I find my self recommending to people that they buy a few, because they don't last much longer than 6 months before the plastic starts to break down and fall apart.
In conclusion, I'm definitely a part of the problem.
My primary example of the absolute loss of quality control is HDD's. Especially for more than 1TB, they often arrive inoperable (making DOA a common term in computer parlance). Or, they start making noise and crash in a week or so. This is happening a lot. The reason is rather simple - it is cheaper to skip QC and just replace the drive than to actually make sure they're working. QC is now your job and not only aren't you paid but often you need to pay shipping for the return of the junk.
Prices for HDD's are amazingly low per TB - mainly you are paying for rest of the hardware, except the very latest models.
And, consider trusting your data to an unreliable HDD. They effort in transferring data, possible setup time if it's a bootable drive. Loss of data when it crashes. It is from there that I coined my phrase: "An unreliable Hard Drive is overpriced at free".
I am currently in the process of setting up Azure DevOps for the first time, which will be self hosted on one of our dev servers. (I have never used TFS before either... well, aside from a failed attempt in setting it up a few years back).
Any of you lot have any experience with it? Particular any obvious "gotchas" that I am likely to hit that you could pre-warn me about?
Currently we use Mercurial for source code, so that will be a conversion job over to Git at some point.
Thanks in advance for any advice. I also welcome your input if you just want to laugh at my impending doom.
If project and team is small and server must be in-house, you can consider Azure DevOps Express. Free for 5 member teams and runs on single machine. However, hosted Azure DevOps would be my choice. When you consider hardware, configuration, maintenance, updates , backups , TCO is cheap.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Ok so I've registered my net core API and a client app with Azure AD, I now have lot's of keys and ids that I need to access my API from the client. All is working as expected. I can't help thinking I've created another problem. I need to put these keys somewhere accessible but secure. Any recommendations?
"We can't stop here - this is bat country" - Hunter S Thompson - RIP
Last Visit: 31-Dec-99 18:00 Last Update: 18-Jun-21 9:00