Doc Avid Mornington

Not actually a doctor.

  • 0 Posts
  • 226 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle


  • Bringing up his actions in a different job doesn’t really seem to have bearing on comparing administrations. Biden has a pretty bad history prior to his presidency as well.

    But also, and more importantly, judging progressiveness just by final results, without referent to the era, is not useful. By this logic, the Biden administration could literally be rolling back progress, and as long as they don’t go too far, we’d still have to call them “more progressive than FDR”. The only useful way to judge progressiveness is as progress made - or at least progress worked for - from the starting baseline.

    I think it’s reasonable to say Biden has had the most progressive administration since LBJ. I was really surprised by how good he’s been, relative to my expectations.



  • I get what you’re saying, here. That’s why I specifically disclaimed making any judgement about whether it would be moral, or wise. But consider the other side of that same coin: the court did this specifically to overthrow democracy and allow Trump, or any other president who will carry out Project-2025 to use this power to maintain an effective dictatorship. There’s no other explanation for this ruling. Would using this absurd power once, now, to restore a court that is loyal to the Constitution and People of America, be worse than letting Trump get in, assassinate any and all opposition, and end democracy? Could we trust it to end there? Would Biden install justices that would immediately reverse the ruling and bring things back to normal, or just install his own loyalists? I dunno, it’s complicated.

    Ultimately, it’s also all just theoretical, anyhow. I find it almost inconceivable that Biden would do this.


  • If your SQL model has nulls, and you don’t have some clear way to conserve them throughout the data chain, including to the json schema in your API contract, you have a bug. That way to preserve them doesn’t have to be keeping nulls distinct from missing values in the json schema, but it’s certainly the most straightforward way.

    The world has more than three languages, and the way Java and Python do things is not universally correct. I’m not up to date on either of them, but I’m also guessing that they both have multiple libraries for (de) serialization and for API contract validation, so I am not really convinced your claims are universal even within those languages.

    I am not the other person you were talking to, I’ve only made one comment on this, so not really “hellbent”, friend.

    Yes, I am pretty sure I read the comments, although you’re making me wonder if I’m missing one. What specific comment, what “case specified above” are you referring to? As far as I can see, you are the one trying to say that if a distinction between null and a non-existent attribute is not specified, it should universally be assumed to be meaningless and fine to drop null values. I don’t see any context that changes that. If you can point it out, specifically, I’ll be glad to reassess.


  • Is that an act of an insane person? It’s apparently legal, now. Do you broadly think that using violence against tyranny is insane? Our founders committed their lives and fortunes to the violent overthrow of tyranny. It would be much easier, sitting in the oval office, with legal authority granted to him by the very people he would be targeting, to authorize the extrajudicial execution of a few traitors. Do you think that extrajudicial execution is insane? Then you’ll have to admit that most presidents in the last few decades were insane, especially Obama. Is it only insane when the target is white people in power, rather than brown-skinned people overseas?

    I’m not commenting, at this time, on whether it would be moral, or wise, but insane? I can’t see how.






  • At the (SQL) database level, if you are using null in any sane way, it means “this value exists but is unknown”. Conflating that with “this value does not exist” is very dangerous. JavaScript, the closest thing there is to a reference implementation for json serialization, drops attributes set to undefined, but preserves null. You seem to be insisting that null only means “explicit omission”, but that isn’t the case. Null means a variety of subtly different things in different contexts. It’s perfectly fine to explicitly define null and missing as equivalent in any given protocol, but assuming it is not.





  • What? Your colleague sounds like they may be struggling with some serious cognitive issues, they may want to see a doctor about that. As for me, I’ve been living with my brain my entire life, and have kept several different sleep schedules in that time, for one reason or another, including rigid adherence to a schedule you would certainly approve of, and at no time has the basic fact that my brain works better later in the day ever changed. Some people never learn that their own circumstances and experience are not universal. Maybe try not to be one of those people.




  • It’s better to have useful comments. Long odds are that somebody who writes comments like this absolutely isn’t writing useful comments as well - in fact, I’m pretty sure I’ve never seen it happen. Comments like this increase cognitive overhead when reading code. Sure, I’d be happy to accept ten BS useless comments in exchange for also getting one good one, but that’s not the tradeoff in reality - it’s always six hundred garbage lines of comment in exchange for nothing at all. This kind of commenting usually isn’t the dev’s fault, though - somebody has told a junior dev that they need to comment thoroughly, without any real guidelines, and they’re just trying not to get fired or whatever.