Debugging tends to be more REPL based than debugger based. It is possible to debug from Eclipse using the build in debugger, but it's not something i have done as it is not really necessary.
18 karma · joined October 23, 2011
Debugging tends to be more REPL based than debugger based. It is possible to debug from Eclipse using the build in debugger, but it's not something i have done as it is not really necessary.
Also it allows (or will allow) users to avoid using Windows just to be able to play games. This is a good thing all around.
For instance, this spring I am going to India with work, after which I want to travel to somewhere in southeast asia, probably with one or two stops, and then home to copenhagen.
It should be possible to have an overview over my entire travel, not just the one leg or a simple return trip as my travels are rarely just that.
(looks good though, I am definitely going to try it)
Seems it would make a valuable tool for managing a larger number of printers, to know when to switch the toner for instance.
The raid boss Onyxia (a great big dragon in a cave, which you could only kill once a week as i recall) had a phase where she would take off and fly above the raid. Once in a while she would then do a deep breath, a fire attack which had a high chance at killing you if it hit you.
Now, all sorts of tactics emerged on how to handle the fire attacks. One that stuck for a very long time was that the number of DOTs (Damage Over Time) would lower the number of deep breaths you got.
I'm sure there were other theories as well, but this one stuck for years with raid leaders yelling at warlocks, the class with most dots, to add more dots and even stacking the raid with warlocks to get as many dots as possible (we need at least 4 warlocks to take her).
In the end there was a developer (or just Blizzard employee) who admitted that it was in fact random. This story pops back in my head once in a while because I think we do this a lot on larger scales too without realizing it: See some phenomenon caused by randomness, come up with a theory, and because it is not easily refuted (after all it works most of the time right?) it becomes common knowledge that everyone follows.
How do the travel indexing sites like Kayak get their data? Surely they don't index or consume APIs from the travel companies individually?
I mean I know it says in your FAQ: "Our experts provide detailed booking instructions for you to buy those flights."
But I am just not totally clear on how this works and how the prices listed are provided. Could you elaborate? Also, is there potential for price differences when an agent finds prices for someone in another country?
I really like being able to navigate in all my open projects at the same time. Not having it is a no-go for me.
Edit: I would still love to hear how it actually is to work there in practice though.
Is this the one?