You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Question for programmers re “Show me your flowchart and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won't usually need your flowchart; it'll be obvious." -- Fred Brooks, The Mythical Man Month (1975) Where do logs fit in this idea?
Ie, how much can you infer about an information processing system if you only have its logs to work with (both normal ops and crash) with no access to code/database schemas? Assume logs are typical design, verbose, unencrypted, unobfuscated
You're honestly sometimes better off with a tool like strafe, which shows the actual system calls an app is making to the OS, at the cost of a slightly lower abstraction level
*strace
depends on who wrote the log lines
in dev, quite a bit. In production, not much.
Logs are the most important thing. I spend a disproportionate amount of time troubleshooting customer installations I don't have direct access to. I fucking pull my hair out as they exhaust every magical bit of fiddling before they let me pull logs and say exactly what it is.
"Logs is how it works" - Steve Jobs
I agree with the other replies so far and would add that the really nice thing about seeing tables is they give you the full domain-model. Logs tend to tell you only what the programmers thought was important for getting the software back to normal operation whatever that may be
That being said, in the fortuitous event that you get some really nice and verbose logs, you can "cross the river by feeling the stones."
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
