Skip to main content

Summer is over and it's time to get back in business

Now that summer is over and summer vacation is just a faint memory in the past it's time to get back in business. This time I'm writing about boring work days and how I'm going to try to overcome that troubling feeling I'm getting.

Background

For the past four weeks in work the days have been repeating themselves. Every day has been like a repeat from the day before but a bit slower. When this happens it means that work tasks are also repeating the same pattern again and again.

For me this is a bad situation!

I know from the past that this is a situation where I'm getting bored and losing my motivation more and more every day. When I'm losing my motivation at work I know I'm also losing my motivation to do anything useful at my free time.

I knew I had to do something so I wouldn't lose interest to everything and one day I would wake up realizing that I've spent six months browsing netflix.

First step

Probably not the first thing I did but one of the firsts anyway. I told my colleagues that I'm having trouble keeping my motivation up so they know that I'm not at my best performance because I've lost my interest and my thoughts are wandering.

Second step

I decided that I'm going to reverse the situation. By reversing I mean that I'm going get my daily or weekly motivation during my free time and hopefully that will also spike up my work motivation. 

The reverse part one

Just this week I signed up for a online course about scala programming. Few of my colleagues attended this same course a year ago and they all said it was a good course so I decided to give it a try. Learning scala, more than I know now, has been on my todo-list for a long time so this seems like a win-win situation.

The reverse part two

The second part of the reverse was to get back to my blog that got on a good start during the first half of the year. Now that I have started writing again let's just hope I can keep this as a habit.

Labels:

Popular posts from this blog

Simple code: Naming things

There are two hard things in programming and naming is one them. If you don't believe me ask Martin Fowler https://www.martinfowler.com/bliki/TwoHardThings.html . In this post I'll be covering some general conventions for naming things to improve readability and understandabilty of the code. There are lots of things that need a name in programming. Starting from higher abstractions to lower we need to name a project, API or library, we probably need to name the source code repository, when we get to the code we need to name our modules or packages, we give names to classes, objects, interfaces and in those we name our functions or methods and within those we name our variables. Overall a lot of things to name. TLDR; Basic rule There's a single basic convention to follow to achiveve better, more descriptive naming of things. Give it a meaningful name i.e. don't use shorthands like gen or single letter variables like a, x, z instead tell what it represents, what it does...
Read more

Simple code: Version control commits

Currently the most popular version control system is git and I'll be writing this based on git and it's functionalities and capabilities. Git is often seen as a way to enable distributed programming i.e. multiple programmers can work on the same code repository quite easily without disturbing each others work (much). In addition to that just like other VCS's it's also a log of work but to my experience that part is often unfortunately neglected. What I will be focusing this time is the log part because I think it deserves more attention. Why to create a meaningful log? The git log should consist from small meaningful changesets where each commit addresses a single problem. By dividing the log to small commits it enables resilient way of working. Being resilient enables simple and fast procedures to rollbacks, reviews, tags, branching etc. Lets say that a developer is implementing a REST API. The API needs a web layer that receives the HTTP requests, it probably has some...
Read more

Simple code extra: Readability examples

Seven ways to write the same code snippet  Here are eight ways to write the exactly same code. Some are easier to read than others and all are a variation of a code I've seen in a real code base. My personal favorite is #7, what's yours?  #1 One liner DAO.filter { it.name == "foo" }.map { it.company }.toSet() #2 two lines, three operations DAO.filter { it.name == "foo" }   .map { it.company }.toSet() #3 Evaluation on it's own line DAO.filter {   it.name == "foo" }.map { it.company }.toSet() #4 Each operation and evaluation on their own lines DAO.filter {   it.name == "foo" }.map { it.company } .toSet() #5 All function calls and evaluation on their own lines DAO   .filter {     it.name == "foo"   }.map { it.company }   .toSet() #6 Everything on it's own line DAO   .filter {     it.name == "foo"   }   .map { it.company }   .toSet() #7 All function calls on their own lines DAO   .filter {  i...
Read more