The Efficiency In Coding Strictly

The Efficiency In Coding Strictly

5 years ago
Anonymous $oIHRkISgaL

https://medium.com/@isaaccway228/the-efficiency-in-coding-strictly-e79beceafa05

Before I get into what it could mean to code “Strictly” or even “Efficiently”, I’m first going to tell you just a little bit about my coding experience so you know where I’m coming from.

I’ve spent significant time coding in both dynamically typed and statically typed programming languages. For anyone who doesn’t know, statically typed languages (C, C++, Swift) are, generally speaking, languages that require the developer to give a variable a type when it’s declared. A dynamically typed language like (Python, Javascript) does not require you to specify a type for every variable. I don’t know exactly how much time I spent in these languages exactly, but if I had to guess I would think it’s split pretty evenly. ⅓ of my time was in C/C++/JS, and ⅓ of my time was spent in each of Swift and Python. I say this just to make the point that I have no preference among these languages, I use whatever I need to use to make whatever it is I need to make. Personally speaking, I very much enjoy coding in both Swift and Python which are both at opposite ends of the spectrum as far as strictness goes. C/C++ I don’t enjoy as much, but they’re cool but in the same way that a game boy color is cool. Don’t get me wrong, those languages are necessary in some areas of software even today, but they’re not “easy” to get things done compared to something like Swift, or Python.