Skip to content

Commit

Permalink
Update 2024-05-03-python-you-have-problems.md
Browse files Browse the repository at this point in the history
  • Loading branch information
LandonTClipp committed May 19, 2024
1 parent b8ab8c1 commit 4279bbd
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/blog/posts/2024-05-03-python-you-have-problems.md
Original file line number Diff line number Diff line change
Expand Up @@ -384,7 +384,7 @@ It is totally absurd to me how much talent is wasted in solving these kinds of p

It should also be noted that one of Python's main selling points is that it's so easy to use, so much so that it's often the first language developers learn. This is only a shallow marketing tactic because once you peel back the veil and see the man behind the curtain, you realize how unfriendly it becomes. This is in fact a common complaint amongst newcomers that the proliferation of tooling, and the lack of any real standard for just about _anything_, can make it difficult to become effective at the language in a professional environment.

It's also my general stance that languages are simply a means to an end. My main priority is not being an expert in a specific language, but to be an expert in delivering business results. When I find myself fighting with and being confused at a tool, it either means I'm just too stupid to understand the tool (which very well may be true), or the tool itself is just inherently confusing. In either case (me being dumb or the tool being dumb), it's serving as an obstacle towards my end goal. I certainly don't think I'm too stupid to understand Python because I have indeed used it to create huge, production-grade, business-critical applications in a number of domains. It's just that I think the complexity I was required to wrangle is not justified by the benefits of what Python offers, especially in comparison to other modern languages today.
It's also my general stance that languages are simply a means to an end. My main priority is not being an expert in a specific language, but to be an expert in delivering business results. When I find myself fighting with and being confused at a tool, it either means I'm just too stupid to understand the tool (which very well may be true), or the tool itself is just inherently confusing. In either case, it's serving as an obstacle towards my end goal. I certainly don't think I'm too stupid to understand Python because I have indeed used it to create huge, production-grade, business-critical applications in a number of domains. It's just that I think the complexity I was required to wrangle is not justified by the benefits of what Python offers, especially in comparison to other modern languages today.

I think it's great that some people really _really_ love Python, so much so that they market themselves as ~~Python experts~~ Pythonistas. That expertise is clearly in high demand and I'm by no means attempting to diminish the importance of that, nor am I try to say that people are _wrong_ for enjoying Python. My only stance, enumerated ad nausaem in this post, is that businesses need to think critically about these shortcomings before deciding they want to accept Python and all its baggage, especially when there are a number of better languages out there for backend-y kind of work (cough \*Go\* cough).

Expand Down

0 comments on commit 4279bbd

Please sign in to comment.