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

help-circle


  • While I understand that, you've also described the supply chain of building an ICE vehicle, extracting and refining fuel, transporting fuel etc.
    Even if the EV suppli chain is currently terrible, that's because regulations haven't caught up yet. It was the same with oil extraction, "why pipe it when you can just have a river of crude oil" mentality. And hopefully regulations are faster to be enforced.
    Anyway, if the end result of a given supply chain is something that goes on to produce less pollution, then that is progress.

    And yes, public transport is always going to be better. Especially if they aren't ICE.
    Even EV mopeds are great. And the amount of electric bicycles I've seen going around is encouraging.

    I agree EVs aren't going to save the planet. But they are progress, and you can't convince me that we should continue using fossil fuels for personal transport.



  • Maybe it's just that I do more corporate conferences instead of exhibition or symposium type conferences.
    I think companies that have adapted for COVID are a lot more set up for virtual participation at their conferences.
    Whereas, a symposium kinda thing where delegates buy tickets expect presentations to be in-person. Which makes sense, it's what they are paying for. otherwise they could've saved money and just watched the stream/VODs


  • It is a recent trend after COVID.
    Before COVID, having virtual participants or presentations, even live streams were a luxury item.

    There was one client I worked with that was an early adopter of zoom pre-pandemic, and they did a lot of multi-venue stuff with presentations happening in all venues, calling out to remote office boardrooms for presentations from that region, stuff like that.
    It was charged at a premium (because it was unknown tech, so needed a lot of supplimentary technicians and equipment to mitigate the unknown risks, as well as get the virtual aspects to the same level of production as the in-person aspects).
    Some of the more important presenters would have technicians with a bunch of studio/streaming kit sent to their location to make it feel fancier for the presenter.
    I'm sure the client saved more on flights and hotels than the extra cost of the virtual aspects of the events. But it was a premium item that not everyone could afford, or was internally set up for.

    Post pandemic, live streaming is expected, it's pretty much a standard option tbh. Every company has their own internal platform (even if it's just Facebook pro or whatever it's called) and all event companies have a multi purpose platform if the client wants something different.
    Virtual participants are done with a single laptop and no backups (unless it's a very high level event), expectations from virtual interactions are lower (before, there would have to be analysis of any dropped frames, bitrate drops, stutters etc), presenters are much more comfortable handling their own tech (some even dial in dangerously close to their time slot, making the techs sweat) and 50-75% of the conferences I do now have virtual presenters.
    It's certainly a lot cheaper, as the tech is now known, it's capabilities proven during lockdown, and the systems and skills to use it were developed as a standard skillset of techs.

    No, I haven't used any 3d virtual things.
    The fanciest I did was a zoom-room to audience wall, but it all got composited into a standard stream.


  • As someone that works in the events industry.

    Conferences are about the networking and social aspects.
    This is not achievable through virtual or prerecorded aspects.
    I've done gigs where a few CEOs zoom/teams/whatever in to show face.
    I've done gigs where it's all in 1 location with only people in the room.
    I've done gigs where it's people in the room, but some satellite venues that "dial in" (even done a few of the satellite venues).
    I've done gigs with CSuites at multiple locations, and each site takes turns presenting some part of the conference.
    Honestly, all of this can be done via zoom or some other platform to much the same effect.

    What you can't get is the face-to-face time, incidental conversations, random introductions, and drunken conversations that happen over lunch, coffee, bar and dinner events.
    And I see this in "happier" clients. TBH, the good clients. The ones that have interesting presentations and engaged audiences are also the ones who benefit most from these extra social interactions.
    The gigs where it's some death-by-powerpoint should have just been a zoom meeting, or dare I say just an email or 2.

    So, I'd say it's how invested you are in the topic.
    If it's something you care about (or affects you directly): go in-person. You will get more from the event than is what is on the schedule.
    If it's something you have to go to, save the planet: watch it online (or whatever is the minimum mandated by your company). You aren't going to benefit from the social aspects, leave that to you manager.

    I am seeing the trend of team leaders and key people attending conferences, with many others watching virtually (like a 1:4 ratio).



  • 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


  • Self documenting code is more about using sensible names and explicit code.
    So addItemToCartByProductId instead of updateCart.
    The idea being, once you get the hang of an API, you can pretty much just guess what the name of the thing you want.
    And this applies at all levels.
    So cart[id] might be better as cart[productId] because id is ambiguous. Is it the id of the cart? Is that keyed by some user session?
    Suddenly you are having to maintain a larger scope in your mental model to try and understand what's going on.
    You could argue the cart variable could be named better. Or perhaps it's an internal variable, and it gets wrapped in accessor/mutator methods or whatever.

    It's the names and syntax that should tell you what things do.
    Comments should tell you why complex or obtuse things are being done.

    However, code used by multiple people (eg libraries, APIs, open source projects, group/company projects) absolutely need the meta-docunentation. The JSDocs, the readmes, examples, install, config, API overview and all that.

    Wikipedia has a good entry on it.
    https://en.m.wikipedia.org/wiki/Self-documenting_code
    Notably the "objectives" part:

    Reduce the need for users and developers of a system to consult secondary documentation sources such as code comments or software manuals[2]

    Reduce, not remove.
    So the documentation still needs to exist.







  • 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


  • The server was now too full of data to do anything,

    This reminds me of something that I always mean to do but totally forget to.
    Allocate 1gb of space for a blank/dummy file on every VM I run.
    When you run into a VM that locks up due to disk space, delete (or resize) the file, get to work fixing the VM, then put the empty file back




  • CS has always needed a GPU.

    CS:go required anything DX9 compatible with 256mb VRAM. Which would be an NVidia 6600, a midrange GPU from 2004 - around the time CS Source was released.

    CS2 minimum spec is a GTX650. Which is a mid range GPU from 2012, around the time cs:go was released.

    Something of a pattern there...

    If CPUs didn't have integrated GPUs, this whole "cs is CPU dependent" thing wouldn't apply, because you would STILL need a GPU.
    It's just that intel bundled a barely passable GPU alongside the CPU.

    TBH, I think you are missing you're argument.
    You should be arguing that there is no way to play cs:go now that cs2 has released. Meaning a potential hardware upgrade requirement.

    That is a bummer. That's pretty shit.

    But it is NOT enshittification.

    That does not claw back value/money from customers to valve or its investors.
    Unless you can show me, beyond reasonable doubt, that Valve is making money from giving away CS2 for free to anyone that has purchased cs:go through the requirement of a hardware upgrade.
    Until then, this is not enshittification.

    Is it shitty? Sure.