I've used rr very sucessfully for reverse engineering a large code base using a break on variable change combined with reverse-continue. Took the time to extract critical logic way down.
I'm interested if anyone has pulled the same thing with eight sleep. Not having access to control my bed's temperature because my internet is out bothers me deeply.
A variant on that I say on one of these is "Do the dumb thing" thing to find the right abstraction. I've seen so mucb code that didn't need to be written if someone had just done the dumb thing. On the flip side, I've also seen so much code that could be so much simpler if after writing the dumb solution, they went back and figured out a better one.
I guess the takeaway is: Prototype.
I followed this. And would recommend vkguide.dev for several reasons. The code here is "clean code" pointlessly abstract void fin(void) so each call is a mystery as to what it does. I came away from it asking, why do I do these things?
My experience with hiring is it's better to error on the side of not hiring. If you make a bad choice, unless it's a flagrant fraud, you're going to spend a couple of months trying to get them to be productive. That's way more time then doing a couple more interview. And firing is risky from a legal standpoint as well.
We hired a guy like that. Clear deficiency in hiring process. I wasn't in management, but letting the mistake fester won't make it better.
Additionally, if someone is that "senior" and good at interviewing, but not at thier job, it's unlikely they will come up to speed at a reasoble rate. Thier primary skill is interviewing, they might not be able to learn the skills they need to succeed.
Let him go!
Whats the use case for this? What computing platform doesn't have a text editor, but does have a webbrowser? Or are we just conditioned to use a web browser for everything?
My goto has become "You're a C++ expert." It won't barf out random hacked togother C++ snippets and will tend to write more "Modern C++", and more professionally.
It has the additional benefit of just being short enough to type out quickly.
Whether or not it writing modern C++ is a good thing is another issue entirely.
There needs to be law or case law so that the manufacturers are proportionally responsible for harm the driver assistance features cause. It's the only way that it'll affect their bottom line enough for them to take safely as seriously as they should.
If you haven't seen "What About Bunny" on YouTube, I highly recommend it. The dog has learned to use buttons to communicate her thoughts quite effectively. My favorite is "Why bunny dog?"
That's a new breed I could support. Just throw together a bunch of different breeds of smart dogs. They'll be much mror healthy than most breeds of dog.
I've found OOP can increase coupling. I actually have this problem at work.
Say I have class A and B. I could write `int x = A:FunctionOfAandB(B b)`, but in this case. So now A depends on B.
It would be much preferable to have free function of A and B. A and B are no longer dependent on each other, just the function to compute the result dependent on A and B.
IMO: The real thing of value OOP provides is calling with object.method. A lot of OOP code looks like `void obj.mutate()`. If you pulled that to what's really happening in "procedural" syntax, `mutate(obj)`, that exposes it for the bad code it is.
>One thing that might help is forbidding abstracts and conclusion sections in papers published in journals, which might cut down on some of the misunderstandings and make it harder to pass off a paper as support for a claim.
I wouldn't go this far, bstracts are needed to determine if the paper is of interest to what you're researching.
Perhaps a more modest refinement that could work would be to forbid conclusions in abstracts.
I think the big takeaway if something like this happens in the future is half float ain't a miesner effect. Makes me increasing skeptical of Taj Quantums claim to a super conductor.
https://tajquantum.com/art-t2sc/
Perhaps the support period should be sold as a "warranty period". People understand limited warranty periods on cars and dishwashers, so it's a known model.
Editor support can really help with transitioning.
I write C++, Matlab, python, and bash all with regilarity, and eventually your brain separates out the sytanx for each one.
I came here to say no, I don't for the silent majority. There's a large amount of pain coming with being so vigilant about security. I'd rather spend my time and energy else where.
Its having to shutdown, and having to boot into another OS. That's fine if you're targeting a mining rig, but for a home pc, you can't do anything else with the machine. Hence the deal breaker.
I was interested, but having to run an entire OS off thumb drive is a deal breaker for me. I'm naive in this area, but would it be that hard to implement it under WSL2?
A paradigm that Dave Farley has mentioned could be on the same level as OOP or structured programming is a completely asynchronous programming language. Every operation would have no garunteee of executing immediately. Such a thing may unlock more performance for cheaper on modern multicore cpus.
He doesn't address the problem of in a large project, sometimes it's better to copy and paste a function to avoid the extra library dependency. DRY and over coupling are two forces that must be balanced by the engineer. Dry is more important at small scales, over coupling is more important at large scales.