193 karma · joined January 10, 2010
Plenty of software architecture and design experience especially wrt distributed systems.
Learning CloudFormation.
Previous: 2013 - 2017 Football Radar 2010 - 2012 Google 2009 - 2010 Taptu 2008 - 2008 Spektrix 2007 - 2008 ORC Software 2004 - 2007 MXTelecom
I find it very hard to interpolate between these examples. And none of them are "hard"! I haven't written an OS or a more efficient linked list. All I've done is plugged away at something until it works.
Anything less than O(n) obviously means not needing to look at every element of the input, i.e. it's already sorted or similar. For most other interview problems that seems like a reasonable lower bound in the absence of more detailed analysis. I guess the recruiter's advice to go practice on TopCoder wasn't just copy-paste.
I would, in the limited example given, prefer to have a 'storage' POJO (annotated with the hibernate annotations), and an 'API' POJO (annotated with the JSON and XML perhaps). Then it seems to make sense that if you're changing the underlying storage you would update the storage POJO.
I very rarely want to return the exact object as stored in my database to the API layer - there's business logic and the like that needs to be applied, and transforming the object into something the next layer requires means you can generally implement tighter interfaces.
(I'm especially interested in whether the restriction most of them impose on having multiple versions of a package is something you are dealing with).
It's a lovely chair for working in, very comfortable and with a decent head / neck support.
It's coming to Mac, and I imagine that'll come to Linux in time too.