• 0 Posts
  • 77 Comments
Joined 2 years ago
cake
Cake day: December 20th, 2023

help-circle

  • I’ve been using cannabis for years and I love it. I am generally careful when it comes to developing dependencies. I check myself every once in a while and I don’t self medicate or pretend I’m taking it for pain or sleep or whatever. I take it because I like being high and I’m not ashamed of it.

    I am worried about long-term effects. Alzheimer’s and Parkinson’s really freak me out and it would suck if there turned out to be a link there. But there’s a good chance something else will kill me before I get there and I’m not sure I want to give up something I so thoroughly enjoy just to live a little longer.

    I tried taking a hiatus in January. I read about mental clarity coming back and feeling more rested. I felt none of those things. I also didn’t feel any intense cravings or withdrawal symptoms. Just boredom and dissatisfaction with life in general and I don’t have a lot of hope of that changing with or without weed.



  • I work at a mid-tier B2B tech company. I specialize in frontend but am otherwise a full-stack engineer.

    My big project over the last two-ish weeks was building a demo environment for one of the company’s products. It involved:

    • Updating some configurations in our backend to ensure the database can store the information for the demo sessions.
    • Writing a class to represent these demo sessions, acting as an interface between the database and runtime environment.
    • Building sets of endpoints so that our products’ frontend can interface with the server.
    • Building a system on the frontend that regularly syncs with the backend on the state of the demo session and provides it to the UI.
    • Building a pretty UI that shows the user the current state of the demo session and lets them update it.
    • Writing unit tests to ensure every individual component of the system works as it’s expected to.
    • Manually testing the system as a user to ensure it’s all working together as expected.
    • Writing a summary of my work and submitting it for review by my coworkers, discussing and applying any feedback given.
    • Deploying my work to production and confirming it’s all still working as expected.
    • Praying to every God that there is no bullshit issue I missed somewhere and will have to take accountability for later.

    Along the way, I got several other smaller tasks, like updating logic in one of our algorithms, adding internal tooling so that the customer service team can stop bugging engineering to fix things and just do it themselves, hypothesizing on the sources of random bugs and updating documentation. In between all that, I’ve got meetings to discuss random other bullshit.

    Still lots of coding, but at this point in my career it’s more about knowing how my company’s systems work together and how to take an idea and turn it into usable software.