|
/ravi
|
|
|
|
|
Beavers are no laughing matter. They'll build dams wherever they damned well please, causing water streams to get rerouted and causing floods. Destroy a dam and they'll be back at it the next day. And since it's illegal to kill them in Canada, you have to get so-called experts involved.
I witnessed that firsthand 2+ decades ago. I can just imagine the stupid paperwork nowadays.
|
|
|
|
|
And we're just trying to re-introduce them here in the UK...
|
|
|
|
|
Ah man, this is such a rooster-up!
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
|
It could pretty easily happen here in Michigan too, but I think squirrel-based outages are more common.
|
|
|
|
|
Quit encasing cables in yummy plastics.
|
|
|
|
|
A question on bubble sort got 7 (seven!) solutions at QA .
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
I was was looking for cool 3 line (or less) STL solution from you.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Unfortunately C++ was not allowed: I was was looking for a cool metaprogramming solution by the CodeWitch.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
|
We are solving home work problems now, because it's easier to learn from the final solution.
Problem is if they're to lazy to do the assignment they ain't going to go through the code to figure it out unless it doesn't work, then they'll just come back here and ask why it doesn't work.
The most expensive tool is a cheap tool. Gareth Branwyn
JaxCoder.com
|
|
|
|
|
And even if it does work, and they pass their course, they'll get an interview question they don't understand and expect us to do it for them as well.
And then, when they get a job they can't do, they'll expect us to do their actual work for them too.
Some people seem to think QA is a free outsourcing tool.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: Some people seem to think QA is a free outsourcing tool.
Well if people keep giving them the code instead of forcing them to do the work themselves that's exactly what it is.
The most expensive tool is a cheap tool. Gareth Branwyn
JaxCoder.com
|
|
|
|
|
CPallini wrote: A question on bubble sort got 7 (seven!) solutions at QA.
Damn low hanging fruit. I can't even get 1 satisfactory answer for a simple question I asked last week! I'm not complaining...just ranting as it fades into oblivion.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
Maybe you're the only one on Earth using OData[^], whatever that is.
|
|
|
|
|
|
repeat question for those who may have missed it
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Not all responses are solutions.
|
|
|
|
|
Did anyone suggest LINQ? :snicker:
Software Zen: delete this;
|
|
|
|
|
I’ve been doing architecture and development in Azure a little over three years, and at the on-premise enterprise-level for nearly 40 years.
The last couple of projects I designed in Azure, I went with PaaS instead of IaaS. No VMs, no load balancers, no containers, and no Kubernetes.
Instead, how I configured the app services (scale up or scale out, as one example) took care of scalability, multiple regions, etc. replaced the older IaaS functionality listed in the 2nd paragraph.
This greatly simplifies the design, makes support less complicated, and puts the responsibility for scalability and up-time on MS.
I would like to read your opinions on the benefits/drawbacks to shifting that responsibility from an IaaS oriented design to a PaaS oriented design.
Thanks in advance.
|
|
|
|
|
Nope, not needed.
VMs are just for legacy applications that can't run any other way.
Containers allow you to spin up the same services across multiple cloud vendors, on premise, and developer boxes relative easy. So specifically if support for multiple cloud vendors or on-prem installation is important, consider using them. They also make it easier to spin up "random services" as part of your application without relying on the cloud provider having a PaaS version of that service - or them breaking it by upgrading it or other entertaining things that happens in the cloud. If you do not need any of this go as server-less as possible (or as I used to call it before the term was invented: shut-up-and-run-my-code... and I still believe this is the better name).
|
|
|
|
|
I just picked up on "shifting responsibilities"; never an easy task; particularly if someone doesn't wanted to get shifted.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
To answer my own question - unifying the desktop appearance for all devices? Thoughts?
So, I have a new laptop, and it upgraded to Windows 11. Now most of you who recall my rants on Microsoft automatically rebooting machines understand that I consider this abhorrent behavior at best. So I'm trying to work with it, get comfortable etc. But it occurs to me - I work in the world of embedded devices and HMI development. If I or my team or customer changed the HMI on a product like Microsoft does, we'd be laughed out of the factory. You just don't do it.
What the elephant is MS hoping to gain but elephanting around with the desktop like this?
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
I think it's a question of whether MSFT's UI designers have greater push for constantly dicking with the UI as opposed to their users having greater pushback against it. And MSFT doesn't interact with users all that much, so those who think they can make the UI "better" (or justify their jobs, to be cynical) hold sway.
|
|
|
|