News for hackers. Stuff that matters.
Re:Falling through the KRACKs by Swizec on Tuesday October 17, 2017 @01:10AM (#15488820)
FWIW I like to jump in and start coding, but what’s happening behind the scenes is that I “see” the algorithm or architecture in my mind. It’s not exactly a foowchart or a state machine, but it does have a sort of plastic manipulatable shape.
Re:Falling through the KRACKs by throwaway613834 on Tuesday October 17, 2017 @02:01AM (#15488984)
FWIW I don't think other people who jump in and begin coding are doing so blindly either. i.e. they do the same thing you do.
Re:Falling through the KRACKs by Swizec on Tuesday October 17, 2017 @02:34AM (#15489084)
Everyone was presenting it as a dichotomy in this thread \_(ツ)_/¯

Seemed relevant to point out that at least for me it’s not.

Re:Falling through the KRACKs by reitanqild on Tuesday October 17, 2017 @02:01AM (#15488981)
As someone who does both (flowcharts etc and exploratory coding) I think I experience something similar.

For me it is not very visual when I code. It is more a gut feeling: this goes here, that goes there. This is good, bad, weird but works etc.

This is nice for me but I know I have to work on how to explain it to others.

Bad example but I guess this is somewhat closer to what I want to be able to explain: "it currently works but it is a bad idea because it means you'll have to remember to patch seemingly unrelated functions x, y and z whenever you update this.

Also, in this case it is even worse as in the worst case you won't see the errors until the quarterly reporting run and that code is well known for having bad test coverage."

Edit: as usual I'm curious as to why parent was downvoted?