• 1 Post
  • 190 Comments
Joined 2 年前
cake
Cake day: 2023年8月20日

help-circle







  • Mint. I’ve been happy with it. I’m more familiar with debs/apt/Ubuntu so I wanted to stick with something familiar but didn’t want to use Ubuntu. It’s worked very well for me for gaming. I just upgraded my GPU from an Nvidia card to an AMD card which, aside from having to manually install the drivers from the terminal, has worked very well.





  • halloween_spookstertoLinux@lemmy.mlhow is linux for gamers?
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 个月前

    I switched full time to Linux last year and primarily use my computer for gaming. It’s been great. I play games through steam so YMMV with other systems. I haven’t had any issues playing a variety of games such as Factorio (built for Linux), GTFO, Horizon: Forbidden West, PEAK, Ready or Not, Plate Up… It’s been rare for me to have an issue. I remember an issue trying to play Plate Up via steam remote play.







  • My computer graphics/computer vision professor in college (two classes, same professor). He treated us as people, explained the logic behind his teaching style (and grading), was extremely knowledgeable and approachable. A lot of professors end up having a sort of air or mystique around them that can make them harder to approach 1-on-1. Usually it’s no fault of their own, they’re just in a position of power and authority over the students.

    This professor really tried to bring his students in by making us feel like we belonged. He actually described his class as the same class they teach at MIT. The only difference was the students and their drive.

    In the computer vision class, there were only about 8 of us and we all did terribly in one of his exams. The next class he asked us directly and openly what he did wrong and how to make things better going forward (tl;dr: more examples). I really respect teachers who admit their mistakes/failures and then try to correct them.



  • It can vary a lot depending on the day and the company/job. Frequently there are meetings that are update/planning discussions, discussions with one or more other engineers on how to build a given feature, debugging existing code to figure out why it’s not doing the thing we want (which is a different but overlapping skill set with coding).

    Ultimately there isn’t really a “typical” day because we wear a lot of different hats. My current job is more coding heavy because I’m at a small startup with only a couple of engineers. In a given week I’m probably doing 10% meetings, 50% coding/debugging/configuration, 20% code review (reviewing other people’s code), and 20% thinking/designing/experimenting with ideas. Those numbers vary a lot though. At a previous job I ended up spending an entire week just doing project management to alleviate my boss’ anxiety over a project (which was somewhat self defeating because it meant I wasn’t getting work done on said project). That job in particular had a lot of politicking and communication which was due to micromanagement.

    A lot of what people don’t realize is that we aren’t just building a feature. We’re building a feature while thinking ahead to known or potential future features. How can we build feature A to enable making features B, C, and D easier/better/faster without also making feature E much more difficult or impossible? It’s about building flexibility into the system while also balancing against time and cost restrictions. We as engineers have things that we see as necessary while the business wants more features and it’s necessary to balance the two. At a healthy org that means that there’s a negotiation of priorities between the two forces. If you only focus on the technical stuff, you won’t ship features. If you only focus on the features, how fast you can deliver features will come to a grinding halt. Your system will also start breaking in unexpected ways which takes time away from building features.

    It’s kinda a rambly response to your question but I hope it helps.