PETE Stack #45
Merged
PETE Stack #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nelsonic
added
the
enhancement
nelsonic
assigned iteles, SimonLab, jruts, samhstn, katbow, sohilpandya, rjmk and jackcarlisle and unassigned nelsonic
|
@jruts thanks for reading the draft and spotting the typo. it's been corrected. ✅ |
nelsonic
added
the
discuss
nelsonic
added
the
help wanted
jruts
reviewed
Feb 16, 2017
| We were ~~pleasantly surprised~~ ***delighted*** to see the _amazing progress_ | ||
| made by the people in the Elixir, Phoenix and Elm communities! | ||
| These technologies are set to "***take off***" in 2017 and we are _excited_ | ||
| to be _sharing_ the technical/competitve advantage with our clients! |
iteles
approved these changes
Feb 16, 2017
jruts
reviewed
Feb 16, 2017
| Each element in our stack was _carefully_ selected based | ||
| on it's individual merits. <br /> | ||
| When _assembled_ into a seamless "machine", | ||
| the stack _unrivaled_ for developer productivity and word-class quality! |
There was a problem hiding this comment.
Is it supposed to be world-class quality? And if it is word-class, how do I interpret this sentence?
There was a problem hiding this comment.
thanks for spotting the typo! just committed a fix. 👍
nelsonic
added a commit
that referenced
this pull request
Feb 16, 2017
jruts
reviewed
Feb 16, 2017
| [github.com/dwyl/learn-phoenix-framework#our-**top-10-reasons**-why-phoenix](https://github.com/dwyl/learn-phoenix-framework#our-top-10-reasons-why-phoenix) <br /> | ||
|
|
||
| + **Elixir** is the _functional_ programming language used to | ||
| build using the Phoenix framework. Elixir is a _beautiful_ language |
There was a problem hiding this comment.
programming language used to build using the Phoenix framework
jruts
reviewed
Feb 16, 2017
| + **Elixir** is the _functional_ programming language used to | ||
| build using the Phoenix framework. Elixir is a _beautiful_ language | ||
| written _from scratch_ to be ***friendly, concise and efficient***. | ||
| ***Yes***, Elixir not a "_popular_" as JavaScript, Java, C# or PHP, |
jruts
reviewed
Feb 16, 2017
| build using the Phoenix framework. Elixir is a _beautiful_ language | ||
| written _from scratch_ to be ***friendly, concise and efficient***. | ||
| ***Yes***, Elixir not a "_popular_" as JavaScript, Java, C# or PHP, | ||
| but its' adoption is growing rapidly and most importantly its' |
There was a problem hiding this comment.
I never know how to write it's or its' ...
would be stoked for anyone with much betterererer engrish to fix the typos in the next PR. 👍
There was a problem hiding this comment.
It should be its in the first case and it's in the second case
jruts
reviewed
Feb 16, 2017
| [***sunk cost bias***](http://www.investopedia.com/terms/s/sunk-cost-trap.asp). | ||
| see: [github.com/dwyl/learn-elixir#key-advantages](https://github.com/dwyl/learn-elixir#**key-advantages**) | ||
|
|
||
| + **Tachyons** is the most _sane_ way of creating a _beatiful_ web app UI |
|
@jruts you are on 🔥🎉 |
jruts
reviewed
Feb 16, 2017
| brilliant and dedicated developers. <br /> | ||
| While Elm is | ||
| [***incredibly fast***](http://elm-lang.org/blog/blazing-fast-html-round-two) | ||
| the _reason_ we love elm is _nothing_ to do |
|
@jruts Sorry I merged this out from under you, got a little carried away! Let's PR in the typo corrections 👍 |
jruts
reviewed
Feb 16, 2017
| having been used by Telecoms companies for over 20 years in production | ||
| with some Telcos reporting 99.99999% ("_seven nines_") of "_up-time_". | ||
|
|
||
| > It's _far_ more likely that the _infrastructure_ provider (_e.g. AWS/Azuer_) |
There was a problem hiding this comment.
well-spotted. fixing now. flipping Microsoft and their "Azure"!! 👍
nelsonic
added a commit
that referenced
this pull request
Feb 16, 2017
jruts
reviewed
Feb 16, 2017
| Nokia continued to _dominate_ the mobile phone industry/market for the next | ||
| ***decade*** producing the _best-selling_ | ||
| **5110** and **3310** we all remember! <br /> | ||
| But by being "_ahead_" Nokia were _unable_ to see the "_contender_" |
jruts
reviewed
Feb 16, 2017
| In 2006 _nobody_ was making/buying "smart" mobile phones | ||
| with glass touch screens that ran "apps" ... <br /> | ||
| in [January 2007 Steve Jobs introduced the iPhone](https://www.youtube.com/results?search_query=Steve+Jobs+iPhone+Introduction+2007) | ||
| and _litterally_ changed the industry! |
There was a problem hiding this comment.
thanks!! fixed. (I need to go back to school!!) 😆
jruts
reviewed
Feb 16, 2017
| and instead **focus** on building something **useful** <br /> | ||
| **focus** on **User Experience** not "backend" **scalability**! | ||
|
|
||
| The _good_ news is that Phoenix was _does_ "***scale***" _really well_! <br /> |
There was a problem hiding this comment.
Phoenix was does "scale" > Phoenix was does "scale"
nelsonic
added a commit
that referenced
this pull request
Feb 16, 2017
…literally noted by @jruts in #45 (review)
jruts
reviewed
Feb 16, 2017
| The **fact** is: we _only_ use JavaScript because it is the | ||
| ["***Lingua Franca***"](https://en.wikipedia.org/wiki/Lingua_franca) | ||
| that _all_ web browsers "_understand_".<br /> | ||
| It's _definately_ not because it's a "_better_" language than Python or Lisp; |
nelsonic
added a commit
that referenced
this pull request
Feb 16, 2017
… improvements but for now, we can ship this!
|
@nelsonic that is all I found in my read-through. Good stuff <3 |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So... the reason this PR has been exceptionally "long time in the making"
is because I wanted to have a decent
learn-...tutorialforEachelement in the stack!beforeupdating this doc!Thanks to the amazing people in the @dwyl community contributing to the tutorials,
we can finally update the Tech Stack document to reflect our plans for 2017...!
This Pull Request "fixes #37 by adding:
Sorry that it's a bit "long"...
If I had "more time" I would cut it down ...
Hopefully someone
elsecan provide a bit of editorial to streamline my ramblings.Thanks for reviewing! happy to make any changes necessary.
(but would prefer this to be merged in soon so that I can show it to Kumar+Katy ...
and then we can iterate/improve laters... e.g. PETE -> TEPPE ?)
Thanks!! ❤️