Timeline for Attempting to prevent learning of poor techniques when self-teaching
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25, 2017 at 13:59 | comment | added | Walfrat | Well the first part of your post is what I answered to you about how to fill "gaps" when they're localized, by opposition to wider concept. I feel like I didn't add anything meaningfull now xD. | |
| Aug 21, 2017 at 17:57 | comment | added | chrylis -cautiouslyoptimistic- | +1 for Code Review, which exists specifically for experienced developers to help improve code. | |
| Aug 21, 2017 at 13:07 | comment | added | Myles | As a further suggestion - I also recommend having at least one or two code beautifiers for the language you're learning, especially if they can help show where a block of code isn't especially intelligible (both to help anyone proof-reading your code, or even "future you" when reading back over something you wrote before). | |
| Aug 21, 2017 at 13:05 | comment | added | Myles | +1 for a list of good queries. I didn't know about half of these (I certainly had never heard of a linter before now), so this is now my go-to post when self-learning - thank you. | |
| Aug 21, 2017 at 0:37 | history | edited | Michael0x2a | CC BY-SA 3.0 |
deleted 2 characters in body
|
| Aug 20, 2017 at 18:59 | history | answered | Michael0x2a | CC BY-SA 3.0 |