Genre not found
Artist not found
Album not found
Song not found

Knee Deep In Marketing
C+ Average Lyrics

No lyrics text found for this track.

The lyrics are frequently found in the comments by searching or by filtering for lyric videos
Most interesting comments from YouTube:

Stanislaus Brown

That was actually a very reasonable video. I like that you are not strident.

Yes, it's important to be exposed to several languages, not just in a classroom settings, but in an actual work environment.

I remember the Java craze when everybody said it would take over the world. I have precisely one Java program that I keep around on my machine - one, after thirty years in IT.

I'm sure C++ has its use cases but I've also heard that it can be difficult to debug because of all the class libraries. I suppose that can be true of any object oriented programming language.

Javascript is now all the rage but it suffers from depending on things other people somewhere else on the net may have written.

I remember a case where a programmer pulled his code from a repo and an amazing amount of Javascript applications crashed because one obscure function in his code disappeared. That's a vulnerability no one expected.

I liked the Fortan example. I've never written any Fortran myself but I do appreciate that older languages have had more time to mature and become highly optimized.

I kinda like PHP. It's certainly easy to use. I've used it as a scripting language for applications that have nothing to do with the web.

But something I find that programmers, in general, overlook, is programming for maintainability.

Good programs can last for decades. And the first thing that happens to a good program, is that it constantly gets modified.

People always want customisation, reports, changes to screens, workflow, new features, etc.

There's a big difference between programs designed to be maintained over a long period of time versus something written quickly to solve an immediate problem.

C++ was developed because of the problem of maintaining huge programs over long periods of time.

PHP was not. It has always been a quick-and-dirty-fix-it-now kind of language. Though it has improved over time. And despite its warts, it is used in a lot of websites, including Facebook.

Dysonia Multiverse News

I agree a lot with the key message of this video. It really doesn't matter which languages to learn so much. Sure, there are jobs listing the languages they are looking for job applicants to have. Your wage or salary is not so much about what languages you know but your education, knowledge, experience and ability. So it's that experience and ability to deliver. The languages they point to is for what they (employers) are working with and using and sometimes they just aren't ready to re-do what they had already invested in.... the issues of 'legacy' software.

Now, when I began programming, I was working with BASIC and Assembly/Machine Language for various CPUs and computer hardware platforms such as 6502 based systems (including 65c816 CPUs and microcontrollers, etc.), TMS9900 from Texas Instruments (used in TI-99/4 and 4A), 68K series, 8080/z80, 8086 through 286 and some additional stuff with 386/486 and Pentium but these later x86 systems to present, I would use languages such as C and C++ and other languages that often have compilers to produce decent performant code. For performance, back in the earlier days, programming in machine language was the best with highly tuned programming. Back then, C++ didn't yet exist in the public commercial tools in the microcomputers era. Around mid-80s, we started to see C. Then C++ was emerging around 1990. C++ was not very beneficial for 8 bit systems and it was in the 16/32 bit era that we saw the emergence of C and C++. There was a few C compilers for C but it's code was only okay but machine language code can be more performant. 6502 machine language wasn't that hard to learn. However, modern CPUs have much more complex instruction set so it was easier to program in C and C++ and other high level languages that would compile. As C/C++ compilers evolved with optimization features, the code would be performant and as computers also got faster, the time and effort to code in machine code on the newer and faster computers was quickly becoming a waste of time for highly advanced code. Over the years, I have learned the myriad of languages including QuickBASIC/QBasic, Visual Basic, Java, various web-oriented scripting/programming/etc. languages such as HTML, CSS, XML, DHTML, XHTML, PHP, PERL, Javascript, and newer stuff like Dart (with Flutter), Typescript, AssemblyScript / WebAssembly, more modern C++, etc. The languages are a long list, so it's matters to understand the software engineering principles and applying them regardless of the languages. The point of using the right tool for the work at hand that meets the requirements and that you can adequately deliver with less work because that is what employers are going to look for... time is money after all.

If you can do the job in a language that meets the requirements that you know well enough to do it in 6 months but you would have to spend 12+ months in another adequate language that meets requirements, its fairly clear what language to use.... under most employment situations, the one that requires less time is what you would be expected to use. There's real world practical considerations.

In my experience, a lot of the languages I have experience in are now obsolete in any work situations but I can tell you C/C++ is one of those languages that have stood the test of time.

Stefan, good job with the video.


I think one of the biggest issues is companies not valuing your skills
(like you mentioned some comments hone in on HR being ignorant and
just ticking off check boxes of how many languages or buzzwords you
purportedly know)....

They really aren't expecting you to be a rock star, just another cog, no matter how talented you know yourself to be.

So that's why we all took notice when companies like Google experimented with idease like giving that Friday back to their devs.
They pay you salary for the entire 9-5 Friday, but they wish you well and hope that you'll use that 20% of your work week on your own projects.

Going even further back, companies like Xerox experimented with allowing individual departments feel the full brunt of the market force.
So the legal department didn't just serve Xerox, they can serve other companies.
The sanitation department doesn't just serve Xerox, they can serve the company next door.

Basically all of these are big organizations realizing that the larger they are, the more impossible it becomes to herd the massive number of cats.

So, when you aren't feeling valued, but you know full well your worth, you need courage. Strike out and do something insane, all on your own. Especially with developers, it seems like greatness is actually not that far away.

It's a Mac Mini in a hands-off Mac Mini colo that serves both the RESTful API and the one page front page of 99.9% of iOS apps out there and a Macbook Air that you can write just about any web app or iOS app from any where on the planet. As long as you can find your zone, get hours of quietness and distraction-free space--you can bank on your incredible brain. Outside of the incredible pain of baby-sitting iOS apps you can do something else entirely--maybe a SaaS (which, when it comes down to it, is just PWA/SPA + Flask/Django + Redis + Postgres/MongoDB--it's simple sh*t). Not everyone can be the next Google, but baby steps of even rudimentary tech know-how--expertly leveraged--can move mountains.


Every programming has a natural lifecycle.

How languages respond to innovation depends on the size of the community. If the community is small, they will redesign to make it blend in the way it should, keeping it compact. If the community is large, they will add a backwards compatible extension, making the language bigger.

The result is that old languages become feature-rich but ugly. While young languages stay slim and accessible.

And then at some stage, the community reaches its maximum size because it becomes easier to rewrite, then to learn it. It gets harder to recruit employees, but there's money to spend. So, then a rewrite happens, or it gets split in multiple applications in different languages.

A nice example is how XML and SOAP got replaced by JSON and REST. Even though XML and SOAP are way more powerful, they are also way more complicated. It just got too difficult to learn.

Ruffian Eo

Does 25-ish years of C++ programming count as experienced? Well - I mostly used it in embedded programming as a less error prone and more productive alternative to C (and the C fanboys never liked it). On the desktop, my embedded software also ran in test beds (software in the loop) as one step towards running it on the embedded targets (which varied frequently in terms of OS and hardware platform).
For Tooling on the PC (stuff like generating code or configuration apps or test systems), we opted for the highest level language which also worked fine for GUI programming (was C# back then, nowadays, I would go with F# or Common Lisp).
At that point I started screening for alternatives (did not like C++11 and what came after (C++17 was more to my taste, eventually)) and I did a language tour, including the hyped functional languages (like Haskell). And to my surprise, what I now use for my explorative, prototyping, proof of concept and tooling language is none of the fancy new languages but Common Lisp. Why? High Level AND fast (if you aim for fast).

For embedded (and probably server side programming), Rust looks like an alternative if people can accept the slow tool chain (it also does a lot a C compiler does not... but still) and really want applications which have higher prospect of being reliable.

The one language I never used and probably never will (unless you pay me triple :)) is Python. The syntax makes my eyes sore and it is slow. So why would I use it if instead I can use Lisp which is closer to C speed and once you got used to it, the syntax makes sense. Python is still in the uncanny valley, performance wise - comparable to interpreted lisps of the era between 1958 and 1990 (after, Common Lisp was more a compiled language than an interpreted one).

If there was more financial and support power behind OCAML, it very well could be the high level language of choice. But sometimes it feels as if it is maintained by just 3 dudes in a basement... And when I benchmarked ocamlopt compiled ocaml, it was slower than F# on .NET core. So I moved on.

Ricky Gai

I believed this topic is depending on what we want to do.

Obviously it take years to master a programming language before we can create amazing software. Nowadays, so many frameworks are done by thousands of engineers, how can a person learns all programming languages right ?

There are two languages namely "Marketing language" and "Lifetime language". A "Marketing language" normally helps to get a job, handle fast changing projects ( eg. mobile apps ) for companies. "Lifetime language" is with you always, to build your own business because we have to stay focus and master it to produce good products.

You can measure speed of a programming language written program via oscilloscope with a loop of turning digital stream HIGH/LOW without delay().

For me, I chosen C# as "Marketing language", C/C++ as "Lifetime language".

Hopes, this helps.

All comments from YouTube:

Antonio Barba

I didn't go to game programming because they used C++, I learned C++ because I wanted to become a Game Programmer! first, determine what you love, then learns the tools. My 2 cents.


how long did it take you to get comfortable with coding? like from zero knowledge to being able to code your own small simple game/application

Antonio Barba

@Pluto I started very young, from age 8 more or less, I was playing around with my Commodore 64 and learned a bit of BASIC. I would say my first useful, non trivial programs were a small text editor in Delphi by the age of 14 and then a simple game in C++ by the age of 16. I was self taught all the way since the beginning

Samuel Evander

How did you do it? I've learned C++ basics and I'm just stuck with getting started. People use different libraries and sometimes the IDE can't open some header files or that something doesn't work. Or I simply don't understand what is going on.

Antonio Barba

@Samuel Evander get a good C++ book and start from there


"determine what you love, then learns the tools."

Great point, but loving the tool is also important.
For example, I love web programming, but I don't like PHP much. Fortunately, I can choose another tool, provided my boss let me choose it...

55 More Replies...

Aniket Banginwar

So basically, its not a leading language but is used in almost all the important sections of the industry.
C++ is the coolest language.


but also hardiest language. In perspective of software engineering, C++ is best tool and dream language. but learning curve is very slow. basic programmer must avoid c++ and start with any other language.


Shrug I'm not saying low or high level language. I'm saying language philosophy. c++ is much harder language to understand its philosophy since c11. for example, see the boost library. even API is difficult to understand. program design is much harder and project management is nightmare.


@lol xd As someone who has used C++ a lot in the past, I find fewer and fewer uses for it lately. 99.9% of applications don't need hte performance it provides. In most modern applications, the bottleneck is not CPU performance or memory alignment, it's remote networks. JVM languages are "fast enough" if you aren't satisfied with the performance of interpreted languages for your task. With the exception of some very niche mathematical operations, JVM performance is within 10% of C performance.

More Comments

More Versions