Front-End Development Micro-community Vol. 3
Akron Front-End Development Micro-community (#AkFED) wrapped up its third meeting on June 25th. The focus was a Lean Coffee format that allowed participants to vote on and discuss a wide range of topics in 5 minute increments.
The group was split off into three teams. Each team wrote a list of topics that they wished to discuss and posted them on the wall under the “To Be Discussed” header. They then voted and the topic with the highest vote went under the “Discussing” header. The moderator for each group kept everyone on track as they explained or asked questions about certain topics.
During this meeting there were a LOT of topics discussed, so we put together a follow-up email with links to various resources and topics: Link Here.
Yellow team discussed Node.js, JS module options, CSS property order, and CSS organization. There were a couple of less experienced coders at the table and the conversation evolved into an overview of what Node.js was. This led into JS module options, but devolved into less complex discussions about CSS. The whole group came to a consensus that alphabetical was the way to go and that naturally led into the organizational aspect of CSS.
Red team discussed React vs. Angular, source control, style guides, custom CSS vs. frameworks, and code workflow. There were a couple newer coders at this table as well, so proper source control workflow was discussed using Git. The feeling towards rolling your own custom CSS vs. using a framework such as Bootstrap was a unanimous “Use both, but for different situations”. When creating a quick prototype or running on a short deadline where time is more important than initial performance, use a framework. When performance is a key factor and you’re working on production code, going the route of writing your own CSS should be the best choice.
Blue team discussed static file cache busting, headless CMS, Angular, text editors, and where to find work.mAngular was discussed as a great use-case for CRUD applications (those that access the database a lot). Kevin informed the group on what “headless” CMS was as well of gave some resource examples on the topic. The site Glassdoor.com was discussed when thinking of workplace potential, and the text editor of choice for Mac users was Atom, while on PC most used Visual Studio.