• 0 Posts
  • 7 Comments
Joined 1 year ago
cake
Cake day: July 31st, 2023

help-circle

  • “In October 2021, Governor Greg Abbott hosted the lobbying group Texas Blockchain Council at the governor’s mansion. The group insisted that their industry would help the state’s overtaxed energy grid; that during energy crises, miners would be one of the few energy customers able to shut off upon request, provided that they were paid in exchange.”

    Incredible. Driving up energy needs to make their fake currency will help the state’s energy grid, because we can then hold the grid hostage until we’re paid.


  • I see two possible reasons for your situation. One is that the company is turning to contractors to fill in gaps in their knowledge/experience, which is why everyone else has no clue how to tackle these tasks and why they get assigned the easy ones.

    The other possibility is that the senior devs are gaming the metrics, letting the employees knock out easy tasks while the contractor is stuck with untangling the knots of the more intractable tasks.



  • You can generally rely on a header file doing its own check to prevent being included twice. If a header doesn’t do that, it’s either wrong or doing something fucky. It is merely a convention, but it’s so widespread that you really don’t need to worry about it.

    You are mixing up some terms, so I want to help clarify. When you #include a header file, you aren’t importing a library. You are telling the compiler to insert the contents of that header file into your source where the #include line is. A library is something different. It is an already-compiled binary file. A library should also come with a header file to tell you what functions and classes are present in the library, but that header isn’t itself the library.

    It may seem annoying to have to repeat yourself between headers and source, but it’s honestly something you get used to.