• 0 Posts
  • 34 Comments
Joined 19 days ago
cake
Cake day: January 2nd, 2025

help-circle
  • Don’t listen to the people saying there’s an issue anywhere.

    All this racist nonsense is just that - nonsense.

    I’ve lived or worked for extended periods in numerous states, from Maine to Alabama, North Dakota, Washington, Texas, California, and all over the midwest, especially in rural areas (worked with trucking companies), and you really don’t see all the racism people claim on the internet, even in the trucker world.

    Yea, you’ll find an ass here and there, but that’s very much the exception today. Far more so than even the 70’s, when being openly racist in a small town was tolerated a lot more (“the older generation don’t know no better” kind of stuff).

    So come to the US. You’ll be fine anywhere except specific areas in certain inner cities (and that’s a general crime issue, not a race issue).






  • Thank the asshole directors for choosing to make sound so crappy any more (my opinion, I think all movies have crap mixing, with too much focus on sound effects so even when voice is brought forward it’s still hard to hear clearly).

    Part of it is the movie audio is mixed for a theater that has multiple channels and speakers, so the output is the better separated and voice can be delivered better. It would need to be remixed to sound better at home, and since all homes are very different, what would you target? (Plus they simply don’t want to pay extra for mixing which doesn’t contribute to seats in a theater). Yea, they could probably use a generic mix, but again, it costs to do so, and some home users would still (justifiably) complain.

    The other is some directors intentionally crapify the mix because they want a certain experience while watching the movie in the theater. One director recently even stated he wanted dialog to be difficult to understand in certain scenes (I forget what movie). I get the director’s intent, even if I disagree.

    The only solution for home that I know is to have a sound system that can manage the separate channels. Many systems now have a sound bar just for voice, so this is already happening to some degree, but I rarely see discrete volume controls for the channels.


  • I’d stop wasting time trying to make it work. Simply save your spreadsheet (you are saving it early, often, and keeping dupliicates, right?), and just copy/paste the file into an email.

    At one point I supported Office for Microsoft, and while they’d never admit it, this process for embedding files has alway been a little wonky (directly from one app to another). Grabbing the file and pasting it eliminates the risk of either app causing a problem because the OLE registration isn’t perfect, by using a file system path to the object.

    I believe you can paste into Outlook a sheet as a table this way, if that’s what you’re trying to do. Not something I’d do, because, again, this kind of stuff has always been a little less than perfect. Attached files seem to have fewer issues.

    Edit: I currently have one machine where URLs in docs (Word, excel, Publisher, Project, Onenote) can’t be launched, an error says “Administrator has disabled this feature”. I gave up trying to fix it (and remember, I supported Office, I know how this stuff works, I have notes from years ago about which reg entries handle this stuff). Now I just copy the URL. It’ll get fixed when I refresh this machine.



  • Documentation has been mentioned already, what I’d add to that is planning.

    Start with a list of high-level objectives, as in “Need a way to save notes, ideas, documents, between multiple systems, including mobile devices”.

    Then break that down to high-level requirements such as “Implement Joplin, and a sync solution”.

    Those high-level requirements then spawn system requirements, such as Joplin needs X disk space, user accounts, etc.

    Each of those branches out to technical requirements, which are single-line, single-task descriptions (you can skip this, it’s a nice-to-have):

    “Create folder Joplin on server A”

    “Set folder permissions XYZ on Joplin folder”

    Think of it all as a tree, starting from your objectives. If you document it like this first, you won’t go doing something as you build that you won’t remember why you’re doing it, or make decisions on the fly that conflict with other objectives.