Forem: Saleem

A place for African side hustles

Saleem — Tue, 25 Feb 2020 12:48:55 +0000

I put together a small site that will tell the stories of Africans with side hustles:

If you're interested in having your platform/site covered, fill in the form here:
https://forms.gle/sCmqaByj9LMo6EtTA

Tech Notes:
Built with Hugo Static Site Generator and hosted free on Github Pages.

Understanding Semantic Versioning

Saleem — Wed, 01 Jan 2020 12:51:32 +0000

After reading this guide you will have a better understanding of the semantic versioning standard used within a majority of software eco-systems.

What is in a Version Number?
How this applies to your Application
Carets and Tildes

What is in a Version Number?

For the rest of this guide let's assume our current version of our dependency is 1.0.0 .

In the example above the version is divided into 3 components, with 1 being the major component, 0 being the minor component, and 0 being the patch component.

When one of these components are updated this is what it means:

Major: Each major update is not backwards compatible with a previous version, this means that 2.0.0 is substantially different to 1.0.0 that it will break your application using the 1.0.0 version if you don't make changes in how you use this dependancy.

Minor: A minor update introduces non-breaking changes this means that for example, a version of 1.10.0 will not cause your application to break - so no changes are required.

Patch: A patch update also introduces non-breaking changes i.e 1.0.5 will still be able to work fine with your application without having to change a thing.

How this applies to your Application

"dependencies": {
    "my_dep": "^1.0.0",
    "another_dep": "~1.0.0"
  }

The above code snippet is an example of the dependencies section in a package.json file.

Carets( ^ ) and Tildes( ~ )

The caret or the tilde that is in front of the version number determines how the dependancy will be updated when you run "npm update".

^ : this will update the dependency to the latest minor version available. i.e if 1.10.0 is the latest minor version - your dependency will be updated to that version.

~ : this will update the dependency to the latest patch version available. i.e 1.0.10

Note: Using "npm update" will not automatically update to the next major version (2.0.0) - you will have to manually update the package.json to the next major version and then fix your codebase of the breaking changes.

Thanks

I hope this helps - feel free to comment or ask questions.

Pomodoro Productivity Technique for Development

Saleem — Tue, 31 Dec 2019 08:51:41 +0000

The Pomodoro Technique

Pomodoro is the italian word for tomato.

The Pomodoro Technique was developed by Francesco Cirillo during the 1980s to improve productivity and combat procrastination.

Why does this productivity technique involve a tomato you ask? Well Francesco used a kitchen timer that was shaped like a tomato like the one in the picture above. So my thoughts are he didn't want to procrastinate and overthink a name for his technique so he just used the word pomodoro :).

How does it work

Basically it involves the following steps:

Decide on a task to be done (typically something that can be achieved within 25 minutes)
Set the timer for 25 minutes
Start working with no distractions, none at all.
When the 25 minutes are over, take a 5 minute break. This is seen as 1 pomodoro.
After you've completed 4 pomodoro's you can then award yourself with a longer break of 15 - 30 minutes.

How does this apply to Software Development?

Sometimes as a software dev there can be uninteresting parts of the job, maybe you're modelling a database, or creating a data layer to fetch data, or anything else that can be repetitive. This technique helps in a huge way to get through the grunt work.

It also makes you super disciplined, as soon as that timer goes off you start working, no checking messages, no social media, nothing. Just focused work. You will find you get things done way faster this way.

Improves Planning

After a while of using this technique you will be able to estimate tasks in terms of pomodoros i.e this service layer integration should take me 2 pomodoros for each model.

How to Start

It's recommended to start with 6 pomodoros for the day, you don't want to over commit. Work your way up from 6 - 8 then possibly move further upward.

In actual time this is 3.5 hours of work a day including breaks, I know this sounds like a little but you will be amazed at how much work you get done.

The original technique places a large emphasis on planning before starting your day. I deviate from this a bit as I find that it causes me to procrastinate about what to do (yes, I'm a serial procrastinator). I don't plan my day in detail beforehand - my plan usually comes to life as I start working - i.e after the first pomodoro of the day.

Make it your own

Take what works for you from this productivity technique i.e if 25 minute work session are too short increase it to 40 minutes for example.

If you've used it, tried it after this article or tried it before, let me know in the comments.

Timer Tools

Instead of going out and getting yourself a kitchen timer, use one of these below:

Tomighty - Desktop Application
Marinara - A Chrome extension