How difficult can development get?

Once again, "racing" requires that various tasks be performed, not just driving. There is also a judgement factor involved which influences the outcome of the endeavour; placing first, second, last. This isn't something that typically happens in a corporate environment. At worst, the degree to which the developer adhered to the plan during development or the time taken to complete the development would come into question. But it is more of a binary measure, since one either meets the deadline or does not, there are usually no prizes for finishing split seconds ahead of the deadline.

Wow. Case in point, oh master. So we've established that you are oblivious to the fact that the OP was using development as shorthand for "what developers do", and to the fact that I wasn't trying to create an analogue between racing and development.

Moving on, as a matter of interest can you show me (a reference) where your definition of development comes from? I've already linked to mine, but am legitimately curious where yours comes from - I can't seem to find it online, perhaps your google Fu is better.
 
Wow. Case in point, oh master. So we've established that you are oblivious to the fact that the OP was using development as shorthand for "what developers do", and to the fact that I wasn't trying to create an analogue between racing and development.

Moving on, as a matter of interest can you show me (a reference) where your definition of development comes from? I've already linked to mine, but am legitimately curious where yours comes from - I can't seem to find it online, perhaps your google Fu is better.

You are the only one sensationalising my opinion. I am certainly not oblivious to that possibility, hence the original point that mentioned a dependency on your definition of development.

My definition comes from experience managing teams where I have developed a formula for successfully delivering value to shareholders that, so far, transcends projects, organisations and even industry.
 
Last edited:
You are the only one sensationalising my opinion. I am certainly not oblivious to that possibility, hence the original point that mentioned a dependency on your definition of development.

My definition comes from experience managing teams where I have developed a formula for successfully delivering value to shareholders that, so far, transcends projects, organisations and even industry.

Well... If all you did was develop it, it probably wasn't very hard...
 
There are still some challenges when doing firmware. By firmware I refer to hardware descriptive languages, anything else is just embedded software ;)

Working with CPLDs where you have limited flip flops to achieve the functionality that the client wants, so in the end you start building the entire thing by hand instantiating raw flip flops.

And then working with FPGAs, where you have limited resources (memory, clock buffers, PLLs, ...) and have tight timing constraints on certain parts of the logic, you also end up placing parts of the logic by hand. Specially high speed logic and the processor is not rated for that frequencies. And if the client insists on not using IP cores (due to the source not being available for audit) you code certain technologies from "first principles", this can become quite fun (multi-port memory controllers, HD-SDI, ...)

You are never bored
 
Top
Sign up to the MyBroadband newsletter
X