3 ms·

Code really badly, and feel no shame in that. Then after the sloppy code has been understood, you can start to iterate on it and polish it, making your code see

• muzani 4y ago
  Some call it "sketching". It's similar to how artists would trace a few lines for structure before filling it out. Another common approach is prototyping, where you build something that will be disposed for the purpose of learning. So you really won't feel any shame because you have to throw it out anyway.
  • kingkongjaffa 4y ago
    Another way I’ve seen this done is to start a new branch in git clearly labelled as “experiment/thing” Which can be reviewed/ saved for later / deleted. Without any pressure. Also “proof-of-concept” to help learn or figure out how something will work. Helpful if you want to try something that isn’t directly linked to an open ticket/issue or even just an issue under discussion and not part of the main backlog.