Author: drag04

Time to check out Agile Programming

There’s a few ways of working when you’re involved when working in a software engineering environment. A big one is the agile manifesto. Although it sounds kind of weird, it’s a actually a quite straight forward way of working. In the manifiesto there’s 4 important values:

Individuals and interactions. To focus on the people that are working rather than int the processes or tools that are being used in the project.

Working software over comprehensive documentation. Personally I find this very important. In big projects that I worked before, my team and I couldn’t really deliver an optimal product due to the fact that documentation was in a bigger priority than the project itself.

Costumer collaboration over contract negotiation. Costumer interaction can be quite tricky some times. Some times, when a client asks for a certain product the people producing it can finish it, give it to the client but the client will have complains or will want to make changes to the now already finished product. Maintaining a constant costumer collaboration ensures that this kind of stuff doesn’t happen, there’s less time being wasted, and the client can be more satisfied with the result.

Responding to change over following a plan. Something that we can take for granted always is change. It’s very rare when something goes exactly how it was planned. Because of this, it’s really importante to keep a mindset ready for anything to change, so that the flow and work in the project is not affected so much.

Now, from this 4 values 12 principles came out in order to optimize the development of software.

  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business
    usain-bolt-smiling
    Continue reading "Time to check out Agile Programming" →

Ethics… They really are something, aren’t they?

Ethics are important in any which way you look at stuff. They’re there to make sure people behave in a certain standard, to help us see what’s good and bad, to let us regulate our actions to other people and ourselves. I think that it goes without saying that in software engineering there exist a code of ethics to fulfill what was previously mentioned. One of the most prominent, and well developed code is the ACM code. Now, before I go into the code of ethics I would also like to add that this is not the only code that has been developed in order to maintain a correct management of work done by software engineers. However, it is the code that has maintain quite a bit of relevance throughout the years. Now, how about we get right to it:

IMG_2369

1st Principle: The Public

Now it’s also important to have the public in your mind. A software engineer also needs to ensure that even when acting towards the best interest of their client, they should also have a consistence with the public interest.

2nd Principle: Client and employer

Kind of goes along with the previous principle. There must be a stated relationship between client and employer that ensures that the employer will do the best for the interest of its client. Without affecting in a negative way the public of course.

3rd Principle: The Product

When you buy something you tend to expect a certain standard of quality. Doesn’t matter if it’s apples or a brand new computer. You expect for the person producing or providing the service you’re paying for will be of acceptable quality for all the parties involve. In software engineering is pretty much the same. A software engineer needs to make sure there’s

Continue reading "Ethics… They really are something, aren’t they?" →