This is the case in general with event code -- spooky action at a distance. Easy to write, easy to understand if you don't think too hard, but a PITA if it breaks and you have to debug it. That's the very definition of spaghetti code that I've come to over the years, so yeah, binding code is spaghetti.
5G -- more lies faster.
harvyk0 wrote:
And I'd probably have a great deal of difficulty getting a (non-self-signed) certificate calling myself "Microsoft Software"
Absolutely you would, otherwise the concept of code signing would be worthless. Getting that certificate requires that the CA verify you are who you say you are.
harvyk0 wrote:
Whilst yes, I can get a certificate and release Trojans, it's one more step I would need to do to look "trustworthy".
Not just one more step, they make it hard for you to avoid giving your real identity to them before getting the signing certificate. If you intentionally sign bad stuff, they know where you live. Also, they can revoke your signing authority, so everything you've ever signed with that certificate is no longer valid -- users who try to install it get a certificate-revoked error -- and you can't sign anything new with it either. It takes time for revocations to filter through the system, and they are very few and far between, but they do happen.
5G -- more lies faster.
David O'Neil wrote:
have you ever used
protectedandprivateinheritance?
All the time. Public is for the public parts of the interface to the class. The others are for the internal implementation details -- the parts we want to be free to rewrite and refactor without consequence. In my experience, a bigger public interface to a class means tighter coupling over time since other developers don't have to think very carefully about how their usage tightens the coupling, so they don't and just go ahead and use it.
5G -- more lies faster.
Jeremy Falcon wrote:
Does anyone else think that's a fundamentally broken way to find a good programmer?
Yes, its fundamentally broken, but it cuts both ways. If they reject you because you didn't give the answer that they found by googling, instead assessing the answer you did give, do you really want to work with that team? If its some HR flunkie that filtering you out, what caliber of engineer are they like to have working for that company? If if the actual devs, how savvy must they be if they can't see past a googled programming problem answer? In either case, do you really want to be working with those developers? Of course, this only matters if you already have a paying job.
5G -- more lies faster.
It isn't always about holding up in court. It is sometimes about whose pockets run dry first. Even if you sue them for legal costs (and win), you still have to pay your legal costs along the way to get to the court decision where you get reimbursed. Stryder did the right thing by not signing.
I live in Oregon, and I'm an engineer.
At a guess, I'd say it's likely that the video cards of the two systems don't implement the same features. When I used to do video processing on Windows, we did a lot with DirectX and found every system we tried, our software on needed some tweak to our video processing. The video in some systems didn't implement features, others did, but using feature B was faster than feature A on it (on most other systems, A was faster than B), and others implemented a feature, but it just didn't work right. Honestly, I don't know how games worked at all. This was about 10 years ago.. a lot has probably changed. However, it may be that your old software is using features that some systems still implement, or implement well, and others dropped.
I live in Oregon, and I'm an engineer.
rnbergren wrote:
Also, I have been thru worse natural disasters. What is the worst one you have been thru? I know mine will not compare to others.
Once it rained for forty days and forty nights straight here... well, not really rain so much as drizzled.. and it does that every few years anyway.. darn, I got nothin.. nothing to see here, move along. I hear you on the office setup thing. I've been in the office a few times on and off and I'm still on the fence of which I like better. The setup is pretty similar, but I miss seeing coworkers in person, but I like not having to commute (way more free time.. to get the house ready for that forty days and nights of rain, of course.. it's been a few years so we're due)
I live in Oregon, and I'm an engineer.
I am constantly reminded of one of my favorites comics[^] by Sandra and Woo about Windows 10 updates.
I live in Oregon, and I'm an engineer.
No, there will not be any such software. In short, your friend cannot return to their original 128k quality files from what they have now. The process you're referring to is called transcoding. Whenever you transcode across bitrates of a lossy codec, you lose information because the quantitization of the samples is different. So, quality was lost in the 128k -> 320k trancoding. More quality will be lost doing another transcoding from 320k -> 128k. Maybe your friend is now at a financial point in their life where they can afford to replace the mangled files?
I live in Oregon, and I'm an engineer.
Eddy Vluggen wrote:
.. this won't work for most of the kids, and he's not going to take responsibility for any failures
So.. then.. just like normal public school in the US.
I live in Oregon, and I'm an engineer.
Vinge's works are some of my favorites, with that series in particular being some of my favorites among his work. That particular series is really interesting for the aliens.. which are really alien.. but not. We're almost to the hexapodia moment.
I live in Oregon, and I'm an engineer.
Good UPSs don't fail with sparks that could start a fire. I've used a number of them over the years (APC, Belkin), and the only thing that seems to fail are the batteries, which wear out and need replacing from time to time. As for surge protectors, there are two kinds, the MOS ones, where the MOS part takes the hit, burning it out a little more each time, and series mode ones, which use a large inductor and don't wear out (they're also hard to find, heavy as snot, and expensive). BTW, a lot of shills copy their reviews onto many sites, so just because you see it on multiple sites, doesn't mean it isn't from a shill, nor even that it's true. It's not called the 'net of a million lies' for nothing :)
I live in Oregon, and I'm an engineer.
Doesn't matter what the code is, or what it runs on, there's still a hardware cost (physical electronic circuitry) and electricity cost to running code. You simply cannot escape thermodynamics.
I live in Oregon, and I'm an engineer.
Sorry to rain on your idea, but it's called grid computing, and has been around for at least 30 years now. Use of a VM is a tweak to the idea, but doesn't address all of the concerns. One that's missing off your list, is who pays for the hardware and electricity to run your VM? Most people want some benefit to themselves for letting you use their hardware. Doesn't mean it's impossible, for example people donate their resources to things like SETI and protein folding. However, when they get nothing from it, they don't like it (e.g. the bitcoin mining browser exploits).
I live in Oregon, and I'm an engineer.
I've found that most problems that are interesting to non-programmers are way out of reach of a beginning programmer. Instead, maybe find out what she wants to do with her new skills, then teach her pieces along that path. I'd actually suggest taking one of the video courses for learning the programming stuff with her. You could come up with the course material and organize it into a meaningful sequence yourself, but that's a lot of work for one student, and you're limited to the languages and tools that you know. I've found that writing games has been one of the most motivating things to engage new programming students with. It is amazing how little code is needed to make an interesting game that sparks a student's interest. The simplest was the one-if-statement wumpus "game" we used in our Java class as our first-program intro to teach the students how to use the Java compiler.
I live in Oregon, and I'm an engineer.
Kornfeld Eliyahu Peter wrote:
Tomb Raider wasn't that much of a game
Maybe not, but the time I got Laura stuck to a rock wall 20 ft. in the air by her...um.. assets.. was priceless. They just don't make entertainment like that any more.
I live in Oregon, and I'm an engineer.
Nothing. I'd already made all the changes I needed so I could work remotely because of jury duty.. and I looted about a half dozen monitors from the e-waste bin at work over the years, so I'm good on that front too :) The only thing I might yet do, is to go in so I can reboot into BIOS and enable Wake-on-LAN on the desktop box. As it is, I'm one power outage away from dead in the water.
I live in Oregon, and I'm an engineer.
Chris C-B wrote:
I am not sure of the USB2 capabilities - is it a maximum of 192 kbps as I have heard mentioned?
Try both and go with whichever sounds better to you. The reality though, is since you're going into the stereo with analog through RCA cables & connectors, it really won't matter which you do.
I live in Oregon, and I'm an engineer.
I don't get the hate on python. It's a typical 1980s language. It is what it is because it's a product of the time it was invented in. You can't apply today's values to a language whose syntax was designed almost 40 years ago and expect it to hold up. Yeah, I know C was around back then, and is the dominant syntax today, but back then, C didn't have much penetration and Fortran was king. Python is kind of an ugly stepchild of Fortran, and shows it.
I live in Oregon, and I'm an engineer.
There's non-biological ways to produce oxygen. A few years back I got interested in recycling of CO2 back to O2, and there's multiple paths to do that. There's also other ways to get O2, like by disassociating water. However, as raddevus pointed out about the biosphere project, making a long term viable environment is hard. The more closed, the harder.
I live in Oregon, and I'm an engineer.