| Like a lot of people who have given interviews, I have my own set of very odd stories. I interviewed a developer and asked him to explain how the system he was currently working on worked on the whiteboard. As he talked he drew two boxes. He drew a line between those boxes. Then as he talked he kept drawing over the line between the boxes. (Now, he was jr to mid-career so I didn't expect a magnum Opus but we value people who can explain themselves because at least if they're wrong we find out before the mess gets too big. But I digress.) Your analysis reminded me of that interaction. What kind of information architecture do you have if you're building objects that big? I mean, as others have said, if this is the main payload being transferred from client to server, it's probably going to arrive as JSON and you're going to turn it into Objects. If it's not that data (they're talking about cold loads) how many other categories do you have that can approach 10k? Configuration? We have libraries for that and they often read a JSON file. Lookup tables for fixed relationships of data in the system? Maybe, but that complicates your testing situation. How many of those categories get loaded more than once per session? Are these really such large startup bottlenecks that we tackle this instead of other problems? GP implied incompetence but I get more of a whiff of desperation here. |