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

RFC: Input ideas #36

Closed
2 of 6 tasks
zonzujiro opened this issue Jan 29, 2020 · 15 comments
Closed
2 of 6 tasks

RFC: Input ideas #36

zonzujiro opened this issue Jan 29, 2020 · 15 comments
Assignees

Comments

@zonzujiro
Copy link
Member

This issue is about

  • Course
  • Event
  • Project
  • Other

By/for

  • kottans
  • non-kottans

Subject: We need new ideas about how to make Input more interesting for us

Term/duration: none

Keywords: Input, Kyiv

So, with @OleksiyRudenko we came to the idea, that we can add some additional part to Input conference and, probably, make it more interesting for us to contribute our time in it.

This issue is made a start for a discussion of what we can add.

The idea to start a discussion - reduce the number of talks and make two streams:

  • one with talks
  • other with workshops. As an example, interviewing visitors about JS all day and give feedback right after the interview
@zonzujiro zonzujiro self-assigned this Jan 29, 2020
@Croftyland
Copy link

I got an idea to invite speaker from Germany. He is member of the
@webpack core team. Will be interesting for you?

@zonzujiro
Copy link
Member Author

For Input? Can be. What experience he can share with auditory?
And will he be interested in trainy/pre-trainy auditory?

@Croftyland
Copy link

Not really,he is better for more advanced audience.

In case of input,I can invite girl from Facebook with interview topic

@OleksiyRudenko
Copy link
Member

Not really,he is better for more advanced audience.

Perhaps he might run a workshop on fine tuning webpack config? Beside speaking on some related and even more advanced topic

@OleksiyRudenko
Copy link
Member

OleksiyRudenko commented Jan 29, 2020

But i agree on that technical conf even for beginners should be something different from INPUT aimed at those who are just entering the industry. Mix up won't work well.

Technical conf might be named e.g. INPUT: FE or INPUT: JS.
I'd suggest branching off discussion on a tech conference to a dedicated thread/issue

@zonzujiro
Copy link
Member Author

IMO, such a guy can be a good candidate for tech conf with advanced speakers.
But we should discuss this format together next time

@Croftyland
Copy link

As for me, word "Input" is not suitable for advanced speakers. We should step away from this idea

@zonzujiro
Copy link
Member Author

@Croftyland RFC is about Input, jeez

@AMashoshyna
Copy link
Member

Interviewing visitors on JS sounds good to me. Last year we also had an idea to make CV workshop. But both are probably more interesting for visitors than for us.

@OleksiyRudenko
Copy link
Member

Collection of topics of interest to our audience from a survey we conducted before launching INPUT

@OleksiyRudenko
Copy link
Member

Bodya Kovalchuk:

Паралельні виступи розбиті по категоріям (наприклад менджмент, веб, геймдев, тестування)

coffee time з крутими спікерами

стійка(і не одна) де є «прожарка» резюме , приходиш кладеш, через пару хв получаєш поради та критику

@OleksiyRudenko
Copy link
Member

Alex Lapshyn:

хочу заполнив таблицу "кем я хочу быть" получить 1) контакты людей, которые могли бы ответить предметно на вопросы по теме
2) контакты людей из компаний, в которых есть открытые вакансии джуновские по этому профилю
3) персонального ментора

@OleksiyRudenko
Copy link
Member

Anna Alymova:

Разработчик порнхаба в маске рассказывает как он туда попал?

@suchov
Copy link
Member

suchov commented Feb 23, 2020

#38

@suchov suchov closed this as completed Feb 23, 2020
@OleksiyRudenko
Copy link
Member

@suchov how 'bout renaming this ticket as "INPUT 3" and reopening it? )

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

No branches or pull requests

5 participants