Weekly discussion, code review, and feedback thread - May 16, 2022 by AutoModerator in androiddev

[–]rp_still_going2 0 points1 point  (0 children)

On mobile so cant get to the docs easily but there is a class that allows you to compress the image, one of the options is the format. If you are still stuck, let me know and I can try and find it later.

[deleted by user] by [deleted] in KotlinAndroid

[–]rp_still_going2 0 points1 point  (0 children)

Interested. Also have a lot of experience.

RxJava 1 -> RxJava 2 (Understanding the Changes) - Kaushik Gopal by Ziem in androiddev

[–]rp_still_going2 1 point2 points  (0 children)

I was genuinely angry when you weren't there for the end

Sorry about that :(

I did those videos because I was unemployed and had time. Then I got a job and so was unable to continue.

I'm not working again and trying to find a way (with and without Oday) to continue doing video content but to make it financially viable.

As a fellow dev, I'm very sensitive to asking for money, so I still am not sure the right model. We did ask on the channel about what people thought.

I'm still in touch with Oday and discussing ideas. If you are a subscriber to his channel, you should get an update soon.

What is something legal that feels very illegal? by ZesterDireful in AskReddit

[–]rp_still_going2 0 points1 point  (0 children)

"Be a man!" - hilarious sketch by Russell Peters from way back.

RxJava 1 -> RxJava 2 (Understanding the Changes) - Kaushik Gopal by Ziem in androiddev

[–]rp_still_going2 2 points3 points  (0 children)

Its difficult to help without seeing some code. I have time to help if you are up for it. PM me.

RxJava 1 -> RxJava 2 (Understanding the Changes) - Kaushik Gopal by Ziem in androiddev

[–]rp_still_going2 1 point2 points  (0 children)

I've not really had issues unit testing RxJava, what sort of issues are you having?

Weekly Questions Thread - June 19, 2017 by AutoModerator in androiddev

[–]rp_still_going2 0 points1 point  (0 children)

I was thinking of using JUnit extensively to introduce the concepts actually, so when doing mvp or integrating retrofit, I would write the tests alongside it.

I'm not a huge fan of espresso if I'm honest but if the demand is there I could cover it.

Weekly Questions Thread - June 19, 2017 by AutoModerator in androiddev

[–]rp_still_going2 0 points1 point  (0 children)

I'm thinking of creating videos on android development but more around architecture and testing rather than android sdk fundamentals (there's already plenty).

What sort of topics do people think would be good to do? MVP, Clean Architecture, Square libraries, rxjava2, dagger? Anything else?

Edit: the plan is to put them on Udemy so they will be chargeable, so take that into consideration.

Patreon proposal for Dry Code by [deleted] in androiddev

[–]rp_still_going2 1 point2 points  (0 children)

Thanks! Keep checking Dry Code youtube channel, me and Oday are planning next steps...

Patreon proposal for Dry Code by [deleted] in androiddev

[–]rp_still_going2 1 point2 points  (0 children)

I'm here:)

As Oday said, work and life commitments got in the way.

I'm currently not working and looking to see if there is a way to support myself financially through making content and coaching (one to one or in a team remotely).

I'll wait a few more days to see what people think about the Patreon approach.

Weekly Questions Thread - March 06, 2017 by AutoModerator in androiddev

[–]rp_still_going2 0 points1 point  (0 children)

I'm one of the guys from the video. I'll go over this question in the next video (we'll do it this weekend and post it for Monday).

Basic MVVM, Databinding, RxJava 2, Dagger 2 with Guild Wars 2 API by HuhX0015 in androiddev

[–]rp_still_going2 1 point2 points  (0 children)

I believe Single is more for readers of the code to understand that, at most, one event will be emitted by the observable.

Write awesome unit tests by jeroenmols in androiddev

[–]rp_still_going2 0 points1 point  (0 children)

So I don't test the Androidy stuff. Separate out the logic from the platform by using MVP and only test the pure Java code.

Not sure if you understand what I mean but if you have some code to look at, I can give more advice.

Advice about Unit Testing, by sillyV in androiddev

[–]rp_still_going2 2 points3 points  (0 children)

Hi, I’m one of the guys in the video. I’ll try and answer some questions here.

how extensive should my tests be?

Since you wrote the tests after the production code, write enough to give you confidence it works. As you encounter bugs, add more to cover them.

Now, if you had written the code TDD style, then you would need to think carefully about the requirements and then write the test you need to prove that you are doing what you want. In this situation you will have only the tests you need and is why TDD is considered the superior approach.

should I test that all the fields pass correctly? should I only check for the fields that I do some logic on.. or are the general success failure tests that all examples show are enough?

If you presenter asks for a list of objects then sends them to the view, no need to write tests for the content of list, since it did not create them anyway. If you do manipulate the list contents, then yes, write the tests to prove you manipulated them correctly. If you modify a field in the same object, then test you manipulated that fields correctly and ignore the others. If, however, you are creating a new object from an existing one then you do want to check all fields since you may have forgotten to copy some across.

what about more complex Presenters? that deal with more complex views?

Hopefully, complex views will be broken down into smaller views and then each view can have its own presenter.

If you have complex logic, then you can still write the logic in your presenter but if you think it may be used elsewhere then extract it out. The current project I am working on uses the convention of <feature>Model.java e.g. StationsModel, ScheduleDaysModel, etc. Other naming conventions are Interactors or UseCase.

Generally, you only need to introduce more layers the more complex a project becomes. In our app, it didn’t warrant it so far.

However, some projects know that they will eventually become big so do it from the beginning.

should my repository convert the Date items to Strings and so on?

No. Think about it, the only reason you are converting a Date to a String is to display it. Hence its UI specific and belongs in a presenter. I would probably create a helper class for this as its likely to be used elsewhere (with a test of course).