Code for People not for Machines @Øredev
It was 2017, sometime in spring, probably March. After conducting a few internal workshops and meetups at my current employer, I finally got the courage to send a proposal to a conference. I thought I knew enough and I had the will to share with others what I know.
Easier said then done. It took me a few days to think of a subject, then another few to write down a short description. I searched and found a conference that seemed appropriate for what I wanted to share and in the last possible moment I sent it to Øredev
I was excited and nervous and I only thought of what would it have been to actually speak there.
Two months later I receive the news: I am not in. At first I was disappointed, then I was sad. But the second day I checked the conference’s website to see the speakers they ditched me for and I thought: I would have ditched me too for these speakers 🙂
At the same time it gave me the push I needed to start applying to other conferences too (I will create posts for those too).
My title for the Øredev conf in 2017 was: “Code for People not for Machines”
and the description was:
From this talk I want the audience to learn a better way of writing their code. In my opinion code should be easy to understand, fast to write and super maintainable.
In my presentation, I will focus on showcasing lines of my code, and lines of code I have seen, liked or disliked and motivate my choices.
By the time I finished, I am confident that the audience has understood the importance of writing the importance of not only writing the right code, but also writing the code right.
As the title suggests, the code must be written for people, for the humans that will read and add to it after you have finished. Many developers think that their code will reach a machine (be it a browser or whatever-else) and they will render and display. But that is never enough. We will look at code samples from different moments in my developer history and review.
I will to bring all the good things I learned (most of them the hard way) and leave them with my audience.
To be honest I am not sure what went wrong, but most probably others were better.
So, Øredev, thank you for accepting my application and for taking the time to review it.