That same question is in my head as I dabble in iOS development. I'll share my thoughts and maybe it will help add to the discussion.
I've been writing code for over 10 years. I understand the benefits of testing (huge benefits), so naturally I thought I should write tests as I learn iOS development. After thinking about it, I decided not to. Here's why.
You already have enough in your head when you're learning something new. If you focus on building what you want, you'll have more success and learn more about Android. Trying to write tests is adding another point of possible failure. I feel it's important to find a lot of "wins" when you're early in a project/framework. Few people want to work on something that doesn't build for weeks. In Android/iOS development, you want to see your app running - it makes you feel good.
Plus, I feel like you need another level of understanding to write tests that make sense. Tests can help you, sure, but it really depends on your goals.
Get your Android app working first. Build features even if it's not the best way to build it. Come back later and refactor. Companies like people who can get shit done.
Your thoughts on "best way" of building is related to me. I always have a trouble with getting things done. I overthink about architecture, clean code, patterns etc.. and at the end I will do nothing :). Thanks for your attention!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That same question is in my head as I dabble in iOS development. I'll share my thoughts and maybe it will help add to the discussion.
I've been writing code for over 10 years. I understand the benefits of testing (huge benefits), so naturally I thought I should write tests as I learn iOS development. After thinking about it, I decided not to. Here's why.
You already have enough in your head when you're learning something new. If you focus on building what you want, you'll have more success and learn more about Android. Trying to write tests is adding another point of possible failure. I feel it's important to find a lot of "wins" when you're early in a project/framework. Few people want to work on something that doesn't build for weeks. In Android/iOS development, you want to see your app running - it makes you feel good.
Plus, I feel like you need another level of understanding to write tests that make sense. Tests can help you, sure, but it really depends on your goals.
Get your Android app working first. Build features even if it's not the best way to build it. Come back later and refactor. Companies like people who can get shit done.
Andy Hunt recently wrote on Twitter: One Weird Old Trick to learn how to write software: Write software. twitter.com/PragmaticAndy/status/9...
I think you're on the right track. Good luck!
Your thoughts on "best way" of building is related to me. I always have a trouble with getting things done. I overthink about architecture, clean code, patterns etc.. and at the end I will do nothing :). Thanks for your attention!