Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Questions #561

Open
vadim9999 opened this issue Jun 19, 2019 · 9 comments
Open

Questions #561

vadim9999 opened this issue Jun 19, 2019 · 9 comments
Assignees

Comments

@vadim9999
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Is it was created as task at GitHub issues? Please provide an issue number or link

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@vadim9999
Copy link
Collaborator Author

Should I curate some interns or be like a developer?

@atherdon
Copy link
Contributor

atherdon commented Jun 19, 2019 via email

@atherdon
Copy link
Contributor

@vadim9999
Copy link
Collaborator Author

@atherdon Coding school

  1. What is my role there? What should I do?
  2. When will you start getting students from companies?

@atherdon
Copy link
Contributor

@vadim9999 do 10-20 questions about coding school and publish it at hackernoon forum:) going totally open

@vadim9999
Copy link
Collaborator Author

vadim9999 commented Jun 26, 2019

I need tasks that I will refresh knowledge in my brain or study a new feature that helps me to take a job.

  1. Loops (for, while, map, find... ) and on lodash
  2. Some tasks on rollup and babel. I have started learning docs of rollup.
  3. Es5 and Es6

@atherdon
Copy link
Contributor

atherdon commented Jun 26, 2019

ok, noted.

  1. as you mentiioned at projects2 fetch - about how to make tests works with es6 - you can add this config to each of project and test if it works or not move fetch to ES6 GroceriStar/groceristar-fetch#306 (comment)

i'll prepare more tasks and put them here soon

@atherdon
Copy link
Contributor

  1. have some ideas, that can increase your skills. I was thinking that having this long list of functions is actually not cool. I didn't plan to work on these modules so long, but as we're doing it - then it's fine. One of my ideas related to improve our methods, by applying some coding patterns. long story short - it's also about separations and adding more layers. So like table(data) will be one entity that is solid and we'll have another entity(interface,operator) that will actually provide a business logic. I made it a week ago - will research more and back to you.

also - with changes that i'm making at fetch - it will became ES6 style, soo... But we can find something more interesting for you.

  1. loops - noted. when I'll crack current bug of fetch - we can extend our code and actually go with some cool stuff. there will be a lot of lodash, I can promise.
    So please control interns so i have time for more preparation.

  2. we have copy assets rollup module #266 that can make our module better. but right now i'm focused on other issue. Not sure why(I assume it's related to our rollup config - they update a main package and some our setups are outdated) but our static files didn't importing well at projects2.0 at fetch. I created a mini-sd module, because right now at master we have a lot of mess. code located here: https://github.com/GroceriStar/sd/tree/projects-v2.0/generator/projects2.0/mini-sd it's a separated module that stored at npm as well. i test it at https://github.com/GroceriStar/groceristar-fetch/tree/projects-v2/src/projects-v2/GroceryLists

another way to master rollup - slowly move our generator to separated script. right now i'm not sure if it necessary to put it into separated repository, because jumping between is hard. and actually interns working on that code. just want to let you know an options

tell me what do you think

@vadim9999
Copy link
Collaborator Author

vadim9999 commented Jun 27, 2019

If the separated generator will be hard for interns we can don't move it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants