= 27d567bc2d48d9f40e9ccc20ea370b15)
Grapes are fine if I pick them off the stems and discard first. Canned fruit is actually a good idea. Those single-serving Dole fruit cups also come to mind as something I can toss in a bag with a spoon, no preparation necessary.
And actually, the hardboiled eggs all-at-once thing seems like a good idea. I think it'd be easier to prepare in advance if it's a one-time investment of an hour total prep/cook time every week rather than 15 minutes the night before every day. Even building a half dozen sandwhiches Sunday evening seems like less of an investment than making one an evening. Any other ideas for batch food-making?
= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
= f037147d6e6c911a85753b9abdedda8d){kind=logo}
Typical programmers don't remember these things because they're rarely relevant for typical enterprise software development*. If they're specifically important to what you're doing it may make sense to ask about them, but I don't think these kind of questions should be used just as some generalized "programming intelligence test".
* DB normalization is more likely to be relevant than algorithms, but often the database already exists.
I'm not so certain about that. I've seen a number of cases where people working on classic 'enterprise' systems struggled for a long time trying to solve problems that could have been neatly resolved using something that is considered 'theory' (like a dynamic programming solution, Lamport's vector clocks, or A* search) and after much trial and error ended up coming up with a ad hoc approach that mostly didn't blow up. If it's purely a web frontend to a database, sure, there isn't that much algorithmic complexity (that hasn't been implemented for you already), but usually there is more to it than that, and having the ability to look at a specific problem and say "You know what this is really an instance of (some already solved problem)" can be very valuable in programming (as in any other field of endeavor).