Mission impossible   Leave a comment

Jak utrzymać się na jako takim poziomie w pracy nad aplikacjami webowymi. Autor z wydawnictwa O’reilly przytacza wielowarstwowy model kompetencji dla dewelopera aplikacji webowych (jest ich coraz więcej):

  1. Networking – DNS and TCP/IP basics provide a foundation.
  2. Web protocols and communication styles – HTTP, REST, Websocket, and WebRTC connect us further. Caching and proxies often appear inside large applications as well.
  3. Data and document formats – JSON, XML, CSV, HTML, and sometimes more options let us share information.
  4. Web server configuration – Creating a host for information means knowing about web servers, operating systems, and sometimes more.
  5. Data storage – Relational databases, NoSQL databases, file systems, and Object-Relational Mappers (ORM) give you places to put things.
  6. Server-side programming – Handling requests and integrating information using your favorite tools and languages. Node and JavaScript? Ruby on Rails? Python and Flask? Or something else entirely?
  7. Content management systems – Reusing existing approaches can save you lots of time, or create new integration problems.
  8. Library and framework management – Which libraries to use, if any? How to combine them? How should you create internal libraries and frameworks?
  9. Bundling and packaging – How do you distribute what you’ve created? Does packaging it as an app make sense? Or, in another context, do you need a Content Distribution Network? Or processing in the cloud?
  10. Device capabilities – It might seem like there are more HTML5 APIs every week, but geolocation, local storage, web workers, and many more are constantly broadening what you can do.
  11. Template design – How do you create easily reusable (and flexible) structures?
  12. Content presentation – How should you structure the content of your site? What should it look like? HTML and CSS dominate here, but it’s also critical to understand the contexts in which content appears.
  13. Interface programming – HTML, CSS, and JavaScript. Data binding has added new JavaScript-centric dimensions.
  14. Performance – How do you make this all happen fast?
  15. Resilience – How do you make sure this happens reliably?
  16. Security – How do you make sure this only goes to the right people and places?
  17. Navigation design – How should people (or other applications) find their way through what you’re building?
  18. Graphics – Show, don’t tell, but with images, SVG, Canvas, or WebGL?
  19. Reach – How do you make sure people (or other applications) can find what you’ve created?
  20. Interface design – How can you create interfaces that people can use? That people want to use? That work in the device contexts of their choice?
  21. Visual design – Making all this work and look good and probably look distinctive is a challenge.
  22. Content – What are you trying to convey, or ask?
  23. Product design – What are you building? What problems does it solve, and how?

Chyba jeden człowiek tego wszystkiego nie ogarnie – liczy się zespół

Posted 7 Październik 2015 by marekwmsdn in Bez kategorii

Skomentuj

Wprowadź swoje dane lub kliknij jedną z tych ikon, aby się zalogować:

Logo WordPress.com

Komentujesz korzystając z konta WordPress.com. Log Out / Zmień )

Zdjęcie z Twittera

Komentujesz korzystając z konta Twitter. Log Out / Zmień )

Facebook photo

Komentujesz korzystając z konta Facebook. Log Out / Zmień )

Google+ photo

Komentujesz korzystając z konta Google+. Log Out / Zmień )

Connecting to %s

%d bloggers like this: