• 2 Posts
  • 509 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle
  • There’s a lot of gamers in this thread too young to remember how overloaded and miserable the free console game servers were.

    Microsoft was like “chuck us like ~$5 per month and we will put up enough servers so the games are actually playable”. At the time, it was the best deal available for console gaming.

    Honestly an argument could be made it was the most economical way to play online, in general, at the time. The console cost was subsidized, and the online servers were arguably at-cost, and you really only needed to buy one copy of Halo to join the fun.


  • “Follow my path and you’ll be fine.”

    Later, at a Republic Tribunal:

    “… and obviously no sane pilot on a training mission would ever consider attempting to navigate those obstactles without weeks of study in advance. And so I exhort the jury not to consider leniency, but to find the defendant guilty of first degree premeditated murder of their wingman pilot in training. The prosecution rests this - quite frankly open-and-shut - case.”




  • MajorHavoc@lemmy.worldtoProgramming@programming.devHow to find a job?
    link
    fedilink
    arrow-up
    14
    arrow-down
    1
    ·
    edit-2
    6 months ago

    Let your mentors know you’re looking for work, and how many hours you can work per week.

    New programmers provide negative value, so there’s not a lot of demand.

    I’m very good and studied hard, but my first couple of programming roles I got entirely because a mentor of mine recommended me to someone who took a chance on me.

    Also keep adding code to your public GitHub. Two of my top developers today I originally hired directly away from their retail roles. One had a ton of academic coding experience and had just not yet landed the right job. The other was just getting started, but posted a ton of low quality homework code to GitHub so I could read it and know who I was hiring.

    Edit: In contrast, one of my other top developers has one of the top CS degrees in the world. So that works too.

    And more than one of my top developers have IT help desk experience. I have had excellent luck when hiring folks with IT Help Desk experience.

    Edit 2: As someone else mentioned - your long term goal is to connect with an IT Recruiter that you trust, and work with them to get your resume, and GitHub, and/or binder full of code you wrote into shape. I’ve hired more than one candidate who admits the simply presented themselves exactly as their recruiter coached them to. And I’ve hired candidates I would have skipped, because their recruiter was someone I trust and they asked me to take a second look at a candidate who made a poor first impression.

    Edit 3: Since this is for newbies, some information about recruiters: we pay the recruiter in addition to what we pay you. The recruiter’s typical pay for a rookie hire is around $50,000.00, if you stay for a full year. Half up front, in case you don’t stay.

    A few things you should know about recruiters: they only need to make a few solid placements each year to earn a living. As a rookie, you’re the hardest to place, and the lowest layout when placed. But, programmers that are easy to place don’t move often, so recruiters may still have plenty of time for you.

    The recruiter is probably mainly placing you the first time in hopes that you come back later when you’re worth big money. The initial payent is nice, but the real payment will be if/when you have 5 years experience and still work exclusively with them.

    Hiring managers like me have recruiters we trust and reuse. If you can get recommended to a great recruiter, they will get you interviews at better places to work.

    In contrast, there’s lots of mediocre recruiters out there. Don’t be afraid to switch to a new recruiter, if you have the opportunity, and your current recruiter isn’t getting you interviews.


  • MajorHavoc@lemmy.worldtoRetroGaming@lemmy.worldBest distro for linux gaming?
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    6 months ago

    I second the folks who recommended a Raspberry Pi and RetroPi variant. For no frills, just-start-playing, it can’t be beat.

    Another option I haven’t seen mentioned yet, is Ubunutu with Steam. Thanks to the rising popularity of the SteamDeck, lots of great games run perfectly, with no fuss, under Steam on Ubuntu.

    But again, with your target including a lot of retro games, a RetroPi is the smooth path. Most of your PS2 games will work fine with some fiddling. Your PS3 experience will be more bound by the current state of PS3 emulation, than by the power of the Raspberry Pi (though you should certainly plan to get the biggest supported model, and get a big cooling kit and overclock it.)

    I’ve played various PS2 games with relatively little fuss on an overclocked Pi3 with a cooling kit.

    For PS3 era games, I would just make the leap to Ubutnu and then just buy any that are Steam Deck Verified, through the Steam store. Some won’t be, but the ones that are should be a good time.

    I, personally, don’t have the life spare cycles to mess with emulating unverified PS3 era games. PS2 era was still very hit and miss last time I bothered for an arcade machine build. I’m sure it’s doable, and might affect your hardware choice. Your best odds are probably Ubuntu, again - thanks to all the investment by Valve.


  • Pi has the power to do up through PS2 just fine, though last I checked the state of emulation for PS2 and PS3 wasn’t good yet, for the average hacker.

    If this is your first time emulating, you’ll have a nicer time learning the ropes on RetroPi on an actual Raspberry Pi. Statistically, you’re not really giving anything up, because anything that doesn’t require insane levels of expertise and esoteric knowledge emulates perfectly on Pi.

    Contrarily, is this isn’t your first emulation outing, or you’re down to go all-in down the rabbit hole; then build the whole PC around whatever you find emulates PS3 well, and the rest should be trivial to add.





  • When something that big barely turns a profit, I immediately suspect Hollywood accounting.

    But if true, they made a game, covered their costs, left the company with an asset that can keep making sales, and probably developed their in-house talent and tooling along the way. That’s a lot of points in the “win” column.

    Wise leaders understand that, in business, victory means getting to try another project with the same team, next year. Failure means disolution of the business. Earn enough years and projects with the same team in a row, and maybe you take one of the big wins one of those years.









  • I’ve given up huge piles of cash by choosing to not work for megacorps.

    It’s worth it to me.

    Confronted with the likelihood that we cannot achieve climate goals.

    The current trend line sucks, but we’ve seen plenty of times in history what the ultra rich ignoring the plight of everyone else looks like. Someone please pass the “not with them” list to me to sign when it’s time to chop their heads off.

    I wish I was joking, but I’m not. Seriously. I’m not with them. I would like to keep my head while we adjust course abruptly.

    Edit: To be clear, I am not advocating. What should happen is that our climate, inequality, and injustice trends get fixed through peaceful cooperation. But our current crop of billionaires don’t show a lot of sign of either wanting that, or having any real awareness of where their current path, historically, goes. Which wouldn’t really be material to me, other than beacuse I’m at risk both from the climate, and from how guillotines historically kill a lot of bystanders.


  • This is terrific. Thank you for starting this discussion.

    I don’t think we can or should wait for individual users to make these decisions. Server admins are the ones who understand the risks and so should make this call. Guidance for server admins based on past experience (cough XMPP!) should be quite welcome.

    I might refine the bit about altered API versions to really focus on the real problem: proprietary extensions. We probably want to leave the door open to try out additions to the spec that come with detailed RFCs.

    But we know from XMPP that proprietary extensions are a huge problem.


  • "When we decided to give the test to the development team (about 15 developers) — most of them got scores that were lower than our threshold (45%), despite them all being rock-solid developers. Also, there were some candidates who managed to get 95% and above — but would then just be absolutely awful during the interview — we would later discover that they were paying someone to complete the technical test on their behalf.

    There is no substitute for taking the time to sit down and talk to someone."

    That’s pretty good advice. Interesting read.