Welcome to General Assembly's Web Development Immersive - Singapore Edition!
This Gitbook is the primary resource used throughout the course, save it to your favorites and refer to it often!
What is WDI
learn web development concepts
aquire the skills of web development
principals of computer programming / system design
experiential learning:
no grades / levels
learn skills not facts
constantly reference real-world tasks
instructors facilitate your learning experience
self-guided
learn how to learn
bring your skills up to the highest potential
What WDI isn't
competition
ranked class
fact based learning / memorization
Important Policies
Please read and adhere to the following, otherwise bad things might happen.
Prework
You should have completed the following in preparation for the course. This is to ensure that you can handle the pace of the class.
These rules are intended to be lightweight, and to make more explicit certain social norms that are normally implicit. Most of our social rules really boil down to "don't be a jerk" or "don't be annoying." Of course, almost nobody sets out to be a jerk or annoying, so telling people not to be jerks isn't a very productive strategy. That's why our social rules are designed to curtail specific behavior we've found to be destructive to a supportive, productive, and fun learning environment.
1. No feigning surprise
The first rule means you shouldn't act surprised when people say they don't know something. This applies to both technical things ("What?! I can't believe you don't know what the stack is!") and non-technical things ("You don't know who RMS is?!"). Feigning surprise has absolutely no social or educational benefit: When people feign surprise, it's usually to make them feel better about themselves and others feel worse. And even when that's not the intention, it's almost always the effect. As you've probably already guessed, this rule is tightly coupled to our belief in the importance of people feeling comfortable saying "I don't know" and "I don't understand."
2. No well-actually's
A well-actually happens when someone says something that's almost - but not entirely - correct, and you say, "well, actually…" and then give a minor correction. This is especially annoying when the correction has no bearing on the actual conversation. This doesn't mean this isn't about truth-seeking or that we don't care about being precise. Almost all well-actually's in our experience are about grandstanding, not truth-seeking. (Thanks to Miguel de Icaza for originally coining the term "well-actually.")
3. No back-seat driving
If you overhear people working through a problem, you shouldn't intermittently lob advice across the room. This can lead to the "too many cooks" problem, but more important, it can be rude and disruptive to half-participate in a conversation. This isn't to say you shouldn't help, offer advice, or join conversations. On the contrary, we encourage all those things. Rather, it just means that when you want to help out or work with others, you should fully engage and not just butt in sporadically.
4. No subtle -isms
Our last social rule bans subtle racism, sexism, homophobia, transphobia, and other kinds of bias. This one is different from the rest, because it covers a class of behaviors instead of one very specific pattern.
Subtle -isms are small things that make others feel unwelcome, things that we all sometimes do by mistake. For example, saying "It's so easy my grandmother could do it" is a subtle -ism. Like the other three social rules, this one is often accidentally broken. Like the other three, it's not a big deal to mess up – you just apologize and move on.
If you see a subtle -ism, you can point it out to the relevant person, either publicly or privately, or you can ask one of the faculty to say something. After this, we ask that all further discussion move off of public channels. If you are a third party, and you don't see what could be biased about the comment that was made, feel free to talk to faculty. Please don't say, "Comment X wasn't homophobic!" Similarly, please don't pile on to someone who made a mistake. The "subtle" in "subtle -isms" means that it's probably not obvious to everyone right away what was wrong with the comment.
We want this to be a space with as little bigotry as possible in it. Therefore, if you see sexism, racism, etc. outside, please don't bring it in. So, for example, please don't start a discussion of the latest offensive comment from Random Tech Person Y. For many people, especially those who may have spent time in unpleasant environments, these conversations can be very distracting. We want to remove as many distractions as possible so everyone can focus on programming. There are many places in the world to discuss and debate these issues, but there are precious few where people can avoid them.
5. Why have social rules?
The goal isn't to burden everyone with a bunch of annoying rules, or to give us a stick to bludgeon people with for "being bad." Rather, these rules are designed to help all of us build a pleasant, productive, and fearless community.
If someone says, "hey, you just feigned surprise," or "that's subtly sexist," don't worry. Just apologize, reflect for a second, and move on. It doesn't mean you're a "bad" person. As we said above, these rules are meant to be lightweight. We've all done these things before.
Sometimes pointing out that someone broke a social rule can be challenging or feel awkward. If you don't feel comfortable pointing out to someone that they are consistently breaking a social rule, ask a facilitator for help.
Scrum / Standup
Every morning at exactly 9.00 (so be here before then), we'll cluster together into small groups of four or five - scrums work best with small numbers of people.
Each person in a group will use a marker to put on the wall:
what they achieved yesterday after class
anything they found particularly challenging
(optional) anything useful they discovered which might help others
draw how they are feeling this morning
The point of our scrums, is not to discuss these issues but to simply flag them and create prompts for conversations later during the labs and breaks.
Journalling
This is optional but recommended. You should keep a Journal! It can be anything: a blog, a Medium series, a Word doc or literally a physical journal. The point is that at the end of each day you should take 15 minutes to write down a reflection on what you've learnt today. What you enjoyed? What you found difficult? And anything else you'd like to put on paper. Later down the course this will be a great tool to help you realize just how far you've progressed and boost your confidence to keep going.
Figure: placeholder
Licensing
All content is licensed under a CC-BY-NC-SA 4.0 license.
All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact legal@ga.co.
