I’m the administrator of kbin.life, a general purpose/tech orientated kbin instance.

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

help-circle





  • Going to second other comments. Even without archinstall. It feels like it will be harder than it is. Umm, just save yourself a bit of time and configure the network and install a console editor (nano/vim whatever) while in the chroot (if going full manual). It was a minor pain to work around that for me.

    There are pages discussing how to do everything (helps to have a laptop with browser, or a phone to look them up). At the end, you generally know exactly what you installed (OK no-one watches all the dependencies), and I’ve found any borks that happen easy to fix because I know what I installed.


  • This does tally up with what I’ve been hearing. Where I’m at there’s been a few hires straight into senior. I’ve not heard of an official junior freeze. At the same time it’s been a long time since I’ve seen a new one.

    The problem, as I commented prior, is that if we no longer bring in junior devs to gain this kind of experience, we lose the flow of junior -> senior. But in most places, the people making the decisions won’t consider anything beyond the end of the current fin year.




  • I think it goes further than that. There’s two things happening with regard to AI and software development.

    1: Stack overflow has become less common as a resource to solve problems. This, as you say has a problem of input into LLMs for future problems to solve.
    2: Junior developers are being hired less because of AI. I assume the idea is that seniors will use AI in the same way they would usually use juniors. Except, they’ve done what business always does. Not think one bit about the future. Today’s senior developers are yesterdays junior developers.

    The combination of AI performance drop due to point 1, and the lack of new developers because of point 2 makes for potentially, a bad future for the profession.




  • I think in the case of forced agreements (both Roku not having a way to select disagree and disabling all hardware functionality until you agree, and blizzard not allowing login to existing games including non-live service ones) no reasonable court should be viewing this as freely accepting the new conditions.

    If you buy a new game with those conditions, sure you should be able to get a full refund though, and you could argue it for ongoing live service games where you pay monthly that it’s acceptable to change the conditions with some notice ahead of time. If you don’t accept you can no longer use the ongoing paid for features, I expect a court would allow that. But there’s no real justification for disabling hardware you already own or disabling single player games you already paid for in full.

    It’ll be interesting to see any test cases that come from these examples.