We live in 2017 in a world where tech exists in every nook and cranny of our daily lives. Everyone has picked up a vocabulary of tech – gestures, button symbols, emojis (and emoji shortcuts :+1:), and so on.
Therefore it’s no longer cute (or excusable on the part of the developer) in my opinion to put out poorly designed software (in) products. Sloppy software delights nobody and frustrates practically everybody. Especially developers!
So in a bid to raise the overall standard of tech, I’m going to call out organisations that put out crappy, sub-standard software into the modern world.
Now that we’re coming close to the end of 2017, I’ve been thinking about my career and careers in general. Having begun my career as a software engineer about a year ago, I thought it’d be timely and useful to do some reflection.
What’s this weird sounding thing called Git? Is it Git or just git? What does it do, who uses it, and is it actually useful? In this post, you’ll learn all you need to know about git (yes, it’s just git!).
I recently re-started to organise what my good friend Kegan and I call “docu-nights” where we watch a documentary film together at my place. There’s never an awkward obligation to sit together and engage in intellectual conversations after these films, but we often wax philosophical in areas unrelated to the film anyway.
I turn to coffee when I’m tired and still have some time left in the day to work. But when I brew or order that cup of coffee in a situation like that, I know I’m drinking for utility, not enjoyment.
“But you can enjoy a cup of coffee and get the caffeine kick from it”, I hear you say. And I fully agree with that. But I’m always able to recognise the trigger for wanting coffee, and the trigger for me to drink coffee these days is almost always sleepiness or fatigue. On days like these, coffee is just a tasty drug for boosting my energy levels (to be paidback later).