Open source is one of the most fascinating things I’ve ever encountered in our industry. It is a movement that essentially groups people together to work on a product because they want to. They usually do it for free, especially during the first stages of the project, and then — get this — they maintain it so that others can use it. Also for free.
I tend to think that if more industries were to adopt open source as we do in software development, things would be a lot easier. Then again, that’s not why we’re here. …
The dream of being your own boss is one that almost everyone goes through at some point during their career. For some strange reason, we tend to believe we can do away with concepts such as “boss,” “9 to 5,” or “team meetings” and just sit down, put our head down, and work on what we love. Like that would solve all our problems.
In some cases, this notion becomes more than just a dream; some people actually succeed at freelance. More often than not, it either remains a dream or quickly becomes a nightmare. …
Coding, like any other skill, requires practice, if you don’t use it every day, your coding chops will go numb. And if you expect to be great, then it’s not just about coding every day at work, that’s not enough, you need to make coding your life. Think of Olympic athletes, they don’t just train a few hours every day, they live for their sport, they train 8 to 10 hours every day, and then they compete. They’re obsessed with finding their weak spots and perfecting them.
If you want to be an “Olympic coder”, then you have to see…
Companies often choose to maintain different repositories for frontend and backend code. This makes a lot of sense when the technologies are different (e.g. using JS on the front and Java on the back). But even if you’re using JS both for front and back, keeping separate repos allows for simpler branching models and version control workflows (each team can handle everything however it better fits their needs).
That being said, when that happens, certain logic components (i.e. pieces of code that solve one particular process) will have to be shared between projects in order to avoid code duplication and…
As Software Developers, we have to work hard to develop a lot of hard and soft skills to grow in our profession.
From working on our patience and determination to solve complicated problems, to improving our communication skills to better explain ideas and concepts to others.
Every day we are faced with new programming languages, new frameworks and new working methodologies. Everything is constantly changing in our industry and we need to keep up with some of those changes if we don’t want to be left behind
The effort is constant, however, as human beings we also have one single…
Have you ever had to lead a team? One where something’s not going according to plan? When that happens, one of the places we as leaders go to — is our own team. Did we screw up? Did we miss something? It’s a fair question, and it’s always important to acknowledge internal problems first. Blaming an external entity by mistake is hard to come back from.
And if the answer is “yes”, two things need to happen, and ideally, in the following order:
The journey to manager (or Team Lead, or Project Manager, or any variation of the role) is filled with personal and professional growth. Much like you don’t become one year older exactly on your birthday, you don’t gain all the experience and required soft-skills to manage a team the moment you’re promoted.
So instead of sitting around, waiting for that promotion to arrive, consider why you’re not a manager yet and find a way to work through those limitations.
The ideal profile of a manager, should meet the following requirements:
Warren Buffett is considered one of the most successful investors in the world, chairman and CEO of Berkshire Hathaway. He’s famous for, well, how much money he makes.
And because apparently, he’s been a really good investor, a lot of people tend to follow his advice to the letter. And while that is a good rule of thumb, we can also extrapolate that wisdom and use it for our own writing career. After all, by doing so we’re investing in ourselves as well.
So, let’s take a look at 9 pieces of advice from Warren and how we can apply…
Learning about different languages — even if you’re not planning on actively using them — is a great practice for any developer. This is because if you spend most of your time focused on one technology, you’ll miss out on any potential improvement you could be finding somewhere else.
Don’t get me wrong: This isn’t about mastering every language — that’s neither practical nor possible. But who’s to say you haven’t been missing out on some functional-programming practices because you’ve only focused on object-oriented alternatives until now?
So in the spirit of one of my favorite programming books of all…
Regardless of whether you’re a back-end developer working with Node.js or a front-end developer using Node.js only as a tool for your packaging and bundling needs, you’ve surely come across the concept of dependencies.
But why are there 5types of them (yeap, that’s not a typo, there are 5 types of dependencies), and what use case do they work for? These are the questions we’re going to be answering today, so sit back, and relax, ’cause this is going to be interesting…
Let’s start with the easy one, shall we?
Normal dependencies are the ones you see listed in the…
I write about technology, freelancing and more. Check out my FREE 5-step-program to start your own blog: http://bit.ly/5-steps-program