Fair enough.
I'd say it's kind of a good time to get into Android Development - Kotlin and Compose has made it highly pleasant and productive when compared to the days of Java and Views.
Fair enough.
I'd say it's kind of a good time to get into Android Development - Kotlin and Compose has made it highly pleasant and productive when compared to the days of Java and Views.
One of the best things about living in a walkable place is that the concept of a weekly shop is basically dead - access to grocery shopping is available enough that I can go as many or as few times to shop as is warranted.
Granted, this usually adds up to once a week or less, but yeah. Big benefit.
This is an important concept to be imparted on those who do not understand the benefits of walkable places - a frequent question is how they can manage to complete their weekly shop without a car, since the car is in their mind needed to transport enough groceries to last the entire week. This is of course necessitated by the fact that their ideal location to shop for groceries is a significant distance away that can only be completed in a practical manner by car.
With where I live, this is unwarranted because I have access to convenient grocery shopping about 200 meters away by foot, and for ideal pricing I go 1 km away on a bike with storage on the rack. I do not want for variety either, I've got multiple speciality shops and 5 different grocery chains within a 1 km radius.
The answers about getting started with Kotlin and Compose are good, but I'd like to offer for your consideration that your app may actually be more appropriate to build as a website. Food for thought.
What a garbage decision, absolute peak cowardice. Resign immediately.
Anything the Heartland Institute publishes should never be treated as anything but toilet paper.
I mean, not really. This is actually a non-trivial topic, and true random is a really bad label for what someone actually wants out of a shuffling algorithm.
See the following engineering blog post on the subject: https://engineering.atspotify.com/2014/02/how-to-shuffle-songs/
Data takeouts are non-optional under the GDPR, so I would be very surprised if that happens.
True random shuffle would be a terrible idea. No one wants the same track showing up multiple times in a row, which would not be uncommon in true random shuffle.
Powered by all-american freedom fries
I'll keep it, cheers
The article is talking about killing it from a product usefulness-perspective, not a monkey making-perspective.
I don't know that I'd use 'insanely' as the modifier here as their position has weakened significantly over time, but they do certainly still play a large role in the Swedish labour market.