Quote:
Originally Posted by MTK358
...
Let me tell you something, Sergei! I was just doing that for fun.
I am not working in a big corporation setting up a huge corporate server without knowing where log files are.
...
|
One of the very first things I learned in this life was that doing something without the ability to debug it is doing it for grief, not for fun.
In my case it wasn't even in programming, it was in electronics. Imagine a long (2 .. 3m), but very thin (50 mm => 2 inches) in diameter apparatus in special "oven" where it's heated to 125C or higher.
It had to be - the apparatus was for oil well logging, the temperatures are high in oil wells.
So, the apparatus fails with temperature, and I don't know why. And when temperature goes back down, it functions again normally.
To debug it I needed to guess which signals to make accessible, but doing so meant soldering to the nodes long wires (the same 2 .. 3m), and circuits in general do not like long wires.
...
So, don't even think of doing anything unless you have a clear plan of debugging. Starting PHP on a WEB server without even thinking where the error messages go (and they go to the server log) is a complete and utter nonsense.
Actually, the very first question you have to ask yourself is not "how am I going to do it ?", but rather "how am I going to debug it".
Much later in my life I took part in design of a pretty well known chip. Chip signals can often be observed using a tool similar to oscilloscope. So, there was a problem with the chip - its die was attached to the plastic by the signal side. The company had a $$$$$$$ tool to drill the silicon at precise coordinates to precise depth in order to just be able to observe the signals. And the company thought about it
before the chip came into physical existence,
while the chip was being developed.
At all, writing code assuming no mistakes will be made is complete and utter nonsense. There is a whole bunch of posts in this forum from people who have problems which are easily seen through compiler warnings which are disabled. So the people scratch their heads at runtime instead of seeing the problems at compile time.
...
So, whenever you have problems of your very special kind, it's because you prefer doing things your special way.