It’s National Coding Week!

This is a way to measure the scale of projects. You give every project, or tasks within a project, a t-shirt size, from XS to XXL. An XS job might take five minutes, an XXL job could keep you busy for weeks. This helps everyone understand how long individual tasks will take, and gives teams a good way to assign jobs. Sounds like a great idea that more industries should use!

This one’s like those acronyms that doctors used to write on medical notes. It basically means an issue that is caused not by the coding, but by the user. “Problem exists between keyboard and chair.” If you ever hear a coder using this phrase about your problem, you’re probably doing something wrong!

This is maybe the strangest one – but it works! If you have a problem with your code that you can’t seem to fix, you try explaining it, line by line, to a rubber duck on your desk. Often, while explaining the problem, you realise what the solution is. Why a rubber duck? Why not!

Named after the scientist Heisenberg, this is a software bug that disappears or changes when you try to debug or isolate it. It’s frustrating, because when you try to show someone else or replicate the Heisenbug, it vanishes, and you’re left looking like you’ve imagined the problem.

This is a way to use many words for a variable without using spaces - computers hate spaces! LikeThisOneHere or ThisOneOverHere. Every new word is like a hump on a camel.