Titre de la conférence, par exemple

Date : 04/01/2020
Catégorie(s) :
Lieu : Nantes

Melior sua. Quoque pondus peragebant subdita animus. Quae distinxit fidem praecipites neu suis umor margine quoque. Lacusque ita secant oppida amphitrite tum. Inter cum cornua bene coeperunt iapeto! Habentem occiduo ensis litora chaos: arce. En savoir plus

A Guide to Solving Web Development Problems

This is mainly about how to solve technical problems that arise from using front or back end technologies to make web pages or web apps but some of these steps will be applicable to solving technical problems in general.

Half the technical problems in web development are caused by something trivial like forgetting a semi-colon somewhere and are usually easily solvable if you’ve had your coffee but for all the problems past this level, you’ll probably need to do some structured thinking.

The Web Development Troubleshooting Steps Summary

1. Define the problem that you’re trying to solve. If you’re not asking exactly the right question then you’re not going to get exactly the right answer.

\frac{1}{\Bigl(\sqrt{\phi \sqrt{5}}-\phi\Bigr) e^{\frac25 \pi}} = 1+\frac{e^{-2\pi}} {1+\frac{e^{-4\pi}} {1+\frac{e^{-6\pi}} {1+\frac{e^{-8\pi}} {1+\cdots} } } }

2. Verify the problem exists. Make sure it’s really a problem by replicating the error on more than one machine.

3. Gather additional information about the problem. Use a javascript debugger, fiddler or any other common tool to get additional clues about the nature of the problem.

4. Back-up your work before making even a single teeny tiny little change. Don’t make things worse when trying to fix the problem. Keep a back-up so you can roll back if you have to.

5. Review your past experiences versus the present situation. Have you encountered a similar problem in the past, if so then test to see if your past approach will fix the problem at hand.

6. Search for people who’ve been in similar situations and how they solved the problem. You have all the information you need so start using a search engine to find possible solutions.

7. Make one change at a time (and then test it). Proceed methodically and if you make multiple changes at the same time then you often can’t tell what worked or didn’t work. So proceed step by step.