297 karma · joined November 10, 2013
Administering the thing was a giant PITA. Lots of GUIs, clicking, and (shocker) more XML.
I recall some sort of pipeline interface where you could manage all the various steps a requests could pass through with various components for doing SAML auth XSLTs and similar operations.
Since leaving that roll, I've seen absolutely nothing about these devices or anybody else who'd ever used them.
1. Check the literature of who is eligible for the bonus. The bonus might get paid out for anyone who was employed as of a certain date.
2. Use this as a negotiation for a signing bonus. It's common to have some vest or bonus on the horizon. Asking to be made whole with a signing bonus is how this is handled. Just be aware that you'll probably be on the hook to pay it back if you leave your new company in under a year
It's not really clear to me what having a curated list of book summaries gives me that I couldn't get from wikipedia or just google searches
This has absolutely not been my experience. I've worked with a few devs who might be curious to know how everything worked. Most devs I've worked with focus solely on the code they write.
I've also inherited many systems over the years and I'd take the ones managed with tf over bash every single time.
A non exhaustive list of what tf helps with.
1. Being able to know what has changed and what needs to change before you run
2. Managing infra outside of the large cloud providers and being able to combine the two
3. Quickly being able to add a new environment or region to an existing cluster
4. Some requirement has changed and some new policy/tool needs to be stitched in across all your environments
https://en.wikipedia.org/wiki/Jevons_paradox
In this case you can think of Artists as the "resource" being used.
Reading through a post-mortem with the active voice makes a much more clear picture to me. It becomes easier to understand the events that led to a problem. From there the key is to figure out "Why did the system not prevent this mistake".
In addition to the examples in the README, I also converted some tables from Dungeon World and one of its supplements, The Perilous Wilds: https://github.com/awwithro/OpenRPGTables
She eventually got lucky and found a 2yr old used bike for $400 which is exactly what she wanted. She just got lucky and got to the store just as they were putting it out on the floor.
1. You haven't yet instrumented the application with metrics yet.
2. The logs are from a third party tool that don't emit metrics
3. The log format is well defined and doesn't change (I'd still prefer native metrics)
Otherwise the issue is that logging messages can and do change over the lifetime of an application. Relying on the content of the log for metrics becomes an implicit API that's not obvious to developers working on the code. I've seen issues of broken monitoring and alerting because a refactor changed log formatting and content. Much better to be explicit about metrics and instrument them directly.
Game in question is Roadblocks for anyone interested https://www.newgrounds.com/portal/view/192217