Sometimes you have to start making changes to code, without knowing ahead-of-time what the code will look like when you're done. I call this 'exploratory coding', and it can be a powerful tool for problem solving in code.
0 seconds of 8 minutes, 18 secondsVolume 90%
Press shift question mark to access a list of keyboard shortcuts
Keyboard Shortcuts
Shortcuts Open/Close/ or ?
Play/PauseSPACE
Increase Volume↑
Decrease Volume↓
Seek Forward→
Seek Backward←
Captions On/Offc
Fullscreen/Exit Fullscreenf
Mute/Unmutem
Decrease Caption Size-
Increase Caption Size+ or =
Seek %0-9
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (4)
Oh, that's what I often tell to my students! And this is why we have cycles in agile development, to stop and analyze the new data we got during development 👍
Very useful tips, thanks :)
I'm glad you found it useful. If you have any critiques or improvements to suggest, please feel most free. I'm always learning. :)
As we all :) I like this minimalist convention. Keep going! :)