sqldba

Ditto!!!

I’ve deep dived, investigated, and fixed tonnes of hard problems.

But my memory doesn’t have an index on them. I can’t think of any on the spot and sort them hardest to easiest.

I can think of achievements (and they end up on the resume of course) but those aren’t necessarily debugging a hardest bug, which is a point in time versus months/years of invested effort.

This is CRAZY.

How the fuck do you explain this level of trolling to your parents! That this is why they shouldn’t repeat neo-Nazi Facebook garbage.

You’re being downvoted but it’s a totally reasonable reply for normal vendor software.

Is Ada still around?

Wow the responses in that thread are toxic as hell.

What’s weird is that they don’t address those issues and improve or replace it.

There’s nothing in the easy database/UI space at the moment and it has gone unfilled for a long time.

Isn’t the whole point of dotnet that it ships with all the executables, libraries and binaries too?

I don’t know how I feel about it myself.

Wow what a reliable source blaming checks notes spending on green energy for a company choosing to not maintain its completely unrelated equipment and leading to these failures.

I wonder why the vertical lines have breaks in them. It didn’t used to be like that in the old days.

The article is not a complete overview of the situation. For that we go to Wiki.

"Boeing considered MCAS part of the flight control system, and elected to not describe it in the flight manual or in training materials."

It... "could not be overridden by pilot resistance against the control wheel as on previous versions of the 737."

"Following the Lion Air accident, Boeing issued an Operations Manual Bulletin (OMB)[13] which outlined the many indications and effects resulting from erroneous AOA data and provided instructions to turn off the motorized trim system for the remainder of the flight, and trim manually instead. Until Boeing supplemented the manuals[14] and training, pilots were unaware of the existence of MCAS due to its omission from the crew manual and no coverage in training.[12]"

It wasn't just "a software bug". It wasn't just culture cutting corners. Even after the first crash they continued to cover up that MCAS was the cause. After the second crash they still refused and it wasn't until airlines started grounding planes that they caved in.

There's a lot more than regulatory oversight could have done. We haven't reached the limits in the slightest.

> Statewide utilities are bloated and inefficient, and they abuse their monopoly power.

This seems overly general. There's plenty of state-wide utilities in the rest the world which are fantastic in every regard including cost.

Shouldn’t the CTO fire the person who was directly responsible for firing Monica? Why isn’t that part of it?

In Australia you pay the marginal tax rate which is nearly 50%, both on acquiring the shares, and (usually) any gains between then and when you sell them.

The article is real poorly written, I can't work out what it's saying the US or EU equivalents are.

I don't think it's going to become viral but I'd wager to say it could be useful for some. I want to track my emotions, too, to see if there's any patterns.

I don’t think it’s normal.

At a previous company I was on call every second week and would receive a call maybe once every few months. That was with many hundreds of servers.

At another company I’m on once a week per month and get called once or twice. That’s with just a few hundred servers.

In the first case all time was reimbursed in lieu. In the second case my salary more than makes up for any inconvenience.

However in both cases I was very proactive in defining what is on call - critical production issues only. If it’s not critical or not production then I won’t log on to look at it.

And in both cases I had a LOT of false alarms from bad alerts when starting. I had all false alarms disabled.

You’ll get push back but I didn’t care - you can’t have an alarm waking up people every night on the off chance that one in a hundred will actually be an error. And hilariously, if you started including your boss on the call, they’d quickly agree it’s not acceptable. The human cost isn’t worth it.

While there’s often tonnes of room for improvements to monitoring and alerting (root cause analysis etc) that others have mentioned - in my experience most of the metrics and alarms are garbage anyway, and can and should be done away with. If it came from a boxed product it should near all be turned off from the get go. That crap is always pointless.

Oh no a server CPU usage has increased and memory is low because - it’s doing what it’s meant to? What junk.

I also have to disagree. There’s a difference between working with others to achieve a certain familiarity with the science and industry to sustain it, and riding on the coat tails of other countries who can provide all of that for you but may pull it at any time such as for trade war purposes.

I know how they feel. I often replace code and feel like it's attacking the author; and also feel like my own code is being attacked when it's replaced.

I wonder what happens when Apple distribute the update and it detects this is on your phone. Do they even notify you?

I do OpsDev too and I’m a fan of the term!

I’m an ops engineer but develop the code to do my team’s operations tasks.

The idea that some brogrammers can come along and bang out a disruptor in this area - which has a few decades of extremely complex learning, patents, and optimisation - just because they can cobble together some ML...

It'd be sad if it wasn't so naive.

It's not those customers they care about. It's the additional million people who will see the news and scour the deals next year hoping for the same.

Couldn't read because of the paywall, then also couldn't read in private mode (because it detected it - fun). To be fair I don't even want to read it, I just want to see the picture.

Ummm. Before iPhone it was common for phones and laptops and PCs to disappear off in repair through third party warranty vendors for weeks and months.

You don’t know how good you have it.

My serial doesn’t come up as affected. I mean that’s great and all but now I’ll be staring at it in suspicion for a good while.

What's wrong with crunchyroll? I thought they were legitimate?

Scripts.

And I hate to tell you but despite what you’ll read on HN every single company I’ve seen and every single vendor I’ve dealt with - is using scripts.

Just simple scripts, in source control, amended by hand, lord hopes applied as part of a CI system, often without any kind of version numbering (so once it’s in the database you don’t know where it came from) and with no rollback.

Declarative migrations do exist. If it’s in .NET then it’s invisible to me, but I imagine it’s pretty rare. Using SSDT (Microsoft) for tooling is possible but has so many edge cases and is poorly documented so coming up with an architecture requires the kind of expert where there may literally only be a dozen in the world, so it isn’t done outside of demos that fail and get thrown out the second you’d ever try to implement them.

As you can see from 300+ comments at the time of writing, the post is entirely unclear about what's happening seeing as everyone still argues about it.

My read of it is that .NET Core becomes the new .NET, not that .NET Core has parity with the existing .NET.

Specifically I can't just retarget my existing projects against .NET Core (or the new .NET) and have them just work.

I didn't know Java had so much mindshare for ETL. Can you explain further?

Is Java separate to Java EE? Does this news have any impact on Java in general?

The article doesn’t seem to point out that this only happens to some people.

I don’t have this issue. But yeah there should be refund policies in place for people who are affected.