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

help-circle

  • That your company has an in-house software dev team is impressive. Does the revenue-generating business have access to that team?

    Not OP, but in a similar situation. We have in-house dev for both tooling/infrastructure as well as revenue generation. For better or worse, leaders have neglected the software tooling and infrastructure that we use to build and deliver our revenue generating software for decades. Some serious cracks in the foundation showing and we might finally start fixing things.



  • I feel this in my bones. Even before the recent round of restructuring we’ve had a significant about of turnover. Our infrastructure is a massive rube golberg machine with multiple houses of cards built on top of it. Institutional knowledge was never written down and it has been leaving the company at an accelerating rate over the past 5 years. Tons of “new blood” making lots of assumptions on how things work is resulting in… humorous end results.




  • I suggest something where you get to work with a wide range of the populus. Opportunities are basically all service industry jobs: waiting tables in a restaurant, working retail, working in a hotel, etc. Learning how to interact with wide swaths of humans is an invaluable skill that will serve you well in your future professional career. I would focus on building social and emotional intelligence.





  • We have a test environment but it’s a hot mess. All the data is made up and extremely low quality. All the things you would normally interface with are also in test, but getting other teams to coordinate testing in the test space is… a chore. We do the best we can with mock services, but without having real services or representative data some of the data pattern assumptions don’t play out. Leaders value writing code and our lack of architects that span teams mean that when team architects either don’t meet ahead of time, make assumptions, or don’t ever agree on a design then…

    We always host UAT. We also track logins. Guess how many users even show up for UAT, let alone actually click on anything.

    This is why the vast majority of our testing happens in prod when our users are doing real work.

    Sorry for the baby rant :)


  • This can also be one of the frustrating parts of open source.

    Find something you don’t like? Fix it. Will the repo owner approve your pull request? Who knows. Maybe they’re a bit absentee. Maybe they view the original behavior as working as designed. Maybe your design doesn’t fit their architectural model, so they’ll (eventually) heavily refactor your changes and merge them in.

    You can always stand up a fork, but keeping those two at feature parity and going in the same general direction can become harder and harder with time.

    That’s not to say not to try! But it also means reaching out to the repo owners/maintainers before making your first change.






  • Rinsing rice does wonders. Without a rice cooker you’ll need to strain it, but it’s still worth it.

    1. Measure rice by volume. Let’s say 2 cups worth
    2. Put into fine colendar and rinse until the water comes out clear. Mixing with your hand will speed this up. You can also do this in the pot you’re going to cook in and dump water out
    3. Put strained rice in your pot
    4. Add cold water. The ratio of water to rice matters a lot and varies by species of rice. The ratio will be printed on whatever container your rice came in. For Jasmin rice it’s 2 water to 1 rice, so for our two cups of rice you’ll need 4 cups of water
    5. Cover, turn on medium-high heat, being to boil. Don’t go far because it will boil over when it does boil
    6. Turn the heat down to low, crack the lid, and set a timer. The amount of time needed will vary based on rice. For Jasmin, 15 minutes is a good check-in time
    7. Pop the lid. See water bubbling up? If yes, replace lid and come back in a few minutes. If not, use a wooden spoon to get a peek at the bottom of the pot. See water? If yes, replace lid and come back fairly soon to check again. If not, your rice is done. Turn the heat off, fluff, enjoy.

    We made rice for years using this method and it is a very reliable cooking method. Rice doesn’t really leave you a lot of wiggle room though, which is where a rice cooker comes in handy. As an added bonus, some rice cookers come with water lines in them. I measure my dry rice into the cooker, rinse using the cooker, dump most of the water out, and fill to the appropriate level.

    Different species of rice have very different textures and somewhat (subtle) different flavorss.

    Some rice, like basmati, can be cooked using the pasta method (intentionally use way too much water and strain the excess off after the rice is cooked). I guess all rice could be cooked that way, but you would be giving up some starch.




  • I really hope the snapdragon x laptops gain some traction. I recently went laptop shopping and what I wanted (good to great display, stays cold, good battery life) line up really well with a MacBook/MB air. I just couldn’t stomach the stupid mark-ups for memory and storage. I wound up with a Lenovo 7x slim. Upgrading to 32 GB memory and 1 TB storage was around $115. The non-emulated performance on windows is solid. Emulated is generally ok for my usage. I’m probably going to try Linux on it when I have a light week, but I’m somewhat wary of the impact that will have on battery life.