3 ms·
I was kind of shocked at the discrepancy between the reality of working as a programmer at a small company and what one learns about how to "do things right the
by krylon 9y ago
I was kind of shocked at the discrepancy between the reality of working as a programmer at a small company and what one learns about how to "do things right the right way" - version control system? What is that? Automated testing? Or even systematic testing? No time, we have to ship the next release! Using global variables sparingly? - Hysterical laughter
The important lesson for me was not to despair and not to get all preachy on the other programmers, but to see how to make the best of that situation. And while it was a real pain at times, I was able to be productive and get some real work done.
Also, if the only tool you have is a hammer, every problem starts to look like a sore thumb eventually. Do not stop learning new things. Both for pragmatic reasons, and because it helps keeping it fun. It doesn't mean one should use every shiny new thing out there just because. But without knowing what options you have, making the right choice is not trivial.
- skybrian 9y agoDo you use source control just for yourself? How do you keep sane?
- tobyhinloopen 9y agoWhen coding on my own, I use: - TDD - Version control systems (GIT) - Issues to describe new features & bugs - git branches - Pull requests with code reviews (I create something based on an issue I created and review the code later, pref. a day or 2 later) It seems tedious and slow at first, but it really isn't in the long run. It results in clean, organised flow of code & projects.
- krylon 9y agoAt work, I used RCS, because it was the lowest-maintenance solution I knew of at the time. After leaving that company, I eventually discovered mercurial, and later fossil.