By Garry Law, Technical Lead
So, I’ve been developing apps for a while now and as any developer knows, communicating to the team in easy-to-understand terms is the key to smooth projects.
Over the years, I’ve picked up a bunch of terms I’d like to share with everyone (I got a lot of them from my time on Stack Overflow):
- Major Surgery/minor surgery – usually to illustrate how much disruption to the existing work that the new work is going to cause.
- Cutting up the vegetables – preparing, conceptualising, scoping work.
- Jimmy – a hypothetical previous developer who left us with their work.
- Steve – a hypothetical freelancer who is going to pick up your work.
- Bob – a hypothetical adult user.
- Cassie – a hypothetical child user.
- Simmering (ideas) – the period between coming up with some key ideas and deciding which ideas work best.
- Eating the frog – Doing an unattractive, but important task.
- Yoda conditions/Yoda code – backwards, the code written is.
- Pokemon exception handling – any attempt to ‘catch all’ error exceptions.
- Heisenbug – a bug that is undetectable when you look for it
- Disaster Driven Development – when someone promises something on behalf of someone else.
- Ref**ktoring – an intended refactoring, rendering your work unreadable by anyone but yourself.
Feel free to add your own in the comments!