Oh look it's a Buzz clone
Slack Code
21–30 of 117 posts
Re: Slack Code
#22Someone please wake me up from this fever dream
Lean into it.
Re: Slack Code
#23When we can code in English, now we can code in group chats.
Maybe it’s the future. Where I can join to coding/spec driven channels to observe or help.
I would do this - coding/spec driven in public. Hope it will be the future.
It would allow also non devs to join.
Re: Slack Code
#24Slack is fine, but the moment they start bringing that stuff into Jira...
Re: Slack Code
#25At this point I literally have no idea what modern coding is supposed to look like. I still open my editor, type stuff in and run make. All these tools are released daily and they just fly over my caveman head.
I used to be that person, and suddenly I haven’t opened an editor or written a line of code by hand in 6+ months.
Same here.
All I do now is spend all day on calls with people whose shit exploded and I'm trying to scrub it off the walls, ceiling and the customers.
Re: Slack Code
#26I feel at this point all new AI announcements can be auto generated by AI.
Next up - Slack releases a model router. Cloudflare builds an agents platform. OpenAI acquires a dev tools startup.
Re: Slack Code
#27Slack is fine, but the moment they start bringing that stuff into Jira...
It's already here! https://www.atlassian.com/software/rovo-dev
Re: Slack Code
#28I'm going to chock this one up as a yet-another "X is your agentic coding hub" PR nonsense.
What are people actually using to manage semi-collaborative agentic coding workflows nowadays? We've moved from on-dev-machine coding to @claude in GitHub, but of course GitHub purposefully weakens the capability of that approach to the point that it's kind of a hack. Github/Linear have somewhat more cohesive experiences but it still feels like tooling for agent teaming is quite lacking and unergonomic.
Re: Slack Code
#29Sounds useful for a PM wanting to spin up a throwaway PoC. But you’d have to rip my IDE from my cold dead hands for any work that extends past the threshold of KTLO.
Re: Slack Code
#30At this point I literally have no idea what modern coding is supposed to look like. I still open my editor, type stuff in and run make. All these tools are released daily and they just fly over my caveman head.
That’s fine, and you’re doing fine. In fact, in a few years you will probably be far more skilled than most “software engineers”.
Real question here, as I'm struggling with this and I'm not finding a lot of evidence to support my inclination (that you are correct).
Why would this person be more skilled? And more importantly, what does it mean to be "skilled" in the era of AI?
I'm trying to be open-minded to both sides, but I have senior engineers on my team with a fleet of agents, shipping code they don't fully understand, and... everything is fine. Stuff still breaks, we fix it. Clients ask "How does XYZ work?" and we say, "Not sure, let us get back to you." And they're totally fine with that answer.
Everything within me screams that this is wrong and we should have intimate familiarity with the system, but I cannot find any evidence that the path of "running a team" instead of "building engineering skill" is not going to work out fine in the long-run. (Yes, my comparison between "team" and "engineering skill" is a bit rough but I'm not interested in the semantics.)
All the evidence that I'm seeing in my own business, with senior engineers meeting clients' needs with autonomous agentic teams is that it's all fine, and while there are gaps, it's actually okay. Clients are happy. Software works 80-90% of the team exactly as it should. Bugs are fixed quickly. We ship more in 3 months than we previously could've shipped in a year. I'm baffled and frankly not as advanced as my devs (I still ask questions one by one to my agent, like a Real Caveman!)
It makes me wildly uncomfortable so I'm trying to wrestle with this. I want your statement to be true, but I just don't see evidence of that.