There is a common trap that we fall into as developers, and it is believing that because some code “worked” that the code was written “correctly”. In reality, for most technical problems, a good developer can likely point out several different solutions. Any of those solutions might be perfectly reasonable, while none of them is the single “correct way”. Different solutions optimize for for different things You can only optimize for a few things at once, and there are always tradeoffs.
A while back I went through the interview process at a company I won’t name here. The first interview was basically just a phone screen, where I was able to chat with my would-be manager about things like compensation range, tech stack, work duties, etc. It went well! The guy was delightful. I moved on to a second interview, which was a live coding session that lasted 1 hour where I completed two technical problems.
It’s either a blessing or a curse when choosing to learn Python or C++ because there couldn’t be two more opposing languages to compare. On the one side, we have Python, a high-level, multiparadigm, general-purpose language most known for its strength and security, and on the other, C++, a high-level, object-oriented, general-purpose language, which is popular for its fast, lightweight capabilities. Python supports procedural, object-oriented, and functional programming and is often described as “batteries included” because of its comprehensive standard library.
PHP famously claims to be the backend programming language for just under 80% of the Internet. However, if you look at the popularity rankings of programming languages, Python is consistently far ahead of PHP. How can that be? Both languages can be used for backend web development, and PHP was even specifically made for that. So which one is better, Python or PHP? If I were starting fresh, I’d pick learning Python versus PHP any day, and here’s why.
It’s hard finding good product people. That fact is really a tragedy because they are probably the most important part of any product-focused organization. I think there is a misconception in the software industry that product managers have a good sense of “what users want”, “what the next feature should be” or “ux design”. In reality, I’ve come to believe that the best product managers aren’t good at any of that, and they know it.
A ruby is a beautiful red gemstone; a python is a beautiful green snake. Aside from that, they’re both very popular programming languages. They’re popular for different reasons, and they’re good at different things. Before you choose between Ruby vs. Python, make sure you ask yourself these 10 questions. While I’m more familiar with Python since I use it for web scraping and data cleaning, Ruby is also worth a mention.
Everyone wants to know the best way to learn to code Python nowadays. It’s a great language, as I’ve written about before, with great career prospects and tons of useful features. For as many reasons as there are to learn Python, there is probably an equivalent number of ways to learn Python. You can already tell because this is a listicle and not a tweet, but the best method to learn Python does not have a single answer.