|
|
|
|
|
by CorvusCrypto
3534 days ago
|
|
I can't for the life of me think of a reason this kind of blog post would make me want to join a company. If anything it shows the opposite quality of a CTO as mentioned in the article. Use what is suited to your needs, don't worry about appealing to the tech crowd. After all, even if PHP is shit, it's not your problem. Let us handle implementation of what you need, we will (or our lead dev will) help you understand pros and cons to certain technologies. Besides, for every article written about why PHP sucks, there's at least 5 PHP devs looking for work :P |
|
I can do that, if you really couldn't do it yourself. It's not uncommon at all.
Like I said, I don't do it because I don't think it would help. But in some cases, it can definitely help. How many startups use their dedication to a specific (incrementally more modern) tech stack as a perk while hiring? Quite a few, and these often have subtly disparaging remarks baked in. And I've absolutely had success hiring and growing my team by explaining why we use Clojure over stock java whenever possible.