developers

So, to set the scene. I'm currently away on a break. I was out walking in the local town when I saw a cake/coffee shop with a sign outside saying "Somerset Cream Tea, Cream or Jam First?"

Now, this is a debated questions in many parts of the UK, and for those that don't know this is to do with what comes first on your scone when having a cream tea.

So, what is a scone?

For those that have never heard of a scone you maybe asking, what is a scone? Well, you could check the link there as they are hard to describe - they are a scone. If someone was to ask me, then I would say something ridiculous like, image a slice of bread and cake had a baby...

Anyhow, a scone is a kind of desert item you would have with something like a cup of tea, though I prefer mine any time.

So, back to the question, jam or cream first?

So, I saw this sign when I was out walking and thought to myself... what is the answer. I then realised the following - after a millisecond thought.

So, firstly you have to cut the scone in half to put either on. Once in half you place cream on the one half and jam on the other.

If you then placed the jam (or the cream) part on top of the other, cream (or jam if revered) half. You would then look at it and say it cream first, as this is on the both. However, if you then flipped the scone over the jam would be on the bottom, so it would be jam first.

So, in reality it can be cream or jam first. Inface you could go one further and put half cream and half jam on each part. Then it would be both jam and cream first at the same time.

So, what is the point of this post?

Now, it may seem like I've put too much thought into this question but I wanted to just use it as an example of perspective. In this case, depending on how I look at the scone it can be either of the cream or jam first. However, its the same for most questions in life.

Depending on how you look at a problem it can change. You just need to change the perspective of your thoughts on how you look at the problem (or item) you are looking at. So, simply try and change the perspective of the problem when you feel you are stuck - even if that perspective means you have to backtrack.

I've thrown away days of code and work in the past to go back and change perspective and find a compete working solution to a problem. It may seem daunting. It may seem wasteful. But it is only these if you spend more time looking at a problem solution that will never work.

Ok, ramble over. Hope you enjoyed my perspective. If so, why not check my other posts.

Featured image Photo by Sarah Kilian on Unsplash

I was taking a look at Quora, something I try to do daily, and while browsing questions I came across this one:

What are some of the reasons why there are so many bad C++ programmers in the world?

This got me thinking. Are there that many? So, I decided to take a moment and write a response which was as follows:

From my experience I've worked with many good developers and some bad. I could provide a list of C programs I've had to go in and fix bugs, obvious bugs, for but I won't

The only bad programmers out there are those that won't learn from their mistakes. Making a mistake and covering a bug is part if the learning experience so I wouldn't call these bad programmers, just those learning.

But to had the question. The problem with C/C++ is that you can have too much control and so ut is easy to create bugs, especially when manipulating memory etc. Again, those that learn from the mistake are not really bad programmers.

Many languages out there will protect you from these mistakes and so that aside, it's probably ab equal number for every language out there.

Just my thought. It's just C/C++ is too powerful a language.

Now, let me say that I stand by this - well I wrote it so I have to. I truely believe that the only bad developers out there are those that choose to not learn from their mistakes.

Those that do not learn from there mistakes are destined to repeat the same mistake again and again.

So, to become a good developer you need to own and learn from any mistakes you make while coding.

Becoming A Good Developer

In order to become a good programmer, you need to learn from your mistakes. By learning from your mistakes, you will avoid repeating them. It's easy to learn from your mistakes when you make the same mistakes over and over again.

To become a good programmer, you should try to avoid making the same mistake twice. Most programming errors can be avoided by writing clean code. Writing clean code means that you should write clear and concise code. Code is often hard to understand for people who aren't familiar with it. It is also difficult for experienced programmers to understand.

I personally think this is more important that learning all the syntax for any 1 or more languages. Once you understand how a program fits together then the language is just syntax. Each language has its own structure and syntax but it follows the same rules for a program.

Learning to be a good developer is learning from the mistakes you make while coding in any language.

Just My Reasoning

These are just my thoughts, my reasoning from the past 26+ years of working in the IT industry as a developer, along with other roles. You may have your own thoughts and ideas, that are just as valid. I truly believe that its not the making of mistakes that are bad, but the not learning from them.

I'm a believer in having code reviews. I'm a beleiver of an iterative development approach. Learn from those mistakes and keep them away from production. Everyone makes mistakes when coding. As long as you learn from these mistakes, they won't be a problem. One of the most important things to remember about programming is to review your code. You will be able to find mistakes and flaws in your code if you do that. Code reviews are very important.