So, either they don't care that they broke those workflows when they made this change, or they didn't know that the workflow breakage would be bad. Both are shitty and implies a lack of understanding of their core user base. So, sending customer reps out like they are now screams to me that gitlab really only cares about presentation.

At least to me, it feels hollow, just like your response right now. It makes me think that Gitlab knew that there was going to be a backlash, and only sent your team out to mitigate damages. "There is no such thing as bad publicity" sort of deal.

If Amazon did the same thing you were doing right now, everyone would be up in arms.

That said.

The method of encoding production database credentials was rot-13. No joke. In the Quartz interface, you could double click on a starred-out set of credentials, and it would run rot-13 on it and display the password. This was for FX, rates, credit card, mortgage, etc etc etc. Having access to this cloud system gave effective access into all of Bank of America and Merrill Lynch.

They probably save a lot of their money by using very, very bad practices.

Still only the second worst security fail I've seen.

Comments URL: https://news.ycombinator.com/item?id=21291935

Points: 5

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=21227288

Points: 2

# Comments: 0

Fun fact: Chicago's city hall has a retention period of zero days on its cameras. Go figure.

So, imagine you have a massive celestial body floating out in space, with a large gravitational field. Its gravitational field is always propagating. Now, take that celestial body, and make it completely and instantaneously disappear. There's now a gravitational differential between the now-gone body, and its previously propagated gravity field. You should be able to detect that if you're close, say through tidal differences.

Very similar happens with black holes colliding, except the gravity differential comes from the two black holes oscillating near each other, close to the speed of light.

Edit: this obviously isn't exactly how this works, since it makes a lot of assumptions, such as the ability to instantaneously remove something. So, don't think of this as how "things actually work", but as a model to help build your intuition.

I'm trying to get out of for-profit tech and into the non-profit space to do data/FOIA/investigative work. It's still "tech work" at the end of the day, but without the deep dread of making rich dudes richer.

I'm tired of being on call 24/7/365.

I'm tired of having to explain why plaintext passwords are bad.

I'm tired of being taken advantage of for being a generalist.

I'm tired of ex-google asshole bosses with massive egos.

I'm tired of carrying a laptop with me "just in case".

I'm tired of the constantly shifting "popular" technologies.

I'm tired of spending weekends indoors studying for work, instead of work giving time to learn.

I'm tired of pretending to find conferences on monitoring systems exciting.

I'm tired of my coworkers and bosses being high at work.

I'm tired of JIRA.

I'm tired of consultants telling us how we're using JIRA wrong.

I'm tired of the politics behind technical decisions.

I'm tired of having to learn another DSL.

It all feels unreal. Can't wait to get out of this field.