Simple Programmer Podcast

So, I've seen a lot of people asking me this question, about what does C/C++ mean.

Well, for new software developers this might not make any sense, after all, why do these companies put in their job listing "we want a C/C++ developer"?

I've had this doubt myself back then and this is totally normal.

This is exactly what George asked me:
"What I don't understand is why I always see C/C++ in the job listing,as far as I know those are different languages and somebody told me that C is mostly for hardware and embedded devices and I'm currently not that interested in that but why do we always see the C/C++ thing and not only one language,do people really always use both languages at the same job?Is it a bad idea to leave C aside and focus on C++ because I am really interested in competitive programming right now?"

So, do you wanna know why some companies ask for C/C++ programmers?

How To Learn C++? (C++ 101): https://www.youtube.com/watch?v=sXr2gRk8nco

So, a lot of software developers end up not being able to decide between two specializations. I often hear people bragging about how they can't decide between two specializations and what should they do if they really want to advance in their career.

Today, I've received a question from a viewer asking the same thing: How could he possibly decide between two specializations?

So Good They Can't Ignore You Book: https://simpleprogrammer.com/sogoodcantignore Get Up & Do Something Playlist: https://www.youtube.com/playlist?list=PLjwWT1Xy3c4V4yB2C2jJc_Tg7o75RRFYm

So, a lot of software developers end up not being able to decide between two specializations. I often hear people bragging about how they can't decide between two specializations and what should they do if they really want to advance in their career.

Today, I've received a question from a viewer asking the same thing: How could he possibly decide between two specializations?

So Good They Can't Ignore You Book: https://simpleprogrammer.com/sogoodcantignore
Get Up & Do Something Playlist: https://www.youtube.com/playlist?list=PLjwWT1Xy3c4V4yB2C2jJc_Tg7o75RRFYm

Writing code is definitely an art. It is far from being something automatic. This is so true due to the fact that every software developer writes a different code, based on their personal experience and how they perceive it is the best practice for writing it.

So, one of the most asked questions I receive is how a code should be written and what are the best practices for writing code.

In this video I'll discuss a little bit more about how many lines of code should a function have.

This is such a particular code and a quote from Code Complete Book sums it up really well: "From time to time, a complex algorithm will lead to a longer routine, and in those circumstances, the routine should be allowed to grow organically up to 100-200 lines. (A line is a noncomment, nonblank line of source code.) Decades of evidence say that routines of such length are no more error prone than shorter routines. Let issues such as depth of nesting, number of variables, and other complexity-related considerations dictate the length of the routine rather than imposing a length restriction per se."

Wanna know more about how many lines of could should a function have?

Should You Comment Your Code?: https://www.youtube.com/watch?v=ErW6fEvulAc Clean Code Book: https://simpleprogrammer.com/CleanCodeBook

Writing code is definitely an art. It is far from being something automatic. This is so true due to the fact that every software developer writes a different code, based on their personal experience and how they perceive it is the best practice for writing it.

So, one of the most asked questions I receive is how a code should be written and what are the best practices for writing code.

In this video I'll discuss a little bit more about how many lines of code should a function have.

This is such a particular code and a quote from Code Complete Book sums it up really well:
"From time to time, a complex algorithm will lead to a longer routine, and in those circumstances, the routine should be allowed to grow organically up to 100-200 lines. (A line is a noncomment, nonblank line of source code.) Decades of evidence say that routines of such length are no more error prone than shorter routines. Let issues such as depth of nesting, number of variables, and other complexity-related considerations dictate the length of the routine rather than imposing a length restriction per se."

Wanna know more about how many lines of could should a function have?

Should You Comment Your Code?: https://www.youtube.com/watch?v=ErW6fEvulAc
Clean Code Book: https://simpleprogrammer.com/CleanCodeBook

So, a lot of you guys are interested in investing and I figured it would be of great help to create a video talking more about other types of investment, especially sweat equity.

If you're not familiar "Sweat equity is contribution to a project or enterprise in the form of effort and toil. Sweat equity, in the context of real estate, refers to value-enhancing improvements made by homeowners to their properties.

Sweat equity is the non-monetary contribution individuals make when developing a project, such as rehabilitating homes for resale or starting a new business venture. For example, a person fixing up and selling homes spends time repairing and renovating the properties. A newly formed company's founders, advisors and board members contribute their time building the business." (Source: http://www.investopedia.com/terms/s/sweatequity.asp#ixzz4RIszRNQJ)

So, can sweat equity pay off? Watch this video and find out!

SUBSCRIBE TO THIS CHANNEL: vid.io/xokz Real Estate Investing For Programmers: https://www.youtube.com/playlist?list=PLjwWT1Xy3c4VWM_cpbXXYIYSaLjiTdtA-

So, a lot of you guys are interested in investing and I figured it would be of great help to create a video talking more about other types of investment, especially sweat equity.

If you're not familiar "Sweat equity is contribution to a project or enterprise in the form of effort and toil. Sweat equity, in the context of real estate, refers to value-enhancing improvements made by homeowners to their properties.

Sweat equity is the non-monetary contribution individuals make when developing a project, such as rehabilitating homes for resale or starting a new business venture. For example, a person fixing up and selling homes spends time repairing and renovating the properties. A newly formed company’s founders, advisors and board members contribute their time building the business."
(Source: http://www.investopedia.com/terms/s/sweatequity.asp#ixzz4RIszRNQJ)

So, can sweat equity pay off? Watch this video and find out!

SUBSCRIBE TO THIS CHANNEL: vid.io/xokz
Real Estate Investing For Programmers: https://www.youtube.com/playlist?list=PLjwWT1Xy3c4VWM_cpbXXYIYSaLjiTdtA-

So, a lot of people have problems with people that don't smoke. Facing a smoker for a non-smoker is a really awful situation.

People that don't smoke get completely annoyed by the smoke and all of this stuff. And one thing that non-smokers usually do is preventing someone from smoking. Without success, of course.

So, how do you deal with people that smoke? Watch this video and find out!

Stop Explaining Yourself Too Much!: https://www.youtube.com/watch?v=1h1XvlGU3xE

So, a lot of people have problems with people that don't smoke. Facing a smoker for a non-smoker is a really awful situation.

People that don't smoke get completely annoyed by the smoke and all of this stuff. And one thing that non-smokers usually do is preventing someone from smoking. Without success, of course.

So, how do you deal with people that smoke? Watch this video and find out!

Stop Explaining Yourself Too Much!: https://www.youtube.com/watch?v=1h1XvlGU3xE

So, this is a question I believe a lot of developers would die to know the answer. As software developers, we usually start learning just one programming language and we then specialize in it.

So, you start working with that programming language till you master what you can with it. However, there comes a time when we, as software developers, reach a plateau. There are no new things to be learned and we feel like it is time to jump to a second programming language.

But... When should we do it? How can we know when to learn a second programming language? How can we know that this time spent learning will do more good than harm in terms of not wasting our time?

Watch this video and find out!

Seven Languages in Seven Weeks: A Pragmatic Guide to Learning Programming Languages: https://simpleprogrammer.com/7lang7weeks John Sonmez Pluralsight Courses: https://simpleprogrammer.com/pluralsight 10 Steps To Learn Anything Quickly Course: http://simpleprogrammer.com/10stepstolearn