Reputation: 73 Whiz
- Author w/DIC++
- Active Posts:
- 253 (0.49 per day)
- 17-December 11
- Profile Views:
- Last Active:
- Mar 11 2013 01:54 PM
- OS Preference:
- Favorite Browser:
- Favorite Processor:
- Favorite Gaming Platform:
- Your Car:
- Who Cares
- Dream Kudos:
Posts I've Made
Posted 27 Feb 2013At my current workplace, the BBC, we are language agnostic, meaning we have to pick up any language that is suitable for the job. However when you really know a language, you should be able to pick up other languages easily, so just spend some time learning a new language in your spare time, say you know it on your resume, and then apply for a job. Easy.
Posted 27 Feb 2013In the UK, I went to the equivalent of a 'magnet school' in the US. We were taught programming, in fact it was my main introduction to programming and I loved it. Currently we are in the process of restructuring our IT/CS curriculum in the UK. It is important to have a secondary school grounding in CS, but currently our schools are only set to give a basic IT introduction (how to use MS Word, Excel etc). The government want to change that, to bring in 'real' CS. However the school tutors are not prepared to teach CS, and are not qualified in it. Hopefully that will change..
Posted 26 Feb 2013I have a blog that I use as a portfolio and generally for sharing solutions to technical problems that I've encountered. It is foremost a technical blog though, and the fact that it functions as a website that potential employers can look at, is secondary. However I keep it professional and don't post non-technical information.
It has been very helpful in securing work. I have been offered a technical book contract through an agent reading my blog and seeing that I have experience in a particular specialism. I also have just got an interview from an employer impressed with what I've written. So I do recommend you set one up, just make sure you are genuinely interested in sharing information foremost, and don't use it solely as a marketing tool.
Here is the website if you're interested: http://www.davidcraddock.net.
Posted 25 Feb 2013TDD is really about writing the tests first. If you're not writing the tests first, you're not doing TDD.
Writing unit tests and aiming for high code coverage (percentage of your code that is covered by unit tests) is a really good thing to do, and is very important in most applications. TDD is one step further however (or backwards, or sideways, depending on your thoughts on TDD).
Posted 25 Feb 2013I have worked on projects that have used Cucumber tests, Ruby on Rails, I am sure we wrote too many tests at times and running all of them took ages!
Watching some dev videos recently I would be more inclined to use unit tests, when writing these tests what you write often becomes part of the classes you use in the final code so you don't feel you are wasting time.
Where any kind of tests really help is when many people are all on a single project and pushing new features out often, it becomes hard to ensure you don't break parts of a system you have not worked on.
So I do use it sometimes and have mixed feelings about it.
That sounds like BDD, not TDD. Cucumber is a tool for writing automated acceptance tests in a domain language. TDD is usually about writing unit tests.
- Member Title:
- D.I.C Regular
- Age Unknown
- Birthday Unknown
- Years Programming:
- Programming Languages:
- Java, Python, PHP, Bash