Can't even imagine the amount of crap in their code-base. I bet that amount of commits is necessary to continuously correct the shitload of mistakes coming from their "Hacking" culture.
iOS at Facebook [pdf]
31–40 of 111 posts
Re: iOS at Facebook [pdf]
#32Earlier quoted context omitted.
This strategy was hugely successful for Microsoft since the early days of Windows NT 3.1: “What Intel giveth, Microsoft taketh away.” The performance advancements on the hardware side of the platform are almost entirely consumed by the ever-increasing complexity of the most popular app on the software side.
That may be successful for the software companies. But pity the user who's stuck with old hardware and wants to know why used computers don't last as long as used cars. Maybe when Moore's Law finally becomes invalid...
Yep. 2005 G5 powermac. Totally usable machine. Can get a dual 2.5GHz boz with 4Gb of RAM for equivalent $40 in the UK.
But no, it's stuck on OSX 10.5...
Re: iOS at Facebook [pdf]
#33This was pretty interesting. It would have never occurred to me that XCode, Git, etc. couldn't handle as much as you throw at it, but it kind of makes sense how they explain it here. Still, I don't think I would like to actually work in that environment where the codebase changed so much so often and had so much dead and redundant code, so I guess I'm glad my interview with them didn't go terribly well (got asked que…
What keywords do you think the interviewer was looking for? Was it along the lines of "disruptive", "game-changing", "innovative", etc.?
Re: iOS at Facebook [pdf]
#34Earlier quoted context omitted.
Sloppy?! Those guys have needs the majority of us will never need to deal with. Did you read the presentation? If anything they're the opposite of sloppy.
The parent is not referring to those needs (which are legitimate). The presentation talks a lot about the hacking culture; how there is a lot of duplicate code, a lot of dead code, a lot of "temporary" code. We call these things technical debt. But it sounds like they just never fix them. Refactors never happen.
I sincerely doubt the fact that there are companies which thoroughly fix "technical debt".
Re: iOS at Facebook [pdf]
#35"Done is better than perfect" "Move fast and break things" I'm glad they're not holding any critical data like our personal information, what we do, what we think and where we are then! If this set of slides embodies 'hacker culture' which it claims to, I am not a hacker, neither are my colleagues and I'm proud of that. The whole thing stinks of arrogance hiding incompetence. I'm not putting anything near facebook, e…
To be fair, most of these specific signs have been removed now/changed (I was an intern there fall 2013). They actually talked about how that used to be a slogan, but breaking stuff isn't really acceptable anymore because facebook is so big. They still wanted us to move really fast though...
Facebook's new slogan is "Move fast with stable infrastructure."
Re: iOS at Facebook [pdf]
#36Earlier quoted context omitted.
Sloppy?! Those guys have needs the majority of us will never need to deal with. Did you read the presentation? If anything they're the opposite of sloppy.
The parent is not referring to those needs (which are legitimate). The presentation talks a lot about the hacking culture; how there is a lot of duplicate code, a lot of dead code, a lot of "temporary" code. We call these things technical debt. But it sounds like they just never fix them. Refactors never happen.
They don't call it debt. It is simply their way of keeping their agility with a huge number of developers. If the flip side is junk that mostly impacts install space, I don't see it as a bad trade-off.
What alternative way would you suggest to keep your mega team productive and shipping features?
Re: iOS at Facebook [pdf]
#37Earlier quoted context omitted.
Sloppy?! Those guys have needs the majority of us will never need to deal with. Did you read the presentation? If anything they're the opposite of sloppy.
The parent is not referring to those needs (which are legitimate). The presentation talks a lot about the hacking culture; how there is a lot of duplicate code, a lot of dead code, a lot of "temporary" code. We call these things technical debt. But it sounds like they just never fix them. Refactors never happen.
Eventually you just hear "New version of our app rewritten from the ground up" when it all becomes one big pile of technical debt.
Re: iOS at Facebook [pdf]
#38Can't even imagine the amount of crap in their code-base. I bet that amount of commits is necessary to continuously correct the shitload of mistakes coming from their "Hacking" culture.
They deal with this with automated code review tools like their Infer static analysis tool (http://fbinfer.com) as well as abstracting away the Objective-C with React Native.
Re: iOS at Facebook [pdf]
#39So the main purpose of most of the 18000 classes is to make it possible for the app to scale up to 18000 classes? :)
Re: iOS at Facebook [pdf]
#40Earlier quoted context omitted.
The parent is not referring to those needs (which are legitimate). The presentation talks a lot about the hacking culture; how there is a lot of duplicate code, a lot of dead code, a lot of "temporary" code. We call these things technical debt. But it sounds like they just never fix them. Refactors never happen.
They don't call it debt. It is simply their way of keeping their agility with a huge number of developers. If the flip side is junk that mostly impacts install space, I don't see it as a bad trade-off. What alternative way would you suggest to keep your mega team productive and shipping features?
Hiring a team whose sole job description is garbage cleanup?