-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Comments
Should I curate some interns or be like a developer? |
explore right now what we're doing. coding at sd is not necessary. let's
put our powers at planning. maybe for quick commits we can work on
generator, but some tasks is not finished yet - so i'm conflicted
|
@atherdon Coding school
|
@vadim9999 do 10-20 questions about coding school and publish it at hackernoon forum:) going totally open |
I need tasks that I will refresh knowledge in my brain or study a new feature that helps me to take a job.
|
ok, noted.
i'll prepare more tasks and put them here soon |
also - with changes that i'm making at fetch - it will became ES6 style, soo... But we can find something more interesting for you.
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 |
If the separated generator will be hard for interns we can don't move it |
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.
The text was updated successfully, but these errors were encountered: