I get it, but the quality of headphones with cords has gotten so bad that the male jacks wouldn't last more than a few months. My son has gone through an untold number of corded headphones because his school iPad is too locked down to use bluetooth ones.
You can spend a little more and get headphones with a replacable cord, and replace the cords if they get broken. Or maybe take the time to solder new connectors onto broken cords.
I spent nearly 2 years at a major pharmacy chain trying to implement various solutions for them and going in circles. Meanwhile, the entire construction of Epic Universe in Orlando took place. I've moved from realist to cynic. In fact, I'm not even working and may just be retired at this point. I just couldn't get past certain things about how these gigs have gone for the most part--so much waste.
I know!!!!!! I've been yelling about this for years how impossible to uplift JVM versions is because of how products were built! It's so crazy. Lots of obfuscated jars went unsupported after like Java 7.
I liked Groovy, but Kotlin was the better successor. Scala was beyond ridiculous as far as learning curve--crazy language. I always thought Java sucked and I spent far too much time working with Java (because money) and having to deal with framework on top of framework as well as all those idiotic design patterns that seemed so important only for me to realize years later that it was all basically a waste because OOP itself is a waste. I was writing better code in Python and Go five years ago without needing those all-important design patterns (okay, a few still translate). I just didn't know it at the time how horrible the situation was in Java. In hindsight, everything about Java was someone's money grab that I was dealing with. Mockito did help me a lot through those times, but I wish I had never gone through them at all!
Unfortunately it also constructs dependencies per request instead of singletons, so you have to rely on hacks like `@lru_cache(maxsize=1)` on the factory functions.
I'd really like to see a Python framework that embraces class-based controllers to do away with this problem; beyond that writing a dependency injection system is not too difficult of a task (the last time I did it for a hobby project many years ago, it was around ~150 lines of code).
Hey, fwiw, thank you for all of your hard work! Mockito and Powermock helped me be a big hero at one company I worked for 2011-2014. Before I arrived as a tech lead there, they had ZERO tests. The QA cycle was weeks, even months long. I instituted a whole new regime of unit and intergration testing for all the applications I was responsible for. Within one release cycle, the bug counts fell to nearly zero and the QA cycle basically became a verification step because there were no more bugs. The only way I was able to pull that off was using mocking and some clever powermock hacks because the code was otherwise untestable and thus un-refactorable. So, thanks!
Pretty sure Powermock is dead in the water now, it did some pretty gnarly things (like patching `Object`) that flat out didn't work in later versions of Java.
I (ironically enough) spent some time replacing usages of it in Kafka test code with Mockito because of this, IIRC there was only one situation where Mockito couldn't easily replace Powermock and I'm pretty sure it was mocking out a private static method, so the solution was to refactor the code under test so that you didn't need to mock a private static method to test it.
You are not allowed to decide how everyone else should live. But just for the sake of argument, take a trip to Montana and get back to me on how well universal EVs would work in much of the US. They're fine for urban and suburban areas. They aren't so great for agricultural work, and certainly not great for people who live in places you probably haven't visited. I don't even think EVs are a solution for people in Nebraska, let alone places where the weather gets really extreme.
reply