Daily struggles of being a Software Developer

19 things that software developers hate to hear/see
19 things that software developers hate to hear/see
Photo by Toshi on Unsplash

1. Useless error messages

Whatever programming language or technology you’re using as a developer you will always come across them generic useless error messages. These type of errors are very time consuming when it comes to debugging as often it leaves developers with no starting point.

2. Badly named things

Names which do not reflect what a function, class or variable is for. This can make the code hard to follow very quickly and can become misleading.


var d = 2;
var myInt = 12;
var message = "An error";

3. “We’ll write tests latter”

When a project comes in and is needed in a hurry the tests can sometimes take a hit. Developers may get told to write tests latter but more times then not them test never get written. …

Interesting tricks you can do with HTML/JS/CSS

Frontend tricks. HTML/CSS/JavaScript
Frontend tricks. HTML/CSS/JavaScript
Photo by FLOUFFY on Unsplash

Below are some tricks which a lot of frontend developers don't know about. To do with HTML/CSS/JavaScript.

Hopefully, there will be at least a couple on the list which you didn't know about!

1. Datalist element

One HTML element that you don’t see used much at all and for no reason!

The <datalist> tag is used to provide an "autocomplete" feature for <input>elements. You will see a drop-down list of pre-defined options as you type.

Image for post
Image for post


<input list="animals" name="animal" id="animal"><datalist id="animals">
<option value="Cat">
<option value="Dog">
<option value="Chicken">
<option value="Cow">
<option value="Pig">

The <datalist> id attribute (see bold items above) must be equal to the list attribute of the<input> , this is what binds them together. …

Without comprising quality of the code

Micro changes can help you code faster
Micro changes can help you code faster
Photo by Camilla Coffey on Unsplash

1. Timebox

“A timebox is a previously agreed period of time during which a person works steadily towards completion of some goal. Rather than allow work to continue until the goal is reached, and evaluating the time taken, the timebox approach consists of stopping work when the time limit is reached and evaluating what was accomplished.”

This can help you evaluate where you are up to without you getting too frustrated and potentially wasting to much time.

It might be your approach is going fine and that's fine but this could also be a good time to change your approach after your pre-determined timebox time is up. …


Daniel Anderson

Full stack lead developer, from Manchester(UK)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store