3 ms·
> Don’t follow rules of thumb blindly. If excitement drives you, you are not alone. In my experience, few things are as exciting as shipping. Watching people u
by ChrisMarshallNY 6y ago
> Don’t follow rules of thumb blindly. If excitement drives you, you are not alone.
In my experience, few things are as exciting as shipping. Watching people use the code I wrote, or turning a mature, battle-tested infrastructure over to a new team, and watching them take it to the stratosphere.
And not having to create a JIRA database for bug reports, because the quality is so high that an occasional email is all you get.
No...scratch that. Failing is also quite exciting. Not what you meant? Sorry about that.
I'm not a big fan of dogma. That includes "Use the latest <BUZZWORD DU JOUR>, or you're a loser," as well as "Stay the hell away from the latest <BUZZWORD DU JOUR>, or you might get hurt."
I write in Swift. Even though it is coming up on seven years old, it's still a baby, compared to languages like Rust and Python. I committed to using it, the day it was announced.
This was because the company that supported it (you may have heard of them) was demonstrably behind the language, and the guy that designed it, wrote LLVM, so I knew it had a future.
I feel like I have really only been good enough at it to be confident, for the last couple of years, despite shipping a number of apps, written in it, since 2014.
I write in PHP, because I don't like to spend too much time on the server end of the API, and want solid, reliable and supported tech on the backend. If I want something more "cutting edge," I'll hire someone that is more familiar with that tech, as opposed to trying to learn it, myself.