nkapias

I forgot a superfluous free tier proof of concept pipeline and it ran every 6 hours for three months before I remembered to shut it off, sorry.

I expect to not be the only one, it certainly drives usage KPIs up and lead to this kind of decisions.

I usually asked my managers by framing it to their goals, if agreed they would schedule with other managers.

It's harder during crunch or when everyone is remote.

I've experienced that being knowledgeable of the inner workings is a risk of getting dragged into every projects.

When scheduling onboarding, I try to enable touring without those drawbacks.

What's difficult about artifacts ?

> They're also a sign that you are trying to concentrate to discourage those "just a quick word" moments which could easily be covered by an instant message.

This is the reason I wear headphones, I don't even switch them on.

It seems to be less broadly understood than before and my work is often disrupted.

Once, an applicant had a pipeline to correlate open positions to his resume and generate cover letters. He was open about it and shared a public repo, thus it was perceived positively.

Finally the job didn't correspond to his profile and objectives. I have not checked if he improved it later, I guess he did.

Thank you (and everyone else who replied). I wasn’t aware of this controversy.

I wouldn’t express an opinion on the subject, however, I’m glad when information is made public, as it allows everyone to weigh whether it should influence their decisions.

> And obviously you’ll want a VPN too (skip Mullvad) — Proton’s VPN works fine for that.

Why skip Mullvad ? I thought it has a great reputation.

To my understanding it depends mostly on the applicant age.

Watchmaking can take a heavy toll on eyesight, due to working with magnifying glasses on tiny parts during decades. Also each brand has unique processes and machinery, for which they have expensive learning courses.

Thus they would rarely consider applicants past their forties even if they have experience and favorable relations.

Noticed different results from friends, we have similar projects and tools.

We're guessing it comes from organizational behavior (culture, governance, management, etc.), we work in diverse teams / regions / companies.

First I've heard of generational ban was in a hundred years old novel from Jack London (maybe an autobiography ? can't remember the name). It certainly was about alcohol, maybe he mentioned tobacco as well, anyway the idea and debate certainly aren't new.

I find bewildering that such concepts are tried only centuries later, and wonder how it comes to be possible. Is it that we can finally enforce them, or that the lobbying have been gradually weakened, or enough data to drive decision, etc. ?

Noticed that in my absence, cats hang where I spend the most of my time when present. If for a few days I only come home to sleep I'll usually find them on my bed. If I work at my desk for a week, then the next days they'll be found on my chair. And so on.. A somewhat reliable habit indicator.

I like your 'llm-developped-app-friendly shared datastore' idea and would pursue it.

While taking ownership of AI slop is not an option for me, I do want to avoid shadow IT.

Might be a moon shot .. could sharing a prompt template with git access to colleagues be a way to enforce it ?

With change management they can be informed of platform / infra and be autonomous to upgrade their app. They usually are in the loop if they have ownership, or will be after it happens a few times.

Also I believe the value is in the output, not the app itself. ROI of a 1 hour AI slop should™ be attained before it rots and they can just spun up a new one.

I might be hopeful and a bit selfish here, I expect my colleagues to own their toolbox.