tdewitt

And I forgot the newlines in the bullet points! :headdesk:

Redpanda

We have lot of open roles in engineering. We're fully remoo. We have people in 17 countries right now. I'm personally hiring SRE in APAC (we need coverage in those timezones) and Infosec.

Check us out: https://redpanda.com

Jobs page: https://redpanda.com/careers/

Agreed for two out of three but I've never used Photoshop. I think it's worse for confluence. There are viable alternatives to jira but I've found nothing even "good enough" to replace confluence and it sets a very low bar.

Because I'm selfish, diving was one of my first thoughts. "I use this all the time!" Context only counts for a time. My wife reminded men of one of her favorite childhood books that has "queer" in the title. It wasn't a slur, it was a synonym for "odd." Then came the 90s and later and "queer" was mostly used as a slur. Then to LGBTQ community took it as their own. It's nearly off limits for the rst of us because saying "how queer" has to be followed by "I mean odd, not a mean way to reference homosexuals." (Is that even the right way to reference people now? I can't track all the variants of binary/sis/etc.)

I think it summarizes the problem of 4chan. It doesn't say anywhere that the media tool the bait and the ADL has an old blog post making it clear that, at the time, it was a hoax. Now the ADL has reclassified it as an actual symbol of hate by alt-right groups and white supremacists.

I think the article paints a picture of the rise of hate groups and the appropriation of a commomly used and innocuous hand gesture. Hell, as a diver, I now have to think about the fact that some Bad Actors have taken what I use to indicate that I'm fine and turned it into "I support genocide."

The barrier to entry for adoption is ridiculously high in the united States. Not only are you beholden to the ethics and morals of some agency but the hard cash necessary is significant ($10k+ in many cases). It's a badly broken system that is ripe for fixing.

Seth is a big deal in the Chef community, so it's important to understand that. In fact, he's a big deal in the devops community.

What he did was make a statement. He made it clear to the Chef _company_ that he can not,non good conscience, contribute code to organizations that he feels are working with extremely bad actors. This is his way of protesting. Chef is able to (and in fact already has) ignored him and restored a copy of his code and formed it under a new name. (Citation needed but I believe that was a statement from Seth I'm Twitter.)

To everyone snubbing Seth for doing this, let's go "Nazi" with it. If Chef did a deal with the Aryan Nation and FOSS contributors pulled their core and support, would people feel the same? Probably not, right? Well, to many, what ICE is doing is _literally_ along the lines of what the Nazi party did. (I'm not asking that anyone agree with that sentiment, just that they acknowledge that it exists.)

So, Seth exercised his right to free speech and right to protest by publicly pulling support for an organization that he has helped significantly. This is a loss for the Chef org and the Chef community. It has also been quite effective because this isn't the first place where I've seen this conversation and it won't be the last, in the next few days.

You don't have to replace the full toilet. There are plenty of options that fit on an existing toilet. You can get simple ones that are just spray all the way up to seat replacements with deodorizers and warm water (they require an outlet). It's easier than replacing your floor and not horribly expensive. Your butt and the environment will thank you.

My phone is a Walmart special $30/no but my wife, on Fi, spends the max (~$90). She streams music for our kid, while driving. Dropping her to $70/mo is a win for me. Obviously everyone is different but I just wanted to point out the per person cap in a normal plan can be higher than the unlimited. I converted her over yesterday.

I'm in the same boat. That phone looks physically perfect for my needs but I don't use WhatsApp, Facebook or most of the Google ecosystem (the exceptions being gmail and calendar for work). I would pay more than what they're asking to have a build without all of that.

I'll clarify:

The batch of phones going out in 19 days is not a finished product. It's expected to be loose fitting, not have endcaps on the switches, not have properly functioning power management and updates have to be done using a terminal. That's beta hardware, at best.

The next few iterations are improvements on the beta hardware but still not yet a finished product until Evergreen. That speculatively Q2 2020 but they've been off by miles with all the previous delivery dates so I won't hold my breath. Until that hardware comes out, which is what a consumer grade product should be, the only hardware delivered will be various levels of beta/release candidate.

By then, you might as well wait a few months for the hardware refresh. I appreciate the goal and the work done and if the hardware was polished and all the pain points were software, I'd be singing a different tune. Software can be fixed after the fact but poor fit and finish on hardware is forever. (And I've been Linux-as-a-desktop since the latter half of the 90s, so I can take a lot of pain. I'm all in on a Linux phone but I'll go buy a dumb phone while I wait for v2.)

Well, I'm out. This is disappointing and is starting to have a pretty bad vapor smell. I shelled out the change for a presale but thevpruce difference isn't worth it for unfinished hardware. I'll check back in for v2 but for now I'm thinking a dumb phone will be the way to go. I with them all the best and appreciate the announcement but with all the delays and now a timeline showing just how far from a finished product they are, my confidence is low.

Yes but not for google apps, slack and a browser full of bloat. I have all this RAM for the actual engineering I do.

You shouldn't _have_ to care but the reality is, if you use your systems and chrome eats 4GB+, then you do care. Chrome regularly consumes a major percentage of my available RAM and I have 32GB.

Try Firefox Preview. It's not feature rich but I've been very happy with it. It is simple and fast.

It's needed as an argument to justify additional scope creep.

Does single window screen sharing work yet?

Perhaps it's just me but I haven't found an xorg problem in my life that's fixed in wayland but I've had a few problems in wayland that don't exist in xorg. My display needs are rudimentary though, so perhaps I'm not the target audience.

Putting wayland aside... is exactly what I've done. I don't need wayland, so I don't use it. With systemd, not only do many of us have problems but we don't really have a choice. I could run my world on Slackware but then I'd be a SPOF (much like systemd) and that's a bad way to build architecture.

Wayland is nearly vaporware, gnome 3 is optional, kde plasma is optional, nvidia drivers are optional and have functional FOSS replacements, pulse I'll grant you (and hope you see the irony) and dbus I can't honestly comment on because the little direct interaction I've had with it was fine but mostly I don't think about it. The flaw with your list is that half of it is optional and anyone who doesn't like those things doesn't have to use them. My daily driver is xfce on xorg.

Two of the three components in your list that are mearly mandatory came from the same engineer. Why we do we keep accepting his code?

FWIW, the desktop world is less important and I run Linux as a desktop. The nightmares I get from systemd are all about my servers. If we could have left servers alone, people like me wouldn't even have cared. As it is, I have to get out the kid gloves when I'm dealing with my service platform because Bad Decisions are now system standard.

The fact that we're still having _this_ conversation, after after a decade since being released and years after mass adoption, should say a lot. I can't think of any other software I have to use on a daily basis that gets so much heat, every time it comes up. One can make all the arguments for it they want but the continued public comtempt means something.

Came here to say this. Potentially interested but I've lost all interest because I can't zoom the page to actually look at the screenshot. I consider this bad behavior and I don't reward bad behavior.

Atlassian has a major flaw in their understanding of how a lot of developers work and it is evident by all heir "new" versions of stuff. They've made simple editing harder (WYSIWYG only, which often makes bad assumptions), made drastic changes to the UI, broken workflows, removed keyboard shortcuts and made it impossible to open an issue full page by clicking a linkbun the web app without first loadingbit as an overlay. They are, hands down, the worst offender of "if it ain't broke, fix it 'til it is" that I've ever seen. I'm constantly advocating for anything else in every org I work with. An issue tracker doesn't need to be full of sugar, it needs to be simple and consistent. Atlassian fails magnificently at both of those.

> I personally have been focused on making positive changes with 15 solid minutes of effort. Because that's all I'm going to have before I'm interrupted. It's annoying and I would much prefer a quieter work environment, but that's clearly not what the org wants.

Doesn't that just feel terrible? I bought noise cancelling headphones because of the open office concept. When that wasn't sufficient, I moved and am now remote. When Slack came in, I used the IRC bridge and setup ignore rules for all the botspam. Now that's gone and I found a web plugin that would do it. Slack changed their code and that no longer works. Every effort seems to be going toward a more disruptive world. 15 minute chunks are no sufficient to do quality work, in my opinion.

We shouldn't spend our days screwing around and our nights on work. If I have to work nights to be productive, I shouldn't have to show up during the day. Even if I didn't have a kid, I'd have a personal life.

Agreed. We used to think similar things about email, Slack has just amplified the problem. One place that I do think Slack is to blame is not providing a way to filter noise. Because they seem to think that Slack communications are business oriented, they've done little to allow an individual to add ignore rules, like one could do with an IRC client. The reality is that even most professional Slack services I've used collect significant noise (I just joined a Slack and was added to more than a dozen channel, each seeming to have their own bots) after just a short amount of time. (Try and find one without a gif bot.)

Synchronous chat is spam and we need to be better about understanding the productivity hit that cokes with always-on comms where we expect instant response.

It was a "good enough" practice until better options came along. It's never been a "good" practice. Take a look at lists of breached passwords and you'll see an overwhelming number of passwords that involve replacing vowels with numbers in common words. Humans are bad at picking complex passwords because they're not easy to remember. We had to adjust the rules over time to deal with that: minimum complexity rules, require a capital letter, require a number, require a "special" (but not too special because we still don't do proper sanitization), no repeating the same password until you've rotated N times, no repeating the same password until you've rotated N times AND there's a minimum age. Those rules all camebinto play because people can't be relied on to be smart about passwords.

Password expirations are insufficient and it has always been a game of cat-and-mouse with people who hate them. Good security is something people willingly use or don't know they're using, so they don't try and work around it.

So if you can't solve for everything, you can't solve for anything? Gun massacres, in this country are on the rise. What else is and at what rate? You're arguing assumptions when we have facts and we can try to do something about facts.

You're right, we can't restart this service. These people are dead. They were shot. To death. We can never solve their problem but if we don't learn from it and try _something_ then we can't avoid the same thing from happening again. And again. And again. And again. (Repeat a few hundred times.)

But don't let me stop you. Solve for allthethings and let us know when you're done. In the meantime, a bunch of us are going to fight to solve for this current problem.

I think you misunderstand the things I'm saying are talking points. The sad white boy having no place in the world and sexual rejection being a new and uniue problem that justifies disproportionate response, is what I'm talking about. That's the alt-right bogeyman. That's the fuel for a lot of this fire.

So then let's go back to stuffing our heads in the sand and doing nothing instead.

Show a link between games and hate crime fueled mass shooting by sad white boys and we can put it on the list of things to worry about. Until then, perhaps making it harder to get guns could help...

That's not how a post mortem works. You want to identify the root cause of an incident and any factors that increased the impact or prolong the incident. Solving for every possible scenario is how you end up solving for nothing. Playing the "what if?" game leads to an infinite set of potential problems and time, being finite, means you can never succeed

When we've solved for the current problem, we can address the next worst thing. We won't know what that is until it happens.

We could also solve for knife and sword attacks because there was that one time in Japan where someone murdered a bunch of kids or chainsaws because of that other one time that guy had a chainsaw but we do more by staying focused.