• 0 Posts
  • 59 Comments
Joined 11 months ago
cake
Cake day: August 4th, 2023

help-circle



  • This kind of information is all suppressed now, but early on when Facebook only had likes, there was a lot of discussion on how downvotes weren’t really needed. It was believed that people engaged more with content they enjoyed, and ignored unfavorable content.

    This is wildly wrong. People obsessively engage with content they hate, to the extent that it probably makes more sense to only have a down vote button. Everyone knows that now, and the big sites uses psychological studies funded by casinos to gamify engagement, entirely in the pursuit of click-pennies.

    What do votes mean? On lemmy it seems nothing. On other sites they mean revenue for the owners.



  • I made a static site with Hexo a few years back. I thankfully didn’t make any “Get started with Hexo” posts but I did only really use it for a few months. I think that puts me in the cluster with the “switch from Jekyll to Hugo” people. Now it just sits there, absorbing some money every two years for the “personal website tax”.

    Shame too, I constantly think I need to get back to it. Hexo is nice, popular with Chinese users I think. I don’t recall now why I liked it over Jekyll or Hugo, but I’ve always loved an underdog. Once I got the hang of using it, it was very customizable and fun to work with.



  • I really enjoyed this game back when, and replayed it a couple of years ago. Very unique RTS mechanics and engine, I’m excited to see this open sourced!

    Perimeter had several weird gimmicks. Bases must be built on terrain that has been flattened with a terriforming tool (voxel/heighmap manipulation of the landscape is part of the game.) The titular permiter is an energy shield that you can put up around your entire base. There’s also only 3 basic units, but units can be fused together (and separated back out) to make more advanced units on the fly.

    The terraforming-as-war approach is neat and I’ve always been surprised that more games don’t try to incorporate similar mechanics. The multi-units are interesting but to me suffer a similar issue as games with many guns but only one kind of ammo. By the time you’ve decided to switch tactics, you might already be too low on basic units of one type to change into what you need.



  • Codex@lemmy.worldtolinuxmemes@lemmy.worldBackdoors
    link
    fedilink
    arrow-up
    169
    arrow-down
    1
    ·
    3 months ago

    I’ve gotten back into tinkering on a little Rust game project, it has about a dozen dependencies on various math and gamedev libraries. When I go to build (just like with npm in my JavaScript projects) cargo needs to download and build just over 200 projects. 3 of them build and run “install scripts” which are just also rust programs. I know this because my anti-virus flagged each of them and I had to allow them through so my little roguelike would build.

    Like, what are we even suppose to tell “normal people” about security? “Yeah, don’t download files from people you don’t trust and never run executables from the web. How do I install this programming utility? Blindly run code from over 300 people and hope none of them wanted to sneak something malicious in there.”

    I don’t want to go back to the days of hand chisling every routine into bare silicon by hand, but i feel l like there must be a better system we just haven’t devised yet.



  • I worked at a place where I did the not-funny-but-serious-and-banal version of this bit, including the burnout breakdown at the end. I’m working on ERP systems now and it’s a lot less stressful, plus things just have normal names like “Accounting Module” or “Third Party X Service Connector”.

    I did love Galactus though


  • As a senior at my last big company job, basically all I did was conduct meetings and do PRs. It’s such a grind.

    My opinion now is that most PR is worthless anyway. Most people give, at best, a superficial skim for typos, lack of comments, or other low-hanging replies (that usually, really, a static checker or linter should be dealing with).

    Reading the code base in little chunks like that doesn’t give you proper context for the changes you’re reading. Automated unit and integration tests would be better for catching issues like that, but of course then who is reviewing and verifying the tests? Who’s writing them for that matter?

    Ideally, pair-programming or having extra people on projects to create knowledge redundancy would help. But companies want to replace juniors with AI now, so that’s not looking good. Senior devs and architects might know the major pieces of much of the code, but can they “load it into working memory” sufficiently to do a quality PR that will catch something the tests didn’t and QA wouldn’t? Not in my experience.

    I think the best actually-implementable solution for most teams is to get rid of PR expectations and take a multi-pronged approach to replacing that process.

    1. use tooling to check for and fix basic stuff. Use a linter, adopt a code standard, get a code formatting tool that forced adherence to the standard and run it on every PR.
    2. Unit tests if you got them, start if you don’t. You don’t need 90% code coverage, just make sure critical paths are covered.
    3. Turn one of your useless meetings into a code review session. Each week/sprint, one Very Important Code section is presented by the developer that works on it most or that last changed it. This helps the whole team learn the code base, gets more eyes on the important stuff regularly, and enforces not just a consistent style but a consistent approach to solving and documenting problems.
    4. PR (and the github PR approval stuff or its equivalent for you) should be streamlined but preserved. Do have a second person approve changes before merging, just to double check that tests have finished and passed and all that. If your team is so busy that no one ever approves PRs then allow self-approval and be done with it. This will make regular code review very important for security and stability, since any dev could be misbehaving unseen, but these are the trade-offs you make when burning out your team is more important than quality.






  • Pick a library you already use with many sub-dependencies. Make a new library with your evil code. Name it in line with the step 1 library. Oh hi there “Framework.Microsoft.Extensions.DB.Net.Compatibility” you couldn’t possibly have anything bad going on in you, plus you sound really boring to review, I’m sure it’s fine.