▲ 550 ▼ Baldur's Gate 3 introducing a native Steam Deck build that improves performance by reducing CPU load and memory usage (store.steampowered.com) submitted 10 months ago by mr_MADAFAKA@lemmy.ml to c/steamdeck@sopuli.xyz 48 comments fedilink hide all child comments
[–] savvywolf@pawb.social 31 points 10 months ago (6 children) I like that they're passionate and supporting Linux and all, but unpaid work like that should be discouraged, imo. permalink fedilink source parent hideshow 12 child comments replies: [–] Minnels@lemmy.zip 21 points 10 months ago (1 child) Maybe it wasn't considered work for this person? They wanted to try and do something better in their own time. I am not saying they shouldn't be compensated but doing something of your own will doesn't have to be work, it can be fun. permalink fedilink source parent hideshow 2 child comments replies: [–] princessnorah@lemmy.blahaj.zone 7 points 10 months ago Alongside that, it seems like there's a good chance that next time, they'll be the goto for doing this sort of porting. permalink fedilink source parent [–] Hazzard@lemmy.zip 18 points 10 months ago (2 children) The best companies will do something like "20% time", leaving one day a week or something to work on whatever, which is fantastic for stuff like this. Some of your employees almost certainly have the best ideas, if you just trust them with the space to prove them out. Great way to get cool stuff like this without unpaid labour. permalink fedilink source parent hideshow 4 child comments replies: [–] vithigar@lemmy.ca 6 points 10 months ago* (1 child) The place I work says they do this and will claim with a straight face that our sprints are budgeted to allow approximately 20% slack time. This is of course not even remotely true in any practical sense. I have not received an explanation for how it's even possible when sprint targets are intentionally set at slightly more than was done in the previous sprint, every sprint. permalink fedilink source parent hideshow 2 child comments replies: [–] Hazzard@lemmy.zip 3 points 10 months ago Haha, you're not wrong. Ours tend to ebb and flow with whatever urgent priority upper management has set as well, and it tends to take slack alongside our tech debts. Our management is listening and getting better though, I'm hopeful that in a few years we truly will catch up on our tech debts and have all our managed products in good shape at once. That said, even in that environment, we've had some pretty incredible 20% success stories. Some of my own experiments from when I've had the time have become proper released features, although I mostly use it to skip the bureaucracy and address my pet peeve tech debts, which isn't the point but is nice to be able to do. And one of our major internal products, with a large dedicated team and roadmap, began as one developer's 20% project a few years back. permalink fedilink source parent [–] Tanoh@lemmy.world 3 points 10 months ago There is a saying (paraphrasing) that sadly is almost never implemented. "Don't tell your employees what to do, hire really smart people and listen to their ideas" permalink fedilink source parent [+] that_leaflet@lemmy.world 4 points 10 months ago* (last edited 9 months ago) [deleted] permalink fedilink source parent [–] Bakkoda@sh.itjust.works 2 points 10 months ago I think it about shouldn't be encouraged. Leave it at that. If they felt the need then by all means. permalink fedilink source parent [–] null@lemmy.nullspace.lol 2 points 10 months ago Let the man have his hobby. permalink fedilink source parent [–] BuboScandiacus@mander.xyz 0 points 10 months ago That was just a passion project and he surely got compensated (probably indirectly) for it after release permalink fedilink source parent
[–] Minnels@lemmy.zip 21 points 10 months ago (1 child) Maybe it wasn't considered work for this person? They wanted to try and do something better in their own time. I am not saying they shouldn't be compensated but doing something of your own will doesn't have to be work, it can be fun. permalink fedilink source parent hideshow 2 child comments replies: [–] princessnorah@lemmy.blahaj.zone 7 points 10 months ago Alongside that, it seems like there's a good chance that next time, they'll be the goto for doing this sort of porting. permalink fedilink source parent
[–] princessnorah@lemmy.blahaj.zone 7 points 10 months ago Alongside that, it seems like there's a good chance that next time, they'll be the goto for doing this sort of porting. permalink fedilink source parent
[–] Hazzard@lemmy.zip 18 points 10 months ago (2 children) The best companies will do something like "20% time", leaving one day a week or something to work on whatever, which is fantastic for stuff like this. Some of your employees almost certainly have the best ideas, if you just trust them with the space to prove them out. Great way to get cool stuff like this without unpaid labour. permalink fedilink source parent hideshow 4 child comments replies: [–] vithigar@lemmy.ca 6 points 10 months ago* (1 child) The place I work says they do this and will claim with a straight face that our sprints are budgeted to allow approximately 20% slack time. This is of course not even remotely true in any practical sense. I have not received an explanation for how it's even possible when sprint targets are intentionally set at slightly more than was done in the previous sprint, every sprint. permalink fedilink source parent hideshow 2 child comments replies: [–] Hazzard@lemmy.zip 3 points 10 months ago Haha, you're not wrong. Ours tend to ebb and flow with whatever urgent priority upper management has set as well, and it tends to take slack alongside our tech debts. Our management is listening and getting better though, I'm hopeful that in a few years we truly will catch up on our tech debts and have all our managed products in good shape at once. That said, even in that environment, we've had some pretty incredible 20% success stories. Some of my own experiments from when I've had the time have become proper released features, although I mostly use it to skip the bureaucracy and address my pet peeve tech debts, which isn't the point but is nice to be able to do. And one of our major internal products, with a large dedicated team and roadmap, began as one developer's 20% project a few years back. permalink fedilink source parent [–] Tanoh@lemmy.world 3 points 10 months ago There is a saying (paraphrasing) that sadly is almost never implemented. "Don't tell your employees what to do, hire really smart people and listen to their ideas" permalink fedilink source parent
[–] vithigar@lemmy.ca 6 points 10 months ago* (1 child) The place I work says they do this and will claim with a straight face that our sprints are budgeted to allow approximately 20% slack time. This is of course not even remotely true in any practical sense. I have not received an explanation for how it's even possible when sprint targets are intentionally set at slightly more than was done in the previous sprint, every sprint. permalink fedilink source parent hideshow 2 child comments replies: [–] Hazzard@lemmy.zip 3 points 10 months ago Haha, you're not wrong. Ours tend to ebb and flow with whatever urgent priority upper management has set as well, and it tends to take slack alongside our tech debts. Our management is listening and getting better though, I'm hopeful that in a few years we truly will catch up on our tech debts and have all our managed products in good shape at once. That said, even in that environment, we've had some pretty incredible 20% success stories. Some of my own experiments from when I've had the time have become proper released features, although I mostly use it to skip the bureaucracy and address my pet peeve tech debts, which isn't the point but is nice to be able to do. And one of our major internal products, with a large dedicated team and roadmap, began as one developer's 20% project a few years back. permalink fedilink source parent
[–] Hazzard@lemmy.zip 3 points 10 months ago Haha, you're not wrong. Ours tend to ebb and flow with whatever urgent priority upper management has set as well, and it tends to take slack alongside our tech debts. Our management is listening and getting better though, I'm hopeful that in a few years we truly will catch up on our tech debts and have all our managed products in good shape at once. That said, even in that environment, we've had some pretty incredible 20% success stories. Some of my own experiments from when I've had the time have become proper released features, although I mostly use it to skip the bureaucracy and address my pet peeve tech debts, which isn't the point but is nice to be able to do. And one of our major internal products, with a large dedicated team and roadmap, began as one developer's 20% project a few years back. permalink fedilink source parent
[–] Tanoh@lemmy.world 3 points 10 months ago There is a saying (paraphrasing) that sadly is almost never implemented. "Don't tell your employees what to do, hire really smart people and listen to their ideas" permalink fedilink source parent
[+] that_leaflet@lemmy.world 4 points 10 months ago* (last edited 9 months ago) [deleted] permalink fedilink source parent
[–] Bakkoda@sh.itjust.works 2 points 10 months ago I think it about shouldn't be encouraged. Leave it at that. If they felt the need then by all means. permalink fedilink source parent
[–] null@lemmy.nullspace.lol 2 points 10 months ago Let the man have his hobby. permalink fedilink source parent
[–] BuboScandiacus@mander.xyz 0 points 10 months ago That was just a passion project and he surely got compensated (probably indirectly) for it after release permalink fedilink source parent