I don't think this is true, or is a reflection of being in tech (assumption on my part about you, correct me if wrong).
Anecdotally, my peers (26ish, so gen z), none of them use AI except me, and that's for work as a SWE. My 68 year old step-dad uses it, but I suspect that's out of boredom more than anything.
I know students are using it for tons to essentially cheat, but I don't know anyone in that cohort using it for personal use of any kind.
I interpreted it as meaning that optimism is an assumption that problems will go away so there’s no need to painfully face them, whereas pessimism is an assumption that things will get worse unless you actively search out problems and fix them.
ah yeah, I mean if that's the case, I think that's orthogonal, right?
In my interpretation of the words, I tend to think of optimism as being the brave thing because having hope is more difficult, and IME, you can only muster energy to solve a problem if hope exists. Conversely, pessimism to me feels cheap and easy, and if you say "everything's fucked, what's the point" then nothing gets solved
So, it's probably more of a quadrant/compass along the axes of optimism/pessimism and proactive/passive
I am consistently surprised that I'm unique for enjoying, and if I may be so bold, being pretty good at, both Ops and appdev. Now I'm not the greatest in the world, but I really do firmly believe now that most generalists should strive to be able to do both at a journeyman level.
To my understanding, this _is_ DevOps in the original sense of the word, and the version where they are a separate team is an offshoot bastardization.
At my last job, it was somewhere in-between where we had DevOps specialists who were regular software engineers who allocated the bulk of their time to building / running infra via Real Code (Pulumi vs. TF, minimal YAML wrangling etc) and built paths for app devs to self-service as much as they could. That, I felt, was a really excellent setup.
> loaded into the working model — the original file is untouched and will stay that way
Commentary text like this, once described here on HN as essentially the chat context leaking into the application, is absolute anathema to me. Something about it makes me irrationally annoyed and immediately not want to use the software.
I think, to me, it signals the pinnacle of vibe-coding in the sense that I can't imagine that the output was looked at closely and the copy still remained. When my own agents try to write stuff like that, I remove it immediately.
I wonder if this is caused by so much of the training data is the web, where millions of articles were written to hit some word count. It's just following what it was trained on.
It’s very annoying. Claude specifically will tend to treat minor clarifying details in a prompt as major features.
I’ve also noticed it likes to spam a UI with explanatory text for every control. Almost like it wants to do tooltips, but doesn’t understand the exact UI for them.
> Its not a labor shortage, its a shortage of people for whom doing the job can pay the bills they need paid.
I think this fact is often missed by middle/upper-middle-class tech folks (like a majority of this forum). From up here, it's eas to view labor as being an equitable exchange between two parties, but as you said, that is simply not the case when the pay doesn't even come close to covering expenses.
The refrain I often hear is that those people should then just work harder and get a better job - but then the question is, who delivers the food? To which I have yet to hear a satisfying answer (besides incentivizing better wages for those workers)
> The refrain I often hear is that those people should then just work harder and get a better job
These are folks who've never had to work a low wage job where bathroom breaks are tightly controlled, except maybe for fun money. I started working at 14, and as a software dev today I've never had to work nearly as hard, or be as utterly exhausted as working these sorts of jobs, which if you are having to do them to pay rent, its difficult or impossible to do extracurriculars like education or networking to move forward.
Imagine your entire workday is on a strict, short term set of timers and if you don't complete a task for any reason an automated rating goes down, and if it happens more than 3 times you are let go. People don't understand the level of stress that carries.
I drove Uber Eats for one day a few years ago (as an experiment) and it was way harder than I had imagined. Seemingly no buildings have numbers on them, and it took tremendous effort to find which door to knock on in most apartment complexes, and the tips were lousy and the pay was horrible.
I don't think this is true, or is a reflection of being in tech (assumption on my part about you, correct me if wrong).
Anecdotally, my peers (26ish, so gen z), none of them use AI except me, and that's for work as a SWE. My 68 year old step-dad uses it, but I suspect that's out of boredom more than anything.
I know students are using it for tons to essentially cheat, but I don't know anyone in that cohort using it for personal use of any kind.
reply