Little coding journey

[coding-rush]

So lazy

I've been discovering all of these amazing coding journals, and subsequently chastising my inability to keep mine regularly updated. I do have a paper journal detailing my progress as I study for my first Oracle Java cert, which is my current goal. Transferring it here is a possibility.

[fyeahcode]

Seriously: First “what”, then “why”

TL;DR: Before you try to fix the error, know for certain where it comes from.

Now, this seems obvious, right? And it is. Yet, I didn’t follow this principle a few days ago, and I beg you not to make the same mistake.

A little backstory. I deployed a rather huge web app I’m writing on a brand-new server. After I had set up the database, I gave it a quick test-run and Node.JS’s generic ECONNREFUSED error popped up. Now, due to the fact that I had just worked on the database, my brain made a connection where there shouldn’t be one.

I proceeded to work on “fixing” the database for the following 7 hours, ripping every last nerve of mine out in the process, without any result. Could connect via CLI, via telnet (even remotely!), via the web interface, only my code kept endlessly throwing the same error.

Then it dawned on me. I added another string to the statement that prints database errors – and it didn’t appear, the message stayed unchanged. How could this be possible?

Well, I hadn’t yet installed the mail servers, and that was where the error actually came from, since Node couldn’t connect to those (which makes total sense, right?). But, never had I spent a single thought on just trying out whether the database worked; never had I spent a thought on the fact that the message was so generic and could come from literally anywhere.

Seven hours lost fixing a bug that did not exist in the first place. Never will I make the same mistake again, I had learned my lesson. Hopefully you can do so, too.

[coding-rush]

This!

[coding-rush]

To stress the importance of writing good documentation.

[thecodinglove]

When I fix a nasty bug in front of the senior developers

/* by Shizzn */

[coding-rush]

Learning to Read Code

Struggles as a Beginner/Intermediate coder are as follows:

- Learning how to read and understand documentation and code in a timely manner. 

- Experience with first client project and deliverables on time no matter what the hours put into achieving them.

- Translating documentation knowledge to practical knowledge. (ie: Ignoring things that don’t make any sense comes back to bite me in the ass). I read things and I think I understand but I don’t. Only to really understand when someone explains it to me face to face. This makes me feel especially stupid and impostor-like.

- Learning things that I think have to do with the issue but actually don't. Wasting time with it and then realizing it through someone else’s experience that it wasn’t the solution I was hoping for. StackOverflow much?

[coding-rush]

Confidence

I wish my brain didn’t remind me of all my shortcomings so  frequently. 

I’m big enough to know that it’s just my brain, that it isn’t actually true. Or too true for that matter. It’s as if it goes on self attack mode because something trivial or something I need to address is bothering me. I’m slowly turning Self Loathing Mode into Let’s Do Something About It Mode. 

I’ll be alright.

[coding-rush]

Code practice sites

Learning to code in a short amount of time (6 months) is hard. You need a lot of help and support, first of all. Second, to surround yourself with senior developers is tremendous as a beginner. Also, not being afraid to sound dumb or ask questions. 

The most teaching experience of all was just to jump into a framework just knowing the basics of a language and try to construct a system. I bumped into things I had no idea about, such as design patterns and business logic, all of which made the code hard to read at first. However, once I familiarized myself with best practices, object oriented concepts, and very general computer science concepts, I was able to hold my own.

Here’s the list of sites that helped me a lot while I was learning:

CodingBat and CodeKata - Mostly logic  puzzles and syntax for python and java in CodingBat’s case, which will teach you to pay attention to what you type. CodingBat and CodeKata will train your brain. If it hurts, too bad, it’s normal. You need to go through these exercises to graduate from “beginner”. And boy, did my brain hurt.

StackOverflow - 99% of the time, someone has asked the same question you’re asking before you. And it takes a quick search there to find it. If you ask a question, there’s a chance you’ll come across a mean answer, but most people try to be really nice. For a site on the internet, it’s surprisingly civil. It’s the collective coding hive mind.

YouTube - When you’re pressed for time and want to see someone do it or explain it in words. I’m a listener so it’s better for me to listen to knowledge instead of reading it. I absorb it better. Sadly, it isn’t as complete as StackOverflow or PluralSight.

PluralSight - I have commented on courses asking for help and the course teachers themselves have replied straight away. You’ll find it very “advanced topics” but you need to challenge yourself and learn new things. Plus, you’ll find very neat technologies and frameworks you could use someday. The ultimate intermediate site. 

Any API (this means the documentation*) on the framework you’re using.

The Head First book series are excellent as well. Also grab a manual on design patterns, especially if you’re starting with Java or C#.

Lastly, the absolute most important concept I learned was the concept of modularity. Doesn’t have to do much with coding itself, but to the way a project is designed.

Keep in mind, I had already scoured sites like CodeSchool and TreeHouse taking in the knowledge but not really understanding it. At the time I thought I did, but I actually hadn’t embodied it. And yes, there is a time where you go from googling keywords and how to do things, to code just flying out of your fingers because you’ve used it so much over and over.

Enjoy this little guide! I’ll be posting more as I go.

Cheers.