Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestions for new episodes #34

Open
artem-zinnatullin opened this issue Apr 10, 2016 · 11 comments
Open

Suggestions for new episodes #34

artem-zinnatullin opened this issue Apr 10, 2016 · 11 comments

Comments

@artem-zinnatullin
Copy link
Owner

Feel free to suggest new themes, please use GitHub emoji reactions to vote.

@PrashamTrivedi
Copy link

Hi,

Here are my suggestions.

  1. Give us some tips on how to use unit testing, architecture etc in
    existing projects. Many of us are working on some projects since months and
    they have around months of planning. On the other hand good explanations on
    these topics are better on fresh development.
  2. Talk about some unknown/less talked classes,apis from sdk framework
    (sdk+support libs).

On Sun, Apr 10, 2016, 9:51 PM Artem Zinnatullin notifications@github.com
wrote:

Feel free to suggest new themes, please use GitHub emoji reactions to
vote.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#34

Prasham H Trivedi

@vanniktech
Copy link

Gradle

  • What cool thing(s) are you using / doing with it?
  • Any custom plugins?
  • Common gotchas

Though I think this episode won't take that long and could be one of the shorter ones.

@netimen
Copy link

netimen commented Apr 14, 2016

Kotlin

  • how to test Kotlin code (mockito has problems with final and nulls)
  • any tips on how to write typical Android code in more idiomatic Kotlin, not just Java-style Kotlin :)

@netimen
Copy link

netimen commented Apr 14, 2016

SOLID:

  • why is it really necessary to write SOLID code? May be it's just some academic impractical stuff :)
  • some real-life Android examples from experience when non-SOLID code lead to problems
  • how to write SOLID Android code for typical tasks? For instance, if Presenter in MVP is made to survive orientation changes in order not to loose data, that's not SOLID.

@netimen
Copy link

netimen commented Apr 14, 2016

Prototyping, why is it needed, what are good tools

@netimen
Copy link

netimen commented Apr 14, 2016

Aspect-oriented programming: what are pros and cons of using AOP, may be some good usecases

@netimen
Copy link

netimen commented Apr 14, 2016

In the first podcast you mentioned that you maintain some job queue, so all the background tasks are immune to orientation changes.

I think it's a vast and pretty advanced and interesting topic — pros and cons of different methods of performing background tasks and caching them during orientation changes.

@netimen
Copy link

netimen commented Apr 14, 2016

Design patterns

What classical design patterns to use in different parts of Android app? For instance, recently I stumbled upon adapter delegates. I never thought that delegate pattern could be used in adapter. And I think there might be tons of other interesting ideas.

It would be cool if you could invite Martin Fowler :)

@netimen
Copy link

netimen commented Apr 14, 2016

Project management for small free-time projects.

Many of us have small projects we do in our free time. May be they don't require complex project management. But still the naive approach "I have an idea and I start coding something immediately" is not the best strategy. It would be great to hear from people who maintain their own successful projects on how they manage them. How do they prioritize the tasks and so on.

Recently I heard a talk about Android architecture (sorry it's in Russian). I can't say I liked it much, but still the idea was interesting. Often we think too much about technical stuff, like how to prevent data loss during orientation change, how to write SOLID code etc. But maybe the user won't like the feature we are developing now and we will just delete it in a month, so we are just wasting time in trying to solve all those problems.

So maybe this topic can be rephrased like this: how not only write good code, and not to make one good feature, but how to build a good-quality project as a whole.

That's all for now :)

@lenguyenthanh
Copy link

lenguyenthanh commented Apr 15, 2016

Kotlin please! Here are some of my suggest topics when talk about Kotlin:

  • Why Kotlin for Android (safe, concise, NPE, extension, functional)
  • Testing (how to deal with default final class)
  • How to code in Kotlin way (Functional paradigm, closures,
  • Perfromance (Runtime, compile time)
  • Anko
  • Generic
  • Annotation
  • Kotlin and Java communication (Translating, using Java code with Kotlin)
  • Kotlin roadmap (async/await)
  • Static analysis tools (Findbugs, PMD, code style, Jacoco, Lint)
  • Proguard

@usakhelo
Copy link

I would suggest to talk about some ideas for new applications. People would like to have pet projects but don't have good idea of what to do.
It was nice to hear job announcements in recent episode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants