Sends original data vs making a copy of data and sending it.
In meme context you’d be just making a copy of your consciousness and putting it in a machine. Whatever reason you’re doing it for - escape illness, survive armageddon, nothing changes for you. A copy of you lives on though.
I mean, just kill the host as soon as the upload is complete. at best you are not conscious during the process and when “you” wake up you are in the cloud. The version of you that awakes gets told that the “transfer” was complete.
Oh I know San junipero, just suggesting the plot of season 2 of future man as another similar reference - minds uploaded to “the cloud” and bodies destroyed on upload complete. Haley Joel Osmand is pretty decent as the antagonist of that season.
Pretty good. Offbeat as all hell. Loses its way a little in season 2 but pulls it back for season 3. Wasn’t generally considered a hit, didn’t make it past season 3.
I guess you ask for C++. There Type* can be null while Type& can’t be null. When it gets compiled Type& is compiled (mostly) to the same machinecode as Type*.
In my experience it doesn’t matter. You have to regularly refactor your code to keep up with new features. The more often you can make time to do it the easier it is.
Unit test to help catch regressions. If you are confident in your test catching a good portion of bugs from refactoring, at least you feel confident refactoring. Worst case, at least you ensured your code is testable. There is nothing worse than refactoring untestable code.
Self-documenting code and when it fails to self-document, comments or refer to a wiki page.
I watch too many videos on expensive guitar pedals I can’t afford.
I’m “on the bench” at the outsourcing company I work for and I am starting to seriously consider going into DSP programming just so I can work on doing this to effects controls.
I want to make knobs available for this this this and this parameter.
I feel this personally today. I just looked at some code in a module where it started out with nice, short functions with good names. I looked back at it today, and it now has a 180 line mega function full of nested conditionals and I don’t know how this happened.
The python code we inherited had some performance issues. One of the guys was like “we should rewrite this in Java”.
Luckily the boss was not an insane person and shut that down. The issue was an entirely stupid “…and then we do one query per project” behavior that worked fine when the company was small but unsurprisingly started to suck as users created more projects.
Instead of a months long complete rewrite, we had a two hour “let’s add profiling… Oh wow that’s a lot of queries” session.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.