Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
As engineers working on a team, we all make technical decisions. What’s the best way to implement this? Where should this function live? Is this library worth using? Some decisions, though, are larger, riskier and more important than that. But generally, they’re also far less frequent. Right now, your team might be struggling to organize the client-side parts of your application. Ember? Angular? Backbone? Flip a coin? Uh…which one has the most…retweets? These choices don’t need to be arbitrary or based on vague personal preference. Come learn a more useful and realistic approach that makes large-scale technical decisions less risky. Help us caption & translate this video! http://amara.org/v/F0or/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the video "Unpacking Technical Decisions," Sarah Mei discusses the complexities involved in making technical decisions within software development, emphasizing that these choices often intertwine with both code and people dynamics. This talk aims to provide a structured approach to tackle high-stakes technical decision-making, which is critical for teams navigating a landscape filled with an abundance of technologies and frameworks. Key points discussed include: - **The Intersection of People and Code:** Mei highlights the notion that programming itself is straightforward, but being a programmer involves navigating complex interpersonal dynamics. This duality identifies the importance of understanding both technical and human factors in software development. - **Framework Selection Challenges:** Developers often face the pressing question of which JavaScript framework to use. The proliferation of options such as Ember, Angular, and Backbone makes this decision daunting, as it can have long-term implications on a project. - **Decision-Making Process:** Mei suggests that technical decisions often stem from a combination of social factors, personal experiences, and established practices. To illustrate this, she describes the varied backgrounds of attendees at the Fluent Conference, all seeking to answer the same question: which JavaScript framework is best? - **Evaluative Techniques:** The speaker presents a four-quadrant system to aid in decision-making, which includes: - **Interface:** The code's usability and functionality. - **Activity:** The level of engagement and updates from the project maintainers. - **Popularity:** The community's acceptance and usage of the technology. - **Accessibility:** How well the project aligns with developers' backgrounds and coding styles. - **Educational Insights:** Mei emphasizes the role of learning through repetition and how deep insights can be derived from community practices. By analyzing the steps developers typically take when evaluating frameworks, one can refine their decision-making capabilities. Concluding her talk, Mei encourages attendees to recognize that technical decisions require a thoughtful approach combining all gathered data and social context. While choices regarding technology may be infrequent, understanding frameworks and making informed decisions based on accessibility and popularity can significantly enhance project outcomes.
Suggest modifications
Cancel
