• 1 Post
  • 55 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle




  • It was PHP and Laravel.
    I started doing fancier things with websockets, redis, cronjobs etc.
    Anything “designed for” laravel hosting wasn’t cheap. So, I learned how to get a VM going and set it up for webhosting.
    Windows is still my daily driver due to Office, Visual Studio and gaming.
    But I have a bunch of VMs and servers, and they are all Debian.
    I enjoy Linux, but I haven’t gone whole-hog into a desktop environment or whatever. Everything has been CLI based





  • The first time you make the Cyclops and go “woah, that’s big”. When you are welcomed on board. When you walk about and go “oh, engine room. And 6 power cells”, when you flick all the lights on and off, when you have to start the engine, when it steers like a bus and you bonk everything I’m sight. When you first honk the horn. When you learn to drive using the cameras. When you learn you can build in it. When a creature attacks and you drop a bouy.
    So many great firsts with the Cyclops.

    The seatruck was fine. But it didn’t seem to have the personality of the cyclops




  • Client side hashing of a password just makes the hashed result the password, as far as security is concerned.
    Unless there is some back-and-forth with the server providing a one-time-use salt or something to make each submission of the password unique and only valid once, at which point that might get snooped as well.
    Better off relying on client certificates if you are that concerned


  • Mikrotik is awesome. They are super powerful and super flexible.
    But they don’t hold your hand, and have a hell of a learning curve.
    Luckily, the quick-set default config thing is actually decent these days. So it’s easy enough to get a basic setup going, then figure out how the bridge works, vlan tagging, where to add IPs, DHCP settings, DNS whatevers and all that.
    It took me about 6 run through of setting it up before I stopped locking myself out accidentally! Probably another 6 before I was confident setting up a new vlan with routing/DHCP/etc.

    Just be aware that there are a lot of popular tutorials out there based on older versions of the software, and older ways of doing things. Look for videos from 2022+



  • Comparing the quality of music videos and recordings of various shows posted on YouTube by TV channels, I do not find any difference.

    Maybe for you, but I generally can.

    Bigger cameras have bigger sensors. This means they can process more light, amcan get more detail, and have less noise.
    The gaps between large triple ccds and smaller single ccds has certainly shrunk. But if a professional has to get the best possible result in all sorts of environments while not wasting time/money, buying a proper camera that isn’t going to need as much post processing, or as many lights (especially with multiple subjects) is going to be a huge timesaver.
    Kinda like photographers with a DSLR Vs an iPhone. The difference has become less, but a DSLR is going to kick an iPhones ass every time.

    Next up is the lenses.
    If you have a small lens with a defect, more of the picture is going to travel through that defect.
    If you have a large lens with a defect, a smaller amount of the picture is going to travel through that defect.
    Also, lenses generally have more abberations towards the outside of the lense (like barrelling or chromatic aberration). If you can only process light from the middle of the lens, the picture is going to be so much better.
    So you make big lenses, and only use the but in the middle of them.

    Finally it’s things like other features.
    From encoding format, framerate & resolution, outputs (clean feeds, native sdi or SMPTE fibre, remote CCUs, return feeds, coms), genlock and timecode syncs. Even to things how the viewfinders, zoom and focus controls work.

    And by the time you are making a $100k camera with $250k lenses, it’s kinda a thing that works for sports, film, TV, whatever. There is a lot of overlap of features, and nobody wants to buy the same lens for 2 different cameras because the cameras are slightly different.



  • I am going through this right now, but without the drugs.
    Mid 30s, waking up to realise my life is a mess, working on getting a diagnosis for ADHD and possibly bipolar, and getting help with depression.
    I am now fixing my life.
    The biggest thing that is helping me is talking about it. Asking for help is important, but just sharing your experiences is also important.
    It was a friend that shared his experiences with me that has put me on this journey of recovery.
    Never any problem solving, or offering solutions or fixes. Just sharing and talking.

    Anyway…

    When I’m doing software dev stuff, I always feel out of my depth. I’m reading interesting articles from people way smarter than I am. I’m reading codebases that are a delight to read through and leave me in awe.
    And I turn to my projects and work, and feel like a fraud. It’s all “standing on the shoulders of giants”, following tutorials just to get things to compile, locking myself out of VMs or network switches from dumb mistakes.
    But I also work in live events, so still technical and a lot of smart people. But when there is a problem, or a unique problem to solve, I’m just like “yeh, the problem is here because…” or “why not just do this…”.
    And these moments make me realise that perhaps I am not a fraud or an idiot. I just have different experience than my peers both in software development and live events. And there is some overlap.

    I think a huge part of it is: everyone is making everything up all the time.
    Some people have made something up before, so they can draw on that experience.
    It’s always worth spending a little time introspecting some of your progress.
    Spending less time googling issues, and realising you can figure stuff out (make stuff up) for yourself? Huge win.
    Remembering correct syntax? Huge win.
    Writing code that only has 1 or 2 bugs? Huge win.
    Recognising that a problem is best solved using whatever pattern/library/etc? Huge win.

    Imposter syndrome is real.
    Dunning-kruger is also real.
    And then the imposter syndrome makes you think you are in the dunning-kruger zone, and makes everything worse.
    Recognizing the progress and successes helps