IdahoEv
Joined 16 years ago
Joined 16 years ago
1) Heavy Strategy: Eclipse and Terra Mystica (tie)
2) Strategy Cardgame: Race for the Galaxy & expansions
3) Abstract: Arimaa. Runner up: tie between Go and Hive.
4) Real-Time Co-op: Damage Report. Runner up: Space Alert
5) Co-Op: Mysterium
6) Wargame: War of the Ring. Runner up: Twilight Struggle
7) CCG or LCG: Lord of the Rings LCG
8) Party Game: Time's Up Title Recall Runner up: Concept
9) Reaction time: Jungle Speed.
10) Most disliked game: Catan or any spinoff thereof
That said, Xing uses Hannah Howard's module A1Atscript (https://github.com/hannahhoward/a1atscript) to add a very Angular 2-like TypeScript annotation syntax, including A2-like component architecture.
That should make Xing apps much easier to translate to Angular 2 than other Angular 1.X apps.
For examples, there's a tutorial walkthrough in the book, which we will be continuing to expand for the next few weeks. (https://xingframework.gitbooks.io/the-xing-framework/content...)
There's a tutorial in the book (https://xingframework.gitbooks.io/the-xing-framework/content...), which is small to start but we are actively expanding.
To do any kind of fixed-price work, you need absolutely ironclad protection against scope creep. Said protection against scope creep usually must start with an extremely detailed specification - the kind of thing that takes weeks to develop, not a 10-minute phone call.
I would imagine Gigster's terms looks something like: • Client gets no input beyond the 10-minute phone call • Interpretation of the specifications given in that phone call is 100% up to Gigster • Any revision of specifications whatsoever results in a change order
With all that experience, my estimate process is now extremely honed. It takes me, quite consistently, 4 to 8 hours for a typical web startup MVP. And that's assuming I can build the product completely with technologies my team has used before.
You see two or three examples of comments in the article, and feel comfortable dismissing her point entirely as a result. But of course a written article has only room for two or three examples.
She wouldn't have written it if there weren't an absolute nonstop stream of this sort of crap over the course of years. A point she made abundantly clear, and an experience that would be oppressive to anyone.
(Not to mention the numerous things that can't possibly be read as "nice or funny", like having all your contributions ignored in favor of equivalent contributions from men. That makes me wonder if you actually read most of the article, or just skimmed and cherry picked a couple things that left you feeling justified in dismissing her.)
When you learn to listen to people who are struggling instead of dismissing them, your life will be better. I promise.
It isn't "political correctness" - the phrase implies that the language has no real effect and changing it is merely for show, or as a political statement.
Using male pronouns as gender neutral has a measurable effect on comprehension that has studied and reproduced repeatedly. Using "he" pronouns as generics does in fact lead both men and women to exclude women in their comprehension of the sentence a statistically significant fraction of the time. See for example http://www.jstor.org/discover/10.2307/27784423?uid=2&uid=4&s....
Revising language not a "thought barrier", it's an actual real benefit.
Your entire premise is false.
11) Social Deduction: Two Rooms and a Boom