At the beginning this folder structure made sense, but currently we have over 210 Vue components (and growing). I haven't found any "better" architecture/folder structure on the web. Do you know any better?
I was thinking about simulating our backend folder structure in the frontend but I'm not quite sure about it (our backend is basically Symfony with folders for each "business" aspect of our system, subdivided in "use cases" (e.g., "return an order unit") that call "services", and "modules" that can be reused across the whole system. Somehow our backend seems to "scale" better than our frontend...
Any sci-fi stories about this (as far as I know, only [1]) ? Does real science have ever talked about it?
[1]: http://dragonball.wikia.com/wiki/Hyperbolic_Time_Chamber
Now I'm thinking applying for a job in Germany (only English-speaking companies from startups to medium-big sized). Do you think I should include a picture, the birthdate and birthplace too?
Thanks.
The term mid-to-senior level can means different things in different countries. I understand that 3 years of experience is the minimum for a mid level and 5 for a senior one. I can be wrong, thought.
So question is if you know good alternatives. Just two features are important for me: size (~iPod shuffle) and storage (> 2GB).
[1]: http://www.apple.com/ipod-shuffle/
So, this is my plan:
July, August and September (2016): Learn the basics, the grammar, watch Youtube videos with German subtitles. I have bookmarked a couple of grammar books and good Youtube channels.
October (2016) to July (2017): I'll be in Germany, this means I'll have to speak! Although what I'm going to do there only requires me to speak English. Will keep improving the grammar and will keep watching, not only videos, but also the TV and the radio and of course I'll talk with German people.
The level I want to reach is the same as my level of English I have now. I know it's a hard task to accomplish, but boy, I'm motivated.
Suggestions, tips and personal experience learning non formal languages are welcome. Thanks!
In the company I'm working at as a front end developer, it varies from a simple paragraph in a Jira task to a non-so-rigorous-sometimes-vague description in a Confluence page plus some screenshots of the UI provided by UX guys.
It is mostly ad-hoc and since the company has many sub-projects within the big one (let say: payments, global features, savings, etc.) it is always hard when you switch to another project and you want to know "what the scope of the project is, the things it should do and the things it shouldn't"
I would like to improve this. How do you handle your requirements?
PS. I guess "requirements specification" is the correct term. But, in case of doubts, what I want to know is how do you specify the functional requirements your app/project/whatever must address.
I worked as an Android developer, as a fullstack developer and now as a FE developer. I feel myself confident if someone ask me to implement something (build X from scratch using Y and Z, even if I don't know Y or Z) but the thing is I feel like I don't know anything concrete about the technologies above. I mean, if someone ask me about "what is a block in Ruby?" or "how controllers should share things in AngularJS", or "what are array comprehensions in Python" or "GET or POST to update something?"... I think I know the answers (because I have deal with that in practice) but I'm sure my answers will be very vague; like if I just know the surface of them.
I enjoy knowing a little bit of everything but a) I don't have enough time and b) I guess I'll have to, at least, master one or two technologies in order to "make more money?". The dilemma is which one? The most I like? The most I already have experience with? The one I think it's gonna be there for at least 10 years? Or perhaps I just can continue being a "jack of all trades"?
Thanks(and sorry for my English).
I know how to write code. I don't write excellent code. I'm getting paid for writing decent code. I'm not very experienced programmer. I know things like OOP, FP, MVC, patterns, Ruby, type systems, http, Java, Android, Scheme, databases, JS frameworks, eval/apply, PHP, etc.
Now, I have no idea about: scalable architectures, how to deal with hundred of thousands of users, db replication, real time, https/ssl, cloud, message systems like zmq, security... in summary I have no idea how to make THE_APP a service that could work in a happy real situation (millions of users, a lot of data, etc).
So my question is: how I can learn all of those things?
[0]: http://dbpedia.org/
a) Going native. Android and iOS by the moment.
b) Going hybrid. SPA. Maybe Meteor/Ionic, Cordova.
c) Going responsive. Just one website.
I have experience with a) and c) but not with b).
Reasons to do this side project:
* Extend my portfolio
* Keep improving old technologies or learning new ones.
* Could be the next big thing! So naive :)
So, it would be great to see your pros and cons listed here. Thanks!
(The hardcover is a little expensive for me). (I know that I can read the online version for free, but I want the physical book).