Hacker News new | ask | show | jobs
by alfl23 4034 days ago
Not sure this is really an engineering success to be shared. 400 people, of which 350 are handling Spring configuration probably. Over bloated, massive effort, with 0 innovation and 10 steps backwards, and still a very slow product. Happy you are profitable, but tech talks should be left to people who truly know what they were doing. Read Twitter's scalability story for reference.
2 comments
iyn 4034 days ago
Sure, there are players that are way ahead of them, but for me the article was interesting nonetheless, there is always something new to learn. For me, the most interesting thing was a non-technical issue - how they organize people into "companies" and "guilds". Not sure if this is the most efficient way, but I think that this helps with "knowledge distributions" (not sure how to call this) across the company - this way more people know what is going on in different teams.

Re Twitter: I've found this article: http://highscalability.com/blog/2013/7/8/the-architecture-tw... but this is from 2013, not sure if there's something new.

link
jacques_chester 4034 days ago
I work in Pivotal Labs, a consultancy best known for RoR and mobile apps (and XP + lean product & design).

Right now I'm working on an app that was, for tedious reasons, downgraded from Spring Boot to Spring 3.2, then re-upgraded.

I'm finding that Spring Boot and some of the more recent libraries (eg Spring Data REST) make a lot of stuff very tolerable. I never have to touch XML. A few annotations and bang, my work is done.

Disclaimer: the Spring team mostly works for the same company as I do -- Pivotal -- but in a distant division from mine.

link