> If your users are less technical then I think it is irresponsible to allow them to make choices that would compromise security and the data of others.
Counterpoint: HN about the iPhone. FWIW, I agree with the statement above, but also suggest a developer account opening up developer flags is a reasonable gate.
(Not sure how else to avoid all the "developers" clamoring for non-public betas of iOS bricking their iPhones, as the same audience that would flip a bunch of dev toggles if available to everyone like developer mode in Safari then scream how Apple should have done more to protect them when their bank account is emptied.)
The Lovable class of tools is fascinating as the value prop is explicitly you do not need to be a developer, you do not need to know what you are doing. I think that makes the responsibility clear in a way the iPhone does not.
But not needing to know what you're doing as far as programming goes != not needing to know what you're doing as far as compliance/legal responsibility goes. Someone using a tool like this still needs to run their operation in a sane manner. Like, how much responsibility does Loveable shoulder here? We don't blame a car manufacturer for most car crashes. They, of course, try to design their cars to be as safe as possible, but the fact that they endeavor to make a safe car doesn't make it explicitly their fault if I'm driving blindfolded and careen off a cliff.
This is something that makes me roll my eyes... seeing people online talking about how everyone can just make their own version of w/e software now. As though running a software business is simply a matter making the computer screen light up in a particular way.
Thank you for writing this yourself, it's informative and refreshing!
If an LLM wrote it, then it's the best simulation of non-LLM writing I've seen on an agent related post. They seem all to have gone through an LLM "edit" (cough) that strips the personality seen in your update.
Engineering's stereotypically low empathy for those who may not connect dots as readily is no problem if teams would make a habit of these simple mechanical compensations.
In my view, the current "value" is driven by the current artificial scarcity of quality web search results.
For now with not all agents controlled by advertising engines, and not all content yet designed to honeypot them, today's agents make good headway bush-whacking their way to finding the right information on which to base task work for you.
If the first page of SERPs for anything, and the extra time needed to suss out quality information to inform your work or task doesn't bother you, then this benefit isn't one you'll value.
Put another way:
Today's agents help "cut through" the same maze of value extraction that Silicon Valley (where market share means find a way to tell users your thing is "free"), adtech, and the content-as-ad-scaffolding industry have built over the past three decades. Why waste time wading through all that when your time is better spent building more of it? :-)
Or, perhaps the person thinks (solves) in abstract concepts rather than linear words. Just because many people mouth words when reading or can't think without hearing words in their head or aloud, doesn't mean others should have to handicap their own efficacy of thought while working it out. Two conceptuals can communicate in a kind of ultra condensed shorthand liner verbal thinkers struggle to follow. Less can't communicate, more can't conceptualize squared off with can't verbalize.
Both groups should synthesize simply and clearly at the end, both should work to get in sync. And both ways of thinking have their uses in a team. Catch: conceptual thinkers can interview verbal thinkers, the other way around is more challenging.
I wonder if there is something to said about the importance of being able to clearly communicate at some higher level being even more important now than it has been in the past, given that developers are increasingly expected to work with LLMs
It's something I struggle a lot with (and I'm currently unemployed)
I mean, I think that's exactly the parent poster's point. It's not an absolute "can this person communicate efficiently on CommunicationBench 3.0-beta7". It's "would I, personally, do well sitting next to this person every day and communicating constantly with them, or would I struggle with that?" There's a very personal piece to this that is both a little arbitrary, but completely practical.
(Caveat: I've always been interviewing for members of a small team who I might very literally be sitting next to every day and communicating constantly with. BigCo interviewing is different.)
Sometimes I think in terms of relationships between objects. I walk around slowly, up and down a hallway, and the "objects" are just vague shapes hovering around the hallway. If I'm thinking that way, it's going to be hard to explain my "chain of reasoning" while I'm in that mode.
Once I have figured out the relationships, though, I can talk about it in words. "Why didn't you do it this way?" "That felt really clunky. This way seemed cleaner, because X Y Z."
But I've never had to go into that mode for an interview. Or maybe the interview is too "immediate" - too interactive - for me to go into that mode.
While visiting not(USA) recently, found Xbox Cloud streaming no longer viable (lag fest) though last year travels (even over 5g hotspot) it was fine. Doesn't bode well for this streaming concept.
Looked for a real console and discovered all small shops and big box chains offer Nintendo and PS, none have Xbox. Speaking with managers revealed they or their suppliers "lost" or "ended" contracts to carry it.
Secondary market / used was dirt cheap – good condition consoles for less than a new controller: €35 for Xbox One S, €85 for Xbox Series S.
The Xbox console is a pretty bad deal outside of the US because a lot of the software features (streaming apps etc.) don't work outside the US. Everyone buys PlayStation instead. Nintendo is of course doing their own separate thing focused on exclusive games.
The ones built into the TVs suck because they don't get updated and are usually really slow and choppy to use. Everyone I know who doesn't use an HTPC, uses an Xbox or PlayStation to watch stuff.
Counterpoint: HN about the iPhone. FWIW, I agree with the statement above, but also suggest a developer account opening up developer flags is a reasonable gate.
(Not sure how else to avoid all the "developers" clamoring for non-public betas of iOS bricking their iPhones, as the same audience that would flip a bunch of dev toggles if available to everyone like developer mode in Safari then scream how Apple should have done more to protect them when their bank account is emptied.)
The Lovable class of tools is fascinating as the value prop is explicitly you do not need to be a developer, you do not need to know what you are doing. I think that makes the responsibility clear in a way the iPhone does not.
reply