3 ms·
What do you mean "betting hard"? It kind of implies that if you didn't get into python in 2008 you missed the boat. But in reality anyone who can code another p
by quickthrower2 7y ago
What do you mean "betting hard"? It kind of implies that if you didn't get into python in 2008 you missed the boat. But in reality anyone who can code another programming language can pick up python if they want to do it for career reasons (or any other reason).
- timothycrosley 7y agoSimilar to parent I bet hard on Python in 2008. That means I've been writing Python for over 10 years. Sure, any programmer can pick up a new language, but I'm able to build (what I believe) are useful projects and release them in Python every single week, outside of my full time job, community involvement and family: https://timothycrosley.com/ https://timothycrosley.com/. That level of productivity only comes from long term investment in a language IMHO.
- chrisweekly 7y agoNice choice. Also, great blog; your `whoami.md` is quite a read. Thank you for sharing! Keep it up!
- elamje 7y agoI concur! https://timothycrosley.com/whoami https://timothycrosley.com/whoami
- crtlaltdel 7y agoi first used python in ~2001-2002 and used it for many things, including a bunch of cgi-bin scripts for a very early VOIP startup. i did not consider myself to be a "dev" back then as i was mostly doing EE work and what little programming i did was split between limited firmware development and "scripting". python was an appealing way to script things out quickly. i didnt have much use for the OO, if anything finding it a layer of unneeded complexity. i would agree that there is an amazing amount of productivity to be gained by reaching for mastery over a language. that said, the efficacy of that mastery is determined by how "useful" the language is in a wider context. this is, for better or worse, highly influenced by "popularity" when it comes to programming languages. Mastering something like brainfuck? ymmv ;)
- quickthrower2 7y agoThanks that makes perfect sense. Often it's the tooling and library experience that makes a difference not just the language. I feel the same way as you do about python about C#/.NET, and I'm happy to have picked C#. I think for most things it would be as good as Python, e.g. web-dev, app-dev. With Xamarin it's a great choice. For data science I'd have to go running to Python or R (maybe I'd do as much in C# as possible), but luckily I don't do much data science.