Having scientific knowledge is useful because we often develop theories on how something should work and then we test it (isn’t that Agile development?). Electron flow in semi-conductors arranged into logic gates forms the bedrock of computing and is firmly rooted in the physical sciences. However, is proposing a theory on how multiple processes can run on a collection of semi-conductor logic gates (or CPU chip), then testing that theory with an experiment called an OS kernel, an implementation of the scientific principle?

When developing software, do you ever catch yourself saying, “In theory, we should be able to do X?” Then some software is built to prove it’s possible, often that software is peer reviewed (code review). As software developers, are we not very efficient scientists in our own niche scientific area, constantly hypothesising and testing? We’re probably fairly unique in that we end up selling our successful experiments as a product, that proves our hypothesis time and again!

Generally, when science makes it’s discoveries and moves on, engineers take over and innovation follows. As software developers, we are using well understood, genuine scientific discoveries in new creative ways.

I am a Computer Science graduate and I’ve argued here that I am a computer scientist. In my heart though, even though we push the boundaries of what’s possible with computers, I know my staff and I are really talented (wannabe scientist) engineers.

You can see in the concepts the importance of people and process and that technology is not the key issue in software development.

http://www.yourdonreport.com/index.php/2008/11/13/top-ten-software-engineering-concepts-v10/

Its a coincidence you raise this point today!

I would describe my self as more of a Software Engineer but merely because of my qualification title. I finished a degree in Software Engineering not Computer Science is this possibly the only difference for me?? Yeah probably

Also with you mentioning people making or breaking you I agree! Over recent weeks we have been having various discussion on management of clients – as a team we know we are all more than capable of getting the ‘work done’ and to standards required but then how do you manage the clients’ expectations.

We develop web apps too and I always feel that because the client isn’t getting ‘something they can see’ – a product in a box they always seem to have higher expectations do you find this? If I was to buy a Blue pen from a shop a week later I wouldn’t take it back and say actually I need it red and it ALSO needs to flash when I write? (After writing that sentence I feel somewhat harsh – so possibly as a caveat it may be that we need to tighten up our requirements gathering)

How do you manage their understanding that to make a website is actually not as easy as people think?

My initial thoughts and good blog by the way I have been subscribed for a few months now.

Eggsy