4 ms·
Change the requirements. Understanding the requirements and adding your domain knowledge, often makes it possible to slightly change the requirements (in agreem
by iveqy 4y ago
Change the requirements. Understanding the requirements and adding your domain knowledge, often makes it possible to slightly change the requirements (in agreement with stakeholders) in a way that seriously reduces implementation time.
- zerkten 4y agoWhat you are really saying is that people should develop influencing skills. OP starts by asking about programming tricks, but then mentions career, so it's hard to discern whether they just want some trivia. A programmer learning any soft skill will pay off exponentially in work and their personal life. The payoffs will be much bigger than any technical skill once two years into a career.
- AnimalMuppet 4y agoWe were working on an accelerator board for a graphics system. It had a memory for textures to map onto shapes. The way the microcode was written, it wanted the texture memory to be "rectangular" - you would move the same distance in the source memory and the destination memory to start the next row. Well, that meant that we had to manage the texture memory as 2D regions, rather than as a 1D linear space. We spent two days thinking about creating a malloc for rectangular blocks. Then we went back and told the microcode people to fix the microcode. I think it was a one-line change for them. So, yeah. Sometimes it's massively easier to push back on a stupid requirement than it is to implement it.