Agree the market is weird right now, but on that specific example - TailwindCSS was built around the notion of reducing keystrokes per style (basically). That's not as useful in the age of AI, of course. CSS-Tricks is about learning what modern CSS can do, which is arguably still useful. An uphill battle, for sure, but I think there's still a place for hand written human content on the web, so I plan to support it even if it's just with my clicks.
> TailwindCSS was built around the notion of reducing keystrokes per style (basically).
That "basically" is doing a lot of heavy lifting.
I don't even use Tailwind and I know the point is to localize basic style information and reduce the amount of weird CSS you have to write via functions and utilities.
Especially because Tailwind came well before CSS started natively having these features (let alone them becoming baseline widely available).
Both of those goals definitely help the current era of agents by making it easier to find the rules that affect an element without needing to reliably search all of the project CSS, and reducing required context use and the need to keep track of selector lists.
By localizing basic style information and reducing the amount of weird CSS you have to write, you have thus reduced your keystrokes per style. We're talking about the same thing.
No, the semantics are different. The goal has never been "type less", which changes how it interacts with your premise. The goal has been reduce cognitive load and increase semantic density and discoverability. And, counter to what you said ("that's not as useful in the age of AI"), those are very useful in the current age of AI.
Increasing locality increases semantic density. As a utility class library, I'd say it's main goals have healthy overlap with other utility class libraries..
A very large percentage of the Tailwind classes also seem to be more or less 1:1 with CSS, or like 1:2.. So it's the locality and brevity IMHO that contributes most to reducing cognitive load.. Or at least in making it faster..
LLMs get along well with high locality..
I'm not sure if I'm disagreeing or agreeing with you now LOL.
> That "basically" is doing a lot of heavy lifting.
Yea. To me Tailwind was to make CSS act predictably for someone who was not an expert and just wanted to make some tweaks in a good expertly-crafted CSS theme design without seeing the strangest unexpected things happening layout-wise.
For a while I was working on a browser for UI designers, which involved pretty heavy use of LLMs talking to CDP. In my experience, CDP is extremely token consumptive.
Haven't released it yet, but a little website for evaluating AI UI design. They're not actual evals, it's moreso just showing the results of different UI tasks across models, reasoning levels, skills, harnesses, etc.
Right. It feels like we're living in a parallel world or something. Can agents code? Sure. Can you let them code on their own for a serious production project? Not a chance.
Which serious production projects have AI agents coding on their own? And I’m assuming that means they are routinely taking tasks and deploying them to production autonomously
Right. The only way I'd feel comfortable doing that is if I spent an inordinate amount of time writing very detailed specs, so in terms of labor offset I'm not sure the juice would even be worth the squeeze there. In other words, a sufficiently detailed spec is nearly indistinguishable from code.
What people seem to be wanting is for an agent to infer vast complex data from terse simple data, which I think is probably impossible on a philosophical level. There's real information loss in language, and compute can only make guesses at the end of the day. I really don't see how we bridge that gap.
Astra does exactly the same sort of things that Sol or any of the previous agents do. They duplicate code, overengineer, miss the point, etc.
I was very optimistic about it when it was announced and saw all the demos, but a week later I find it only marginally better (and in some cases worse) than before.
Yeah, Astra, not like it matters. It will gleefully make db queries that perform full table scans instead of adding an index. I need to intuit that that's what's happening and then explicitly instruct it not to be negligently dumb.
Consider that the people who have never have never had to be on-call for a product that results in losses for the company in the event of an outage, and/or have never had to attend an RCA meeting have just as much of a voice in this discussion. Some segments of the software industry don't even have to worry about those sorts of things, and it's easy to get myopic after a while...I doubt that a long time dev at hobbyist-centric wearable manufacturers or audio plugin shops has the same sorts of concerns as someone who has specialized in ad delivery for social media sites.
Allowing only people who have served on call or made concrete contributions to multiple RCAs to have input on the software development process is a wonderful idea!
me too; and my coding agents are slowed down (from developing features) because I require them to refactor the code to be more readable; my code metrics tests force AIs to leverage functional programming and design patterns).
Yes agents can produce code that compiles and runs, but I had to add tools to keep them on track, document their work, follow a process, check their outputs. I also use other AIs to generate developer documentation and review code.
It is like managing a bunch of idiot savant eager-to-please interns, except unlike interns, coding agents do not (yet) learn and improve on their own.
I bought it on day one in 2016, and like everyone else, I was wowed by the planet hopping experience for about an hour or so. Then I put it down and didn't think about it again.
Then I picked it up a few years later, and discovered base building. Had more fun than the first playthrough, but it didn't click. Eventually I hear about something called the Galactic Hub, which is a star system marked by players as a central spot to build their bases. Kind of like a human home in the vast empty universe of NMS.
I get curious about it, and look up instructions on how to get there. I did some quick napkin math and realized it would take literally dozens of hours of grinding - nonstop travel - to get there. However, as it turns out, there's a loophole with black holes. When you enter a black hole, it spits you out into a totally different place in the galaxy. From the players perspective its random, but players got together and figured out that each unique black hole always sends you to the same spot in the galaxy. So they constructed a black hole "highway", along with an app that let you input your desired coordinates, and it would give you the list of black holes that would most optimally get you near your destination.
So I spend an evening playing the game, switching back and forth from the game to my laptop, inputting coordinates and slowly making my way closer and closer to the hub. Eventually I find it, and what was amazing was that it was the first time I'd seen any evidence of another player in the game.
That moment felt utterly magical, because while I was playing a game, I had an actual, real objective that I formed entirely on my own.
So yes, the game is an odd duck, but it can really open up with the right mindset.
That kind of play is pretty rare these days. The current way is to put in portal coordinates (which are pretty much mandatory in NMS social media) and just walk through to the destination. Or have someone take you there from the Anomaly. And while what you did is still possible and cool, would you have still done it if given the chance to take a portal? Would most players? (No.)
The most interesting creative decisions happen within a tight set of constraints.
Side note, I also had to expand my definition of "creativity" early in my career. I grew up and was educated as an artist. Even received a Bachelor of Fine Art Painting. Never took a single class on anything to do with computer science. As I was transitioning my career towards programming, I was worried that I would lose my creativity. It took me a while to realize that programming was intensely creative, just as much as being an artist. They simply have different aesthetics.
I've been on this kick for a long time. A few years ago I was exploring a UI design tool that was entirely keyboard-driven, using pneumonic keychords inspired by Vim: https://github.com/danielvaughn/stride
My experience is that while it's awesome to have really deep keyboard-driven experience, it can't _only_ be that. You need some graphical controls to help guide users.
To be fair, the article doesn't say that AC is banned - it mostly focuses on the HOA-style local ordinances and permits that discourage people from using AC.
reply