Simple Programmer Podcast

Simple Programmer is now BACK with a brand new YouTube ChannelSUBSCRIBE HERE: https://simpleprogrammer.com/subscribespyt

I got a question today about my billing rate, so whether it's real or not and I found a few questions like this. I just want to say upfront that when I say something or do something or do something like if I post on my blog post or if it's on a marketing message or an email or something, it's generally true. When I first started out I think I was charging like $30 or $40 an hour and to me that was really, really good. I had gotten this one contract where I was charging $100 an hour and I said, "Wow, this is crazy how—I can't believe someone would pay me $100 an hour." Then I heard of people that were charging more than that like $200 an hour. As I started marketing myself and building up the reputation in the industry I started raising my rates and I got to the point of charging $300 an hour and the first time I threw that out to a client and they didn't even blink. They didn't try to negotiate me down. They just signed the check. It took some time to get to there and I can understand the scepticism about it, but honestly, and I'll tell you this right now, just this last couple of weeks was the first start time I started turning down people at $300 an hour because it's not worth it. While it might seem like something you won't EVER be able to accomplish, this is way way more possible than you can imagine. In today's video I'm going to share some tips on how you can bill $300/hour as a freelance software developer and how you can do it too.

Simple Programmer is now BACK with a brand new YouTube ChannelSUBSCRIBE HERE: https://simpleprogrammer.com/subscribespyt

Recently I came across a Quora question that was asking "I'm A Programmer and I wanna quit, what should I do?". Believe me. many programmers go through it. Programming by itself is a hard thing. It requires focus and it has, indeed, a big biiiig learning curve. That is one of the reasons why so many developers get frustrated in actually trying to program and create some kind of software the right way. "This is what I've learned about learning to code: You feel confused and completely unworthy like 99% of the time. But that one time you make something work, it's MAGIC." If you're thinking about quitting programming, you should definitely be aware of some stuff. First thing is to question yourself: Why have you started programming at first? In today's video I'm going to help you out when it comes to finding the right answer if you should quit programming or not. Should You Quit Programming Workflow: https://simpleprogrammer.com/workflowquitprogramming

Simple Programmer is now BACK with a brand new YouTube ChannelSUBSCRIBE HERE: https://simpleprogrammer.com/subscribespyt

You're going for your next coding interview for a node.js job. Then, you should expect lots of different questions regarding node.js. What do you do then? Why don't so many developers still don't prepare for questions about programming language and stuff? Node.js framework is actually not a framework or a library, but a runtime environment, based on Chrome's V8 JavaScript engine. The technology was first introduced back in 2009 by Ryan Dahl at the annual European JSConf and was immediately recognized as "the most exciting single piece of software in the current JavaScript universe". However, it wasn't until recently that a wide adoption of server-side JavaScript with Node.js started. The interest in this technology peaked in 2014, as per Google Trends, and remains high. (Source: https://www.altexsoft.com/blog/engineering/the-good-and-the-bad-of-node-js-web-app-development/) In this case, you definitely should be prepared to answer questions like what are the pros & cons of node.js, what is node.js, and more. Answers should look like this: "Using Node.js for backend, you automatically get all the pros of full stack JavaScript development, such as: better efficiency and overall developer productivity code sharing and reuse speed and performance easy knowledge sharing within a team huge number of free tools" In today's video we'll go through some Q&A about node.js and how you can nail your next coding interview applying for a node.js position.

Simple Programmer is now BACK with a brand new YouTube ChannelSUBSCRIBE HERE: https://simpleprogrammer.com/subscribespyt

If you work for some company writing code, you've probably dealt with code reviewers. These code reviewers aim to find flaws in your code, usually with the objective of improving and making the overall system works better. However, this is not always what happens. Sometimes, these code reviewers are complete idiots and they tell you nothing that matters. They don't make efforts to provide decent feedback and, end up being complete bastards. So, what should you do in these situations? I recently got a question from a subscriber and he asked me the following question: "I recently started with programming for Front-end development and working on my first project started 2 months back. A Code review was done last week and the feedback which i have got have 18 comments. For half of them I consider myself responsible as those comments are about formatting things and some redundant code, but latter half of them are just because of exiting logic which somebody else worked for same project and I have applied same to new functionality I am adding to the application. And comments are slightly rude like strict commanding statements, expressing aggression about how long it took for him(code reviewer) to understand the code. Could you help me how should I respond to this as this is first time for me and I really don't have any idea that would I be able to fix them all making sure code doesn't break down." How should you handle passive-aggressive or even aggressive code review comments? Watch this video and find out.

Simple Programmer is now BACK with a brand new YouTube ChannelSUBSCRIBE HERE: https://simpleprogrammer.com/subscribespyt

As soon as I decided to change my career as a developer and become a web dev. I have been rejected by almost 30 companies, sent hundreds of job applications and literally got almost no response back. It has generally been the same story. I would breeze through phone rounds, do well enough in on-site interviews that I would have a lot of hope, and then I'd get a friendly rejection e-mail. The easier thing to do would be just to give up and pretend like it never happened. But I insisted. And it got me the job. In this video, I'm going to tell you why you should not give up if you're receiving rejection after rejection emails.

Simple Programmer is now BACK with a brand new YouTube ChannelSUBSCRIBE HERE: https://simpleprogrammer.com/subscribespyt

This might be your roadmap to maximizing your salary as a software developer. The million-dollar question is: How do you negotiate your salary without losing the job offer or seeming greedy? Ashley did it, but first she had to avoid the most common salary negotiation mistake... Most developers fall into different traps when it comes to negotiating a job salary. It might be due to hundreds of different reasons, but, what I often see, is: don't negotiating at all. Developers also make the mistake of saying out loud their salary expectations, saying what they did earn in their last job and more. If you're really feeling like this, then, Josh Doody is the perfect person to help you out on this one. On average, Software Developers improve their job offers by $46,150 when after Josh's negotiation techniques. In today's video, Josh and I will discuss more about some amazing techniques when it comes to negotiating your salary as a software developer.

Simple Programmer is now BACK with a brand new YouTube ChannelSUBSCRIBE HERE: https://simpleprogrammer.com/subscribespyt

Programming Reality Vs Expectations (What You Think Vs. How It Actually IS!)

Programming reality can be very different from its expectations. #programming #programmingreality #programmingexpectations

If you're a new developer, or even an aspiring developer trying to break into tech, you probably think that, by becoming a programmer, you'll be coding all day long, writing code that will change the world.

You couldn't be more wrong.

Coding is much more than just writing code. When we expect to be writing code all day long, software development is much more about solving problems than it is to writing code all day long.

In today's video I'm going to tell you the reality vs expectations of programming and let you decide if this is the right career choice for you.

Simple Programmer is now BACK with a brand new YouTube ChannelSUBSCRIBE HERE: https://simpleprogrammer.com/subscribespyt

Don't learn to code in 2019. Learn to problem solve instead. Does it sound like something that most people don't talk about? I bet it does. But this is definitely the reality. I often see this with newbie and experienced developers. They try to learn all the possible outcomes of coding, learn to program in a hundred different languages... Only to start feeling overwhelmed. And that's when they still find coding to be absolutely difficult. But why that happens? Because they absolutely have no idea how to solve problems. And this is why, building an entire application might be a long distance dream for most software developers. I've been there too. When most programmers are given a programming problem in an interview, they make several key mistakes. The most severe of those is the improper allocation of time. You have heard the saying "measure twice and cut once," then you are probably familiar with the idea of spending upfront time to make sure something is done right, rather than diving right in. It is astounding how many developers can write and maintain large enterprise systems dealing with all kinds of complex logic, database access, etc and cannot for the life of them solve a moderately difficult programming problem given in an interview in less than 30 minutes. It is also astounding how many developers who can not write even a single line of code, can also fail at same problem, in exactly the same way. Based on those two statements, your first assumption might be that asking someone to solve a programming problem as part of an interview would be a bad idea, because it isn't really telling you if they are good and just crumble when asked to do something like this on the spot, or if they can't program at all. So get to it! Start learning how to solve programming problems. Reverse strings, sort linked lists, help grandma pick the highest yielding grandsons and a granddaughters to send Christmas cards to!

You are looking for a job but you do not know anyone. You see all of these developers getting their programming jobs before you, and you simply start to ask yourself: How come that they get these programming jobs and I'm able to get none?

So you are looking for a new programming job, where do you go first? Indeed? Monster? Hacker News?

You sent all of these programming resumes but you're able to get no responses back. What do you do?

This happened to me. I sent all of those resumes but I was able to get NO RESPONSES back.

This is when I decided to go that extra mile. To finally bypass HR. And that's how I got my programming job.

I reached out to the CEO, hiring managers, CTO of a lot of companies and sent them this email:

"I saw your post on Hacker News Who's Hiring June 2016. I read up on the company and I was really excited at the fact that you guys are trying to change the fashion industry by trying to offer high quality clothing to people all around the world at a cheaper price. I was wondering if you could talk to me more about your time there and why you love it?

Here is a link to a project I made for you. I did not know python or react, but I wanted to learn because I love to continuously learn and improve my skill set. I hosted it on AWS also using Ec2 instance and cloudfront.

Also, are you hiring for junior full stack engineers?

Best,

Antonio"

In this video, I'll teach you how you can do the same so that you can finally land your programming job.

Simple Programmer is now BACK with a brand new YouTube Channel

SUBSCRIBE HERE: https://simpleprogrammer.com/subscribespyt

Coding interview preparation takes a lot more than just understanding how to write code. When it comes to a technical interview, nerves kick in and you, as a programmer, need to be calm and confident.

What most people don't do, however, is preparing for a coding interview the right way.

Don't get me wrong... Technical skills are definitely important. But your performance on a coding interview can't rely solely on that.

This is when coding interview preparation comes in... Especially, the 24 hours before your actual coding interview.

For that, you need to have a routine, preparation and know everything you can about the job description and your resume.

So... Do you wanna know more about coding interview preparation and how to prepare for a coding interview? Watch this video and find out!