• 0 Posts
  • 59 Comments
Joined 10 months ago
cake
Cake day: August 24th, 2023

help-circle
  • I feel like something like https://www.storj.io/ is on the path to what we would want/need?

    There might be some additional requirements for a true CDN to ensure data is closer to where it’s needed and in as many regions as needed though with the right amount of bandwidth. The data gets stored all over the place, but that doesn’t mean its optimal. But they do seem to claim it’s faster on their website…

    Edit: For those not wanting to click, TLDR is they use excess storage around the world and make it accessible anywhere, and safe from failures. People with excess storage can join the network if they have enough storage/bandwidth and pass some tests. Their API is S3 compatible.





  • No one cares if you leave a ticket open due to a bug or incomplete feature

    Product sure as hell cares if you’re going to ship a bug or incomplete feature.

    Never worked at company that wasn’t the case in over 15 years.

    Product owns the work they ask us to do. We do their bidding.

    And we certainly aren’t allowed to just change the scope of tickets at our own discretion without checking in





  • This is my typical experience as well, too many people don’t do a code review of their own PR first.

    When I was a junior, I had this coworker who did all my reviews. I was doing my absolute best and wanted to show that I was learning, so I would review all my work before submitting it and think, how would he review and respond to this code.

    That just stuck with me and it’s my normal practice now.

    I eventually learned that’s not as normal as I thought. I also tend to give better code reviews than others.

    Edit: the other thing I do is check in with who will be reviewing my code well before I submit anything someone might think is weird and have a discussion about it before the reveiw. If it’s weird, there might be a better way unless were stuck due to technical debt or something, and doing that early vs at the end usually saves time.





  • You can try Kotlin Compose Multiplatform.

    It can target JVM (windows, Linux, Mac) and then work on iOS and Android.

    Android and JVM are stable. IOS is alpha and works well. Should be beta this year.

    WASM support is coming as well but is experimental.

    You can do as much multiplatform as you want and do as much platform specific as you want.

    Compose itself is a declarative UI framework. Your UI is code.

    Edit: You do require a Windows, Linux, and Mac machine to build the executables for each desktop JVM app, as well as a Mac for an iOS app. Android you can build on any of them.