This is essentially my chain of thought and what I have done. Even if it is a simple request that is confined to a single component when a developer looks at the codebase they can know that all API calls are called from Vuex modules and not modules _and_ components.
That then leads me to my next question though, if I am using Vuex to abstract the API calls is it bad practice to use Vuex actions for API calls that don't need to be saved into the store?
Interesting timing with coming across this article for me. I have started developing re-designing our site frontend to use Vue with Vuex and the point this author makes about where to put the API logic also made me scratch my head a bit. Sometimes I just need to make a simple API call that does not alter the application state and just needs to grab some information and render said information in 1 component. Technically, in the component, I can just call Axios and get the data then and there, but then I have other components such as the Login that does need to set some Vuex state and therefore that's abstracted away further in the actions/API class as all documentation seems to suggest that's what you should do. I suppose I am just finding it a bit of a challenge to keep things a) consistent and b) not overly abstracted for the task at hand.
Spent 9 months of the year developing a REST API for a project that is launching in the coming months whilst finishing my CS degree online (finish in May). Have learned a lot along the way, mainly more about the HTTP protocol in general but also unit testing and working with third-party contractors that are building SDK's to interface with my API. All in all been a very challenging year professionally but have learned a lot of lessons that will help in the years ahead.
Was a paying Spotify user for about two years and recently jumped ship to Google Play Music to give it a shot and I'm pretty happy about it thus far. Haven't been any songs that I had on my Spotify playlist that I couldn't find. There is a few things it is missing that's not ideal (no podcasts in Australia) but the bundling of YouTube Red with the subscription + the ability to upload my bandcamp-downloaded tracks that I can stream back that aren't on either Spotify or Google Play Music is fantastic.
Podcasts is just the main thing I am wanting at the moment, but I can still access them via the Spotify free account.
I'll never understand locking people up for having an addiction and treating them like criminals. I'm not too educated on how it's handled in America but in Australia you can go to your doctors and get signed up to a methadone program without worrying about any legal repercussions.
My fiancé works at a pharmacy in Melbourne, Australia and says some of the most lovely and friendly people who just want to get themselves together come in regularly to get their $5 dose and it's saddening to see how badly society judges them.
I've only been programming professionally for a year but can't see myself wanting to get out of it anytime soon, maybe ask me in 10 years to see if that view changes. But at the moment am thoroughly enjoying learning as much as I can - coming from a job I didn't enjoy as a full time baker to having my weekends back, normal social hours and just having more spring in my step by doing something I have a genuine passion for is a great feeling.
Discover weekly is hit and miss for me. Some weeks I find plenty of great material, and others I find a lot of junk - that being said I can understand it would be hard to match music you'd like all the time.
I'm a part time developer that is still at uni but learning the ways of how maintaining code is doing in a professional environment.
Just curious, how often are practices like these where the company you work for gives you a detailed overview of all the coding conventions you should follow? Is this absolutely expected to be followed strictly when you start any job as a developer? Is this something a lot of workplaces follow or mainly the big boys(Google, Facebook, Twitter, etc). If you miss maybe one or two coding conventions in a huge commit for instance, do you hear about it or does the reviewer just fix it and you can see what's changed?
Just curious as I'm still new to transitioning into the workplace when it comes to source control. I work with one other developer (my boss) who wrote for more or less the entire system himself and there is no such document - I just have to observe the patterns used and follow suit.
I did a unit at university learning C at the beginning of the year and you sound similar to my lecturer. We used VIM, no fancy IDE's and we had to compile our code in the command line using flags such as -ansi -Wall -pedantic and would be marked down even if we had warning for not following the coding conventions. Same goes for allocating any memory we did not free, etc and to illustrate how to use debugging tools such as gdb, valgrind.
Was a tough unit that definitely did not hold your hand (I had done a lot of Java before that which handled things like memory allocation for you along with a much more forgiving teacher) but I am grateful I did the unit and really enjoyed the harder-approach my lecturer took.
Ah someone from my area - I commute into south bank everyday from Ferntree Gully. I actually don't mind the train trip in. It's a bit further to a train station from Olinda though (assuming that was how you travelled in).
As someone who until Oct last year worked weekends and weekdays getting up at 2:30 am to bust my ass in a bakery for dismal pay and virtually no social life due to the hours - I work part time as a junior developer now and looking back at my old life I don't know how the hell I did it. It motivates me to do the best I can each day so I don't end up back there.