I have just started web development and am looking to become a full stack developer. I've heard that a wise start is to use a variety of powerful tools to improve workflow. However, due to little experience I am unable to filter down the best ones.

I have discovered a comprehensive list of such tools on https://www.keycdn.com/blog/web-development-tools and want to select a few from each category i.e javascript libraries, frontend frameworks, Web application frameworks, Task runners / Package managers, Languages / Platforms, Databases, CSS preprocessors, Text editors / Code editors, Markdown editors, Icons, Git clients / Git services, Web servers, API tools etc.

I understand that different use cases may demand a different choice, and thus, I have two parts to this question:

  1. A tool from each category which is both good and supports a variety of uses i.e.the best 'in general'.

  2. A tool from each category which is good for my current use case i.e. a website which custom recommends a product (from a large database) based on questions users have to answer and simple algorithms.

Reasons for the tool(s) you recommend will also be appreciated.

  • My experience: frameworks are quite volatile and change often. The knowledge you get from these is not worth much. Better lay a good foundation of basics, e.g. Vanilla JavaScript, TypeScript, plain CSS, plain HTML, Linux and Shell. For learning, choose tools that you can use locally and offline, like Git and SQLite. For Webserver, definitely learn about the classic LAMP stack (Linux, Apache, MySQL or MariaDB, PHP), but quit PHP soon (bad Unicode support and ugly in many ways). Jun 9 at 13:11
  • That said, your request is probably too broad and too opinion based, even for this site. Jun 9 at 13:14
  • @ThomasWeller Thanks for replying!...one question- could you explain the PHP part a bit better-do you mean that I partially learn it and leave it midway? Jun 9 at 17:25
  • @ThomasWeller If yes, then where should I stop? Jun 9 at 17:28
  • Indeed, sort of that. Maybe implement one project with it. Solve or work around the issues you find and get the project to an end. During that project you'll learn things like PHP compares the two strings "4779" and "0x12AB" as equal, ?: is left associative and stuff like that. Likely after that project you don't want to implement PHP any more. Jun 9 at 17:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.