• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: June 25th, 2023

help-circle

  • not sure i agree with that. I mean ok, i recently had three interviews for a company where each interviewer asked me almost the same questions. That was clearly a waste.

    At my place, we do a 30min introductory call with the boss first, to quickly weed out unfit candidates and not waste employee and interviewee time with interviews. if that’s ok, then there’s three interviews of 45-60 minutes, one with the product owner that focuses on soft skills and team fit, one with the team your applying to and one with the other team (like frontend or backend) with more technical things, and also just if you’d like to work with this person.

    no amount of interviewing will ever guarantee that things work out and unfit people can slip through cracks. And i hate wasting time in tons of interviews. But i’d also not want to work at a place where i know my coworkers were hired after just 1 hour quick chatting. That so little time to get an idea of a person, to spot any red flags. Heck, the ‘tell me a bit about yourself’ section of an interview is already 15 minutes and not usually very helpful.





  • You misunderstand, the first two commands are just one time setup to install a specific python version and then to create an env using that version. After that all you need is `pyenv activate myenv´ to drop you into that env, which will use the correct python version and make sure everything is isolated from other environments you might have.

    You can also just create an env with the system python version, but the question was specifically about managing multiple versions of python side by side and this makes that super easy.

    You could also combine it with direnv to automatically drop you into the correct environment based on the folder you are in, so you don’t have to type anything after the initial setup.








  • there’s a lot of stuff you can do, and you can end up with something usable, though not great, at least not in my experience. NVidia’s drivers are to blame, they don’t really work well with opengl and have lots of issues (and also regressions).

    The 550 beta driver is ok-ish, steam flickers but I can play games. Drivers before 535 also somewhat worked, though it really depends on your GPU.

    But I don’t think you will have it working acceptably without some work.

    Here’s some pointers on stuff to try:

    • check protondb for how other people got games to work, you can filter by your GPU.
    • try running through gamescope or gamemoderun
    • try the modeset=1 (and maybe fbdev) kernel parameters for nvidia drm
    • and there’s tons of env vars and other things that can help, I couldn’t summarize them all here, but as a pointer: XWAYLAND_NO_GLAMOR=1, WLR_RENDERER=vulkan, LIBVA_DRIVER_NAME=nvidia, GBM_BACKEND=nvidia-drm (for the drm above), __GLX_VENDOR_LIBRARY_NAME=nvidia
    • try the beta drivers, if those are available somehow (I’m on arch so they were easy to install), or just different driver versions in general.

    The above is meant more as hints than something to copy paste, so use at your own risk. You can of course always just install a second DE with X11 and log into that for gaming and use your regular DE for everything else