• 0 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: September 29th, 2023

help-circle





  • Worst case I have all my OCRed documents as raw files which I can migrate to whereever.

    Files still exist. For my case encrypted as well. My backups roll on the data, not the container.

    But I’m not trying to convince you, I tried answering the questions :)

    And two answer your last question clearly: I survived before paperless, I’d get along without it. I find a new tool to mitigate my manual labor as good as possible - if that’s not possible then jo harm done. I know I’m flexible, I can learn new tools and I’m never vendor or tool locked-in. I have a high level of self confidence when it comes to my tool chain and how I’d adapt any part of it - from password manager to cloud storage and my mail flow.

    To be honest I couldn’t self host anything if I’d had the fear of being lost if a tool is discontinued.


  • For me it was a few hours wrapping my head around how paperless ngx works and its setup. I had a folder structure as you described already on my Nextcloud so I just configured paperless to observe it for new files.

    Where I spent more time then reasonable with was the tagging - you can automate it based on… Well everything.

    Now I just let it suggest me tags based on my existing documents plus add a NEW tag to the ones I’ve never reviewed. That’s just a reminder for me though to review tags when searching, I don’t actively re tag new uploads.

    If you have a docker environment I suggest just pulling a container up3, throwing all your documents in it and see if it would save you time or cost you time. Would be an hour well spent!personally the OCR alone is it worth it for me - my country still loves paper letters and being able to copy text out of that is awesome (IBAN, account numbers, etc - all the stuff that’s suspectible to typos).











  • I apologize - it wasn’t my intention to imply that at all! Emotional self management is a critical skill for managers - and that shouldn’t mean “go away, emotions!”. A trainer and coach I highly respect phrased it simply: “emotions are. They exist if we like them or not.”.

    What I intended to convey was “do not use a public platform to channel your emotions.”

    If this would’ve been a private conversation I would integrate an explanation of my current situation, feelings and context for my reaction. And also this sounds abstract it can totally be a “dude I’m absolutely pissed. I need you to work with me through this.” (this works btw in both meanings of “pissed” ;)).


  • Oh that was in purpose! It shouldn’t matter that I personally am angry. My employees should never NEVER try to prevent me from being angry but focus on doing the best job they can.

    That’s what I admire about Linus: he realized the negative impact his anger had on the performance of others - and fixed it!

    To be clear: I can be angry - but my anger isn’t the reason I want things to change. Being angry is MY FAILURE as manager!

    Think about it in another way: do you want your colleagues do things they thin prevent you from being disappointed, frustrated or angry - xor do you want then to move your collective goal forward no matter what you’d think.

    Another example: if I’d be the one to have caused this communication mess I’d want my employees to call me out - even though I will get angry the moment I realize I’ve fucked up big time!


  • As many seem to have overlooked itb this is from more than a decade ago.

    And to those setting “not being toxic” == “being vague”:

    Suggestion if you’re in a situation: separate the subject discussed from the person and, to the contrary to what is said in some other posts, be very specific!

    Improvised example:

    Hey all,

    patch xyzz and its aftermath communication is unacceptable.

    It’s content is not to the standards we have set here (explain).

    Even worse, in the communication aftermath we blamed behavior of user space applications for bugs that are within our domain instead of owning up.

    The bugs within the kernel will be focused on with highest priority by a, b and myself.

    For the communication: (consequences). As explained the patterns shown here are unacceptable.

    I have decided to no longer have x as a kernel maintainer on our team/enforce pairing for all communication/set up stricter consequence catalogue. Any specific action,really…

    Not perfect as it’s very early here, I haven’t slept well and I’m not deep into the topic.

    Just remember to separate subject to be discussed from person(s) acting please.

    And always remember: bad communication is really easy and a lot of managers trained that their whole life! ♥