-
Notifications
You must be signed in to change notification settings - Fork 18
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
Comments
Hi, Here are my suggestions.
On Sun, Apr 10, 2016, 9:51 PM Artem Zinnatullin notifications@github.com
Prasham H Trivedi |
Gradle
Though I think this episode won't take that long and could be one of the shorter ones. |
Kotlin
|
SOLID:
|
Prototyping, why is it needed, what are good tools |
Aspect-oriented programming: what are pros and cons of using AOP, may be some good usecases |
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. |
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 :) |
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 :) |
Kotlin please! Here are some of my suggest topics when talk about Kotlin:
|
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. |
Feel free to suggest new themes, please use GitHub emoji reactions to vote.
The text was updated successfully, but these errors were encountered: