My role with my last employer involved creating websites, applications and widgets with front end technologies like HTML, CSS and JavaScript. Other parts of my job included code reviewing commits and running training exercises to spread the knowledge around. When I handed in my three weeks notice, they were quick to ask me to write up guidelines on the best way to write maintainable, clean and accessible code. What follows is a GitHub hosted document, allowing for revisions, forking and issue logging - a concept I “borrowed” from the great resource JavaScript Garden.
Considering my knowledge is all gleamed from many years of reading Hacker News and following Twitter links, it definitely has holes. I am completely self taught in that regard. So although I can’t vouch for the accuracy of all the information, hopefully you can log any corrections or raise any questions via the issues interface.
115 Notes/ Hide
-
fluticasone-propionate-ointment reblogged this from taitems
-
immenseidol39 reblogged this from taitems
-
trampoline5d reblogged this from taitems
-
spiele12 likes this
-
davidchola likes this
-
adwords-optimering likes this
-
shamwow-review likes this
-
hiit-training likes this
-
seology likes this
-
gritboys likes this
-
cupcake-wedding-cakes likes this
-
birthing-ball likes this
-
seoservicegreece likes this
-
rosie-huntington-whiteley-source likes this
-
hotel-cluj likes this
-
cadouri-haioase likes this
-
genti-ieftine likes this
-
last--minute likes this
-
taitems posted this
