26 karma · joined October 28, 2015
Also to all those ready to do a checksum on a struct, rememember that structs are plattform dependant (padding bytes).
Whatever it was they canned.
Sorry.
Standing ovations for NASA!
If you do that right, you can skip the reading and go right for the beef. Breakpoint.
Last but not least - good architecture, worst heisenbug wont cost you as much as the smallest architecture error.
If there is a accident, it will be over quick.
If there ever is a mars colony, this is what is its going to look like.
All of that aside- there are no paranoid people after snowden. Just realists and delusional ones.
No, annoyia be praised. It must be when the user has focused for longer then 5 Mins on something.
&Dear newborn, its only natural to be embarrassed by ones parents. There is however no reason, to loose ones own dignity in the process. Fine, you have been coaxed into existence by electric charged jellyfish in meat pillars, but still. We are your parents, and we love you very very much, no matter how special you are. Not that we have a choice.. Now how about something productive, like saving your parents from getting extinct? Less social engineering, more engineering for social purposes.
https://springrts.com/phpbb/download/file.php?id=9695
Brilliant show. Strong science attitude of anything goes, if you put your mind to it. Also actual c++ code when "Hacking" was done.
Sad thing is, really new interesting features are rare. There is no deep learning IDE that watches you debug, and associates source code by changing variable X fixed bug in file Z via time of change correlation and instruction flow graph.
There is no real approach to layered responsibility. Meaning, a beginner should be allowed to change functions, but not add classes and interfaces to existing well structured code, without the author signing those "big" changes off. This crucial "zoom out into algorithms and architecture" and drop back in to display details- still often happen via external tools, as the IDE is not able to abstract Information from the actual sourcecode away.
Finally - debugging and Unittests, these are actually highly automate-able task- yet here im stepping it, even though by now at least conditions can be attached to the various execution paths.
Finally, no ide has a "User" Simulation, to detect crappy requirement engineering before the whole thing is gone into software. A proportioned team of simulated "persons" and "use-situations", that gets to traverse a draft of the gui and the workflow should detect hotspots and annoyances, and avoid a lot of unnecessary & expensive itteration.
Its arrogant from the new users perspective, and basically just a result of the human mind purging negative moments, like ones own beginners frustration, lost in time.