From 904e96b131327acb80a816e4626a0df9e45c6f64 Mon Sep 17 00:00:00 2001 From: Tyler Renelle Date: Wed, 11 May 2016 18:14:06 -0600 Subject: [PATCH] added to #4 --- client/src/blog/posts/4.js | 2 ++ 1 file changed, 2 insertions(+) diff --git a/client/src/blog/posts/4.js b/client/src/blog/posts/4.js index 2d522c3..4e5672c 100644 --- a/client/src/blog/posts/4.js +++ b/client/src/blog/posts/4.js @@ -37,6 +37,8 @@ let body =

Those are two extremes - target somewhere in between, see my list of job boards. Apply to medium-sized companies.

Conclusion

+

Thing is, my wife actually started making cash before knowing the definition of "algorithm". Experience is people who disagree do so on principle, not evidence. Their example is some offshore-borked project (compared to American artisanal code) and their mustachios quiver with rage. If you disagree, ask yourself - are you a hipster? Maybe it's the "Uncertainty Principle" as my real-life examples I partially coach. Perhaps striking out on your own without a helping hand is a different story. But I keep hearing the same thing over: "you need the fundamentals," and I keep seeing that actually proven wrong. To me evidence speaks louder than theory.

+

You don't have to be the best to succeed in this industry. Not everyone need be an engineer; some can be coders. You don't need countless years' experience in substack languages, understanding pointers and registers or a framework's history to succeed. Those nuggets will help you absolutely, but they're not strictly necessary. Am I encouraging mediocrity? Of course not, but the barrier to entry is lower than the nay-sayers say. You'll learn what you need as you go, and you have to start somewhere. Start here!.

;