Let’s put a story point estimation on that. Then we can extrapolate time range and risk.

How’s it going so far?

The solution to this problem. . .

is that they have to create a support ticket with you, that you then put in progress, and you walk them through your documentation, and then log your time spent onto that ticket. (/s)

There’s an alternative to creating too many tickets that only add overhead and then make it harder to get into the project. Creating a good amount of tickets.

I took the OP reference as demand for ticket creation when they don’t make sense and only hinder development through unnecessary overhead. E.g. creating a ticket before a quick analysis, or creating individual tickets when one story/feature ticket would be enough. Or more specifically in this case, having to create one before fixing a critical blocker.

EoD? End of December? End of Death? (reference to world going to end)

That’s a lot of dollars, ching ching ching

got it; arse

It would certainly be an issue if you didn’t have one

The problem was named after an incident in 1996 in which AOL’s profanity filter prevented residents of the town of Scunthorpe, North Lincolnshire, England, from creating accounts with AOL, because the town’s name contains the substring “cunt”.

haha

those are terms, this is substrings within words

I haven’t seen branches or variables being called arse

Then again, I do like to catch exceptions as up so I can throw up

Simple changes require only simple reviews.

Responsibility is shared. It’s not one or the other.

Many people don’t know what they’re doing. That’s kind of expected. But a tool provider and seller should know what they’re doing. Enabling people to behave in a negative way should be questioned. Maybe it’s a consequence of enablement, or maybe it’s bad design or marketing. Where criticism is certainly warranted.

Commit with Co-authored-by: Copilot

or maybe better --author=Copilot

It would certainly help evaluate submissions to have that context

oh, that’s a cool website

adds it to bookmarks and search bookmarks

But did it reach test or production environment yet? Or will it die in development environment.

Even C# has something that few people use, but it has something.

Huh? Are you claiming few people use NuGet?

Formatted, so I can read it

Exception in thread "main" java.lang.NullPointerException: 
 Cannot invoke "String.toLowerCase()" because the return value of 
"com.baeldung.java14.npe.HelpfulNullPointerException$PersonalDetails.getEmailAddress()" is null
 at com.baeldung.java14.npe.HelpfulNullPointerException.main(HelpfulNullPointerException.java:10)

I think using display: grid; as your default is the better default, so you’re all set. :)

It baffles me when people use flex layout when it’s clearly visually a grid layout. Nothing here is flexing with varying element sizes and auto-fill-wrap-break of items.

A colleague of mine prefers flex too. But to me, grid is so much more intuitive and simple.

https://css-tricks.com/quick-whats-the-difference-between-flexbox-and-grid/

For me that’s the wrong way around.

I want to be able to fix the issues I see. I hate it when I can’t.

I’m thankful I am full stack and can do my stuff across borders. I hate the interfaces, waiting for stuff, or being hindered by dissatisfactory (to me anyway) stuff from them. So I’m glad when I have control over the entire stack - from talking to the customer to running production.

Anything I don’t have control over - most if it doesn’t get done, the rest can be okay or bothersome.

I hate that I don’t see what the admin set up and does on the infrastructure. It makes it harder to assess issues and potential issues and how they could correlate with infrastructure changes and activities…