I feel the pain having had to build a browser based pdf editor with features not found anywhere else. React was hammered into working and turned out pretty good. But my god, it was quite a journey. As with all enterprise projects, this one was shelved because business changed their minds. Two years of figuring it out just wasted …

Hiring a fairly competent editor is affordable (sometimes even cheap). Specially now that a lot of the commercial copywriting has taken a hit with the ai slop

Its like acting. Some people can do it without acting coaches. But it’s best if you invest in them.

It’s like saying that in a post-Viagra world there shouldn’t be men who have trouble getting laid.

Don't want to get too deep into your analogy. I was addressing the "DevOps cannot code" part. To me it is a leadership failure if a DevOps team is still afraid of tackling bigger challenges (like the example given by the OP). That, of course, depends on whether DevOps teams will exist in the long run.

The very fact that we are talking about "DevOps" teams (that do not include dev) is wrong from the very start.

DevOps is a methodology, not a role.

I've always felt that DevOps became a function/team partly because companies and especially SWE's started complaining that they were spending too much time "doing Ops work" and product/business started demanding more features for which they running out of cycles. And add to that the burnout from being on-call (especially if the dev team is relatively small and you have to go on-call every 2-3 weekends).

When I still did on call ops, devs got notified before us if their apps were the problem. We got notified first if it was our infra

Having an ops team does not mean devs get to through on call team over the wall to someone else. That's a sure recipe for resentment and turnover

For most HR departments it is a role, it even has a career path.

> the "DevOps cannot code" part. To me it is a leadership failure

Have you done devops yourself? It sounds like a resounding No. Like you complained ops doesn't like to code (not a core skill for the job), ops complains that devs can't understand basic concepts of how their software runs. Is this also a failure of leadership? Is everyone supposed to know parts of everyone else's jobs?

The UI is hard on the eyes. I tried using it but felt overwhelmed by the design. Feels like I’m working with an IRS form.

Thanks, I adjusted the brightness after your comment.

As for the design, it's a matter of taste; mine might be different from yours.

Agree. The colors need to be pulled back from the 100% saturation, and the body font size is too small.

Maybe add a skin around the sphere to make it look like the earth. Then the targets become places.

The real benefit is due to discipline. These models have removed a certain amount of friction you had. However, you’re now more of an editor than a writer. Keep that in mind and don’t lose the writing muscle.

Sounds like LLM powered support. This is the sort of run around you can program into such systems.

I am also betting on this. Google used their dumb bots in support since time immemorial, but now these dumb bots are supercharged by LLMs. Except they are still as dumb as before.

I still remember trying to get my Google Play account unbanned in 2014 after I clicked on my own ad in the app once to test that it’s working. Lovely times. Got the account back, but not due to my actions - their dumb bots masquerading as humans were giving me the runaround, and then I just randomly got my account back.

No, LLM vendors are not HIPAA covered entities. If users choose to enter their own healthcare data then that's on them and there is no legal protection.

https://www.hhs.gov/hipaa/for-professionals/covered-entities...

No. I could choose to post my personal medical information in the town square, that doesn't make the town square a HIPPA entity.

Friendly suggestion to read (and study) The Ultimate Sales Letter by Dan Kennedy. In addition to anything else you do. Guy is a prick. But, he’s a prick who has made me $$$.