waynesonfire

> they require much more manual work

Yes, needing to RTFM is much more manual work. Better to deploy bugs.

yep, this was obvious from day one.

> People who have an ignored/avoided LLMs completely are not able to just pick them up today and be as productive as people who have been learning the best ways to use them over the last couple years.

How's it up there in that tower? Citation needed.

oookayy, suurre thing boss. Just make sure calculus is one of those "a lot of different options"

> You have to disclose use of AI.

This is no longer true.

I'm not sure how to phrase this question... so here are some thoughts I'm having.

Suppose you find a habitable planet, land there and start colonizing. Would we have to bring our bacteria / viruses with us to survive? Like, the idea that it would not be possible to get the flu again; but is therea trade-off? Would other bacteria eventually mutate sufficently to become infectious, and perhaps, would be even worse.

Our immune system would be tested. Assuming there is bacteria on the habital planet, it's not clear what would happen.

I guess the core of my question is: how homogenous is life?

> Artists value "originality"

Really? Who says?

it's only "difficult" because google, microsoft, etc have conivenced the community that self-hosting e-mail is not possible and for some reason, further propetuated by IT influencers that have drank that koolaid.

all complete bullshit; they arbitrraly occasionally block to protect their moat raping privacy. e-mail is the most rewarding self-hosting capability. like anything, there is a learning curve but at the end of the day: it's easy, stable, a pleasure to host. there are solutions that ease the learning curve. after a while, all the e-mail do make it through.

i'm so happy that my communications are not indexed by these hyperscalers.

stop listening to these pussies claiming how difficult it is. they're projecting their limitations.

Among a few things ive boticed one notable is devops has been less of a blocker / faster to address issues. Most of the time the asks are trivial but incompetent Devops couldn't figure it out. Now they can ask ai and through their elevated permissions quickly solve the problem.

You, and this entire thread is missing the point. Nobody is wrong but, the point being missed is that "leaders" isn't one thing.. there are leaders at every height of the organizations hierarchy and even to the sides. As a basic example, do you mean the immediate manager? their manager? their manager? The CTO? Each operates at ever more abstract level of detail.

Won't work.

A man who carries a cat by the tail learns something he can learn in no other way - Mark Twain

What a silly observation.. of course they matter. This, among other things called experience, seperates senior engineers from bright young green minds. Good thing those same green minds have all this extra time to throw at the problem to catch up and appear senior.

It's a terrible idea to delegate swap, a capability that is expected to operate under severe memory pressure, to a subsystem that fails under such conditions.

don't miss that can't-miss appeal!

If only the LLM coding zealots were aware of this wisdom.

> the 662 MB used by the "Renderer" is shared between many Windows components

Fine, shutdown the weather and stock ticker apps.

that seems very risky. it doesn't take much effort for the interviewer to spot a trickster, forfieting the interview. There is also no telling the second problem would be easier. I'd rather take my chances and hope i solve it or try to limp through with a hint.

Cool story bro. I used a llm to help me name a variable.

I disagree. Sony can't bring back Walkmans because a Walkman won't generate the returns Sony demands. Furthermore, they refuse to open-source it so it stays hidden in a vault.

Plenty of people would lose money, break even, or God willing, make a tiny profit, diving into this problem. Regardless, it would make society a happier place.

Yes, you're describing a fundemental feature of DNS.

¯\_(ツ)_/¯

Not quite done right.

> because it is using the public ip instead of the private one.

For this edge case, the issue is not with DNS; it's that the router is not configured to allow internal clients to access the network through the public IP, vis-à-vis hairpin routing.

> - Run two haproxy instances,

This made me consider my haproxy architecture. I use haproxy acl rules and the use_backend directive to enforce security policy and routing. It denies http requests based on source ip address per service (host header)

I think a good middle-ground is to use a single haproxy but two frontends; one binds to the public interface and one for private. haproxy is now no longer responsible for routing, the router is.

because when crashing on a motorcycle, it's only the cyclists face that's turned inside out and in such a way that it's not a burden on society to treat a vegetable.

Why? Because if you need to serve ads that are being blacklisted by DNS, you need something like this.

why isn't your mental model to use DNS?

Why would you think this ai slop suddenly breaks that barrier?

one day we'll get the equivelent of language server for build systems.

very impressived with no LLM results. If I want LLM, I don't need to use a search engine to engange with it. That's a different product.

> My first and only layoff

Won't be your last.