2 ms·
I'm puzzled by this whole "external" vs. "internal" dichotomy that you've built. Perhaps noticing that your plane isn't being unloaded quickly is "external", b
by timr 18y ago
I'm puzzled by this whole "external" vs. "internal" dichotomy that you've built. Perhaps noticing that your plane isn't being unloaded quickly is "external", but the likely solution to the problem (building some sort of high-performance, distributed database-backed scheduling architecture that track thousands of bags, flights and people in real time) seems to become "internal" very rapidly. Where's the line?
Moreover, what you describe as "external projects" sounds suspiciously like "walk around and fix individual problems in the world". That's great, but it's not scalable -- it's consultancy. Somebody hires you, and you tell them to move their Coke machine to save 116 steps per inspection. To me, the difference between that and an interesting software problem is the difference between noticing that a Coke machine needs to be moved, and writing a pedestrian traffic simulator that can be used to optimize the positions of Coke machines in any context...but maybe we're saying the same thing?
In any case, it's never a good idea to let your spoons rust.
- edw519 18y agoThose were just examples of what others did to influence me. That's all. I used to have to write the tools I needed first just to be able to do my job. No longer. Almost all of my tools are available. What you call "walk around and fix individual problems in the world", I call "find problems anywhere, then build scalable solutions". Sorry if I didn't make that clear. It's the antidote to OP's original complaint of "me too" solutions.