Spectrum is now read-only. Learn more about the decision in our official announcement.


Romania's First JavaScript User Group


A *few* notes from yesterday's meetup.

May 30, 2019 at 1:50pm

A *few* notes from yesterday's meetup.

May 30, 2019 at 1:50pm (Edited 2 years ago)
Hey guys, A few notes from yesterday's meetup. Ps: hope i'm not acting out of place for posting this && it's a damn long post && sry for the corporate-ish language, i just find it much easier to express certain ideas more concisely this way.
The big ideas regarding the 'future of iasiJS' could be resumed in a few lines like this:
Main Directions:
  1. Meetups - monthly - all levels
  2. Workshops - seasonal - junior (mainly)
  3. Conference - yearly - mid-senior
  4. Community 'Projects' - on-going - all levels intertwined
Main Focuses: A. Organizational Culture B. Online Engagement - for Spectrum atm C. Growing the community - more peoples more funs
=== === ===
(1) Meetups
=== You've mentioned that a queue for future presentations is already 'in the works'. - Big up.
=== The people from ${.net iasi} have been posting their future meetups, even with little details other than the name of the Event.This helps a lot in terms of creating ${customer} interest. -- I'm aware than it has been mentioned that situations could arise, where the speakers can't make it to the presentation, and this is the main issue with following a similar approach.This could be somewhat avoided if we were to apply a similar 'paper submission' to that of conferences, where slides, notes and/or even a simple draft-ish laptop-camera-ish recording of the speaker were to be submitted ahead of time. This requires further thought, but I wanted to propose a starting pint for this topic.
=== Another nice-to-have direction would be to focus on a certain Topic for a period of time (ex 3 months) -- it can be an issue like server-side rendering, memory management, good practices in insert-framework-here - basically any topic which could invite multiple meetups/discussions/threads over a said period, but would provide increased value for the ${users} who attend/join in. -- In the long run, such efforts could be synced with other UserGroups, and even though each community has a monthly presentation only, Iasi could have one-or-more presentations each week, which approach the same issue, from different points of view / fields of activity. This would also create a great environment to better document the topic, and provide great packs of materials for future presentations on the subject, great learning spots for anyone interested, and nice research points that would encourage a deeper dive in such subjects -- which could be later shared with the world. Optimistic, sure. Doable, indeed.
=== One thing which I've seen being requested in other meetup groups as well, is having all presentations recorded and/or live streamed. In lack of anything, anything would do as a start - a simple phone/basic-camera recording is better than nothing. As it picks up, this can be improved. -- Another would be to have materials posted as a follow-up to each talk. Again, for starters, simply posting the slides with the actual video would be a great step forward. A simple follow up to that would be to have relevant materials or the sources used to create the talk, posted on the group. In an ideal world, these would be created ahead of time, when the speaker submits a talk, but we're getting a little ahead of ourselves atm.
=== === ===
(2) Workshops
-- This got me personally wet af enthusiastic, and I think that Iasi JS is the perfect environment to develop such an initiative. My thoughts on the matter would include: -- start simple: get a few devs which have half a saturday free each month - make a few simple 2-4h, hands-on, intro-to-${framework} || basics-of-efficient-${thing}. -- As the target audience is junior level, getting some code down with your own fingers, gives them a great foundation to research the ${topic} further on. Getting them ^^ hooked ^^ on React, teaching them a bit about Git, getting started with sass/less, or approaching any simple-but-practical 'requirement' would be pure gold.
-- This can be further sustained through Spectrum, where a thread containing relevant links to documentation, youtube videos, etc, could create a great engagement, both at the start and in the long run. This would also create an environment where juniors could help each other, as any little experience/knowledge could go a very long way. IT creates involvement, it encourages interaction and it gives a sense of belonging and appreciation, which is the foundation of any group culture. -- in the longer run, these could be aggregated into a 8-h day-long workshop, optimally at the start of the faculty year (oct) -- when interest is high -- or right after first exams of second term (apr-mai) -- when depression for slacking off and fking up at the tests -- would have most appeal and would be a great time for absorbing info - especially if it's simple, practical and actually used in the 'real world'.
=== === ===
(3) Conference
Not much to add here, but I would like to point out a few ideas that were discussed. -- As Dean stated: Even if people can buy a ticket for 60-70Euro, the conference must assure an adequate baseline experience, as if for the price of 140Euro. As some people/companies will actually pay said 140Euro, that's the minimal viable standard for the whole attendance. -- Pricing policy: the general feeling from the crowd was 'very acceptable and doable' or even 'go higher, to actually represent the value provided', the main feeling from the core team was 'i know it's much, but we can't go lower'. This might be a good discussion point for Spectrum. -- Timing : it's a very short time to set everything up, yet if the speakers are on board, and the sales campaign (addressing companies, for start) starts within june, it's well within decent parameters. This could also be used to assess the technical/experiential wants/needs of JSers from different companies, to cater to said requests with the 3 users from Iasi, and/or use them to target the speakers for future conferences/meetups/etc.
-- Regarding the idea of delaying the conference, Vlad's arguments regarding 'already having confirms from speakers', 'november being less active and more accessible for getting location and participants', and also the audience's 'what would actually change if we delay with 6 more months, if we would just sit idle or doodle ideas, and be exactly in the same point as we are now only 6 months later.
-- Live streaming and virtual ticket: the idea of having live streaming thoughout the event (like other conferences do) was universally praised, while having to pay a virtual ticket (10-30Euro) was not so much - the reasoning being that it would defeat the purpose of sharing information with all those interested in it (which is the main purpose of such JS usergroups/communities).
-- A point is to be made here about the 'fairness' of some people having to pay for the conference, while others can simply watch it online -- countered by Vlad's argument that 'people attend the conference for the experience in itself, for the atmosphere that we are aiming to offer, for the chats after the talks and the networking in general and that can only be felt by those who physically attend. Even more, as the target is to assure most of the tickets through companies, not individual sales, this might be a mute point.' -- This can also constitute a great opportunity to create 'Conference Kits' (t-shirt, stickers, whatever) that the online viewers could purchase for said '10-30Euro', and would further enhance their experience and engagement.
=== === ===
(4) Community Projects
These would involve members getting together 'outside the normal meetup timeframe' and working together for a certain goal. These would include:
=== Creating 'Hack Teams': -- multiple groups of 2-3-4 developers, each on their area of focus (design-layout-styling / front-end-js / node), which gain experience working together, and thus better know how to push a product in a short amount of time. -- can include all levels jr/mid/sen working together, and facilitate a greater knowledge transfer and learning experience, with bonus impact for the 'outside community'. The juniors would have a tremendous learning experience, as they would get exp with working within different teams, would get direct code reviews and guidance, and would have a practical project contribution to show off to future employers. Also it creates a great mindset of helping out - which benefits everybody, not just Iasi JS. -- then simply be present at any of the concurrent hackathons - Civic Heroes, CodeForRomania, StartupWeekend, or any other that might pop up -- or even create our own: get together, form teams, solve an issue, or create our own apps (i personally wouldn't mind creating the next gagillion-dollar flappy-bird-ish app, that could pay for the next few hundred conferences).
=== Creating our own apps: -- anybody can propose a project (such as the 'events calendar aggregate' discussed here). Teams organize themselves, and can also work independently. Basically, start simple and see where it gets us. The bottom line would be that it creates purposeful engagement, which is right up the alley with our current goals. -- creating our own games - this goes hand in hand with having informal meetups -- so, we make a few teams, pick a genre (racing, platformer, etc), get a few days for each team to create their game, and in one day in the weekend we get out the vodka and have a tournament playing said games -- with punishments/rewards involving getting shit-faced-drunk among friends and colleagues, and giving love to all the dead relatives of the dev team when you've lost because of a stupid bug. This could also be spiced up with having each bug found institute a punishment for the dev team. All in all, there is a lot of potential to be had, and a lot of ways to go about it.
=== Having informal events -- as does JS Pub, what would stop us from gathering people together one night, and having a good old-fashioned Pub Quiz related to Javscript? In the first part, people could make their predefined team (friends, colleagues within a company, random foreeveralones on the spot) and duke-ing it out. Beers will be present, shots for the winners, all the good stuff. In the second part, all devs are split into 3 teams - jr/mid/sen and they are all given the same set of generalized questiones -- and if at any point the jr team beats the sen team at a topic, we can kindly offer them a blank resignation form and directions to the mcdonalds employment line. Again, the sky is the limit. --'Portofolio Reviews' as designers currently do, we could follow the model and have juniors present their work/code and get practical insight about what they could improve. As with all the others, if implemented adequately, it could easily check-off all the Main Focuses.
=== === ===
(5) Extra
=== Regarding the events aggregate, I;m the one who created , as it was a clear need to such a tool. In the past two weeks, I've been neglecting it, but that's besides the point. The whole point was for it to become a useful tool and nothing else. It is created with vanilla JS, no frameworks, no snippets - so it is easy to adapt into anything else. I'm more than willing to push it to github and make it available for all, and if anyone wants to get on board with this, it can become an iasiJS project and we could recreate/adapt it to whatever better suits the needs of the community. In short, if people want to get involved, and create a team to develop this tool, i will 'gladly renounce ownership or any shh like that' and would be more than happy to join the grind.
-- As a secondary point of constant engagement, last week I've made , a basic 'library' which kindly insults the dev when an error occurs. This can be an on-going project, where anyone could propose new insults to throw, and new members can join in the fun. When there is enough salt added, it can be launched as a fun project from iasiJS, to gain a little more notoriety in the outside world.
I know this was a lot to take in, but I honestly hope it helps to at least narrow down the key points of interest moving forward, and to help us with providing some nice value to all involved.
Fun times ahead :)

May 30, 2019 at 1:53pm
Great job man, we would definitely love to do the Extras :D
sry for the formatting. working on editing it right now.
btw, do you know if our events are showing up on inis? (I'm asking because we are the only private meetup I know and hope that doesn't mess it up)
On inis itself, the event shows, because they are all individually hard coded. Events that have passed are not generated, as this is the case here.
The only thing that might not work if the event itself is private on Facebook, and people that follow the link and don't have access to it might get a 404 or something from Facebook itself. Haven't checked that part.
As I was saying yesterday, a good starting point for jshame would be the bash insulter
I would suggest having it as a webpack plugin or eslint plugin rather than on window error, the reasoning behind this is the fact that you could very easily deploy it in prod.
Also, I would add the following Are you pulling a Leeroy Jenkins ?
Yes. I wanted to mention it but couldn't remember the name :))
Basically, any implementation would do, as the point of the library/plugin/whatever would be to create fun engagement amongst members (old and new) and to gain a little notoriety as a Community. <3