http://www.jsfuck.com/ | |
// RUN THIS IN JAVASCRIPT | |
([]+{}+[])[!!{}+![]]+([]+ | |
{}+[])[!!{}+!![]]+(!{}+[] | |
)[!{}+![]]+([][{}]+[])[!{ | |
}+![]]+(!{}+[])[![]+!!{}+ | |
!!{}+!![]]+({}+{})[(!!{}+ |
##How to start as a Front-End Developer
I've been asked this question many times by friends/colleagues and never had the chance to answer it properly.
I believe it's not about how many things you need to know more than it's a process you should flow. also it's not all about learning you should practice skills you gained and sharpen them often.
So, I curated here what could work as a plan/resources for you to use:
It's about semantics here you should know how you can fully describe structure of data you are displaying and when to use different tags to describe what. This important for maintainability/performance of your code and also for search engine and screen readers.
- no upfront installation/agents on remote/slave machines - ssh should be enough
- application components should use third-party software, e.g. HDFS, Spark's cluster, deployed separately
- configuration templating
- environment requires/asserts, i.e. we need a JVM in a given version before doing deployment
- deployment process run from Jenkins
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
- Follow standard conventions.
- Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
- Boy scout rule. Leave the campground cleaner than you found it.
- Always find root cause. Always look for the root cause of a problem.