VDubinator Coder

Recently, I read an article called " Great Development Teams Have a Culture of Discipline ." The article got me thinking a bit about discipline and work especially as a Software Engineer. It even got me Googling quotes about discipline. I'll share just a few here: I fear not the man who has practiced 10,000 kicks once, but I fear the man who has practiced one kick 10,000 times. - Bruce Lee Confidence comes from discipline and training. - Robert Kiyosaki Discipline is the bridge between goals and accomplishment. - Jim Rohn Discipline is rarely enjoyable, but almost always profitable. - Darrin Patrick There are many, many other similar quotes about discipline and many of them are very good. Looking at these quotes and considering the points made in the article, I started to wonder how well I was doing with discipline. Would I consider myself a disciplined individual? A disciplined employee? A disciplined Software Engineer? That last question got me thinking,

"That item is nearly done. I just need to run it past the team lead to make sure it's good to go." Have you ever heard a phrase like that? What about something like this? "So, I had that finished and then I ran it by the team lead and he made some great suggestions to make this more reusable. Unfortunately I'll basically have to rewrite the entire thing, but it should make it easier in the future." Do you see anything wrong with either of these scenarios? What about this one? "The team lead is out of town, so that item will have to wait until she gets back so she can look it over." Situations like these come up every so often in development. There are some simple solutions to each of these. With the last one, the team lead should have designated someone to act in her stead while she was out. In the second one, the poor junior developer should have worked closer with the team lead from the start. The first one, though, isn't really an

This is and entry in a series about Starting Out In Development . The goal of this series is to provide brief introductions to critical tools, concepts, and skills you'll need as a developer. Version Control Overview Version Control. Maybe you've heard of it and maybe you haven't. But what is it, exactly? This post is an attempt to describe some of the basics of version control and the concepts behind some of the most popular implementations of version control. Version control probably sounds more complicated than it really is. The core concept behind version control is actually quite simple. Version control is all about keeping track of the changes to a chosen file or set of files. In essence, you tell version control what files to track and it keeps track of all of the changes to those files. Not only does it keep track of changes, but it also keeps track of who did those changes, any comments they make about it, and when they made the changes. Sounds simple e

Someone close to me has decided to become a developer. What an awesome decision! I've really enjoyed my career as a developer and get excited for others who want to pursue that path. It's a great career. Hearing that this individual wanted to start on this path got me thinking of all the advice I'd like to give them and all the tools, concepts, and skills they'll have to learn. It's a long, tough road, but it's worth it! This series of posts will be a brief introduction into many of the concepts one will likely need to learn in order to get started as a developer. List of posts: Chrome Dev Tools Version Control overview Starting Out In Development - Subversion Starting Out In Development - Git

This is the first in a series about starting out as a developer. The goal of this series is to provide brief introductions to critical tools, concepts, and skills you'll need as a developer. Chrome Dev Tools One of the biggest tools I use when developing on the web is Chrome's Dev Tools. Every browser has its own set of dev tools and they're pretty similar, but Chrome's seem to be the most mature and simplest to use. What are they? Chrome Dev Tools is a toolkit provided by Chrome that lets you, as the user, inspect the HTML of the current page, see what resources it's using, what JS code it's running, and many other things. These tools are designed for developers to help them debug and develop web pages. While there are a lot of features in this toolkit, there are a few basic ones that you can start using right away. Basic Features Opening Dev Tools There are a few ways to open Dev Tools. The easiest way is to press F12 on your keyboard. Go ahead. P