• 0 Posts
  • 173 Comments
Joined 2 years ago
cake
Cake day: August 7th, 2023

help-circle





  • It really comes down to the calculus of how much I like them vs what did they actually do (with some things being truly unforgivable).

    For example, Sylvester Stallone recently came out in big support of Trump. To me, that makes him a huge ass. That said, I’ll still watch Rocky 4 if it comes on (all the while, in the back of my head thinking “wow, really, Trump… that’s your guy?”). So my perception of him and his movies change, but also it’s his right to be an idiot.

    In the same vein, Rob Schneider has recently made his whole personality a bitter old conservative "comic’. He really brings little of value to the table, so he can easily be dismissed. His value/drama ratio isn’t worth giving him the time of day – we’ll outside of this example.

    I can’t totally divorce the person from their content, but I try when their stuff is great and what they did isn’t too repulsive.




  • Recently switched to a new contract, which resulted in me switching from IDEA Ultimate to vscode. This picture is terribly accurate.

    In intellij I usually do code reviews by checking out the code and comparing the branch to origin/main to step through the changes. Just a right click menu option to compare branches.

    I took for granted that this is just a thing IDEs should do, so I looked in vain for a while before googling it and finding out I need a plugin for that. (If I’m wrong please help me find the button, I still believe it must be in there somewhere. Surely the owners of GitHub can compare branches?)







  • It sounds like you need your own API with some sort of persistent store. You may be able to reuse what you’ve done as the view layer?

    If this were something I was going to tackle, I’d start by identifying the types of users (authors, admins, users, etc.)

    Then I’d think about the kinds of workflows those users are going to need to do. E.g. admins can edit or delete anything, authors can alter their own content, users can only view data, etc.

    Now with some loose requirements in mind, start thinking about how to solve the problems for your users. This is when you start evaluating what technology might be a good fit for your problem domain.

    You could probably throw together a trivial API that only you can publish to fairly quickly if that is sufficient for what you are trying to do. I dare say chatgpt can spit out a simple rest API in whatever language you like quickly and pretty accurately.

    I wouldn’t chase making a static website tool dynamic. That will almost certainly end in heartbreak.