> Even though Microsoft's software had not caused the CrowdStrike incident, Microsoft immediately jumped in and offered to assist Delta at no charge following the July 19 outage," the letter said. "Each day that followed from July 19 through July 23, Microsoft employees repeated their offers to help Delta. Each time, Delta turned down Microsoft's offers to help, even though Microsoft would not have charged Delta for this assistance

Two vendors offer you free on-site help, during the biggest outage in history, and you turn it down?

This isn't the CIA, it's Delta Airlines. Bring those overpriced security monkeys in, make em sign an NDA, and have them sit there and watch you type.

To not do that... even if they were useless... I can't find a justification ....... other than being able to later claim it wasn't Delta's fault it was down so long, and nobody having evidence to the contrary.

https://www.gnu.org/software/make/manual/make.html

I much prefer Make to alternatives like Just or Taskfile. Besides the fact that more people know Make, Make actually has incredibly useful functionality that alternatives remove 'for simplicity', but then later you realize you want that functionality and go back to Make. Sometimes old tricks are the best tricks.

An Introductory Guide to Electricity Markets regulated by the Federal Energy Regulatory Commission: https://www.ferc.gov/introductory-guide-electricity-markets-...

Deregulation and competition: https://en.wikipedia.org/wiki/Electricity_sector_of_the_Unit...

First of all, feedback is not a great way to build relationships. If it's positive feedback, and it's not perceived by them to be demeaning/dehumanizing/etc, most people will like it, regardless of relationship. But if it's negative, nobody likes to receive negative feedback, but especially not from someone they don't already trust. First build a relationship, then give negative feedback, when appropriate (which is a very qualified when).

Second, asking if you can give feedback is like asking if you can ask a question. The other person is going to feel rude if they say no, so they will instead feel pressured to say yes, and now you have a position of power over them, they feel bad, and you haven't even given the feedback yet. If the feedback is positive, just give it, don't ask them if it's okay. Nobody will legitimately complain about praise. If the feedback is negative, keep your friggin' trap shut, unless you feel the feedback is absolutely necessary, from you, right now. If it doesn't need to come from you, or it's not absolutely necessary in this moment, then wait until you have a normal conversation with them and allow it to enter conversation naturally and gracefully.

Third, don't offer feedback if the person has not already requested feedback. You can offer to them that they can give you feedback, but if they don't provide the same reciprocal offer to you, don't push it. Feedback isn't a right, it's a privilege.

Fourth, you absolutely should be afraid of giving feedback to people who might use that feedback against you. In fact, just sharing your thoughts about things in general, out in the open, can unintentionally hurt people's feelings and turn them against you. I have personally found out on several different occasions that I somehow hurt someone's feelings unintentionally, just because of my opinions on some topic (engineering-related, business-related, etc) that wasn't personally directed at anyone. Your tone, messaging, content and context can and will have unintended consequences, so think before you speak. If you're unsure of the outcome, either don't speak, or accept the consequences.

Fifth, this is general knowledge, but always complain up, never down. On the other hand, praise everyone: your boss, your direct reports, your peers. Praise costs nothing but does make people like you (and others).

If the only thing people hear you say is positive things, you will probably be one of the best-liked people at work. Giving negative feedback generally won't help you, and many won't be open to it, so choose wisely when you give it.

I think the law deals with similar concerns by not basing a judgement on how someone feels, but rather on actions and agreements. Did they lie, cheat, steal, deceive, coerce, manipulate, intimidate, threaten, abuse, etc in context of some agreement or lack thereof. But that's just the law; obviously there is an entire world of morality/ethics that exists outside the law with different considerations.

I'm just saying, he hit on a minor, and he doesn't appear to be a moron, so screw this guy.

The Agile Manifesto is a failure at trying to make Agile happen because it can't tell you how to make it happen, because it varies wildly. No manager can read a book on how to "Agile-ify" their org, they have to apply their brains and figure out how their specific version of "Agile" will work. But the skill-set required to do this is not a Managerial skill, it is a lower-level-worker skill. But it's also a very advanced lower-level-worker skill.

And that's why things like "Agile", "DevOps", etc will fail. People at the higher end have no clue how to make it happen, and people at the lower end who have an idea how to make it happen don't have the power to make the organizational changes to do so. You need a way for the lower-end people to tell the higher-end people what to do, and have the higher-end people listen to them, and make the changes happen. This is very hard in a traditional organizational hierarchy, because higher-end people have big egos and bigger concerns over things like politics.

You mean Jobs? Philly definitely has more. But I found Balto to have more going for it, despite being tiny in comparison. Culture-wise, Baltimore has loads of everything (except the "we're pretending we're NYC-lite" that DC and Philly push). There's loads of green spaces, festivals, multicultural cuisines/neighborhoods, industries. Baltimore even exceeded Philly in things like hackerspaces/makerspaces/tool libraries. And Balt has [some] free public transit! And though the history isn't pushed much, there's a ton of it all around. I'd also argue the Inner Harbor exceeds any Philly tourist district in terms of interesting ways to waste a saturday for a wide range of people. Then you've got the stadiums right near the harbor, the light rail to whisk you up into the lush suburbs, and more quirkiness and charm than practically any city in the US.

But I might be biased.

I love the BMA. It's a free museum with a great restaurant, cool exhibits, a nice park across the street. Nearby is The Book Thing, a free book store. Also another (non-free) book & record store, Normal's. And another, Urban Reads. And another bookstore/coffee shop, Bird in Hand. And a farmer's market. And a vegan restaurant. And the quirkiest diner ever, Papermoon. And a small rock venue. And a worker-owned co-op coffeeshop that President Obama visited. All in a four block radius.

Dang, I miss Baltimore.

What's weird to me is that nobody has to submit their standard or paper to ISO or a journal, they could just put them on a blog post somewhere. But people still complain that these organizations, who people voluntarily submitted their papers to, are actually charging people for what they said they would charge for, or take the rights they said they would take. It's not like somebody was tricked. This is like a manufacturer giving their jeans to Wal-Mart to sell and complaining that Wal-Mart is taking a cut. Yeah..... they're selling it. That's how that works. The manufacturer could always sell them out of the back of a truck... but they don't want to.

I cringe when I see a team blindly implement the design in a paper. Design to your needs, not somebody else's! Papers are great places to take ideas from, but you should never treat them like gospel, or copy them outright. It's the same trap as designing your solution around your tools rather than vice versa. When someone brags about implementing the design in a paper, I expect it to work poorly (at least until they figure out all the stuff that wasn't in the paper).

Papers are experiments, whereas Best Practices are the experiments that were reproduced by many people in many places over a long period of time. If what you're building matters (not R&D), implement the best practice first, not the experiment.

There is no God, but there are working groups of angels discussing Existence Standards.

The problem of "what to keep" isn't even digital-specific. In my youth I probably bought two dozen disposable cameras, had the pictures printed, even paid for the CD-ROMs when they became available. Where are those pictures now? Who knows! That's why I like Marie's message: it's not about throwing away junk, but keeping what you love close to you.

Holy shit, this. I thought I was crazy for feeling emotionally blackmailed by my parents. They effectively told me that if I wasn't a constant part of their lives, they would be miserable - after things like blaming an episode of depression on my poor academic performance. At the same time being callous and judgemental towards me, and each other. I'm just surprised that they expected me to stick around?

But I'm not convinced on the latency/compute/storage comparison with Kafka or other solutions. I think a POC would need to be built and perf tested, and then tweaked for higher performance and lower cost, like most software. Considering the volume of traffic that mail software is designed for, I can't see how even a large provider like Stripe would have difficulty scaling a mail system to match Kafka. It's not like mail software is written in Java or something ;-)