Arun

@arunkumar_9t2

Mobile Platform - Android . Previously . I built and Iconzy. Opinions here are my own.

Singapore
arunkumar.dev
Vrijeme pridruživanja: kolovoz 2010.
364 fotografije ili videozapisa Fotografije i videozapisi

Tweetovi

Blokirali ste korisnika/cu @arunkumar_9t2

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @arunkumar_9t2

  1. Prikvačeni tweet
    16. pro 2019.

    I am excited to announce my next Android project: Scabbard! It's an / plugin to visualize Dagger 2 dependency graph. It works by using Dagger SPI and seamlessly integrates directly with the IDE. Hoping to launch later this week. Example and thread👇🏼

    36 replies 166 proslijeđenih tweetova 839 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  2. prije 21 sat

    Finally got around using simple names for Scabbard graphs. Planning to make this default and provide option for using qualified names. Graphs should be less wide now.

    1 proslijeđeni tweet 14 korisnika označava da im se sviđa
    Poništi
  3. prije 21 sat

    Doing something similar with actions and Firebase hosting.

    You should continuously distribute your blog 😊
    6 korisnika označava da im se sviđa
    Poništi
  4. proslijedio/la je Tweet
    22. sij

    Scrolling is the new smoking.

    107 replies 1.179 proslijeđenih tweetova 5.265 korisnika označava da im se sviđa
    Poništi
  5. 22. sij

    Fixed link:

    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  6. 22. sij

    In my humble opinion, it is best to modularize. Even offsetting a bunch of utils code into own module unlocks benefits mentioned above. it would be helpful to unpack what incorrect modularisation in your terms is and how they make it worse than monolith.

    1 reply 6 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  7. 22. sij

    Relying on faster machine also it not super helpful because in distributed teams with high contribution rates, CI costs quickly pile up. Better parallelization and caching is a safe bet instead.

    1 reply 4 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  8. 22. sij

    Arguments were made that faster machine and pure Java works great for incremental build. True, but at scale we wouldn't have privilege of incremental often since pulling unrelated code causes recompilation whereas in modularized project this is offset by both local/remote caching

    1 reply 3 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  9. 22. sij

    Apart from this modularization enables: * Local/Remote caching. Share CI build results with local. * Easier definition of code ownership * Feature isolation and of course build times.

    1 reply 5 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  10. 22. sij

    Compile avoidance (avoid compiling if ABI did not hav incompatible change) is another win for build times but currently Kotlin does not support it but there are some ideas.

    1 proslijeđeni tweet 3 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  11. 22. sij

    Modularization does bring some impact in some areas like configuration time. It's been unavoidable due to how Gradle is designed but there are steps we can take to reduce it; namely Task Configuration Avoidance.

    1 reply 4 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  12. 22. sij

    Moving on to optimal setup, it is the structure of the DAG that matters. Even on infinite cores we can't build all modules in parallel because of dependency chains. Bazel terms it critical path (see attached). If you have more independent nodes, you have more parallelization.

    1 reply 5 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  13. 22. sij

    Some explanation from Buck but same applies to Gradle, Bazel. I should also note Gradle constructs a task graph but same execution principles apply.

    1 reply 5 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  14. 22. sij

    The reason I said modularized builds are faster is simply because of how DAG works. Build graph is represented as DAG and it is easy to have independent leaf nodes in a worse setup too. All independent leaf nodes are built parallelly which does not happen on a monolith projects.

    1 reply 6 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  15. 22. sij

    Disagree and it is not worse as this tweet makes it to be. I'll even say a worsely configured modularized project will have better build time relative to a monolith project on clean builds. Let's unpack what is "worse/incorrect" since the original tweet did not expand on it.

    "Modularization makes builds faster" is probably the most harmful myth circulating among Android developers today. It's time to realize that while correct modularization might potentially improve your build times, incorrect modularization will surely make them worse.
    Prikaži ovu nit
    1 reply 1 proslijeđeni tweet 17 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  16. proslijedio/la je Tweet
    15. sij

    Been using the JetBrains Mono font for some time now. Happy to see it released publicly!

    19 replies 132 proslijeđena tweeta 512 korisnika označava da im se sviđa
    Poništi
  17. 12. sij

    Happy to see Scabbard mentioned in turning point.🙂 And kudos to for sitting down and driving the migration. And yes, use more dagger.

    Spent more than two weeks writing and rewriting this post...just like any other I write because I have terrible anxiety about my writing. Anyway, yet another post about someone being pushed into using Dagger and what they think of it
    Prikaži ovu nit
    1 reply 8 korisnika označava da im se sviđa
    Poništi
  18. proslijedio/la je Tweet
    10. sij

    Let’s be honest. The real RxKotlin name is RxJava KTX.

    1 reply 3 proslijeđena tweeta 65 korisnika označava da im se sviđa
    Poništi
  19. 31. pro 2019.

    Happy new year folks. 🎉🎈🎊

    18 korisnika označava da im se sviđa
    Poništi
  20. proslijedio/la je Tweet
    31. pro 2019.

    U+ ┏━━┓┏━━┓┏━━┓┏━━┓ ┗━┓┃┃┏┓┃┗━┓┃┃┏┓┃ ┏━┛┃┃┃┃┃┏━┛┃┃┃┃┃ The year of the Dagger ┃┏━┛┃┃┃┃┃┏━┛┃┃┃┃ ┃┗━┓┃┗┛┃┃┗━┓┃┗┛┃ ┗━━┛┗━━┛┗━━┛┗━━┛

    105 proslijeđenih tweetova 799 korisnika označava da im se sviđa
    Poništi
  21. 28. pro 2019.

    Shoutout to for icon and illustrations. He is awesome to work with.

    4 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi

@arunkumar_9t2 još nije objavio nijedan Tweet.

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·