440 karma · joined September 18, 2010
https://x1agent.com - AI Dark Factories on K8s | https://hotwired.sh - Desktop agent orchestration | https://treble.build - Figma to Code
Having Codex/Claude write all of it won't really benefit you imho.
Just using tailwind and anchoring around a design system like shadcn is just way easier for a team to align around than somebodys made up css language.
Gitlab pricing was bonkers. It always felt like their sales team were trying to play gotcha with us over the years with pricing schemes that would milk us for money.
I think in principle, its sound. Im also just baffled hearing anecdotes from friends that are in big corp world and hearing the type of incidents they have, and how they respond to it.. It makes me wonder if there is enough capable talent to go around for the "boring corp" crowd.
Hint: I don't think there is nearly enough talent to go round, but for these companies, its either that they think they have solid experts (and didn't), OR its not a real priority until you get hit.
I've tried to focus more on end-user use-cases in my own product positioning, even though security is absolutely at the top of my list. This was hard to watch because it felt it demonstrated a security feature that is really secondary to the purpose of an agent.
What would be a spin in this AI category that would excite or surprise you?
Honestly, I think if you had a push model for this, some folks would be willing to pay for it, but I don't know a whole lot about this space and your potential competitors. Happy to chat more if you want.
Its shifted so much for me. I used to think that I had a solemn duty to read every line and understand it, or to write all the test cases. Then I started noticing that tools like CodeRabbit, or Cursor would find things in my code that I would rarely find myself.
I think right now, its shifted my perception of my role to one where I am responsible for "tilting" the agentic coding loop; ultimately the goal is a matter of ensuring the agent learns from its mistakes, self-organize and embrace a spirit of Kaizen.
Btw thank you for your work on Django, last 20 years with it were life changing (I did .NET before).
This is spot on. I think the tooling is evolving so much particularly on the design side that its not worth the "translation cost" to stay (or even be) on the Figma side anymore.
This was a huge motivation behind me trying to design an AI automation platform that comes "batteries included". I also think a lot of orgs, even engineering orgs do not know how to configure basic things like Claude plugin repositories into their installs.
The async aspect of it is convenient, but for me as a team lead, often times the standup is also an opportunity to ask follow up questions, to see if stories are on track, or to determine if somebody would benefit from pairing for the day. These things become increasingly important if you have an uneven balance of dev experience or domain knowledge within the team.
Dr. Rochelle Walensky, Director of CDC was actually in an interview recently where she said 75% of Covid deaths occurred in people with 4 co-morbidities.
https://www.youtube.com/watch?v=Pa7N-iNkaUE
This statement begs the question of what percentile of deaths occurred with no co-morbidities at all. In my mind at least, I don't know enough about the death rate to inform if its bleak or not judging as a healthy 41 year old without complicating medical factors.
It may be an ecosystem problem but I think the big projects have an obligation to set the tone for what is acceptable elsewhere and not just jump on the next wizbang thing that’s marginally better or more correct.
Pros and cons but I see the cost of maintenance being very high in client side js compared to backend.
It worked right off the bat for me while react-sortable-hoc did not.