TIY-Durham/2016-SPRING-FEE

语言:

git: https://github.com/TIY-Durham/2016-SPRING-FEE

2016年春季在北卡罗来纳州达勒姆的铁场进行前端工程类库
Class Repository for Front End Engineering in Spring 2016 at The Iron Yard in Durham, NC
README.md (中文)

您好,欢迎来到前端工程!

恭喜您入选2016年春季铁人队,并欢迎上课。这是一个激烈的计划,凯莉和我真的很期待亲自见到你们,并在即将到来的12周内更好地了解你们。我们也非常高兴能够教导和指导大家,看看你将要建立什么样的精彩内容,以及你将在课堂上完成任务和项目的有趣方式。

关于班级

如果你是那种想要在你离开之前知道你要去哪里的人,那么你可能首先要阅读课程大纲,其中列出了课程的基本路线图。故意隐瞒细节,因为课程和材料的节奏非常依赖于你,学生。

这是一个冷酷的现实,你们许多人已经从自己的经验中意识到:从观看视频和回答问题来学习编程等技术技能非常困难。还有一个额外的现实:在很短的时间内也很困难。等等,什么?这不就是你要来找我们的吗?嗯......是的,但没有。

学习 - 实用技能的高效获取 - 慢慢适应和突然出现,但是对技能的实践和发展的高度集中关注时期可以让你取得巨大的进步。这就是:一个高度集中的紧张,沉浸式活动时期。令人兴奋,令人筋疲力尽(甚至对我们的教练来说),并赋予他们权力。但是,为了获得最大的成功,您需要为这种体验做好准备。

我假设你已经知道了......

  • ...如何使用你的Mac。 - 您可以轻松查找文件,浏览文件夹,删除内容,安装和打开程序,以及使用这些程序执行相应的操作。如果这没有描述您,请从“返回基础”开始。
  • ...如何使用浏览器(如Google Chrome)。 - 您可以浏览网页和网站,使用Google或类似网站进行搜索,并在互联网上填写表单。毕竟你还怎么申请这门课呢?
  • ......如何进行有意义的,富有成效的研究。 - 鉴于您不熟悉的主题,您可以使用自己喜欢的搜索引擎,库或同行网络来发现有关该主题的准确信息。您甚至可以进行元研究 - 研究 - 研究某个主题,找出其他人正在寻找的内容,并发现您自己问题的有效性。
  • ......如何列举问题和解决方案的步骤。 - 提出问题,您可以 - 以不同程度的细节和成功 - 生成描述问题的步骤列表和几个可能的解决方案。如果你把这些步骤交给另一个合理的人,那个人可能会跟着他们来完成解决方案。
  • ...如何按照一系列步骤重现问题或解决方案。 - 给定一系列步骤,您可以认真遵循它们并认真完成,产生类似的结果。这体现在许多不同的领域:烘焙(不仅仅是烹饪),机械修复,工艺(比艺术更多),农业或园艺。
  • ...如何读写基本的HTML和CSS。 - 给定明确的方向,您可以以60%或更高的精度再现给定的设计。关于你被告知使用X或做Y的原因可能还有很多问题,但你知道“标签”是什么意思以及如何将“样式”应用于其中。

如果这些技能中的任何一项对你来说都很困难,那并不意味着你将成为一个可怕的开发者。这些不是成为一名成功的开发人员的先决条件,只是像这个快节奏的环境中的潜在限制。如果此列表中的某些内容让您感到害怕,请询问我们。我们有可能使用一些资源来快速掌握这些主题中的一个或多个。

灌注泵

为了在这个(或任何)课程中取得最大的成功,你的大脑需要初步了解我们将在课堂上(非常快速地)涵盖的术语和概念。你不需要很多 - 最少20个小时,但也许100个小时左右是最佳的 - 你不需要多年的经验 - 课前30到90天就足够了。

作为第一步,完成我们的准备工作任务:00 - Ready Player One。这可以作为您在学习过程中个人所在位置的初步衡量标准,并为您提供在第1天成功所需的初始曝光度。请不要将此(或任何)任务视为游戏级别进行殴打;您的目标不仅仅是完成作业一次,而是通过熟悉材料来实现学习目标。

日常生活

课程开始后,您将使用类似的流程提交作业并展示进度。每个作业将作为README.md文件在适当编号的文件夹中提供,我们在课堂上一起制作的任何代码都将放在该文件夹旁边。您将负责在此回购中打开一个问题并包含指向您的工作的链接以供审核。有关该过程的详细信息,请参阅Wiki中的关于分配。

本文使用googletrans自动翻译,仅供参考, 原文来自github.com

en_README.md

Hello and welcome to Front End Engineering!

Congratulations on being selected for the Spring 2016 cohort of The Iron Yard, and welcome to the class. This is an intense program, and Kelly and I are really looking forward to meeting each of you in person and getting to know you better over the course of the upcoming 12 weeks. We're also really excited about teaching and mentoring you all, seeing what awesome things you'll build and what interesting ways you'll approach the assignments and projects in the class.

About the Class

If you're the type who wants to know where you're going before you leave, then likely you'll want to read the syllabus first, which lays out the basic roadmap of the class. Details are intentionally withheld, as the pacing of the class and material is very dependent on you, the students.

Here's a cold reality many of you already realize from your own experience: it's very difficult to learn a technical skill like programming from just watching videos and answering questions. There's an additional reality: it's also very difficult in a short amount of time. Wait, what? Isn't that what you're coming to us for? Well... Yes, but no.

Learning -- the productive acquisition of practicable skill -- comes slowly in fits and spurts, but a period of highly focused attention on the practice and development of a skill can allow you to make great leaps of progress. That is what this is: a highly focused period of intense, immersive activity. It's exciting, exhausting (even for us instructors), and empowering. However, in order to be most successful, you need to be primed for that experience.

I assume that you already know...

  • ...how to use your Mac. -- You can easily find files, navigate through folders, delete things, install and open programs, and perform the appropriate actions with those programs. If this does not describe you, start with "Back to Basics".
  • ...how to use a browser (like Google Chrome). -- You can navigate through web pages and sites, perform searches with Google or similar, and fill out forms on the internet. How else did you apply for this class, after all?
  • ...how to perform meaningful, productive research. -- Given a topic that you're unfamiliar with, you can use your favorite search engine, library, or network of peers to discover accurate information about the topic. You may even be able to perform meta-research -- research about research -- on a topic to find out what others are looking for and discover the validity of your own questions.
  • ...how to enumerate the steps of a problem and solution. -- Presented with a problem, you can -- to various degrees of detail and success -- generate a list of steps that describe the problem and several potential solutions. If you gave those steps to another reasonable person, that person could probably follow them to fulfill the solution.
  • ...how to follow a sequence of steps to reproduce a problem or solution. -- Given a sequence of steps, you can follow them carefully and conscientiously to completion, producing similar results. This manifests in many different areas: baking (moreso than just cooking), mechanical repair, craftsmanship (moreso than artistry), farming or gardening.
  • ...how to read and write basic HTML and CSS. -- Given explicit direction, you can reproduce a given design with 60% or more accuracy. There are probably lots of questions remaining about why you were told to use X or do Y, but you know what "a tag" means and how to apply "styles" to one.

If any of these skills are a struggle for you, that doesn't mean that you'll be a horrible developer. These aren't prerequisites for being a successful developer, just potential limitations in an environment as fast-paced as this one. If there's something in this list that scares you, ask us. Chances are we have some resources that you can use to get up to speed on one or more of these topics.

Priming the Pump

In order to be most successful in this (or any) course, your brain needs some initial exposure to the terms and concepts that we're going to cover (very quickly) in class. You don't need a lot -- 20 hours minimally but maybe 100 hours or so would be optimal -- and you don't need years of prior experience -- 30 to 90 days prior to class is sufficient.

As a first step, complete our prep-work assignment: 00 -- Ready Player One. This serves as an initial gauge of your individual place in the learning process and gets you the initial exposure you need to be successful on Day 1. Please don't treat this (or any) assignment as a game level to be beaten; your goal is not just to complete the assignment once but to fulfill the learning objectives by becoming familiar with the material.

The Day-to-Day

Once the course begins, you'll use a similar process to submit assignments and demonstrate progress. Each assignment will be delivered as a README.md file in the appropriately numbered folder, and any code that we produce together in class will be in that folder alongside it. You'll be responsible for opening an Issue in this repo and including links to your work for review. For details about that process, see About Assignments in the wiki.