I sat through an egregious demo of an AI add on for documentation. The flow was load doc (e.g. pdf) -> data filled into a specialized form view. To really wow me, they showed how I could type in the AI chat interface "change the title to 'abc'" and then it would make the change in the form view.
Why can I not just type the new name into the title field itself? Well, this is supposedly easier and in time the AI will learn and get the title right 100% of the time, so there won't be a need for me to edit it.
This is a major player in the industry, not some random kid.
This is where I see a lot of AI stuff right now honestly.
It's just "I want the computer to figure this out for me even if it takes longer than the old tools, because I cannot be bothered to learn how to use the old tools"
I think though if you re-phrase this to “I am lazy…” (the CORE common trait of every great SWE I have priviledge of working with in the last 30 years) “… and I do not want to manually do any work I can automate” things look a lot different through that lens
And then there’s the mindset of “the existing toolsets don’t fit my mindset very well, so I’ll have AI recreate them in a way that only makes sense to me and then harass everyone to adopt the new tool because I understand it.”
Someone didn’t like how our Jira tickets and Confluence docs were structured so they vibe-coded a new ticketing system that has a custom web UI with a Microsoft Access database on the back-end. Management and Customers don’t like it for a good range of reasons but he requires everyone who works on his projects to use it.
Another person didn’t like our build script for generating a templated Ansible role so they made some kind of MCP adapter or harness to ask you canned questions on what your role is named and what features to include, then scrapes our docs to get the required directory structure and generates it. It does literally the same thing but sometimes does it wrong and consumes tokens regardless.
It’s like the XKCD comic about competing standards, but accelerated for any person who is minorly inconvenienced and has API tokens to an AI service.
> I am now a research engineer at Salesforce AI Research. I spend more time supporting scientists & building rapid prototypes, rather than working with a large team of engineers.
I appreciate the PoV of people with different challenges, but my full-time job is not about building rapid prototypes so the guidelines are worth a bit less to me.
Python makes it very easy to do these experiments without changing cpython itself. For example, a lot of the cases for the "not set" Sentinel can be handled by making it MyClass | None. Treat None as "not set". If you need a "no-op" then you can give MyClass a field or something which implies it does nothing. And then override the bool dunder method to make it return false if the no op field is set to true. If you really want, you can have a classmethod which returns a "no op" instance of MyClass so people can easily call your func with MyClass.no_operation() when you want no op, and null when its not actually set.
Sentinels just help you wrap that up nicely and for more general use cases, but theres value in stepping back and thinking about where the unset vs no op case matters.
I agree with the article, but I'd also ask people to extend this thinking past just software they build.
If you're putting anything out there for consumption (software, articles, presentations, documentation) ensure your own voice is the dominant one in the output.
I look at it as a giant experiment. Any research tends to be very investment heavy, and people are given a lot more leeway to try things which are wildly unprofitable.
I'm glad they're doing this, because it lets me see an extreme of LLM development.
If anthropic is making as many PRs as stated in articles, then rolling back is unlikely an option. More likely it'd be a new commit to fix it, and with a feature flag to preserve the "wrong" behavior (even if wrong, since people will probably depend on that function since its original behaviour).
Those sorts of changes are really rough to manage. Maybe still manageable by LLMs but we'll find out.
I've always worried about the level of "IP laundering" which is done by LLMs.
While that's not technically the case here (given Mononoke's license) it is still quite negative in my view. We will have fewer people wanting to share ideas openly since LLMs are so good at not only finding them, but also not attributing them. This also leads to a loss in diverse collaboration, which is probably one of the biggest drivers for good software.
Right now there's probably a lot of these "novel" ideas floating around which models can present as their own, but that's raiding our coffers with no inbound future stream.
It's interesting to see how over the span of just a few years a lot of people went from:
> Architecture astronauts are out of touch and shouldn't give any advice because they haven't written code in ages. Only the hands on engineers can shape it since the design evolves in step with writing the code.
To
> I focus on the architecture patterns and high level goals and let the LLM take care of the rest.
Similar commentary was shared about anyone not writing the code daily, not just the architects.
No gotchas, I just think it's something which calls for introspection.
I'm one of (if not the) original architecture astronaut, so you may not want to listen to me, but you're sliding from "architecture astronauts are bad" (true) to "architecture doesn't matter" (false).
Arguably, architecture is the only thing that ever mattered. Below the level of architecture you're dealing either with algorithms or API calls. Algorithms can be validated by tests and API calls can be validated by tests and the type system.
But architecture is the one thing that could make or break a project and that you can't test for ahead of time. You either know how to create a good architecture or you don't. In fact, the whole point of the Spolsky's Architecture Astronauts' essay is that bad architecture (and bad architects) are a big problem.
AI works amazingly well below the level of architecture, but (I've found) it's not very good at architecture.
I agree architecture is important. But I think the best way to design a good architecture is to have a high level plan, and then feel it out by coding parts of it (usually near component edges / interfaces) in the actual domain with real use cases.
That exploration helped me see whether general "best practices" are applicable in this frame, and let me justify if not.
That was also prevailing opinion pre LLM:
> Only the hands on engineers can shape it since the design evolves in step with writing the code.
So I'm curious to know where people changed their minds.
I think your argument is you can't create good architecture without writing code. I sort of agree. You can't be a good software architect without knowing how to code, and you can't be a good architect of a specific code base without being familiar with the code.
But I don't think you expect an architect to have written all the code, right? I don't even think you expect an architect to have read all the code.
The whole point of being a good architect is understanding the abstractions so that we can focus on the overall system without necessarily knowing all the details. I don't need to know the FFT math behind JPEG to integrate an image library.
So there's no real change in opinion. Architects were never expected write or even understand every line of code.
I think they are lying to themselves. The patterns change with the hardware and environment, i sure code different and use other data structures when having to account for VRAM now, network security, etc.
Going from the specification to the code is not a one way street. You adapt the whole chain. Saying the only thing that matters is the spec is squinting your eyes and hoping for the best.
You stop learning how things actually end up in memory, compute, storage and network this way. Not sure how you can build a secure and fast spec then.
And even if you do know i never understand why not typing it out. You can use a lib if you don't want to worry about these details or know you are not skilled enough (tls f.e. ...). But having AI do it introduces uncertainty where there can be determinism.
I think it's just laziness and people not liking the pain of learning or needing to show off whatever first. Who knows. Still don't see a reason to use these tools outside of learning or whatever i used a google search for before.
Only in the last few years did I start using SQL properly. Before that my pipelines would live in python. Now I offload as much to the db as possible, and keep my python simple glue. I'm very happy with this compared to other methods in pandas or polars.
If I still need to do db-like things in python I think duckdb is better.
I also really enjoy programming, and relate to your comment below about sometimes waking up in the middle of the night because your brain figured out how to code a hard problem.
Sorry to hear you're having a rough time with work. I do think AI availability has made otherwise smart people put out lazy work. But I also think that there are more people who still "code by hand" than you think.
You might find some joy by going to certain events where people talk about different items coding-wise. I enjoyed the talks for this conference recently https://www.youtube.com/@softwareshouldwork (particularly Richard Hipp's, Delaney Gillilan's and Carson Gross' talks), maybe you can find similar spaces. The benefit has been Youtube's algorithm recommending me better software talks now too.
Thanks for the recommendation, I in fact couldn't sleep past 5am today and woke up to check an SQLite presentation on that channel. Pure gold!
I think that's how it is, we just gotta fine-tune the algorithms on our favor. I'm doing it slowly with Youtube (I'm into rock climbing recently, and it's been a fun ride on YT). My Twitter feed can actually be pretty amazing, even my IG one. I don't check them much often any more but they're still pretty good. No BS.
The trick is not to fall for the stupid videos with millions of views. I just recently learned about Mukbang or something like that (a weird trend where people binge eat on YT). Crazy
Why can I not just type the new name into the title field itself? Well, this is supposedly easier and in time the AI will learn and get the title right 100% of the time, so there won't be a need for me to edit it.
This is a major player in the industry, not some random kid.