Yo whatup

  • 0 Posts
  • 84 Comments
Joined 1 year ago
cake
Cake day: September 28th, 2023

help-circle




  • I poked around in the registry a bit too much awhile ago and managed to delete my only user. Oops! Completely bricked my install, couldn’t even unfuck it with safe mode shenanigans. Had enough space to clone my entire drive so I just lost a couple days of time fiddling with it, only a couple hours actually copying my shit back and forth.


  • Ah, r/unpopularopinion one of the subs I almost never visited cause 90% of the stuff on there was just plain stupid.

    For my part, I don’t think there’s a large gulf between racist opinions on the two platforms, just on decorum regarding slurs.

    Yeah. I’d probably make the argument that 4chan is just open about the racism while other platforms like reddit have at least some enforcement leading to it being less blatant.


  • I mean like most of us I came from Reddit. If I knew which sub the post was in I’d have a pretty solid opinion but as is I’d assume they probably got downvoted to hell for some unfair reason. Happened to anyone active on occasion so it wouldn’t be surprising. Since it has so many up votes I can’t imagine, without the context of the particular sub, that they weren’t just getting piled on.





  • Eh? How’s that work. I’m not going to sit here and say there isn’t too many factories in Java but as a concept it’s extremely useful. You hand off a “factory” to something which actually creates the object. This is really useful in for example serialization. How so? You could register factories (mapped to some sort of ID) which get passed the serialized data and return some sort of created object. Now the core serialization code doesn’t know nor care how exactly any particular type gets serialized. Pretty nifty huh?

    Some languages have better ways to encapsulate this functionality but that’s what the factory concept is


  • No python is statically typed. You have type hints, which makes the language tolerable but like their name implies it’s a hint at the type. You can perfectly legally pass in something completely different that doesn’t conform whatsoever.

    The primary thing static languages provide is static typing, that being the ability to determine before runtime that all the types are valid. A good example of this is how C++ programs will refuse to compile if you try to invoke a method that doesn’t exist on the type. That’s because it’s statically typed. At compile time you know that the code is wrong. Dynamic languages fundamentally don’t work like that. You cannot know until runtime if the method you called or the field you are trying to touch exists or not. Again type hints help a lot with this but that doesn’t change how the language actually operates.



  • So the big important part of git is that it’s a collection of commits. A branch is just a labeled commit and each commit is a list of what changed from the parent. Rebasing (the most confusing one for people) is when you fiddle with a commit from underneath yourself. Or in even more simple terms editing a parent commit. Rebasing is extremely powerful but most useful for when you notice a bug you wrote a couple commits ago. Fixing such issues via rebase (or !fixup commits you auto squash at the end) keeps your history clean. It’s as though you never wrote the bug. The other thing you do a lot with rebasing is moving your branch up in the history cause somebody updated the remote.





  • It’s complicated. Paul isn’t really a good guy, but he’s not really a bad guy either. He’s just a dude. He’s a dude who has limited vision into the future from which he cannot escape. He’s not using his future vision to pick the bad choices he’s trying to pick the best ones he can and the hand he’s dealt kinda just sucks.



  • Um what? I didn’t like hide extra meaning in what I said. High quality code doesn’t imply all that extra shit you added. It’s code that’s easy to read and modify. Typically this just means you name stuff well and document things that aren’t obvious. Usually my docs explain why something exists since thinking it’s unnecessary cause you don’t remember what the original problem was a common occurrence before I started doing so.

    Is high quality code ran through a formatter? I’d hope so yeah. There should be a consistent code style across the entire project. Doesn’t matter what it it long as it’s consistent.

    100% code coverage is meaningless and as such a pointless metric. Also 100% coverage is explicitly tied to the implimentaion as all code paths have to be reached which is obviously not a good idea (tests have to change when the implimentaion changes as you’re testing the implimentaion not the api).

    Really a lot of this is just meaningless buzz words as an attempt at some sort of gotcha. Really don’t understand how you even interpreted a statement so simple in this way.