uhghghgggg "m8" Also, you do realise by saying that you're not helping at all and making a fool of yourself?
Good luck you guys are doing great and I am sure I am not the only one who thinks that nadeox is a great support staff member ! And I really liked to read that you care so much about your fellow colleagues. It is the most important thing when developing.
I know your pain. Had some nasty bugs to track down at work myself last 2 days, very hard to diagnose when your stack trace collapses at the same time and you just get vshost32.exe stopped responding. Even launching externally and attaching debugger there to just get picoscope stopped responding and a memory address. No error code or anything. Sheer rage inducing. Got seniors to see if I was missing something stupidly obvious with how I'm debugging and not getting any exception info, they came up blank too. They're more surprised I've suppressed it through sheer guess work at this point
As a person with a poor understanding of how to code properly I see working with code as a form of modern sorcery. As I learn more however I am beginning to think that those good at it think so too. It occasionally scares me wondering how much of our systems out there run in ways even their creators don't fully understand as to why they work, but Then again something tells me that stipulation applies to much more of what we interact with in our daily lives; Its pretty incredible everything complex works as well as to does considering the amount of random bugs that exist in any design. I wonder how many successful well known systems out there exist purely on a good guess, probably a decent amount i'd reckon.
About the jist of it. Code doesn't work and you don't know why. Code works and you still don't know why
There are things that are done to minimise the impact of that sort of thing. But yeah. For example using methods/functions can help. Historically code was a massive sequential list of instructions, methods/functions turn your code into many many smaller lists of instructions. You then tell the main bit of the program to run these smaller lists in order to achieve what you want. For example in the real world eating an apple is a very complex set of manoeuvres and instructions, if you split that task into 20 smaller tasks (for example "grasp Apple") then you can make things a lot easier (this is also true outside of programming). This provides some really nice benefits, for example you can test each method separately and hopefully each method will have some level of robustness to it. This generally works, but of course you still have to find which methods are broken when things go wrong and figure out how to fix them. Plus you have to make sure they are all talking to each other in the way that you expect. If you write a method that expects an alphabetic list of data and you give it an unordered list of data it may produce undesirable results. However, once you have written a function that does a thing, it is no longer important to remember exactly how it does it. As such when I program I honestly have no what the exacting details on how I implemented every method are, I can usually remember the gist of it but if something goes wrong with a method I usually have to spend a moment to re-familiarise myself with the details of my own code, which is why writing comments (comments are just notes that you can leave around your programs code, they never make it into the running version) in your code is so important. So in reality while I may not know exactly what is going on, most of the time it is only important that I did know when I actually wrote it. The rest of the time it is only important when it needs fixing.
We wish you a merry update, we wish you a merry update, we wish you a merry update and happy new year New car we bring,to you and other players, Bruckell LeGran for you, wherever you are, LeGran for Christmas And a happy new year We wish you a merry update, we wish you a merry update, we wish you a merry update and happy new year
Now try working on the codebase for commercial software like picoscope (which I personally work on) where years of development was done across thousands of files before you even joined the company
I had similar problems with the license plate I was making yesterday. It kept crashing the game, and I went through the code a dozen times trying to figure out what was wrong, then it just magically worked and I have no idea what I did or if I even did it. That's obviously on a much smaller scale, but still incredibly frustrating
Not to bring it back up, but these forums aren't bad, in fact the worst thing about them is that people are nitpicking about every question that was already answered/has bad grammar. An example, ROBLOX, Wreckfest, Minecraft, etc. I am perfectly fine with the state of these forums. If you're not, maybe you shouldn't be on these forums.
i can nitpick some more if you want? All i3's have hyperthreading, the i3-6100 is a 3.7ghz dual core *with* hyperthreading.
UPDATES OUT !!!!!!!!!!!!! FOR REAL THIS TIME holy S*** I just watched it appear on steam in the last minute
My Subscription feed just got filled with new BeamNG videos. Shame I won't be able to play until the new year since I am really looking forward to it. But I have uni hand ins and then am going to my parents house for a while to see family and then down to Wales to see the other half of my family.
