• 0 Posts
  • 49 Comments
Joined 2 years ago
cake
Cake day: July 4th, 2023

help-circle
  • Gift cards are for people who you are obligated to buy something for, but don’t really like enough to put in any effort. They are a way of telling people, “I like this company more than I like you. I could have just given you money, but I couldn’t be bothered to shop for you, but I really wanted to make sure that any money I had to spend on you went to this company.”
    If you don’t believe me, why would they just give you a universal gift card? Did you know that they have been making them right here in the USA for a couple hundred years now? They even have decorative pictures of us presidents on them. And they are not just good in the US, you will find that they are taken most places on the planet.







  • There are plenty of things that you deal with on a daily basis that are significantly more dangerous than asbestos. And if it had been treated like the hazardous material that it is as soon as we knew it was hazardous, then it would still be used just like all the other hazardous shit we deal with daily. However, as is the usual story, companies not only hid what they knew, but outright lied about its dangers. They called it a miracle material with no downsides. And it is amazingly good at what it does, so it was put in fucking everything, much like AI is today. And so people died for profit. A lot of people.













  • I don’t know about intellij, I have worked mainly in VS Pro. I will tell you some of The things I can do in VS that help and then I’m sure intelliJ probably has similar functionality or plugins that will add it. Check to see if you can generate call graphs or call maps. VS enterprise has the ability to add each function to a graph and build up a diagram for you. Unfortunately pro and standard do not.
    Ctrl + “-” will jump back to last. This allows you to reverse through the call tree.
    You should be able to display a call stack that at least tells you how you got down to where you are.
    Make notes about reimplements you want to make and move on. Sometimes just writing it down so you won’t forget is enough for my brain to let it go.
    In VS Pro you can create a break point and then right click on the red break point dot and add conditions and\or actions. Conditions stop it from breaking there unless a condition is met, this is great when you only want to catch one iteration of a loop. Actions are something that will be evaluated and done like printing out information “$FUNCTION, myvar {my var}” will print out current function name, myvar, the value of myvar". You will be surprised how complex of a variable it will print. For instance it may print out an entire structure or contents of a class. You can then set the action to not break, that way the code performs the action and keeps going. Doing this will allow you to generate as detailed a list as you want of breakpoints in the order in which they get hit plus any variables you want to track.