My first month on the dev team

So I've been working at Netsells for about a month now and I thought it would be a good time to write a post and talk about some of the more important things that I've learned from my first month. Without a doubt I've learned so much and I don't think that the amount of things I learn will be slowing down any time soon.

If you don't already know what I do at Netsells. My role is an iOS developer but I also have experience in PHP so I can help out the web development team when we're getting busy. If you want to find out more about the work I do then you can read about my role here.

Here's a list of some of the more important things I've learned and why I think they're important:

I'd say that the most important thing I've learnt is that no matter how small the project is, USE GIT! Before I worked at Netsells, I sometimes used git but I never systamatically used it on every project. My time at Netsells so far has completely changed my mind. If something does go wrong and you can't fix it locally its so easy to then go back through your previous commits and get back to a stage where everything worked. A good way to look at it is that it might take a bit extra time to set up and to use but it can save so much more time if things go wrong or the device you're working on breaks or gets lost. One rule to remember with git is to commit often and little. This way you can really fine tune the points you can step back to should you need to. Working with git by yourself is helpful but also more of a backup tool. However, when git really comes in handy is when you're working in a team.

The next important thing I want to talk about is about the way that you save your files and organise your hard drive or storage space. I don't really need to say too much about it as it speaks for itself. The more organised you can be, the easier you'll find things when you're under pressure looking for that document or file you need urgently.

While we're talking about hard drives and organisation. Remember that just because you might have a new machine, things can still go wrong or your machine might be lost or stolen. The way around this is to back up everything that you would need to start from a new machine should you ever need to. There are many different ways to do this and its really up to you about which one you use. The important thing is that you actually use one of them. I prefer to use an external hard drive and Apple's built in Time Machine utility. However, some people are starting to use Cloud services. I personally haven't used any of them that have the dedicated purpose of backing up your files but a quick Google will find you a good one.

The final thing I'm going to write about today is the importance of writing neat and readable code. This is something I have to remind myself about quite a lot. Its easy to get carried away and be that focused on getting the task finished and working that you don't really think about what your code looks like. However, if you're working as a part of a team or plan to come back to your code at somepoint you'll soon discover that the bit of extra time making your code neat and easily readable will of been time well spent. Certain IDE's have the functionality to automatically style your code to a certain style. These are good but its more helpful if you can get into the habbit of doing it yourself as your write it.

I hope you've enjoyed reading this and if you think there's anything important that I've missed or perhaps you have you're own list of important things. Feel free to comment and I'll respond and I may even add some into the post.