News for hackers. Stuff that matters.
Re:How AWS came to be by hinkley on Saturday July 02, 2016 @01:56PM (#12023267)
> like many startups, when it launched in 1994, it didn’t really plan well for future requirements. Instead of an organized development environment, they had unknowingly created a jumbled mess.

Somehow this sums up many of the frustrations I've had working in software. I point out to people when they're making these kinds of decisions, and I call them on it when they romanticize it into an unhappy accident instead of a form of insidious, latent neglect.

I find it infinitely amusing when software developers become homeowners and complain about the exact same sorts of myopic shortcuts and idiotic decisions made by the former owners, without a hint of dissonance.

Re:How AWS came to be by sidcool on Saturday July 02, 2016 @02:42PM (#12023423)
I would like to hear your experiences with software.
Re:How AWS came to be by hinkley on Friday July 08, 2016 @01:11PM (#12057040)
Michael Feathers and I are of an accord on many topics, including the use of salty language to describe untenable situations. He has books but I really have enjoyed some of his presentations and one-on-ones on other people's podcasts. Googlestalk him.