• 0 Posts
  • 33 Comments
Joined 1 year ago
cake
Cake day: August 16th, 2023

help-circle











  • A perfect example is this guy from my last job. Thought himself a leader. Thought himself knowledgeable. Always had an answer, regardless of actual facts. Alternated between barking out orders and lamenting on how he had to do everything himself. Constantly getting schooled by people who actually knew the subject matter. Those who had been around just kinda put up with his BS because he filled a position that nobody else wanted.

    Enter new management, who was very impressed with his authoritative tone, apparent breadth of knowledge, and willingness to lick boot. Suddenly management is bypassing dude’s bosses to go straight to the horse’s mouth and get the straight dope (which often involved taking credit for other people’s work and bus-chucking whoever was handy). All because someone who barely knew what he was talking about spoke confidently to people that had no idea what was going on.








  • You can make rules network-wide, per-app, or per-incident. The latter is useful for getting a handle on app behavior. Like if you see it contacting ‘updates.somedev.com’ weekly, you can choose to allow or disallow permanently based on how benign you think the app is. But more likely, anything trying to phone home has a dozen CDNs it’s trying to hit rather than an easily identifiable URL. Block one, it tries to hit the other. Maybe today, maybe next week. It gets overwhelming (which IMO is a feature for the dev, not a bug).