Re:What Insiders Say About Yahoo's Problems
by empath75 on Wednesday July 19, 2017 @07:09AM
(#14803435)
As someone who used to work at aol, it was all similar problems there. Facebook was based on Aim and Aim away messages. Aol didn't give a shit about Aim internally and just let it die. Aol also invented a lot of devops-y tools years before stuff like chef was released, then didn't open source any of them and slowly laid off all the teams working on them. They spent years in this weird gray area where nobody knew how to use their own tools any more, but there wasn't any real buy in or understanding of modern development practices (Agile? What's that?) so there wasn't any buy in for AWS/chef/Jenkins/etc, either. Just years and years of wasted time.
[ Parent
| on HN ]
Re:What Insiders Say About Yahoo's Problems
by utkarshs12 on Wednesday July 19, 2017 @08:59AM
(#14803933)
I think the "hacker-centric" culture has a lot to do with that. It definitely seems technology companies should if nothing else, at the least, identify "technology & their hackers" as their core competencies. Only when they do that will they create a culture like Google, Facebook because ideas to open-source internal tools and seeing the potential in it can only come from hackers. I had read once, that Facebook keeps jumping their hackers from one project to the other every few months to expose them to fresh ideas. Hackers do love building new things all the time; Facebook has probably cracked this.
Re:What Insiders Say About Yahoo's Problems
by dozzie on Wednesday July 19, 2017 @09:52AM
(#14804254)
> Aol also invented a lot of devops-y tools years before stuff like chef was released [...]
You mean before cfengine that started in 1993?
> [...] then didn't open source any of them and slowly laid off all the teams working on them.
Back then it was not a common practice for companies to publish their tools as open source. It's a very recent development. It cannot be held too much against AOL that they didn't.
> [...] there wasn't any real buy in or understanding of modern development practices (Agile? What's that?)
Again, time doesn't match. Agile manifesto was written in 2001.
Your opinions would have much more substance if the timing of the events was right.