🐍🩶🐢

She/They

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

help-circle

  • I have no idea how we got to it before at I mostly use smaller channels and friends, but I just tapped on the # channel-banner-name at the top, without having to think about it too hard. I have never seen this screen until now, but having separate tabs for all the shared links, media, pins, and members is something I wish more apps did.

    I hope they can find a happy middle ground for users, or give users enough customization options where they can configure what works for them. I hate that only 3rd party apps for things like Reddit and Lemmy actually give you control over your interface. Is it too much to ask to have customization options like the old days? 😥



  • 🐍🩶🐢@lemmy.world
    cake
    tolinuxmemes@lemmy.worldLinus does not fuck around
    link
    fedilink
    English
    arrow-up
    127
    arrow-down
    1
    ·
    7 months ago

    I was curious as I couldn’t help but laugh, but damn dude. That is rough. Hilarious looking at it now, but I feel bad for whomever was at the receiving end.

    Of course, I’d also suggest that whoever was the genius who thought it was a good idea to read things ONE FUCKING BYTE AT A TIME with system calls for each byte should be retroactively aborted. Who the fuck does idiotic things like that? How did they not die as babies, considering that they were likely too stupid to find a tit to suck on?






  • I code daily on mine, by choice. I also have no issue coding on Linux and will happily spend all day in a CLI. Homebrew is just as easy as using apt or what have you, at least in my personal experience.

    It isn’t always perfect.There was a bit of head scratching over shared libraries one time, until I figured out what stupidity I had to do to make Apple happy, but that is the only notable thing I can remember.

    However, coding on Windows can be super painful depending on the language, especially with all of the backwards paths. The only coding work I enjoy doing on Windows is C#. Worst case WSL2 is around when I need some sanity.

    No matter what, I have any of them available to me and the battery life on a MacBook Air is amazing. The corporate laptop is actually a decent machine and the size and weight is pretty good, especially considering the monstrous bricks the previous models were. Mobile workstation woes I guess. The most amusing part is AutoCAD 2024 running smoothly on the Mac. I never knew it could be that snappy.


  • 🐍🩶🐢@lemmy.world
    cake
    tolinuxmemes@lemmy.worldText editor war
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    8
    ·
    8 months ago

    Brilliant! I don’t entirely disagree with that. I had vim forced on me at my old job, including actual vi on some of the more ancient systems. I got so used to it that I don’t really know how to use nano and definitely not emacs.

    I never understood what the big deal was. Write. Quit. If you can’t remember that ‘w’ means write and ‘q’ means quit, I don’t know how else to help. Add in some decent options in your vimrc and it is pretty comfortable. I am in no way some guru who knows every shortcut and fancy command out there, but I like using it and it is the first thing I install on a new system.

    I am not one to judge what text editor, OS, phone, car, or computer you like. You do you. If I was a sysadmin that had to deal with people who really shouldn’t be on those systems and that was an easy way to discourage people from screwing with it, then hell yeah.





  • For the love of all that is unholy, learn and get comfortable with the command line. Go install WSL if you are on Windows. Not saying you have to be a master, but learn how to compile your code manually, get around the OS, tab complete, grep, ps, and other simple commands. Learn the basics of a text editor. vim/emacs/nano. Just pick one or two. Learn how to redirect output to standard and error out. Simple shell scripts.

    Debugger. If you do not know how to set breakpoints, with or without conditions, and inspect variables, go learn today. I have junior developers that can’t do this.

    Critical thinking and investigation. This is a rather loaded term, but your problem solving skills will go a lot farther than how your code looks. Bad but working code can be improved. Alternative solutions can be found. You at least understand the problem and an approach to take. If you don’t understand how something works, figure it out. Ask your senior team members. Spend time in the debugger and the source code, if available. Good documentation doesn’t always exist. You will not always find the perfect answer or tutorial on the Internet. If you are going to use code off the internet, you damn well better understand how it works and how to expand on it.

    Keep up with the standards and updates to the languages you use. A lot of tutorials can be out of date fairly quickly. Newer language features can be a huge boon and you get a sense of where that language is going. Older ways of using libraries and languages can be hard to avoid, but make an effort to check. Speak up to your seniors if you find something that may be useful or if something is now considered bad practice.

    Look at source code on GitHub/GitLab/Whatever and then the all mighty practice.

    In my opinion, once you can get a handle on the above, then you can go back and learn more advanced principles, algorithms, read textbooks, and things like that. They will make a lot more sense. This may seem a little opposite than what most people would say, but for me a lot of the things I learned in school or read previously started to click.



  • 🐍🩶🐢@lemmy.world
    cake
    toLinux@lemmy.mlGamedev and linux
    link
    fedilink
    English
    arrow-up
    24
    ·
    edit-2
    8 months ago

    Image transcription. Pasted from source, Reddit Post

    Despite having just 5.8% sales, over 38% of bug reports come from the Linux community

    Article

    38% of my bug reports come from the Linux community My game - ΔV: Rings of Saturn (shameless plug) - is out in Early Access for two years now, and as you can expect, there are bugs. But I did find that a disproportionally big amount of these bugs was reported by players using Linux to play. I started to investigate, and my findings did surprise me.

    Let’s talk numbers. Percentages are easy to talk about, but when I read just them, I always wonder - what is the sample size? Is it small enough for the percentage to be just noise? As of today, I sold a little over 12,000 units of ΔV in total. 700 of these units were bought by Linux players. That’s 5.8%. I got 1040 bug reports in total, out of which roughly 400 are made by Linux players. That’s one report per 11.5 users on average, and one report per 1.75 Linux players. That’s right, an average Linux player will get you 650% more bug reports.

    A lot of extra work for just 5.8% of extra units, right?

    Wrong. Bugs exist whenever you know about them, or not. Do you know how many of these 400 bug reports were actually platform-specific? 3. Literally only 3 things were problems that came out just on Linux. The rest of them were affecting everyone - the thing is, the Linux community is exceptionally well trained in reporting bugs. That is just the open-source way. This 5.8% of players found 38% of all the bugs that affected everyone. Just like having your own 700-person strong QA team. That was not 38% extra work for me, that was just free QA!

    But that’s not all. The report quality is stellar. I mean we have all seen bug reports like: “it crashes for me after a few hours”. Do you know what a developer can do with such a report? Feel sorry at best. You can’t really fix any bug unless you can replicate it, see it with your own eyes, peek inside and finally see that it’s fixed.

    And with bug reports from Linux players is just something else. You get all the software/os versions, all the logs, you get core dumps and you get replication steps. Sometimes I got with the player over discord and we quickly iterated a few versions with progressive fixes to isolate the problem. You just don’t get that kind of engagement from anyone else.

    Worth it? Oh, yes - at least for me. Not for the extra sales - although it’s nice. It’s worth it to get the massive feedback boost and free, hundred-people strong QA team on your side. An invaluable asset for an independent game studio.



  • The orange kiva bots? Amazon stole/purchased a robotics company for those as they wanted to develop them inhouse. A lot of the issues with robotics is cost and imperfect environments. Even dumb shit like changing the warehouse lighting can screw up sensors, guidance systems, and other automation if it wasn’t designed that way. Customers want automation, but they don’t want to pay for it. If we have to cheap out on sensors, cameras, drives, and other parts, it makes for less reliable systems depending on the application.

    There is nothing more demoralizing than knowing a design is going to fail from the beginning because sales let the customer dictate the parts and design elements to cut costs. Then we get yelled at when it doesn’t work perfectly or make rate. Or worse, it does/did work but the customer now uses the system in a way it wasn’t designed and sabotage any good we might have done for them. Best is when a customer doesn’t maintain a system, something that has to start on day 0, and then throws a tantrum when it breaks down all the time.

    Robotics and automation isn’t perfect. I have seen some great systems run with little to no downtime and shitty systems that operators have to constantly babysit. Us engineers try our best, but we have to use the tools we are given. I will say that technology overall has boomed over the last decade, but the parts and shipping situation since the pandemic started still hasn’t been solved.