peatfreak

> Its creation must have upset a lot of people.

Indeed. About the only difference in essence between this and well written contemporary post mortems is that individuals are named. In other words, it's not a "blameless" post mortem; on the contrary, the knives come out and people are savaged by name.

I agree. I find the writing in this article to be unclear and it's making me very confused.

Why and how are Bloomberg articles constantly getting to the top of Hacker News? Was there every any resolution to their murky article about their claim that Supermicro mainboards were apparently getting compromised on the production line?

> To me, "maximum data for the hell of it" isn't about generating insight by looking at trends, it's about generating insight during incident analysis.

Agree 100%.

"Don't do it because it's hard! And you should listen to us because we have the meta-knowledge and experience (now) to know everything there is to know about this topic, plus the bravery to admit in public that we are only human and we make mistakes."

Isn't this the mantra of all of these types of articles?

OK, yes, it usually makes sense. Especially in the case where you are like these guys and experienced enough in some relevant area to know just how difficult it can be. These are perfectly good reasons from technical, business, and project planning perspectives.

Isn't there a TLDR where they mentioned when it does make sense to build your own TSBD? Presumably in some case where you have a team of serious, high-grade experts who know exactly what they are doing; have requirements that cannot be met by any of the other offerings out there; and where the whole thing has been specced out and deemed reasonable?

Exactly!! If a meeting time is unsuitable I just tell the other person and they almost always agree to move it. Even most manager types (resonable ones anyway) don't schedule non-critical meetings for 9am the next morning.

Yeah..... I'm not buying into this 100%...... it sounds like typical corporate BS that he is complaining about, and it was his choice to work instead of being with his family during a serious time of ill health.

Like others have mentioned, I get the impression there are many sides to this this story, just like any other story. And yes, it does come across as extremely whiny. And also somewhat naive.

Yaaaawwwwwwn.... I'm not exactly sitting on the edge of my seat for part II.

I wonder whether these types of microphones are suitable for field recording.

> Noobs are tolerated

Sounds enticing!

I just read one chapter, which I thought was OK. It felt more like a book on how the C programming language translates to operating system concepts, rather than a book about the operating system concepts themselves. For example, the chapter I read discusses malloc() and indicates that it allocates memory from the heap, but it doesn't mention sbrk().

> Most {net,dev,sec}ops engineers aren't writing blogs.

Unfortunately, in my experience this is true. It's not for lack of motivation or desire, it's because my day job is stressful and tiring. The last thing I want to do when I come home in the evening is to spend my valuable personal time writing a blog about what I did at work. I would rather spend time with my family, or do something like that.

Of course, I could try to schedule time during work hours to write a blog on the company website by talking with my manager about it. Unless this advances any strategic or political agenda, it's unlikely to happen.

> 2) The blog being in a public Git repository is nice for transparency.

The expectation that all your code is on a public repository (I blame GitHub for this) is one of the most horrifying developments in software engineering.

Yes, I enjoy it too. I did spend a lot of time doing this when I was a student and during my bachelor years.

> Emacs/lisp users always make posts like: "look at this great [thing] to completely simplify [thing]" while simultaneously posting 82 steps to get it all working and automated :)

LOL. As a dyed-in-the-wool Emacs user for 20 years, I have to admit that this is true. On the other hand, it makes me happy that the flagship software project of Free software is still alive and kicking. Moreover, people have been making these comments about Emacs ever since the early 1980's.

These days, my .emacs is very minimal and on any new machine my standard setup can be manually recreated in five minutes, mostly using Customize.

There is no need for any complicated thing that has to be automatically downloaded and updated in-place from a source control management repository. This is especially important when, for example, you are working in a heavily fortified corporate network, where access to the outside Internet needs to go through strange proxies if it is allowed at all. And in these cases it's usually a stressful environment to begin with, so when your boss -- who doesn't know anything about programming and just wants to see results quickly, dammit -- asks you what you've been doing all day, you don't want to have to explain that you spent all your time figuring out how to get Emacs to work over the corporate proxy.

While we're on the topic of Samsung EVO and Pro SSDs, does anybody know if there's an 870 series of Samsung SATA SSDs coming soon?

It gets a lot harder to have this attitude when you have a family to support. But meh to that.

> They are in the right space at the right time

I should have made myself clearer by explaining what "space" I was referring to. I wasn't referring to any sort of educational space, I was strictly referring to the abundance of co-working spaces these days, especially "cool" ones. WeWork is the archetype of the cool (and expensive) co-working space.

The area I live in has an abundance of these types of workspaces. It's almost comical. One of the newest (it hasn't completed construction yet) is advertising a creche. I thank my lucky stars that I'm in a privileged enough position that I (currently) earn enough that my partner can stay home and be the primary carer of our daughter whilst I go and work in my studio/workshop in an unfashionable (but surely up-and-coming) part of our city.

Cool, thanks. Now at least I have a way to refer to this phenomenon that I know very well.

I've never heard of this term, and I wonder whether it means what I think it means...?

They are in the right space at the right time, they have the right image, and they are probably backed up by a hefty amount of good luck (and investment money) to boot. There are a million and one co-working spaces, I've spent a huge proportion of my professional life at one co-working space or another, in some form or another, certainly ever since they became a "thing", and my rule of thumb that has come out of all of this is that the fancier and more salubrious (and expensive) one is, the less likely one is to produce authentic or meaningful work (obviously according to my own personal definition of meaningful and assuming that authenticity is important to the worker).

Thank you for posting this. This is a topic that I've long been fascinated by but never knew anything about. I'm way in the older end of the bell curve of age distribution of Hacker News readers, so I've personally experienced how pornography has evolved over the past thirty (or so) years, i.e., ever since I became curious about sex and turned on by naked women. And without a doubt the "hardness" and easy availability of pornography today is in a completely different universe to the sort of pornography I was consuming when I was thirteen years old. There's no escaping the fact that pornography must do _something_ to children's and teenagers' minds, in terms of expectations about sex, their own self-esteem, or whatever, and I've often wondered what these effects are.

Moreover, and moving on, now that I'm a new father with a two-year old daughter, I cannot even _look_ at pornography without feeling queasy. The full nastiness of the activities, production, what obviously goes on behind the scenes, etc, hits you in the guts and is truly sickening.

"At CoreOS, our aim is to arm these companies with the tools to build their cloud services – and run our digital lives – correctly. We’re also dedicated to making it so easy to run these highly complex systems that they take care of themselves. What if they’ll never miss an update again. They’ll have all the security features turned on by default and new versions of applications will ship quickly and safely." What a load of absolute dreck this article is.

This is so depressing.

Awesome! Thanks.

Can anybody recommend good books (other than the SRE Book), blogs, mailing lists, IRC channels, articles, videos, etc, that have SRE as the focus and go into it deeply?

For example, I'm looking for forums where you can engage in serious discussion about the role, or other books/blogs/articles that aren't simply regurgitating what the SRE Book says.

> I always get the feeling that most man pages are written for people who already know how to use the commands, rather than people new to them.

This is actually true. In some of the early Unix documentation or an interview (I can't remember which), one of the core Unix developers said pretty much this, i.e., that man pages were more like a collection of rough notes to help the developers of the Unix system itself not to forget how the commands should be invoked.

As usual, NYT is ON IT. https://twitter.com/NYTOnIt

Why would you expect it to be easy?

> That said, I haven't found anything worth leaving Emacs for.

Exactly. Every so often I try to make a half-hearted effort to move to a more moderen editor, or even an IDE, but for all its flaws even nothing comes close to Emacs. Vim is pretty good, but tries to do too many things it's not supposed to; for vi-style editors I prefer Nvi.

Emacs 19 was a model of low-defect, stable software, and my experiences reinforced that widespread notion. Over time and subsequent major releases, it grew and grew, and the complexity got too big to perform adequate QA, now nearing the point of unmaintainability. I also love it and use it daily, but I really wish the developers would show some restraint when considering whether to add new features (i.e., packages).

Having said that, the very core text editing engine, i.e., the part that's written in C and the basic Elisp editing functions around that are still rock solid as always, and for me this is still the ultimate model of what a text processing engine should be. It handles large files beautifully (and errors gracefully when it cannot), does file locking well, goes to great lengths to ensure the integrity of your file, all of that basic core stuff is just superb and well thought out, by a lot of brilliant people over a long time, and that's all very well optimized. I think the problem is that too many third-party extensions are included with the core release.