Kotlin’s approach to storing values in containers is quite similar to the one found in Java. It is really handy to get used to idiomatic use of Kotlin’s standard library as it greatly enhances the experience.
Now that Get Noticed is coming to an end (this is the last “competition” entry) I’ve decided to dedicate some time to reflect.
There has been a really important event this week, namely Google I/O 2017. I’d like to mention three things that I believe will have big impact on my life or career choices in the upcoming days and months.
Have you ever found yourself working on your git project, having some unfinished feature on the way when suddenly someone asks you fix something on development branch or quickly push a hotfix to master.
As soon as your application requires more memory for its objects it requests more heap size. However if your application requests more memory that is assignable to one process on your device you encounter a problem.
I really loved helping with and attending the 14th Linux Session this weekend. It was a very rewarding and enriching experience for a bunch of reasons.
As of now, after the Linux Session the application is stable, looks pretty and I haven’t noticed any major bugs in version 1.5.
As you may recall from a post some time ago I’ve created a loose mockup for myself to refer to while designing the app. Because it’s so bad it can get some laughs out of people, here it goes again.