Summary of NordicJs ‘‘16
NordicJS - What is it?
This year the conference was held at Munchen bryggeriet in Stockholm, a big venue for holding conferences and bigger kinds of meets. Approximately 800 people came to se the talks that were held for two days.
The speakers talk about things from js framework performance to how to create art using math or how to program a rasberry-pi to send you photos of your cat from your home. Most of the talks are generally brief demos of the application or topic with purpose of get you kickstarted or inspired to learn more on the topic.
Talks were generally 30 minutes, with the exception of a few “ligtning talks” wich were shorter, 5 minute talks from people/businesses attending the conference.
My Take away
TL;DR Prototyping and MVPs are great!
The second is that it is really great doing TDD and prototyping. I’d rather do prototyping over TDD since prototyping tests even the ideas and interfaces, rather than just the code. But I still have much faith in writing tests.
The third one is something I took from the first talk, the talk from Jeremy Keith talking about the resilient web, progressive enhancements and most importantly the power of the URL; being able to post an URL wherever on a post-it and whomever goes to that URL can instantly install your service, right then and there, from any device with just a browser. That message and point talks about how powerfull of a media the web really is.
There were alot of great talks and I was totally exhausted and super filled with inspiration at the end of each of the days, so I will only tell of the talks I remember the most.
His talk bout resilience. The first talk everyone was super pumped exited to be at #NordicJs, we were not yet annoyed by the pressing heat and low amount of oxygen, and this ,really original guy came up and talked us through some history how things came about, and how stable some things were, and how unstable some other things were. Then he told us his methology and approach to things, and everyone was super inspired! Blog about resiliance
Her talk was “From Software to hardware”, a talk and a case study how she with JS and a ras-pi take photos of her cat.
She walked through how she setup and installed node on a ras-pi, then setup all the things in order to make the ras-pi work a camera, check for movement, take photo, scan said photo for cat faces with an algoritm, if there was a cat in the photo: send imageURL as a text to Tomomi. The project is live and she keeps getting loads of texts and enjoying it!
TL;DR Separate the hard things from the easy things with modules.
I thought Ashleys talk was very philosophical, and she kept on asking philosophical questions about ‘why’ and ‘what is modularity?’ and followed them up with quotes from philosofers.
Ashley showedstats started giving you performance issues when you had too many modules in your code. Fewer modules resulted in greater performance for your application.
In the talk there were some more stats on how NPM has grown and even more philosophical questions, but my main take was just what I said in the beginning, separate the hard parts form the easy ones in your code.
TL;DR Performance test-results depends on scenario-testing and circumstances
Slides Afrom yesterday’s talk: https://t.co/4Nh8WOXEb2— Evan You (@youyuxi) September 9, 2016
Evan was the person I did the 2nd most research on (I watch alot of #funfunfunction), I started doing a resume site with Vue for testing it out partly.
Evan talked about JS Framework performance, and taught us how diffrent architectures handle diffrent scenarios worse/better depending on some circumstances. The conclusion was that we should all take performance test-results with a grain of salt, and atleast run the scenarios we intend using diffrent tools for their intended purpose before we be the judge if it is correct or not.
Like some frameworks handle rendering small changes deep into the component-tree very well, while it might do inital render and full re-renders poorly. While other frameworks might be super fast at inital render and do full re-renders at blazing speeds.
He was the first one mentioning doing a protoype in order to actually test if the tools/framework was a viable option for the project you had in mind. Not relying too heavily on generic test-results.
TL;DR Dirty dirty front-end tricks with css calc() and cool email hacks with :checked that no project manager or sales person must be aware of.
Vitaly is editor-in-chief at Smashing Magazine, and he was the one starting the second day, he brought candy (I caught the first one he threw, epic catch!) and alot of energy and humor.
Using a width value not to set the width but to trigger which of min-width and max-width will set the actual width. Mind. Blown. #nordicjs— Anders Bornholm (@osirisguitar) September 9, 2016
He showed us really cool tricks for responsive font-sizeing and how to do interactive progressively enhanced emails, all with zero media-queries. The tricks were cool and inspiring and a bit horiffying with what you actually can do with email!
TL;DR Do performance tests in TDD
When working in some projects and doing some kinds of services, there may after a while in production/development come up issues on certain occassions, maybe even uncomfortable occassions.
Performance matters, and sometimes the cases in wich performance lags behind might not be all that appearant until you test for them. Also, doing performance tweaking is easier earlier in the process rather than refactoring an already matured codebase.
Mattias Petter Johansson @mpjme
“If you know map, I will teach you monads”
TL;DW Visual patterns from mathematical rules
A week almost after the event, MPJME and Irina did a collab and together they made a Cellular Automata it is actually not that fun to code them, but the results are really nice too look at.
TL;DW ESNext is easy to grasp, service-workers are aweseome!
I had a great time at #nordicJS and if you want to read more what other had to say about the conference, I suggest to scan the hastag #nordicJS.
If you want to watch more of the talks they uploaded all the talks to youtube and saved them in an unordered playlist here.