6 ms·

Let me give some senior developer feedback on these statements. Developing kernels is a highly technical job. I can imagine that you have to think hard before

Let me give some senior developer feedback on these statements. Developing kernels is a highly technical job. I can imagine that you have to think hard before writing any code. Once you figure out a proper solution, you can invest some time into writing high-quality code. But remark that no code is written bug-free the first time! Now contrast this with a consumer facing application. The biggest challenge there is not stability or technical structure. The biggest challenge is to provide a useful, user friendly application. You cannot just think this up in your head and hope all is fine. The "no plan survives contact with the enemy" very much applies here. There is no point in investing into code stability when that code has a high chance of getting thrown away. Get the "useful and user friendly" figured out very fast, using an iterative approach. And only then start focussing on stability and all the rest. Plus, sometimes it makes more sense business wise to shift focus more towards features instead of stability. Anyway, each project is different. So when you see advice, make sure you first check if it applies in your case or not.

User23 4y ago
Correctness and pleasantness are entirely distinct. In most cases incorrectness has little or no effect on commercial success whereas unpleasantness will sink a product instantly. There are some areas where incorrectness is also highly unpleasant, kernels and compilers being two examples.
mooreds 4y ago
> ... when you see advice, make sure you first check if it applies in your case or not. I wish everyone understood this. There are four things you need to do to successfully apply advice: 1. Discover it (lots of ways to do this, even more now in the age of the internet). 2. Determine if it is good or not (you can rely on the wisdom of the crowds, other people's judgement based on qualifications, books, references, etc). 3. Determine if it applies to you (you have to make this call, requires thinking about the context of the advice giver and your situation). 4. Actually apply the advice. This requires making the changes suggested and is intrinsically individual. Step 1 happens pretty naturally, and we're well set up for step 2 (though of course people get fleeced by snake oil salesmen all the time). Step 4 is intuitive. But, don't forget step 3!
qprofyeh 4y ago
This is correct, yet dangerous to say this without mentioning a timeline. I would say do anything (that works) to get customers to pay. Then do everything (good enough) to get them to stay.

User23 4y ago

Correctness and pleasantness are entirely distinct. In most cases incorrectness has little or no effect on commercial success whereas unpleasantness will sink a product instantly. There are some areas where incorrectness is also highly unpleasant, kernels and compilers being two examples.

mooreds 4y ago

> ... when you see advice, make sure you first check if it applies in your case or not. I wish everyone understood this. There are four things you need to do to successfully apply advice: 1. Discover it (lots of ways to do this, even more now in the age of the internet). 2. Determine if it is good or not (you can rely on the wisdom of the crowds, other people's judgement based on qualifications, books, references, etc). 3. Determine if it applies to you (you have to make this call, requires thinking about the context of the advice giver and your situation). 4. Actually apply the advice. This requires making the changes suggested and is intrinsically individual. Step 1 happens pretty naturally, and we're well set up for step 2 (though of course people get fleeced by snake oil salesmen all the time). Step 4 is intuitive. But, don't forget step 3!

qprofyeh 4y ago

This is correct, yet dangerous to say this without mentioning a timeline. I would say do anything (that works) to get customers to pay. Then do everything (good enough) to get them to stay.