... doesnt necessarily mean good-quality. See gnu for example.
Name:
Anonymous2013-07-22 7:17
>>5
But you have both devs who write code, and no deadline.
Also, your slaves are working for free.
Name:
Anonymous2013-07-22 8:10
>>6
The goal is to write the project in good code whether it is open source or not. I might decide to make it open source if they can get it right first.
Name:
Anonymous2013-07-22 8:35
>>7
Define good code first.
Then write rules, and make the devs follow them.
If you're still not happy with the quality, just >>>/diy/
>>1
Incentive them with rewards per product/objective. And only feed them when necessary (1 or 2 meals a day). They code like it is their purpose in life.
Name:
Anonymous2013-07-22 16:38
Closed source
... doesnt necessarily mean good-quality. See nearly every closed source program for example.
Name:
Anonymous2013-07-22 18:32
If it takes one programmer one day to do a task, it takes two programmers two days to do the same task.
How to fix this?
Outsourcing, that's how.
Name:
Anonymous2013-07-22 20:23
>>1
Give shorter deadlines and gave simpler goals.
Developers must understand the customer's needs and the end user's needs, and just generally know the why: what's the reason for the deadline, is it due to budget constraints or do we need to ship something by a certain date because of external reasons; why is there a requirement that doesn't make sense; and what is the most important problem that the software tries to solve and why does it exist?
Bad code is relative, and might be just what is needed to do the job now. Unnecessary generalization is a waste of time and money.
Employ more cheap, effective and hard-working developers in your company. Once this good for nothing developer know that he/she is going to be replaced, he/she will wake up
Name:
Anonymous2013-07-23 14:31
Make him rewrite it from scratch once he's finished. The second copy will have good quality.
Name:
Anonymous2013-07-23 17:09
so many corporate whores around here
enjoy being losers and shit programmers (calling yourself a ``coder'')
Name:
Anonymous2013-07-23 17:14
>>19
good goyim who obey their bosses and program in javascript, the language of the future, usually call themselves code ninjas or code rockstars
Name:
Anonymous2013-07-23 23:23
>>14
Have you seen the doom source? I mean the engine is amazing and all, but that pile of crap is an example of what can happen when you have a team use c instead of c++.
Have you seen the doom source? I mean the engine is amazing and all, but that pile of crap is an example of what can happen when you have a team use c instead of LISP