| • The growth of the JavaScript community in Latin America, with multiple conferences and meetups across the region.
|
| • The challenges of finding high-quality content in Spanish for software development and JavaScript specifically.
|
| • The trust issue in Latin America, where people tend to assume English content is better quality than Spanish content.
|
| • The need for more translated content, particularly on the bleeding edge of technology.
|
| • Efforts by platforms like Platzi to create high-quality Spanish content for programming and software development.
|
| • Organizing JSConf Colombia conferences to provide access to quality educational content in Spanish
|
| • Highlighting local talent and avoiding the "colonial approach" of educating others
|
| • Creating opportunities for Latin American attendees to speak at international events
|
| • Challenges faced by community organizing in Latin America, including:
|
| • Finding people with expertise to share content
|
| • Language barriers (language of instruction vs. interpretation needs)
|
| • Securing sponsorships and resources from local companies
|
| • The JSConf Colombia conference is looking for speakers and workshop presenters
|
| • Travel, accommodation, and childcare expenses will be covered by the organizers
|
| • A call for proposals (CFP) can be submitted through cfp.jsconf.co until June 11th or 12th
|
| • Juan Pablo Buritica is returning to organize the conference after retiring from it previously
|
| • Julian and Catherine will co-direct the conference this year, with a plan to pass on responsibilities to junior organizers in the future
|
| • Mikeal Rogers discusses the explosion of JavaScript tooling and how it can be overwhelming for developers
|
| • A conversation ensues about whether supporting older versions of Node is necessary or detrimental to community progress
|
| • npm version compatibility issues
|
| • Security vulnerabilities and upgrades
|
| • Tooling complexity for newcomers to JavaScript development
|
| • Trade-offs between ease of use and long-term benefits
|
| • Return on investment for learning complex tools like Babel and Flow
|
| • Importance of starter kits and instant setup for beginners
|
| • Adapting to new tooling and its potential benefits
|
| • Standardizing build chains and workflows for popular projects
|
| • Importance of separating concerns between building and authoring
|
| • Need for one-click install or configuration tools
|
| • Comparison of different frameworks and their approaches (e.g. Create React App, EmberCLI)
|
| • Benefits of having a standardized toolchain and community support
|
| • Discussion of compatibility issues with third-party libraries and dependencies
|
| • Defining company culture through open source principles
|
| • Challenging remote work myths and lazy communication habits
|
| • Benefits of distributed teams, including cultural diversity and flexibility for non-traditional schedules
|
| • Importance of asynchronous work and breaking down tasks into manageable steps
|
| • CSS Grid specification as a pick of the week
|
| • Discussion of CSS Grid and its benefits over Flexbox
|
| • Bcrypt security UI and browser vendors' increased emphasis on secure page indicators
|
| • Removal of Symantec trust certificate by Google Chrome due to 30,000 improper certificates issued
|
| • Mention of Tavis Ormandy's work in finding security vulnerabilities
|
| • Introduction to NextJS as a React-based isomorphic frontend framework with server-side capabilities |
