4 ms·
The typical narrative of the mediocre duct tape engineer. "I want to put something together fast by trial and error, without having to go through actual thinki
by partycoder 10y ago
The typical narrative of the mediocre duct tape engineer.
"I want to put something together fast by trial and error, without having to go through actual thinking or understanding. I don't care about details, just give me an example that I can copy, paste and duct-tape with another piece of code, so I can ship my product and charge some idiot a fortune for some spaghetti with meatballs code."
Documentation does not necessarily have to follow the format of a tutorial and can vary in levels of detail. Tutorials on this topic do exist. There, LMGTFY: https://docs.python.org/3/howto/regex.html https://docs.python.org/3/howto/regex.html
How did I find it? Google: regular expression site:python.org
- iaskwhy 10y agoIs it really wrong to learn something new with examples and without having to read a full book before typing the first few lines of code? I prefer to learn by trial and error.
- partycoder 10y agoIt is a valid option to explore by trial and error. But once you have obtained something that seems to work, if you can't explain why it is working, it is a bad moment to stop. If you construct an entire system by trial and error without an understanding of how and why it's working, you are exposing yourself and your customer to serious risks. Even if things do not crash, if your code gets audited (e.g: when another person joins your team), you will have a bad time explaining your choices. As a professional engineer, it is expected of you to know what you are doing, and fudging code is the easiest way of getting sacked to the sound of a trumpet.
- iaskwhy 10y agoRight but the article was about a beginner learning a new language, I don't think a beginner is expected to have audit-proof code for quite some time.