DEV Community: Robert Fish

How every developer job is not the same

Robert Fish — Sun, 14 Apr 2019 07:21:30 +0000

A new job is like moving into a new house. You don't know where everything is , you're not sure what is right and wrong yet but you have a rough idea of it all. This rush of the unknown and excitement is what alot of my colleagues would describe as the honeymoon phase . These first days, weeks or even weeks are the best parts of a job but they aren't the reality of that job.

But with these times, i believe these are the times where you get reflect on your previous job and see how much better this new exciting place is, the new people you'll meet and the new problems you'll solve. I apologise for such a short piece but i haven't written in months so look forward to much lengthier pieces. Until then, keep pushing to be the best dev you can be!

How to be a better developer (both in the terminal and out)!

Robert Fish — Thu, 03 Jan 2019 06:47:27 +0000

I'd like to start this off by putting a prefix on everything. This is all subjective and my own opinion. No matter where you look, there will be some shared tips and new ones so take each one with a grain of salt.

Think before you code

A simple but useful tip. This tip gets overlooked quite a lot because of time constraints(trust me, i've been there too) and lack of forward thinking but the ugly truth is. Without planning, those deadlines will creep up on you alot faster so think ahead and plan a-little and what you need to make and how that thing will work with everything else.

Look at all sides

While you look at a button that toggles something and think simple. The user on the other hand thinks the exact opposite. This is because you got to have that consideration for how the product is made and how the product will be used. If the interaction is clunky and unusable then you haven't done your job right.

Write code that solves a problem, not creates one

This is a fairly simple concept yet alot of us are guilty at making this mistake. We write code that solves one problem, yet creates 3 issues at the same time. With every line of code, think about how this solves the problems without repercussions, if you come out of this exercise without creating headaches for someone else or yourself for that matter. Then you've done your job right.

Document it and people will follow suite

A huge hate for alot of us is writing documentation. I know what you're thinking. Boring, useless, waste of time. I get that but at the same time, you know what makes a good product? Good documentation! If your product can explain itself easily in your documentation then more devs will adopt it and use it. It can be a few comments or a whole sentence explaining a function. No matter what it is, you're helping your fellow dev understand your code which makes their life easier and you can take ease knowing you've written quality code and documentation.

So that's it for now but let me know in the comments which one you have to adopt this year. Good luck 😃

Starting the new year(2019) #discuss

Robert Fish — Tue, 01 Jan 2019 06:33:33 +0000

I'd like to start off by saying happy new year!

2018 has been a crazy year for me and many other people. I spent most of the year starting my own business as a freelance web developer and it went amazing for most of the time, for the most part... It definitely got stressed and crazy times because of the inconsistent income but it was time for change so i took a leap. I got approached by a young startup to become a SWE to build their products and infrastructure. Now looking back, i am so grateful that i took that oppurtunity to join their team.

Now 2019, a year that starts with me finishing up stuff to get all those aforementioned products launched in Q1. I am definitely unprepared for what comes next, but what i can say is that i'm strapped in for the ride and excited to see what comes next.