

As a developer of many years I hate to tell you sometimes that it’s all the information we have when something breaks also. Most code is a god awful mess. Thankfully I love a good mystery.
As a developer of many years I hate to tell you sometimes that it’s all the information we have when something breaks also. Most code is a god awful mess. Thankfully I love a good mystery.
Honestly if taken out of context, hawt.
90% of programming I have seen after a decade plus of doing it full time is minor changes being made to code that was already made by someone. Likely not documented. Likely already changed in a dozen little ways. Math isn’t the problem. Understanding what the guy who wrote it is often the problem.
Oh and you can’t ask them because they likely don’t work here anymore.
Being a programmer is more like being a detective than anything else unless you work for a small company.
I am saddened to see that this thread had no mention of how many horses it takes to run a router. What do y’all think? Would one be enough? It would need to work in shifts to keep up time at 100%. Maybe 3 to be safe?
This is exactly what I came here to say. They are militantly against duplicates. Doesn’t that mean on a long enough timeline the number of new questions have to eventually reach zero?
I use stack overflow every day and have for years. I have never once had to ask a question.