301
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Feb 2024
301 points (73.6% liked)
Mildly Infuriating
33925 readers
635 users here now
Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means: -No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating.
-At this time we permit content that is infuriating until an infuriating community is made available.
...
8. Reposting of Reddit content is permitted, try to credit the OC.
-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
founded 1 year ago
MODERATORS
Yeah, I don’t trust the auto save to save my work properly. I work as a Software Engineer, and any small change I make, even if I’m not done with the change and I’m just thinking, my hands immediately default to CTRL+S.
Always always make sure your work is being saved if it means something to you. Especially since windows will force update and reboot your computer. Battery’s can die, power can go out and your computer shuts down. Applications can and will crash.
Why do you trust ctrl-s though? You are a software engineer, you know that a bug in the piece of code that saves the document would affect both calls, regardless of whether its invoked by a timer or by the end user pressing keys, right?
I mean we have all been bitten by op's problem In the past but it was exactly the same issue, autosave not enabled (most likely didn't exist) what's with all these, I don't trust software to do it's job so I do things by hand?
Particularly from software developers or other technical users. Found a bug in a piece of software, report it, you don't need to change your behaviour for the next 20 years and tell everyone anecdotes about you still don't trust a regression.
There's a couple things... First, it's a habit to be constantly pressing CTRL+S. I've been doing it for many years, I'll continue to do it probably until I stop using a keyboard. It's such an easy keystroke, since my hands are almost always hovering over the keyboard. Second, in some software you can create new documents without first creating a file on disk. This means that when I go to hit CTRL+S, it prompts me to save the file. That's not to say that some software can't save a recovery version of the document in the event the software crashes, but I'm not going to bet money on it working 100% of the time. I'd rather be proactive and personally make sure my work is saved. Gives me peace of mind.
I already covered your first point, you don't need to.
As for your second point, autosave still does its job. The fact that you haven't chosen a name and a folder for your document doesn't mean that the software hasn't created one on disk that keeps getting autosaved. When you decide to finally save the document, that file gets renamed and placed where you want it.
I mean this is trivial stuff that got solved a long time ago, I don't see people on this thread saying I don't trust electronic payments, I only write checks but somehow everyone think a basic feature is broken everywhere
Every single one of us has been bitten by auto save that didn’t work. I’ve personally lost hours worth of code to auto save glitches and poorly timed save runs. People don’t trust it because in the past it has had and/or caused problems with their workflow.
Ctrl+S is a manual confirmation that I saved it, and is a step taken before running any code, especially through a terminal in an IDE where if the auto save hasn’t kicked in will mean the changes aren’t reflected.
ctrl-S is deeper, older code. And yes, a bug in that would affect both manual and automatic saving. Meaning the bug has greater exposure and therefore would be detected faster.
More easily detectable bugs are less of a problem, because lack of alarm indicates lack of those bugs.
It’s this: (P => Q) => (!Q => !P)
Basically P is the bug existing and Q is someone detecting it. The more powerful the implication arrow on the left side of that equation, the more powerful the implication arrow on the right side. Or if you prefer probabilities: a greater conditional probability on the left means a greater conditional probability on the right.
Worse bugs that affect more systems are less worthy of the user’s attention.
If current_time > x invoke deper,older code that you somehow trust
Alternatively, more modern implementation suggested by someone else in this thread
At every keystroke, invoke deeper older code that you somehow trust
While not impossible, pretty hard to slip a bug into something like that and if it happens it gets identified,reported and fixed like all bugs. Users tend to be quite vocal about data loss.
Also some software developers tend to overcomplicate things, this is not rocket science