TLDR: I wrote a project to show to potential employers. In the end, I liked the architecture I wrote from scratch so much that I think it deserves to become an open source library on its own. Find the link at the end.
I found myself out of a job during lockdown (by my initiative at first, but now it's taking longer than I planned) and decided to start preparing for job interviews by having a sample project to demo to companies in lieu of making a different test or take-home exercise for each potential employer.
Being an Android developer, my project should be a simple app that fetches some content and displays it on list. Additionally, you can select one of the rows to see details about the item you clicked.
I remembered from my previous time job hunting I had created a few of those apps. I took them as a starting point and wrote a new project that took the best parts of different projects.
I started with a MVP project and rewrote it with a MVI architecture - I had grown a big fan of MVI over the last few years. Because I had time (not so great companies were hiring) I did several rounds of tweaking the MVI architecture I was using. After each iteration I liked it more, and could see how this was very generic and powerful that could be used by a lot of people...
Eventually I got to a point where that sample project is finished but now I felt like I had something bigger to do: this architecture deserved to see more than my private git repo. I had to turn it to a library!
So I wrote a library based on that architecture (there were yet a few more changes). It finally reached 1.0. So far I've heard encouraging feedback from close friends but I think it's time to show it to the world!
I'm an Android developer who has been around since the 1.5 days. I've had the pleasure of working with leading companies such as IG Group (largest CFD trading provider) and Bloomberg.
I actually see this as a great fitness tracker (that is why I might buy it) but I don't see it as a smart watch (and I'm not complaining about that).
In order to be a smart watch it would need to do more "smart" things such as showing notifications, interacting with third-party apps, etc. If you have a Windows Phone you can talk to cortana so it's the closest thing to a smart phone you can get on that OS, but still it's clearly not as powerful as what Android Wear and probably Apple Watch can do.
Check your bank account in the end of the month. It's going up!
Don't forget that if you earn less money in the same country then you'll pay proportionally less taxes. Made up numbers: CA = 120k gross -> 80k after tax. Another state: 100k gross ->70k after tax; Difference in cost of living: 10k). Now you are breaking even. Of course, totally made up numbers.
And as an extra, for every extra dollar you have in a cheaper state, you can do more with it than in CA.
Sure, I would love to make the same kind of money in the cheapest corner in the world but companies aren't there to make us rich; they are there to have a business! If you want to try to convince company to pay for what you produce instead of paying a fair salary, try contracting instead (and be good at selling yourself)
I have 5 years of Android experience. I have worked for great companies like Bloomberg and IG. I have moved from London to Adelaide after my partner received a job offer here.
SEEKING WORK - Android Developer in Adelaide, Australia (will consider remote work / in other cities)
I am an experienced Android developer (nearly 5 years of Android development). I have a very deep knowledge of the Android SDK and of Android UI/UX guidelines which is essential to create great Android apps with an "Android" feeling.
While in London I have worked for great companies like IG Group (the largest global CFD provider) and Bloomberg.
You can find my Stack Overflow, LinkedIn and portfolio in:
- offshore or no offshore, scattered teams will have a lot more communication problems (= waste of time, requirements not fulfilled, etc)
- if you outsource a product, you will eventually get something that looks like what you asked. As soon as you throw it to prod, publish or whatever applies, you will find many unexpected problems. These problems usually are identified much earlier if you develop in-house. Possible explanations: Quick questions could have flagged those issues, but because teams are in different timezones, probably those questions got lost in a "todo.txt" somewhere.
- if you have to outsource, I recommend that you have people in your main office actually working with the remote team (doing the same tasks - e.g. coding). This way you know the quality of the product from the inside, how good are the people developing it, how extensible it is, etc.
I decided to write this application because whenever there are delays on my line, I never check tfl website. Sure I could have checked every other day that week, but not on the day with a bad service!
Using this app I can get the current status, weekend status and set up my regular commutes so I get notified if I'm going to be affected by problems. Simple and fast.
We make use of push notifications so it won't drain your battery! ;)
Suggestions and feedback are more than welcome! Please share!
TLDR: I wrote a project to show to potential employers. In the end, I liked the architecture I wrote from scratch so much that I think it deserves to become an open source library on its own. Find the link at the end.
I found myself out of a job during lockdown (by my initiative at first, but now it's taking longer than I planned) and decided to start preparing for job interviews by having a sample project to demo to companies in lieu of making a different test or take-home exercise for each potential employer.
Being an Android developer, my project should be a simple app that fetches some content and displays it on list. Additionally, you can select one of the rows to see details about the item you clicked.
I remembered from my previous time job hunting I had created a few of those apps. I took them as a starting point and wrote a new project that took the best parts of different projects.
I started with a MVP project and rewrote it with a MVI architecture - I had grown a big fan of MVI over the last few years. Because I had time (not so great companies were hiring) I did several rounds of tweaking the MVI architecture I was using. After each iteration I liked it more, and could see how this was very generic and powerful that could be used by a lot of people...
Eventually I got to a point where that sample project is finished but now I felt like I had something bigger to do: this architecture deserved to see more than my private git repo. I had to turn it to a library!
So I wrote a library based on that architecture (there were yet a few more changes). It finally reached 1.0. So far I've heard encouraging feedback from close friends but I think it's time to show it to the world!
Please tell me what you think!
https://pedroql.github.io/mvflow/ https://github.com/pedroql/mvflow