Nim sounds as the most ideal language when comparing to Python, Rust, Julia, C#, Swift, C

vim and make serve well as universal IDE for most programming languages (maybe apart from C#?)

Drivers run in kernel mode to access the hardware

Curated list of basic to advanced C Interview Questions to ace your interview from InterviewBit

Mistakes programmers need to look out for

• Programming is more about practicising than passive knowledge gain.
• Understand the solutions solved/suggest by your peers, introspect on why he could solve it better and why you couldn't.
• Be a perpetual learner.
• Don't just reuse, reuse and add value.
• Re-affirm and reconfirm your learning.

I was going through my Firefox bookmarks and I found article. I had read this article two years back and had commented that I found it to be useful. I read it back in May 2018. As of now, November 2020, my programming skills are still novice-level. I haven't implemented the ideas or followed suggestions given here.

It has been 2 years and 5 months since I found this article to be relevant and it baffles me that I haven't taken action by making use of the knowledge given in this article. Two long years flew by. I guess reviewing my bookmarks is something that I will do more often.

The article was posted on May 23, 2018 and I had stumbled on it the next day itself, i.e., May 24, 2018. This gets me thinking that we could finds solutions for problems(latest ones in this case) once we identify it, articulate it, hit the search button and just read stuff. I could presume that what happened next was that I misunderstood "finding a solution" to "realizing the solution", and perhaps became complacent or maybe there were more problems that didn't come to my awareness to identify and further find solutions. I'm not quite sure. Should I have identified my problems and googled more so that I could have learned C and C++ sooner?

I wonder what held me back from taking action to accomplish and master something that usually takes not more that 5-6 months maximum.

On learning programming

• Master one first programming language first, before moving to the next.
• Learn at a slow for the first two programming languages. This is important for beginners
• Practising coding is more important than watching tutorials or reading books. You learn more by practising than by reading or watching videos.
• Apart from tutorials, immitating open source projects is very important
• Read others code and immitate it. You'll be surprised at how fast you're learning.
• Make use of StackOverflow, Quora and programming subreddits.Ask questions there. Interact more.
• Practice more. Write code from time to time. Debugging skills imporove with more coding practice.
• Test your skills with quizzes, challenges and competitive programming

When to use different programming languages (advice from an Amazon employee):

• Java - enterprise applications
• C# - Microsoft's spin on Java (useful in the Microsoft's ecosystem)
• Ruby - when speed is more important then legibility or debugging
• Python - same as Ruby but also for ML/AI (don't forget to use type hinting to make life a little saner)
• Go/Rust - fresh web service where latency and performance were more important than community/library support
• Haskell/Erlang - for very elegant/mathematical functional approach without a lot of business logic
• Clojure - in situation when you love Lisp (?)
• Kotlin/Scala - languages compiling to JVM bytecode (preferable over Clojure). Kotlin works with Java and has great IntelliJ support
• C - classes of applications (operating systems, language design, low-level programming and hardware)
• C++ - robotics, video games and high frequency trading where the performance gains from no garbage collection make it preferable to Java
• PHP/Hack - testing server changes without rebuilding. PHP is banned at Amazon due to security reasons, but its successor, Hack, runs a lot of Facebook and Slack's backends

a.k.a. Strongly typed enum pattern

Collection of programming bit tricks with bitwise logical operators: & | ^ ~ << and >>

A thorough primer on C programming, specifically for the Texas Instruments TM4C123 or TM4C1294 microcontrollers. By Jonathan Valvano and Ramesh Yerraballi of UT Austin.

Do you have what it takes? Signup on www.venturesity.com and unlock opportunities.