3 ms·
Lots of late night programming, then lots of late night paid programming. It all boils down to putting the time into learning. The difference from self-taught c
by bliti 13y ago
Lots of late night programming, then lots of late night paid programming. It all boils down to putting the time into learning. The difference from self-taught coder and professional developer is the paycheck. Though the self-taught coder might have experience writing code, it will not have experience developing software. Two different things altogether. That is why you need to put in the time in both scenarios.
- franl 13y agoThis is one of my biggest concerns: writing code vs. developing software. I'm trying my best to follow/learn best practices, but the contract job I'm at right now kind puts quality aside in favor of "JFGID right now!" And since I'm still fairly new, I feel like I'm taking shortcuts just to get things working in a timely manner sometimes.
- bliti 13y agoYes, that is quite common. People will start asking for 100% quality at 100% time. Then reduce time to 80%. Problem is quality is closely tied to time. As a result, code starts being written under the guise of it being a temporary solution. "It will be fixed on version 2." - is what clients or managers often say to keep you at ease. Solution? Do your best. No one is perfect. Make sure to document the code well (comments) for future revisions. But realize that this is how a lot of software is written. In all size companies.
- franl 13y agoHa, I heard something like "it will be fixed on version 2" multiple times last week. The more I do this the more I realize I can only do what I can do (and try to get better where there are shortfalls in skill/knowledge). Like you said, no one's perfect. Thanks for the reminder and tips!