4 ms·
demand more money now, concentrate on learning to work with people, but do not give up on code quality. Not entirely, anyway. You can't turn the whole app into
by SideburnsOfDoom 14y ago
demand more money now, concentrate on learning to work with people, but do not give up on code quality.
Not entirely, anyway. You can't turn the whole app into a good one in any reasonable time, but when you fix a bug, take time to apply the boy scout rule ( http://www.informit.com/articles/article.aspx?p=1235624&seqNum=6 http://www.informit.com/articles/article.aspx?p=1235624&... ) Don't put that down as a separate task that your management can approve or deny, it's part of doing the job of coding properly. That way, at least the buggy parts of the app get better.
You should not be focused only on your career when making coding and tech decisions, but look at it this way: in a year's time, you're in an interview for a job you really want. What are you going to say "I can read and maintain shitty code" or "I can make shitty code better"?
Also consider: documenting your app's architecture (or lack of it) and conventions (or lack of them).
Also consider: reading up on architecture, testing, refactoring and code quality. If nothing else, these will help you get your next, better job. Off the top of my head, try "Domain Driven Design" by Eric Evans, "Growing object-oriented software guided by tests", "Refactoring" By Martin Fowler, and on the last topic "Clean code" by Robert Martin and "Code Complete" by Steve McConnell
Big ball of mud apps (http://www.laputan.org/mud/ http://www.laputan.org/mud/ ) may be common, but it doesn't have to be that way - you can learn some pitfalls to avoid
- molmalo 14y agoI don't think that money resolves everything (at least, normal sums of money, lol). If they are paying him the minimum, that means they don't value what he does. I guess that's the reason he has a lot of projects to handle... probably other developers have left for the same reasons. Reductio ad absurdum: If somebody offers me a full time job of sewer-cleaning, paying me 15k, i'd probably pass, because I value other things besides money. I want to enjoy what I do, and the market right now (at least for the dev community) gives me enough options to choose where I want to work. He'd probably learn A LOT more, somewhere else, working with other people, and where the company actually values him. Someone would think that the kind of people who hires devs in such conditions, having a high employee turnover, would start to value them a little more. Sadly, my experience knowing a few cases firsthand, is that they think "there's always someone else".
- SideburnsOfDoom 14y ago> He'd probably learn A LOT more, somewhere else, working with other people, and where the company actually values him. Most likely. I'm suggesting that until that happens, in preparation for that, he can learn as much as he can from what's in front of him; and do a good job too.
- SideburnsOfDoom 14y agoI should get this reply onto programmers.stackexchange, where the original poster can see it, right?