• 3 Posts
  • 233 Comments
Joined 2 years ago
cake
Cake day: March 3rd, 2024

help-circle



  • Kotlin has been the right way to make Android apps for 5 years now and a first class citizen for far longer. Kotlin Compose has been the right way to make UI on Android for about 3 years. going back to Java will ultimately hurt you and will be coming from either a very opinionated, controversial source or something that is way out of date.

    i started on Android in 2012, and Kotlin + Compose is just better. also, tutorials are a dime a dozen since they’re generally AI slop or just recreations of the official docs. i hesitate to take a “git gud” stance, but learning from official docs is a career skill.

    speaking of AI slop, i don’t think it’s the worst idea to get an LLM to guide the learning experience. use it like a calculator: it’s not an excuse not to learn; it’s a tool to help you learn, even if it will to some extent do the work for you.





  • i’ve been using FitBod for ~4 years now. started with a similar setup, and now i have to go to the gym to challenge myself. it will suggest progressions over time, but you’ll find what’s right for you over time. it really depends on your goals, which in my experience will change over time if you stick with it. keeping a log and generating workouts is most of what i use the app for.

    you also don’t just increase linearly. increase reps then weight, but then go down in weight to work on technique. don’t give into ego lifting and use your full range of motion. setbacks are also normal. practice self-forgiveness, but come back hard next time.

    i went from an overweight slob who never worked out to being the guy most people assume is an athlete. this is just my experience, but progress is possible.



  • other commenters have hinted at this, but the main point of most of the good advice is this: don’t use the system Python install (ie the one from apt) for development. uv is my go to, but the idea behind *conda, pyenv, asdf, etc is the same. the underlying OS shouldn’t be an issue; you should be able to ship the code between OSs and build just fine, ideally.


  • generally speaking, i think it’s good practice to find several recipes and compare and contrast them. you’ll find opinions and get a sense for what the writer’s priorities are (quick, fewer dishes, what they usually have in the pantry, etc) and can figure out which writer has similar priorities to you. or just synthesize a recipe from those sources. this does require some technical know-how, but i think this is a good skill to have.


  • the first issue is familiar to me as my first laptop had this issue, while running Windows XP. the fans were going out and simply couldn’t move enough heat. the solution then that mostly worked was one of those laptop stands with fans built in. it worked most of the time, but a real solution might mean cleaning out the chassis and maybe replacing the fans.

    for the second, i didn’t really have trouble setting up the Nvidia drivers just following the docs. sorry if that isn’t helpful; i’m stuck with Nvidia for my ML/CUDA stuff.





  • chrash0OPtoSelfhostedwhat do y'all use for CI/CD?
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    this is my experience as well. we have a bespoke wrapper around Jenkins, and the more we can test locally the less time we have to spend waiting for the system to fail. it’s one of the reasons i’ve adopted just to script things locally as if it was CI.