6 ms·
SOAP? Jesus. I think his list is behind the curve; a modern web dev would want to learn: - Javascript, Javascript, Javascript - Frontend: Backbone / Angular/
by Torn 14y ago
SOAP? Jesus. I think his list is behind the curve; a modern web dev would want to learn:
- Javascript, Javascript, Javascript
- Frontend: Backbone / Angular/ whatever MV* framework takes your fancy
- Backend: restful web services, good APIs. MVCs like Rails/Django if you can't push that stuff to the client.
- CSS pre-processors (SASS, Less, etc). Using classes instead of IDs, for modular, re-usable css. OOCSS ideals and methodologies.
- Dependency management via AMD / requireJS.
- Templating (underscore, dust, hogan, etc.) be it client or
server-side.
- Page performance (PageSpeed Insights, Chrome Dev tools, etc) - to get content on the page ASAP, in seconds. On that note, to keep up with the Velocity web perf conference.
- Monitoring and Analytics - Real User Monitoring, Synthetic Benchmarks, A/B testing, Dashboards
- Fast development pipelines through something like Mimosa
- nicholassmith 14y agoThat sounds more inline with the jobs I've seen floating about for web-devs recently, although there's probably plenty still relying on the good old tools.
- jasonlotito 14y agoOh, that's some clever scotsmaning there, laddy. =)
- venus 14y ago> MVCs like Rails/Django if you can't push that stuff to the client Uh, how exactly would you push your API to the client?
- mcgwiz 14y agoI believe he means that if you cannot use an architecture where you push presentation logic to the client as JavaScrpt (aided by an MVC-like framework like Backbone), serve all HTML/CSS/JS statically, and serve data dynamically through a web service (e.g. node + express or express-resource, RoR or Sinatra, MS Web API or WCF), then it's important to know a modern (MVC-based) server-side web framework dynamically generating HTML.
- jonknee 14y agoOnly learning new stuff is all fine and well until you're tasked with integrating systems and the other vendor provides a SOAP interface and a giant WSDL file for documentation. It's happened to me a lot of times, I can't imagine that I'm unique.