finance ff

  “Wow! This was so cool!” my friend says. “ How do you even find these things ?” I tell him that I got it from the newsletter of <so-and-so> website where people post interesting stuff. And the next question goes, “Well, but how did you find out about the <so-and-so> website?” And then I end up telling him about this person on Twitter whom I follow and how she tweets interesting things and how she is SO cool. “Okay but how did you find out about this person?” … And every time, the conversation comes to an abrupt end either because my friend stops asking further questions at the risk of seeming too dumb (and ends up giving me an unsatisfactory “Oh Wow” reaction) or because I fail to remember the exact source (and end up telling something along the lines of — “I just found it while… hmm… browsing on the Internet”). What I also want to say is that these cool webpages/people that I come across can come to anyone. But that sounds like patronizing. Not helpful. And I want to...

  Recently, I undertook the task of migrating the Android codebase at  Kure  to AndroidX. It seemed like the perfect opportunity to try and fix the build speeds of the project. Gradle has always had a bad rep for being slow and resource-intensive, but I was quite surprised at how minor changes to the project’s build configuration could massively improve the build speeds. To give you a sneak peek of the time I was able to shed from our clean builds, here’s a before and after metric from the build scan. pre-optimisation 🐢🐢 post-optimization ⚡️⚡️ Going down from 5.5 minutes to  17 seconds?? That’s bonkers It’s easy to go overboard with optimizations that you can perform to bring down your build time even further. But I am going to intentionally focus on the minor, painless measures I took to come close to this metric for the sake of keeping this post, beginner-friendly. But first! Before starting off with the optimization, it’s important to benchmark our project to se...

  I am about 3 months into my  journey  as a new software engineer. I work at a place where the bar is high for what it means to craft quality software. My peers are well-educated and highly disciplined engineers with many years of experience. Those conditions alone would be enough to cause someone new to wonder things like “Am I good enough to be here?” or “Will I be able to keep up?” To top it off, however, I have the fact that my background in software is non-traditional. My degree is in music and I am self-taught in programming. You can probably imagine the kind of impostor syndrome  that someone in my position might feel when surrounded by people who are so smart and credentialed. The self-doubt could have been paralyzing. But, somehow it didn’t last very long at all. So, how did that happen? How did the doubt give way to the enthusiasm to learn and grow that I mostly feel today? I made a list of 31 experiences that helped me embrace being new and non-tradi...

    https://kaspermovies.biz/   https://clrur.com   https://stephealthlife.com