Hi,did you try this in android studio lady bug? If then can you please provide some details
@thetechiegarage2 ай бұрын
Hey, not really. What challenge are you having with Android Studio LadyBug?
@jonathancasagrandefilho52313 ай бұрын
Amazing tutorial, really, thank you. Showing configs and not cutting the video to let us lose on how you made it. Please do something similar with Jacoco.
@thetechiegarage3 ай бұрын
Thanks for the feedback Jonathan! Jacoco is a great suggestion. Will consider it in the future videos
@leonelp95935 ай бұрын
horrible you never told us how to disable rules
@thetechiegarage5 ай бұрын
Hi @leonelp9593, that is covered from minute 22:13 onwards. Incase you need more detail into it check the documentation here pinterest.github.io/ktlint/latest/rules/configuration-ktlint/#disable-rules
@kerryphilip38265 ай бұрын
Loved the video. where can I get a copy
@thetechiegarage5 ай бұрын
Hi Kerry, thanks for the feedback. You can get it from Amazon. DM me on Twitter/LinkedIn for a local contact too.
@clelialopez7 ай бұрын
This video is very complete. Thank you very much for taking the time to create this content.
@thetechiegarage7 ай бұрын
You are welcome. Glad you found it useful👌
@amerelsayed7 ай бұрын
Why you use detek and ktlint ? I mean of them can work with linting
@thetechiegarage7 ай бұрын
Ktlint focuses on enforcing Kotlin coding standards and mostly style/formatting related rules to fix things like indentation, naming conventions etc, while Detekt provides a wider range of rule sets besides the style and formatting rules that can help detect code smells like the complexity and potential bugs rule set (refer to the documentation here detekt.dev/docs/rules/comments). I find combining the two gives the best of both worlds. That aside, how to go about linting is very opinionated based on what a developer deems important for their projects. Is there one that you prefer over the other for your personal or team projects?
@iannjari68337 ай бұрын
awesome stuff annie 🎉✌🏾
@thetechiegarage7 ай бұрын
Thank you Ian🙏
@kibettheophilus8 ай бұрын
Good stuff 🎉
@thetechiegarage7 ай бұрын
Thanks Theo!
@MamboBryan8 ай бұрын
Really awesome video 👌🏾👌🏾👌🏾
@thetechiegarage7 ай бұрын
Thank you Mambo🙏
@davidodari81188 ай бұрын
Great content on Detekt 💯
@thetechiegarage8 ай бұрын
Thanks David!
@jacqui_gitau9 ай бұрын
Very informative video! Can't wait to implement this tool in my projects. Waiting for the next video!
@thetechiegarage8 ай бұрын
Thanks Jacqui! Let me know how you find them😃
@louisasaburi95149 ай бұрын
Am not even an android developer but I feel like I can manage a whole android app development project😂
@thetechiegarage8 ай бұрын
The energy we love to see! 😂Hope you get to experiment with android and let me know how you find it
@kibettheophilus9 ай бұрын
Great session, I have learnt new stuff: customizing rules and also about the detektGenerateConfig task(I usually create the config manually then copy from existing projects😅).
@jacqui_gitau9 ай бұрын
😅
@thetechiegarage8 ай бұрын
Thanks! Glad you learnt something new. I am guilty of doing it manually before too😂
@breensrobert10 ай бұрын
💡 insightful
@thetechiegarage10 ай бұрын
Thank you Breens
@MamboBryan10 ай бұрын
Awesome session 🎉🎉
@thetechiegarage10 ай бұрын
Thank you!
@hopevalentinemiriti209710 ай бұрын
Guurllll 🎉🎉🎉🎉🎉 I'm late to the party 😅😅but tumefika sasa!! Great moves❤kudos Mwari
@thetechiegarage8 ай бұрын
Thanks Girl♥
@jacqui_gitau10 ай бұрын
Thank you for the session. You have explained the concepts very well. The demo has helped me internalize the process of integrating ktlint in my projects. Can't wait for part 2 😊
@thetechiegarage10 ай бұрын
Glad it was of help. Part 2 is coming soon😊
@wayne_gakuo10 ай бұрын
@eddasteve578210 ай бұрын
Go go Annu🎉👏🏾👏🏾👏🏾
@thetechiegarage10 ай бұрын
Thanks Edda!
@Mo-xq5oc11 ай бұрын
You are doing well🎉
@thetechiegarage11 ай бұрын
Thank you!
@soyaro11 ай бұрын
You're gonna go far!
@thetechiegarage11 ай бұрын
Thank you Steve!
@iquid749411 ай бұрын
I feel like most of the core engineering problems have already been solved. we can only iterate on existing technologies & maybe scale up
@thetechiegarage10 ай бұрын
@iquid7494 If you are referencing technical debt bit, I think there definitely should be room to improve to allow for maintainability, scaling of your application/solution and ease of onboarding new members onto the codebase. This improvements can be usage of improved libraries, 'better' architectures, overall 'cleaning the codebase' etc, which generally make the developers work easier(maintaining and scaling the app) and better user experience(if the improvements help with say stability, responsiveness of the app,..). That aside I totally agree with you on most of the core engineering problems have been solved.
@danielmwai642711 ай бұрын
Kudos! Really Niice
@thetechiegarage11 ай бұрын
Thank you!
@muniukariuki21411 ай бұрын
My advise to software engineers across the board; there are no sacred cows when it comes to it. A common phrase used in devops comes to mind here. "Cattle, not pets". Focus more on the business value and not get attached too much to the code you've written. By treating software artefacts as replaceable resources, we embrace a culture that embraces and allows scalability, innovation and improvements when it comes to it. And remember, every code you write today is basically legacy code tomorrow 🙂 Keep soaring Annunziata and good to see you picking up this interesting topic.
@thetechiegarage10 ай бұрын
Great way to look at it! First time I am learning of the "cattle not pets" analogy but it fits perfectly in the Engineering world with the ease of disposability of "cattle" as compared to ''pets" that are no longer serving value. I totally see its essence in adapting to business needs.
@ruttovalentine319811 ай бұрын
Great content ... cant wait for more
@thetechiegarage11 ай бұрын
Thanks Valentine!
@louisasaburi951411 ай бұрын
You're very articulate and demonstrate knowledge of subject matter, and I feel the conversation is edifying, and insightful🙂